Where everything comes from

Every band of the home page, what a visitor sees in it, what fills it, and the screen you edit that on. Then the card, part by part. Nothing here changes anything: it is a map.

Every band carries its name in the editor's List View, spelled as it is spelled here, so the thing you read about is the thing you click. A shorter map, with every screen name as a link that opens it, is inside your site at Settings › Site details › Guide.

What is static and what comes from the plugin

The theme draws every page on its own. Table and Type Core adds the records (dishes, services, hours, slips, booking rows, site facts) and, with it active, the bands that state a fact about today stop being typed text and read those records instead.

What reads your records, on the three homes

A slip can carry a photograph: set its Featured image. It is what Today's changes tapes up beside the slip's line.

What the same bands show with the plugin off

The theme's own typed stand-ins: a slip, a card, an hours figure, a line of times, written into the pattern as ordinary blocks. They carry no weekday and no calendar date, so a site without the plugin is never wrong about the calendar; it says "Today" and a pair of times, and you type what is true for your house. The stand-in is what a plugin-free site publishes, and it is what you edit by hand if you never install the plugin.

What is static either way

These are theme sections made of ordinary blocks. The plugin does not touch them; you edit them in the page, in the Site Editor.

A service's schedule is never retyped on an inner page. Where an inner page prints a service's days and hours as a line of its own — the two stamps and the three walk-in rows on /book/, the evening room's stamp on /about/, the hours beside each service in the laptop rules on /visit/, the nights and the last order in "After dark" on /visit/ and /contact/ — the line is bound to that service's record, exactly as the tiles on the homes are: change Services › Days, Start, End or Last order and those lines follow. With the plugin off they print the schedule as typed in the pattern. A sentence that mentions an hour in passing ("the globes go on at half past five") is yours, typed, and stays as you wrote it.

The day room's hours are the door's. The day room's stamp on /about/ prints the hours your door keeps on most days of the week, from Hours (07:30 – 17:00 on the demo, Tuesday and Wednesday; a tie goes to the earlier day). Change a weekday's row and the stamp follows; with the plugin off it prints the hours typed in the pattern. Any paragraph can do the same: it is the hours binding's door_range field, with day set to usual (the default), week (the earliest opening to the latest closing) or one weekday's key, such as tue. There is no "today": a bound line is not worked out again on a cached page, so it never claims a date.

On the inner pages the plugin's own blocks are the content: the card on /menu/, the drinks list on /drinks/, the week, the address and the arrival facts on /visit/, the policy rows, the booking flow and the enquiry form on /book/, the privacy record on /notices/. With the plugin off the theme draws a static twin of each; see with the plugin switched off.

A cached page stays true

A page built once and served to everybody cannot claim an hour. So the server prints each live band in its clock-free state (today's candidate slips, the day's schedule, the week) together with the windows and the schedule themselves, and a small script in the page re-derives the hour from them in your site's timezone: which service is being served, which slips are still up, whether the door is open. It is the same mechanism the menu card and the header's open line have always used. A visitor with no JavaScript gets the clock-free state, which is a real answer rather than a blank. See how a cached page still knows.

The all-day home, band by band

The bakery and bistro homes reorder these bands and add a few of their own; The three homes has the order for each.

1. The header

2. The hero

By hand: the words stand on the dark side of the photograph, with an ink ground laid under them. Replace the photograph with a lighter one, or move its focal point, and look at the result at 390 and at 1440 before you publish.

3. The served card

4. Today's changes

5. The day in five services

6. A dish, told

Static. The photograph, the story, the price and the marks are typed on the page. Rewrite it for a dish of your own.

7. On the grinder

8. The night band

9. The kitchen · 11. The room

Static. Three portraits with names and roles; a mosaic of the room from morning to night. Both are Image and Paragraph blocks on the page.

10. Book a table

Nothing in this band claims a table is free, because nothing in it knows. The booking page does the booking; see Booking, orders and enquiries.

12. Visit

13. From the journal

The three newest posts, each with its featured image, category and title. WordPress's own Query Loop; it needs no plugin. Posts.

14. The footer

The card, part by part

The card page, /menu/.

The index

Five services numbered, each with its days, its hours, how many dishes and what they cost, over the allergy statement, the tax note and the dietary filter. All of it is derived from Services, Dishes and Settings › Site details.

Four plates from the pass

Four dishes photographed large before the card begins. They are the dishes you ticked Featured, in the order of the service each is first served at. See Photographs.

A service's band

A section heading

A dish row

A row a slip writes

A dish whose line changes every day ships with no line at all; the day's slip supplies it.

A struck row

An Instead slip strikes the row, stamps its number, and hides its photograph.

The struck row keeps its name and its place, because a reader has to see what was taken away. It takes a 2px strike, carries a stamped mark and the word beside it (never colour alone), and loses its thumbnail, because a photograph of a dish you cannot have is a lie.

The foot