Layouts · Shops, cafés and venues · The full pattern
Shops, cafés and venues: the full pattern
Plan it first: the blueprint It lists the pages you need and what to write on each one.
People come to my place, during opening hours.
Sites like this: café, restaurant, bakery, bar, barber or salon, independent shop, pharmacy, tasting room, spa.
What a visitor comes to find out
“Open now? What’s on? Where? How do I book or order?”
Untested Worked out from research and real briefs. No site has been built from it yet, so treat it as reasoning to check, not a tested template.
Planning a site? Read from the top. Designing or building one? Jump to the structure or the file.
Explore the website
Four kinds of page. Home is on every site like this; the other three depend on the business. Pick a situation to see which pages stay.
Show the plan for
On every page, when the business needs itLanguage switch
On every siteDepends on the businessLeft out for this businessOne page for each item
Home
“Open now? What’s on? Where? How do I book or order?”
- Status
- Always
- Address
/- Eight sections, top to bottom
- What this is · Open now · Main action · On today · How to find us · Prices · Who you’ll deal with · What clients say
Menu or price list
“What’s on and what it costs, as text, with allergens.”
- Status
- If: Can you publish prices? Yes, fixed prices or “From” prices or ranges
- Address
/menu- Four sections, top to bottom
- Prices · On today · Questions people ask · Main action
Locations
“Which branch is open, and where.”
- Status
- If: How many places can people visit? Several
- How many
- One page for each location
- Address
/locations/{location}- Five sections, top to bottom
- Open now · How to find us · Services · Who you’ll deal with · Main action
Book or order
“Book or order, or hand off to the system that does.”
- Status
- If: What should a ready visitor do? Book a time or Order ahead or Send an enquiry
- Address
/book- Four sections, top to bottom
- The form · What happens next · Main action · It’s sent
How visitors move through it
- Every page is one click from the homepage.
- The main action (get directions until the business says otherwise) sits on every page.
Every page, previewed 4
Wireframes with example wording. Gray bars stand for your own text.
- HomeOpen now? What’s on? Where? How do I book or order?On every site
- Menu or price listWhat’s on and what it costs, as text, with allergens.Depends on the business
- LocationsWhich branch is open, and where.Depends on the business · one per location
- Book or orderBook or order, or hand off to the system that does.Depends on the business
Why it works
A nearby visitor wants to know: are you open now, what have you got today, what does it cost, where exactly are you, and can I book or order?
So the homepage leads with Open now, what’s on, where. The action changes with the opening state.
What each part of the homepage is for
- What this is always
What the place is, and where.
- Open now always
Today’s state first; hours as text.
- Main action always
Book a table, order ahead, message, or come in.
- On today optional
Today’s bake or specials, if someone will keep it current.
- How to find us depends
Address as text, landmark, getting there.
- Prices depends
Short lists (a barber’s prices) sit on home; long menus get a page.
- Who you’ll deal with depends
Barbers and stylists people book by name.
- What clients say optional
Attributed, dated.
On every page
- Language switch required when it applies
Several languages: a way to switch is required on every page. Where and how it shows is Design’s.
Which button leads
The main action changes with how people buy. The first rule that matches the business wins.
What should a ready visitor do? Book a time
Book a time or dates, then phone
Tables and chairs are booked. When closed, the booking still works; say when you next open. observed
What should a ready visitor do? Order ahead
Order ahead, then come in (directions)
Bakeries and cafés taking pre-orders. observed
What should a ready visitor do? Message us
Message (WhatsApp, Viber, SMS), then phone
Ordering by WhatsApp (pharmacy delivery, Tirana venues). observed
Otherwise
Come in (directions), then phone
For a walk-in place the action is getting there: hours, address, map link. our reasoning
Check before you build
- Whether a salon books a slot (venue) or a person (practice).
- Where online-only shops that take orders by message belong.
- Whether an events mode belongs here.
- Reviews and real photos of the place carry most of it.
Make it yours
A pattern is a starting point. Some of it holds for every business like this, some of it bends, and some of it only you can answer.
Holds for every site
- Home
- On the homepage: What this is, Open now, Main action
Depends on the business
- Menu or price list If: Can you publish prices? Yes, fixed prices or “From” prices or ranges
- Locations If: How many places can people visit? Several
- Book or order If: What should a ready visitor do? Book a time or Order ahead or Send an enquiry
One pattern, two situations
The same homepage, drawn by the pattern from each situation’s answers. Sections the answers leave out are gone.
- Main button
- Get directions
- Pages
- Home, Menu or price list
- Left out
- Locations, Book or order
- Main button
- Book
- Pages
- Home, Menu or price list, Book or order
- Left out
- Locations
What you’ll need to supply
For the homepage alone. Nobody can write these for you; the file marks each one as still to supply.
- What this is
- What you do, in plain words
- Open now
- Regular hours, as text
Questions only you can answer
- Do opening hours decide whether people come or call?
- What should a ready visitor do?
- How many places can people visit?
- Can you publish prices?
- Do clients care which person they get?
- How many languages?
What changes with the answers
| How many places can people visit? Several | A location page per branch; home shows the nearest or a list. |
|---|---|
| What should a ready visitor do? Book a time | Booking leads; when closed, the page says when you open next and keeps booking available. |
| Can you publish prices? Yes, fixed prices | A menu or price-list page as HTML text. |
| How many languages? Two or more | Language switcher; menus in each language. |
Answer for your own business
The plan, every drawing and the file on this page redraw as you answer.
Inspect the structure
Every page as a wireframe: the sections in order, what each one is for, and what moves on a phone. Select a violet label for its job, the content it needs and every page it appears on.
Home answers “Open now? What’s on? Where? How do I book or order?”
On a phone · First screen: open now, the action and the address. Most venue visits start on a phone, nearby.
On a phone · The address opens the map app: link it, don’t embed a map (NN/g).
Menu or price list answers “What’s on and what it costs, as text, with allergens.” Prices page pattern
Locations answers “Which branch is open, and where.” Location page pattern
Book or order answers “Book or order, or hand off to the system that does.” Enquiry, quote or booking page pattern
Use it in Design and Build
Everything above, as one file you can hand on. It describes the site’s structure. It doesn’t design or build anything.
- In the file
- 4 pages, 21 sections in order, the main action, and what each section needs from you
- Still to decide
- 9 open questions. Anything you haven’t answered travels as a question, never a guess.
- In Design
- The order of pages and sections is the hierarchy to design. The look, type and images are yours to choose.
- With a coding agent
- Give it the file with your design. It lists every page, its address and its sections in order, and marks the content you still have to write.
JSON is for coding agents and other tools. Markdown reads like a document, for people.
What it isn’t: a finished site, a template to publish, or proof the structure works for your business. Status: untested.
For designers and developers: what each stage reads
Design reads
- pages[].name, job and order (the hierarchy)
- pages[].modules[] in order, with jobs and role
- status “depends” (unresolved) vs optional
- page_frame with required/recommended strength
- pages[].phone_first and phone_notes (the phone order)
- primary_action label and intent
Read pages[] in order and modules[] in order: that is the hierarchy. jobs[] say what each module must achieve; status "depends" means unresolved, not optional. Look, type, imagery and Elements are Design’s; nothing here prescribes them.
Build reads
- pages[].route and one_per (routes and repeating pages)
- pages[].modules[] in order
- modules[].slots with need, many and any profile obligation
- primary_action.intent and second_routes (implemented per platform)
- page_frame (required/recommended)
- left_out (must stay out)
- entities, when the project names them
Make one route per page (one per entity where one_per is set), modules in the given order, every slot with need "required" filled before ship. Implement each action so it achieves its intent on this project’s platform. Do not read why as an instruction.
QA checks: Check that each included module does its jobs, required slots are filled with real content, left_out items stayed out, and the primary action leads where its label says.
The research behind it9 statements · 4 sourced · 3 untested or unknown
Use it when
- The business has premises and opening hours, and the visit is the point.
- Many people look a place up in a map app first and come to the site to confirm hours, holiday closings and what that location offers.
Not when
- You sell mainly online with delivery.
- Each thing you sell needs its own page (a car dealer, a furniture showroom with a catalog). Listings, rooms and tours →
- Clients pick a named practitioner and pay for advice or treatment by appointment (a clinic, though a salon is open: see unknowns). Advisers, practices and clinics →
Boundary cases
Which sections go on which pages
● required · ◐ conditional on the brief · ○ common, not required. Select a section to find it in the drawings.
| Job on the page · section | Home | Menu or price list | Locations | Book or order |
|---|---|---|---|---|
| Positioning | Required | |||
| Local information | Required | Required | ||
| Conditional | Required | |||
| Primary action | Required | Required | Required | Common |
| The offer | Common | Common | ||
| Price | Conditional | Required | ||
| Trust & proof | Conditional | Common | ||
| Supporting evidence | Common | |||
| Reassurance | Common | |||
| Service navigation | Common | |||
| Conversion point | Required | |||
| Required | ||||
| What happens next | Required |
What the research says
- 21 of the briefs we studied asked for what’s on today, or for a one-page site.
- NN/g: people come back to the site to confirm hours, holiday closings and services at a location; contact pages should give a map-linked address, phone and hours. schema.org models opening and special hours as structured facts.
- Menus as PDFs fail on phones; NN/g’s evidence includes a menu PDF a user gave up on. The FSA accepts written allergen information on a menu and requires it before purchase when food is sold at a distance.
Rules for your field
What a business in this field must show (a registration, prices with tax) depends on its own rules, not on this pattern. Those rules are still being worked out, so none are applied here as requirements.
Common structural mistakes
- The menu as a PDF or a photo of a chalkboard.
- Hours that are wrong for holidays. People trust the map app’s hours over the site’s.
- An embedded map with no address in text.