Case Study
White Rock Farm Website Makeover
How we took a family farm’s website, first registered in May 2017, and rebuilt it to current WordPress standards in about three to five days, using AI and the farm’s own knowledge of its customers, products and story.
Covers June 17 to July 27, 2026.
The goal
A site the farm can run itself, live before the July 4th market
White Rock Farm is a sister company of White Rock Future Tech LLC; the two share the White Rock name. White Rock Farm sells grass-fed beef. Its website had grown up around a page-builder design: a single long home page of about 21 sections built from 62 page-builder widgets, five plugins, and one paid add-on that the site could not run without. The domain was first registered in May 2017. The site still worked, but it was hard to change, and the person who keeps it up to date is new to WordPress.
The goal was to replace it with a WordPress site that keeps the farm’s look, that a non-technical operator can edit in the standard WordPress editor without touching code, and that the family can publish safely with one button. It had to be live before the farm’s July 4th market.
At a glance
The scale of the work
| Measure | Result |
|---|---|
| Old site | Domain first registered May 2017; page builder, five plugins, one paid add-on |
| Bulk of the work | About three to five days |
| Core rebuild, first commit to a tested, editable site | Under three days (about 67 hours), June 17 to 20, 2026 |
| Live on the new site | June 30, 2026, before the July 4th market |
| Main pages moved to the standard block editor | 8 |
| Site content | 12 pages and 7 products |
| Commits, site and publishing tool | 105 |
| Automated test assertions, site | 290 passing, 0 failing |
| Automated test assertions, publishing tool | 337 passing, 0 failing |
| Test gate before anything goes live | Six automated layers plus a person’s visual sign-off |
After the core rebuild, the publishing tool, the owners’ change requests and final fixes followed over the next few weeks.
Issues
Six problems and how we overcame them
1. The first rebuild looked right but the owner could not edit it
A fast first pass put the page text and images inside the theme’s code. Every page displayed correctly and passed review, but the operator could no longer change a word in WordPress. We rebuilt every main page in the standard block editor, locked the farm’s colors and fonts into the theme so edits stay on brand, and made “can the operator edit this without code?” a test that every page must pass. The lesson we kept: check that the person can do their job, not only that the page appears.
2. The page builder could not match the design
Rebuilding in the old page builder matched the agreed design by only about 79 percent on average (65 to 86 percent by page) and would have left a paid add-on to keep updated on a site nobody tends full time. We retired the page builder and used plain WordPress with no paid plugins. The new pages match it from 75 percent on the recipe page to 100 percent on the home page, with six of eight pages at 86 percent or more. Both sets of figures come from comparing screenshots with the design.
3. A page that loads is not a page that works
One recipe’s “Back to all recipes” link pointed at a section that did not exist, and the page still loaded without error. We added checks that follow every link to its target, compare desktop and mobile screenshots, confirm every page has a search description, and confirm the contact form’s keyboard order. A person still looks at every page before it goes live.
4. No safe way to publish changes
The first publishes were done by hand and exposed traps: an old copy of the site in the wrong folder, a feature file that had not been saved, and links that had to be rewritten without damaging stored data. We built a publishing plugin that takes a backup first, runs eight checked steps, and rolls back on its own if a step fails. It first rehearses on a throwaway copy; only a passing rehearsal shows the “Promote to Production” button.
5. Family reviewers on a different network
The owners reviewed the work from home, on a different network from the developer. A WordPress site tied to one address would have sent them to a dead link. The site now works out its address from each visit, against a short list of allowed addresses, so everyone could review the same work.
6. Claims the farm could not stand behind
The old site showed certification seals the farm does not hold, and two different addresses and phone numbers. We removed the seals, replaced them with an accurate written statement of the farm’s USDA grass-fed verification, and kept the contact details in one place so they cannot disagree.
Modern standards
What changed, and what did not
- The standard WordPress block editor in place of a page builder, with no paid plugins.
- The farm’s 10 brand colors and 2 fonts locked into the editor, so edits stay on brand.
- Real pages with their own addresses in place of one long home page.
- Secure connections forced for every visitor on the new site.
- Checked on phone and tablet widths with no sideways scrolling.
- A search description on every page.
- A contact form handled on the site itself, with no outside service.
- Publishing through a tested backup-first button, never by editing the live site directly.
We are careful about what we do not claim. The old site already ran a current version of WordPress, so this was not a software upgrade; what was old was the design and the way it was built. We did not measure page speed, so we make no speed claim.
AI and the farm’s knowledge
How AI and the farm’s own knowledge divided the work
AI did the heavy lifting: it wrote the theme, the publishing plugin, the tests, the operator manual and the project records, and it ran the checks. That is what made the timeline possible.
The farm supplied what AI cannot. The words and photos came from the farm’s existing site and its own pictures of its herd. The family made the calls: the cow line-drawing logo, the grass-fed wording, prices left blank rather than guessed, and a family vote on the recipe layout. The farm’s content owner sent written change requests for the header and footer, which were built the same day. Two stock photos fill in where farm photos were still to come.
Our part was the experience to run it: deciding what to build, setting the tests a page must pass, treating the operator’s skills as a design requirement, and keeping every live publish and every risky step in the hands of a person.
Who We Are
White Rock Future Tech LLC provides AI-related services for small to large businesses. We also offer CIO/CTO services on a part-time and consulting basis. Our company uses AI in our daily work, which is kept in house on private networks when dealing with client materials and IP. We check each claim from our AI agents against their citations as well as checking for supporting information.
AI is a potentially game-changing tool for business today. We believe that the use of AI, in the correct hands and with appropriate guardrails, boundaries and rules will be as transformative as the introduction of the Personal Computer (PC) was back in the late ’70s and early ’80s.
Find out what your project really takes.
Book a free 30-minute consultation. You will leave with a realistic sense of size, cost and risk, whether or not we work together.