Fictional neighbourhood kitchen
Read the menu. Then order in two taps.
A small demonstration restaurant built to show what the setup work produces: a menu you can actually read on a phone, one obvious action on every page, and practical visit information that answers the questions people call to ask.
The order button is inactive. On a real project it links straight to the restaurant's own existing ordering provider - their current system is used, never replaced.
What we cook
A short seasonal menu that changes a few times a year. Wood-fired flatbreads, a handful of shared plates, and three or four mains. Everything is written out in full on the menu page, in text, so a phone can read it and so can a search engine.
How it works
Walk in and put your name down, or order ahead for pickup. The bar takes walk-ins all evening. Larger groups are asked to get in touch first so the room can be arranged.
Finding us
The visit page has the hours, the parking situation, the accessibility notes, and a direct link to directions - the things people would otherwise have to phone and ask.
This week
Flatbread night, every Wednesday
Every Wednesday from 5pm the kitchen runs the wood oven all evening and adds two flatbreads that are not on the regular menu. No booking, no set price - come in and see what is on the board.
An event notice like this is exactly the kind of change the monthly care plan covers: supplied by the owner, added in one approved batch.
Owner-supplied photography goes here
Three photo slots, on a real project
The template reserves space for up to eight owner-supplied photographs across the three pages. Until real approved images exist, the slots stay visibly empty rather than being filled with stock or generated pictures.
index.html.