Le Mandorle — an avant-garde Italian 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.

Press something. It is your restaurant now.

Le Mandorle is near-black with a terracotta that appears once and means something when it does. Yours might be white tile and morning light, or brass and candles, or something nobody has built yet.

So do not read about it. The panel on the right is the real Theme tab out of the builder, and the frame beside it is the real site — the same renderer that publishes a live restaurant. Nothing is a mock-up, nothing you touch is permanent, and nobody is asking you to sign in first. Go on.

Now walk the whole thing

6 pages, and every one of them is here. Nothing below is a screenshot: the frame renders it through the same engine that publishes your site, so every tab is the real page and every link inside it works. Switch to Phone to watch the same design reflow.

Why it looks like this

An avant-garde Italian kitchen has to signal that it is not the trattoria the guest is picturing, and it has to do it without abandoning Italy. This design does it typographically: an old-style serif set very large against a near-black ground, with none of the warm-wood cues the cuisine usually reaches for.

The opening is a reserve bar — the sittings, the menus, the route to a table. For a room where the decision is which menu rather than whether to come, that is the correct first screen.

Pulling the home page apart

Nine blocks, arranged for a room that sells menus rather than dishes:

• Hero — Big opening image, name & buttons, in the Reserve Bar treatment: Centred name over the room, booking bar pinned across the base.
• Intro statement — Big opening statement line.
• Signature dish — One dish, full screen — name, story, price.
• Press bar — Press mentions or awards as a ruled band.
• Menu preview — A few dishes on a sliding rail.
• Scroll story — Numbered chapters beside a pinned photo.
• Reviews — Guest quotes with stars.
• Ambience — Full-width video or photo mood band.
• Call to action — Headline + button band.

The statement block currently reads Flour, eggs and patience — pasta rolled at noon, gone by ten. — one line you will rewrite in about four seconds.

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 editorial layout gives each menu its own opening plate and then sets the courses as type. For a restaurant offering three tasting menus at three lengths, that structure lets each one be read as a complete proposition.

Prices are stated once per menu, with supplements listed where they apply. Pairings sit against the menu they belong to. Because these are structured fields, a price change reaches the menu page, any home-page preview and the structured data in one edit.

Whichever layout you choose, the point is the same: every dish, description and price is real text in the page with Restaurant schema around it, not a PDF and not a photograph of a laminated sheet.

How a table gets reserved

There is no basket in this template — it is built for a room that sells reservations. Everything routes to a booking form that offers only the sittings your service hours define, and collects the menu choice, party size and dietary requirements at the same time.

With Stripe connected, the same form can hold a card or take a deposit, paid directly into your account. Deposit receipts and cancellations are emailed automatically in your own branding.

The pages behind the menu

The story page suits a kitchen with a lineage and a manifesto: narrative, quote, interview, timeline and a gallery page for plating photography at full width.

Upload your menu. The AI does the typing.

The worst job in setting up a restaurant site is typing the menu. You do not have to. Send in the menu you hand to guests — card, board, PDF, ten pages if it runs that long. What returns is not a scan but a structured menu: every section, every dish, every price, with dietary and spice marks read off the page where they were printed. Nothing saves until you have looked at it — every field is editable on the review screen.

And because it is data rather than a photograph, it can do work. 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.

Search titles and descriptions are drafted the same way: press Write with AI and it writes from the page in front of you. You still approve every line of it before it goes anywhere.

Ten minutes to live — and taking bookings

The waiting is the part that has been removed. Consider it a fully fitted kitchen waiting for your knives. Ten minutes to live, and the booking form does not need setting up: it is already answering. The booking appears in your inbox; the guest gets a confirmation before they have put their phone down.

One Stripe connection turns the site into something that collects money: deposits on tables, payment on orders, paid direct. Our commission is 0% at every plan level. Stripe’s standard card-processing fees apply to online payments. That is the only deduction.

1. Pick Le MandorleThe 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

Point your own domain at it

Nobody prints someone else’s name on their menu, and a web address is no different. You start on a TableSpark address so you can publish today, and move the site onto your own domain whenever you are ready — the one on your menus, your napkins and your Google listing.

You do not touch a certificate or a redirect rule. TableSpark issues and renews the SSL, points the bare domain at your chosen host, and keeps the search signals consistent. If the domain is already yours, nothing needs buying; you are told precisely which DNS record to point where.

The email after the booking is yours to design

Most guests will see this email more often than they see your home page. On booking, an email goes out on your behalf with everything the guest needs — when, how many, where, how to reach you, and a one-click way to give the table back. Reminder emails, deposit receipts and cancellation notices are cut from the same cloth.

And the email is yours to design, not ours. Six templates, your accent colour, your logo, a cover photograph, the header layout, a sign-off in your own voice, your links and your social accounts. Once your domain is connected the email leaves from your address as well, not a generic one.

Not a mock-up: the frame runs the actual guest-email renderer. Press a template or an accent and watch it change.

What is editable — which is nearly everything

• Yours from the first minute: the restaurant’s name, the copy on every page, the photography, the dishes and prices, the opening hours and address, and the theme itself.
• Kept for you: the load-bearing decisions: long-menu layout, mobile ordering behaviour, responsive stacking, and colour contrast that does not collapse when you change the palette.
• Never locked: restructure any page, delete sections outright, add new modules, and create or remove pages. None of it is locked.

Built to be found, not just to be live

A live link proves the page exists. It does not prove Google can read it. Sites sit at a perfectly good address and never appear in search — because of a leftover noindex, canonicals that disagree, pages nothing links to, a menu trapped in a PDF, absent restaurant schema, or verification never finished. What follows is expensive: searches for your name, your dishes or your street send guests to marketplaces that take a cut of the booking you would have had for free.

None of it is left for you to assemble. Rankings and indexing are Google’s decision and no honest supplier promises either — but the configuration that makes them possible is done.

Questions before you start