Olive Hill is a family-run Turkish meze and BBQ restaurant in Watford. Their new site went live this week, and the thing I am proudest of is not the design. It is that nobody at the restaurant has to ring me to change a price.
The brief, as it actually was
The family wanted four things. The menu online and correct. Photos that look like the food. A way to book a table. And the ability to change any of it themselves at eleven at night when a dish comes off the menu, without waiting for a developer.
That last one is the one most restaurant sites get wrong. Either the site is a page builder the owner is afraid to touch, or it is a custom build where every change goes through an agency and a monthly invoice. Both end the same way: the online menu drifts from the real one, and the first a customer hears about it is at the table.
How it is set up
The site is a static build, so every page is plain HTML that loads fast and reads cleanly to Google and the AI assistants. Behind it is a content studio, built on Sanity, where the family edit the menu, the photos and the page copy.
Two details make it work for people who are not web people.
Live preview. When they change a dish, they see the actual page update beside the form as they type. There is no "publish and hope" step. What they see in the studio is what the customer sees.
Whole pages can be switched on or off. A seasonal menu, a Christmas page, a private dining page: each exists in the studio and has a switch. On, and it appears in the navigation and the sitemap. Off, and it vanishes cleanly, with no dead link left behind. The site grows and shrinks with the business without anyone touching code.
Everything else is what every site from this studio gets. A gallery and a virtual tour. Table booking wired in. Restaurant schema, the structured data that tells Google and the assistants that this is a restaurant, with the address, the phone number, the opening hours and the rating from more than 1,100 Google reviews, all generated from the same content the pages use. And an llms.txt, a plain-text map of the restaurant for the AI models, so when someone asks an assistant for Turkish food in Watford, there is something accurate for it to read.
Why not a page builder
Because a page builder makes the owner the developer. Every change is a layout decision, every template is a trap, and the moment something looks wrong there is nobody to ask. The studio here does the opposite. The family change words, prices, photos and switches. The design does not move, the structure does not break, and the search markup stays correct because it is generated, not typed.
Cem, who owns the restaurant, put it better than I can: "Nothing is ever too much trouble for him, and he always takes the time to explain things and make sure everything is done properly."
The site is at olivehillrestaurant.co.uk. If you run a restaurant, a clinic or a salon and your menu, price list or treatment list is out of date online right now, that is the problem this solves.
Paul Redman runs Redman Studio, an independent web design and engineering studio in Watford, Hertfordshire. A build like this one is the Business tier on the published price list.