Léonie — a modern French 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.

Go on — change something.

Léonie is a near-black room with an ink blue that only shows where it must. Yours might be white tile and morning light, or brass and candles, or something nobody has built yet.

The controls beside the frame are not an illustration of the Theme tab — they are the Theme tab, driving the same engine that publishes real restaurants. Press whatever you like; nothing is stored and nothing is signed up for. Go on.

Open it properly

6 pages, and every one of them is here. None of this is an image. The frame runs the real renderer — the one that publishes live restaurants — so each tab is the actual page and the links go where they say. Press Phone and watch it reflow.

The room this design is for

The passe-partout opening — an image framed by generous margin, like a mounted print — sets the register immediately. This is a room that does not raise its voice, and the website should not either.

A near-black ground with an old-style serif is a combination that can look funereal if it is not handled carefully; here it is rescued by space. Every block has more margin than it needs, which is the visual equivalent of a room with tables far apart.

The home page, block by block

Nine blocks, framed rather than filled:

• Hero — Big opening image, name & buttons, in the Passe-partout treatment: A small mounted photograph in a gallery field of paper.
• Pull quote — A large standout quotation.
• Feature rows — Alternating image and text rows.
• Sourcing — The growers and makers behind the menu.
• Menu preview — A few dishes on a sliding rail.
• Ambience — Full-width video or photo mood band.
• Reviews — Guest quotes with stars.
• Reservation form — Live availability slot picker, saved to your Inbox.
• FAQ — Accordion of questions.

The menu page: a printed menu a search engine can read

This template uses the Editorial layout — each section opens on its signature plate, then the dishes are set as type in ruled columns, the way a printed card reads. The editorial layout — a plate opening each section, dishes typed in ruled columns — is the layout that respects careful menu writing. Dish names at this level are sentences, and chopping them into cards would ruin them.

Set menus are handled as their own structure with the price stated once, and pairings sit against the menu they belong to. Because prices are fields rather than typography, one edit changes the menu page, any home-page preview and the structured data together.

Layouts are a matter of taste. What is not optional is that every dish and price is readable text with Restaurant schema attached — a PDF menu would be invisible here.

The booking flow

There is no basket here. The template is built for a room that sells tables, and everything routes to the reservation page, where the form only offers sittings your service hours actually define.

The form collects party size, dietary requirements, occasion and a free-text note, and all of it arrives with the booking in your TableSpark inbox. The guest is confirmed by email in your own branding within seconds, and can release the table themselves if plans change.

Where the restaurant explains itself

The story page is built for a chef with a house style to articulate — a long narrative, a quote, an interview and a timeline — and the gallery page carries plate and room photography at full width.

Photograph the menu. That is the whole job.

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 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 LéonieThe 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 — 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.

What lands in the guest’s inbox

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.

The frame below is the real thing: it is drawn by the same renderer the booking system uses, not a picture of one. Press a style or a colour and watch it change.

The line between the design and your restaurant

• 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.

Live is not the same as findable

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.

The questions we get asked