Table Racine — a produce-driven restaurant website template

Starter is £19/mo excl. VAT and includes a complete restaurant website, a live structured menu, enquiry and newsletter forms, and managed search readiness. Growth is £39/mo excl. VAT and adds direct live bookings, a custom domain with managed SSL, and table and floor-plan operations. Full is £69/mo excl. VAT and adds online ordering and multi-site management for up to five restaurant sites. TableSpark commission is 0%. Stripe's standard card-processing fees apply to online payments.

Do not read this bit. Touch it.

Table Racine runs on charcoal with a green that reads as a market stall rather than a health brand. Yours might be white tile and morning light, or brass and candles, or something nobody has built yet.

Skip the description. The panel is lifted straight out of the builder and the frame is the real renderer, so what happens when you press an accent here is exactly what happens in your account. Nothing you do is saved or asked about. Go on.

Open it properly

5 pages, and every one of them is here. Everything below is rendered, not photographed. The frame uses the same engine as a published site, so the tabs and the in-page links are all real. Phone shows the mobile layout.

The room it imagines

A produce-driven kitchen has a website problem that no fixed menu has: everything on the page was true yesterday and might not be true tonight. This design accepts that instead of hiding it. The opening is a counter — what is on it today, who brought it, and when the room is open.

The palette is a dark counter lit from above, and the type is a geometric display face against a plain sans, which keeps the emphasis on nouns: the vegetable, the boat, the farm. When the design gets out of the way, a list of ingredients becomes the most persuasive thing on the page.

The home page, block by block

Eight blocks, all of them editable modules:

• Hero — Big opening image, name & buttons, in the Counter treatment: Copy and opening hours held on the dark side of a counter photograph.
• Signature dish — One dish, full screen — name, story, price.
• Marquee strip — Scrolling awards or words.
• Gallery — Grid, masonry or moving strip.
• FAQ — Accordion of questions.
• Numbers — Headline stats.
• Reviews — Guest quotes with stars.
• Call to action — Headline + button band.

The menu page — the most important page you own

This template uses the Index layout — the sections are listed first and open in turn, so the shape of the whole menu is visible before any single dish is. The menu is an index: sections named first, then opened in sequence. For a kitchen where the menu is rewritten most mornings that is the fastest structure to maintain — you are editing a list, not rearranging a gallery of photographs that no longer match what arrived.

The sourcing detail belongs in the description field, and this template expects it there: the grower, the boat, the variety, the age. It reads well to a guest and it is exactly the kind of specific text that a search engine can use when somebody searches for a producer by name.

The layout can change; what does not is that each dish, its description and its price are text on the page, wrapped in Restaurant schema — rather than a PDF or a picture of a card.

Take the order yourself

This is the part worth pressing. Table Racine uses the Delivery app ordering layout — sections run down a rail on the left, the dish list swaps beside them without losing your place, and the basket follows the scroll. The ordering page is the full delivery-app treatment: a section rail down one side, the dish list beside it, and a basket that follows the scroll. For a kitchen with a retail counter or a lunch trade it turns the site into a working order channel rather than a menu with a phone number.

Because the same menu data drives both the menu page and the ordering page, a dish taken off at eleven in the morning disappears from both. Nothing goes stale in one place while staying live in the other, which is the failure that makes most restaurant ordering pages untrustworthy.

Dine-in wants a table number and nothing else; collection wants a number to ring; delivery wants somewhere to go. No mode asks for the others’ fields.

Where the restaurant explains itself

The story page is where a produce-led restaurant makes its argument: a long narrative, a sourcing block for named suppliers, a values triad, and a gallery of the market rather than the plate. The visit page covers hours, the door, the map and the questions a small room gets asked daily.

The menu builds itself from a photograph

This is where most restaurant websites stall — and where this one does not. A phone photograph of the real menu is the whole input. Out the other side is a structured menu: your sections, your dishes, your wording, your prices, with the marks read from the card itself. You get the last word: the review screen shows every field before anything is written.

A menu locked in a PDF is a dead end. This is not that. From there the same data runs the menu page, the ordering page, the highlights on the home page and the Restaurant structured data a search engine reads. Change a price once afterwards and all of them follow.

Each page also has a Write with AI button that drafts the search title and description from what is actually on that page, so the fields that decide whether Google shows you are never left empty. The wording arrives in the field, not on the live site — review it first.

Publish today, take bookings tonight

What usually takes a project plan takes a coffee break. It is a complete restaurant site that happens to be about somebody else. Fixing that is the job. A ten-minute job for most restaurants, and there is no separate switch to flick for bookings — they work on publish. Every reservation arrives in your inbox and the guest is emailed a confirmation immediately.

Connect Stripe — it takes about a minute — and the site starts taking deposits on bookings and payment on orders, into your account. You keep the order. TableSpark charges 0% commission at every level. Stripe’s standard card-processing fees apply to online payments.

1. Pick Table RacineThe whole site copies into your account, menu and all.
   1 min
2. Change the name and the wordsClick any block and type. The restaurant name propagates everywhere.
   4 min
3. Upload your menuPhotograph it and let the AI build the sections, dishes and prices.
   3 min
4. PublishYou are live on your address. Bookings work immediately.
   1 min
5. Connect StripeNow you can take deposits on tables and payment on orders — direct to your account.
   1 min

Your name over the door

Your address is the last piece of the name, and it belongs to you. Publish today on a TableSpark address, then point your own domain at it whenever it suits: the one already printed on your windows and listed on Google.

We handle what usually needs a technician — the SSL certificate and its renewals, the bare-domain redirect, and the canonical signals that stop a move from costing you visibility. Domains you already hold are welcome, and the change is one line in your registrar.

The confirmation email, in your own branding

The booking is not the last thing a guest hears from you — it is the first. Each booking triggers an email in your name: the date and time they chose, how many are coming, where to find you, and a link to hand the table back if plans move. Reminders before service, deposit receipts and cancellation notices come from the same place.

It belongs to your restaurant visually, not to the software. The choices are six base designs, an accent colour, a logo, a cover photograph, three header treatments, a personal sign-off, links and social marks. With your domain connected it also sends from your address, so the email is from the restaurant in every sense a guest can check.

Below is the actual renderer, the one that sends after a confirmed booking. Press any of the styles or colours and it rebuilds in front of you.

Where the template ends and you begin

• Yours from the first minute: text, photographs, menu, prices, hours, address, colours, typefaces — everything a guest can see.
• Kept for you: the invisible work — menus that scale, baskets that behave, layouts that reflow, and type that stays readable on every ground.
• Never locked: add, remove and reorder blocks anywhere, and do the same with pages. What ships is a first draft of your site, not a contract.

Being on the internet is not being in search

A working address is the beginning of search visibility, not the end of it. The failure modes are boring and fatal: a noindex tag, canonicals that contradict each other, pages nothing points at, a menu only a human can read, no restaurant structured data, unverified search accounts. The consequence is paid discovery. Someone types your restaurant’s name and meets a listings site, a marketplace, or the place across the road.

The whole checklist is done for you. Nobody can guarantee a ranking or that Google will index a given page; what can be guaranteed is that the technical groundwork is not your problem.

Before you begin