Delirio — an avant-garde tasting menu 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.

Delirio is near-black with a violet that looks like stage lighting rather than a colour swatch. Yours might be white tile and morning light, or brass and candles, or something nobody has built yet.

There is no demo video and no sales call. What you see on the right is the actual Theme panel from the builder, wired to the actual site renderer on the left. Press a colour. It will not ask you to register and it will not remember what you did. Go on.

Go through it like a guest would

6 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 kitchen behind the layout

A restaurant that serves one menu, at set times, to thirty people, has the opposite problem to a busy bistro: not how to convert a hungry stranger, but how to convey that this is an event worth arranging a life around. The design leans fully into that. It opens on a concierge panel — seatings, the date, the way in — rather than a menu button, because there is nothing to browse and everything to book.

Violet on near-black is a deliberate refusal of restaurant convention. There is no warm wood, no linen, no gold. The room this design imagines is lit like a theatre, and the photography is given full-bleed space to behave like set photography rather than food styling.

The home page, section by section

Nine blocks carry the page, every one of them editable:

• Hero — Big opening image, name & buttons, in the Concierge treatment: Booking desk beside the room: services, party sizes, availability.
• Signature dish — One dish, full screen — name, story, price.
• Intro statement — Big opening statement line.
• Image break — Full-width image band with optional caption.
• Seasonal calendar — What each month or season brings.
• 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 Dinner as dramaturgy — a tasting that argues with your expectations, course by course. — one line you will rewrite in about four seconds.

A menu that reads like a card and indexes like a page

This template uses the Compact layout — a tight priced list with no photography — the density a menu of composed plates actually wants. The menu is compact by design — a tasting menu is a sequence, not a catalogue, and setting twenty courses as photo cards would be absurd. Courses run as a tight typographic list with the price and the length of the sitting stated plainly at the top.

What this layout protects is anticipation. Guests should arrive knowing the shape of the evening and not much else, and the compact list gives exactly that: the courses named, the wine pairing offered, the dietary conversation flagged before booking rather than at the table.

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 shopping basket here, and that is the correct decision for the format: this template routes everything to the reservation instead. The booking page only offers dates and times that are actually available from your service hours, so a guest never chooses a sitting that does not exist.

Deposits are the mechanism that makes a thirty-cover room survivable, and connecting Stripe turns the booking form into one that holds a card or takes a deposit at the point of reservation. The money goes directly to your account and TableSpark takes 0%. Stripe’s standard card-processing fees apply to online payments.

Where the restaurant explains itself

The story page is built for a kitchen with a manifesto: a long-form chef narrative, a pull quote, a Q&A and a gallery that can carry plating photography at full width. The dedicated gallery page exists for the same reason — rooms like this are photographed constantly, and the images are part of the sell.

The typing is already done

Start with the job everyone puts off. Photograph your menu — the printed card, the chalkboard, the laminated takeaway sheet — and upload it. It comes back as a real menu — sections in order, dishes, descriptions, prices, dietary marks and spice levels, all filled in. It lands in front of you for approval first, with every value editable.

The important part: this is structured data, not an image of a menu. That same menu immediately drives 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.

Every page carries a Write with AI button for the search title and description — it reads the page you are on and writes the first draft. Read it, sharpen it, publish it. The order matters.

Ten minutes, then you are open

There is no kick-off call and no staging link to approve. Everything is designed and wired — you are changing the words and the photographs. Ten minutes, give or take, and it is live — with the reservation form answering immediately. Both sides get told at once — the booking in your inbox, the confirmation in theirs.

Money is one connection away. Link your Stripe account and the site can take deposits on bookings and payment on orders, paid directly to you. No per-order fee, no revenue share, 0% commission on any plan. Stripe’s standard card-processing fees apply to online payments.

1. Pick DelirioAll the pages and the demo menu copy into your account.
   1 min
2. Change the name and the wordsType over anything. The restaurant name updates throughout.
   4 min
3. Upload your menuThe menu is built from a photograph rather than typed.
   3 min
4. PublishPublished — and the booking form answers from that moment.
   1 min
5. Connect StripeNow you can take deposits on tables — direct to your account.
   1 min

Your domain, our plumbing

The address on your napkins should be the address that loads. Start on a TableSpark address, then bring your own domain across — the site does not change, only the name it answers to.

The certificate, its renewal, the secure connection and the redirects are managed here, along with the canonical and sitemap signals that make a domain move safe. Bring your own, and the setup screen tells you the one value to paste and where.

What lands in the guest’s inbox

A confirmation email is the only piece of your restaurant a guest keeps in their pocket for a week. The guest is emailed straight away with the particulars — date, time, party size, address, phone — and a link to release the table themselves. Service reminders, deposit receipts and cancellations all travel on the same design.

You are not stuck with our house style. Choose from six styles and make the rest yours: accent colour, logo, cover photograph, header layout, sign-off, links and social accounts. Connect the domain and the sender address becomes yours, which is what makes it read as genuinely from you.

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: all copy, all imagery, the entire menu with its prices, hours, address, and the colour and type choices underneath.
• Kept for you: the engineering underneath: long menus, small screens, reflowing sections, and contrast that survives your colour choices.
• Never locked: rearrange every page, drop blocks you dislike, pull in new ones, and add or delete pages entirely. The structure is a suggestion.

Live is not the same as findable

Publishing a page and being present in search are separate achievements. A site can be live at a working link and still be missing from Google: a stray noindex, conflicting canonicals, orphaned pages, a menu locked inside a PDF, missing structured restaurant data or unfinished search verification will each do it. That gap gets filled by directories and marketplaces, which are delighted to charge you for guests who were already looking for you by name.

That groundwork is already laid here. Neither rankings nor indexing can be guaranteed by anyone — but the setup that so often prevents them is complete here.

What restaurants ask us