Plein Ciel — a haute cuisine 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.

Plein Ciel is bone paper and one ink blue, with more white space than most restaurants dare use. 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.

Every page, as it publishes

6 pages, and every one of them is here. This is the live site, not a gallery. Every tab renders through the engine that publishes real restaurants, and the links inside it work. Try the Phone view.

What kind of restaurant this is

At this level the website’s job is to remove doubt, not to persuade. A guest booking a room like this has already decided; what they need is the shape of the evening, the price stated without apology, and a form that works. The design gives them that and almost nothing else.

The opening is a course ledger — the sequence, the sitting times, the price — set as type on paper. It is the least decorated hero in the whole library, and for this kind of room it is the most confident thing the page could do.

Pulling the home page apart

Nine blocks, arranged so that nothing shouts:

• Hero — Big opening image, name & buttons, in the Course Ledger treatment: Tonight's numbered courses beside a full-height dish photograph.
• Signature dish — One dish, full screen — name, story, price.
• Intro statement — Big opening statement line.
• Seasonal calendar — What each month or season brings.
• Image break — Full-width image band with optional caption.
• Menu preview — A few dishes on a sliding rail.
• Press bar — Press mentions or awards as a ruled band.
• Reservation form — Live availability slot picker, saved to your Inbox.
• Call to action — Headline + button band.

The statement block currently reads Classical technique, obsessive sourcing, and a dining room that runs like clockwork. — one line you will rewrite in about four seconds.

The menu: legible to guests, readable by Google

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 indexed layout lists the sections first, then opens each in turn — the structure of a printed carte rather than a web page. For a menu of long dish names in careful French it is the only layout that does not chop the writing into fragments.

Set menus carry their own block, with courses named and the price stated once. Wine pairings are listed against the menu they belong to rather than buried in a drinks list, which is how a guest actually decides.

The important part survives any layout: dishes, descriptions and prices are indexable text carrying Restaurant structured data, not an image a crawler has to guess at.

Ordering: a delivery app that belongs to you

This is the part worth pressing. Plein Ciel uses the Chip bar ordering layout — sections become filter chips across the top, so a short menu is ordered from in three taps. The ordering page here is arranged as a chip bar — sections as filters across the top, dishes beneath — which is the right register for the boutique and takeaway trade a room like this runs: a small, curated list rather than a whole menu.

Everything else behaves as it does across the library: the basket stays on screen, choices are inline, and payment goes into your own Stripe account with 0% commission taken by TableSpark. Stripe’s standard card-processing fees apply to online payments.

What the guest is asked depends on how they are eating: table number, phone number or address, and never all three.

The pages guests read before they come

The story page is written for a kitchen with a house style to explain: a long narrative, a pull quote, a sourcing block for the producers a room like this names, and a gallery. The separate gallery page carries room and plate photography at full width.

Upload your menu. The AI does the typing.

The tedious part comes first, and it is barely a part at all. Upload the menu exactly as it exists today, whether that is a printed card, a photograph of a board or an old PDF. Sections keep their order, dishes keep their descriptions, prices land in the price field, and dietary and spice marks come across where they were legible. You are the proofreader, not the typist.

That structure is the reason the rest of the site works. Everything downstream reads from it: 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.

The title and description a search result shows are drafted for you too, by a Write with AI button that works from the page’s own content. You edit before it ships, every time.

From nothing to taking reservations, in ten minutes

Most of the work was done before you arrived. The design, the layouts and the plumbing are all in place; what is missing is your restaurant. From opening the builder to a live site is usually about ten minutes, at which point guests can already book a table. Your inbox catches the booking; an automatic email catches the guest.

The money side is a single step: connect Stripe, and deposits and payments go directly into your account. Nothing is skimmed at any plan level — 0% commission. Stripe’s standard card-processing fees apply to online payments.

1. Pick Plein CielThe 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 and payment on orders — direct to your account.
   1 min

Point your own domain at it

A restaurant’s address is part of its name. Publishing does not wait for a domain. Start on ours, move to yours — the same site, a different name over the door.

The technical work is ours: issuing and renewing the certificate, securing the connection, redirecting the bare domain, and keeping the search engines aimed at the live address through the change. You can keep the domain you have had for a decade — the change at your registrar is a single record.

Every booking sends an email — in your colours

Something arrives in their inbox with your name on it. That is worth designing. It arrives at once, with the booking details, your address, your phone number and a link the guest can use to cancel without phoning. Everything after the booking — the reminder, the receipt, the cancellation — comes from here too.

What the guest sees is your identity, not our template. Six templates; your colour; your logo; a cover shot; a left, centred or banded header; your sign-off; your links; your social accounts. Your domain, once connected, becomes the sending address as well as the web address.

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

What is editable — which is nearly everything

• Yours from the first minute: the restaurant name, every line of copy, all photography, the menu and its prices, opening hours, address, and the colours and typefaces in the Theme tab.
• Kept for you: the layout logic — how the menu reads at 200 dishes, how the basket behaves on a phone, how sections stack on a small screen, and how the whole thing stays legible when you switch to a light palette.
• Never locked: move sections, delete them, add new ones from the module library, create pages, remove pages. Nothing here is fixed.

The difference between published and discovered

Getting a page online is easy. Getting it discovered, read and understood is the actual work. Live and invisible is a common combination — caused by stray robots directives, canonical conflicts, unlinked pages, PDF menus, missing schema, or verification that stalled halfway. The restaurant ends up buying back its own customers, because the people searching for it are meeting someone else’s page.

You inherit it finished. Nobody can sell you a ranking or guarantee indexing. This sells you the groundwork that makes both possible.

Things worth knowing first