Saison Bleue — a contemporary 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.

Take it for a drive.

Saison Bleue is bone paper with a blue that belongs to an inkwell. Yours might be white tile and morning light, or brass and candles, or something nobody has built yet.

Rather than explain, here is the thing itself: the builder’s Theme controls on one side, the live site on the other, both real. You cannot break it, nothing saves, and no account is required to have a go. Go on.

The whole template, not a sample of it

6 pages, and every one of them is here. What follows is the site itself rather than pictures of it. The same engine that publishes a live restaurant is drawing it here, links and all. The Phone toggle shows the small-screen version.

Who this was drawn for

A French dining room in Tokyo is an exercise in restraint twice over, and the design follows: bone-coloured paper, a single ink blue, an old-style serif for the headings and a plain sans for everything else. There is no texture, no gradient and no shadow anywhere on the page.

It opens on a vestibule — the pause between the street and the room. Rather than a hero photograph shouting the restaurant’s name, the visitor gets the name set small, the hours, and a way through. That is the correct temperature for a room where a booking is made a fortnight ahead.

What is on the home page

Nine blocks, arranged for restraint:

• Hero — Big opening image, name & buttons, in the Vestibule treatment: Ruled inner frame over a vignetted room, status and address on the base rail.
• Pull quote — A large standout quotation.
• Menu preview — A few dishes on a sliding rail.
• Numbers — Headline stats.
• Sourcing — The growers and makers behind the menu.
• Press bar — Press mentions or awards as a ruled band.
• Gallery — Grid, masonry or moving strip.
• Reservation form — Live availability slot picker, saved to your Inbox.
• Call to action — Headline + button band.

The menu: legible to guests, readable by Google

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 menu is set editorially: each section opening on its own plate, then dishes typed in ruled columns like a carte. It is the layout that respects a menu written in careful language — long dish names, provenance in the description, a wine note underneath — rather than chopping it into cards.

Set menus are handled as their own structure, with the courses listed and the price stated once, which is how a déjeuner and a menu dégustation should appear beside one another. Change a price and it updates on the menu page, in any preview block on the home page and in the structured data together.

Any of the layouts leaves the substance intact: real text for every dish, description and price, marked up as Restaurant data rather than published as an image.

From interest to a booked table

There is no basket in this template, deliberately. A room like this sells reservations, not baskets, and the entire conversion path runs to a dedicated reservations page with a form that only offers real sittings.

That form does more than collect a name. It carries party size, dietary notes, occasion and a free-text request, all of which land in your TableSpark inbox with the booking rather than in a separate mailbox — and the guest is emailed a confirmation in your own branding immediately.

Story, visit, and the practical pages

The story page is written for a kitchen with a lineage: chef narrative, a quote, a timeline of the rooms they have cooked in, and a gallery. The separate gallery page carries the room and plate photography that a restaurant at this level will always have and rarely has anywhere good to put.

Upload your menu. The AI does the typing.

The menu is the longest thing on any restaurant site, and it is the thing you type least. Whatever the menu is printed on, photograph it and upload it; the format does not matter. TableSpark reads it and builds the structured menu for you: sections in the right order, dish names, descriptions, prices, and the dietary and spice marks where it can see them. You review it, fix anything the camera got wrong, and it is done.

The distinction that matters is that a search engine can read every word of it. Everything downstream reads from it: 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.

A Write with AI button on each page writes the search title and description from what is on it, so no page publishes with those fields empty. Always your last word — the draft lands in the field for you to edit before anything publishes.

How long this actually takes

The gap between deciding and being live is measured in minutes, not weeks. The template is already a finished site; the work is making it yours. Ten minutes is a fair estimate from first login to a live address, and bookings start working the instant you publish. Reservations collect in your TableSpark inbox and each guest is confirmed by email automatically.

Payments are one link away. Connect Stripe and deposits and order payments flow directly to you. Zero commission, permanently. Stripe’s standard card-processing fees apply to online payments. That is the end of the list.

1. Pick Saison BleueThe complete site lands in your account, ready to edit.
   1 min
2. Change the name and the wordsClick, type, replace a photograph. The name updates site-wide.
   4 min
3. Upload your menuUpload a picture of the card; the AI does the sections and prices.
   3 min
4. PublishPublished, on your own address, with the booking form answering.
   1 min
5. Connect StripeNow you can take deposits on tables — direct to your account.
   1 min

Moving it onto your own domain

What is printed at the bottom of the menu should be your own. Go live immediately on a TableSpark address, and swap in your own domain at any point afterwards — including one you already own.

Certificates, HTTPS, the redirect from the naked domain and the search-engine housekeeping around a move are all handled for you. Bring a domain you already own, and we will tell you exactly which record to change.

The email after the booking is yours to design

Between booking and arriving, the confirmation email is the whole relationship. The moment a guest books, TableSpark sends them a confirmation on your behalf: the date, the time, the party size, where you are, how to reach you, and a link to release the table if their plans change. The pre-service reminder, the deposit receipt and the cancellation note share it.

None of it has to look like us. Six designs to start from, plus your colour, your logo, a photograph, the header treatment, your own closing line, your links and your socials. Connect your domain and it sends from your address too — so what lands in a guest’s inbox looks like it came from the restaurant, because it did.

The email below is being generated live by the same code that sends it for real. Try the templates and the accent colours.

What you change, and what stays

• Yours from the first minute: the wording anywhere on the site, the photographs, the menu and prices, your hours and location, and the palette and typefaces.
• Kept for you: the parts that break when hand-built: a menu that still reads at two hundred dishes, a basket that works one-handed, and contrast that holds whatever colour you choose.
• Never locked: add, delete or reorder any section on any page. Add pages. Delete the ones you do not want. The template is the starting line.

Findable, not merely online

There is a gap between a website that loads and a website that gets found, and it is wider than most owners expect. Working link, zero visibility. It happens through stray noindex rules, conflicting canonicals, orphaned pages, PDF menus, absent structured data and unfinished verification. And the restaurant pays for it: people searching your own name find aggregators and commission-charging platforms instead, so you rent back an audience that was yours.

It is handled in the box, not in an add-on. No guarantees about rankings or indexing exist anywhere in this industry. What exists here is the technical work, finished.

Questions before you start