Paradoja — an experimental 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.

Paradoja is bone paper with a violet accent that behaves like a laboratory label. 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.

Open it properly

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

An experimental restaurant sells anticipation, and the fastest way to destroy anticipation is to explain everything. The design keeps the first screen almost empty — a cartouche, a name, a way to book — and lets the story pages do the persuading further down.

A pale ground with a violet accent is a deliberate inversion: experimental kitchens usually go dark, and going light instead reads as clinical precision rather than theatre. The old-style serif keeps it from looking like a technology company.

The home page, block by block

Nine blocks, most of them quiet:

• Hero — Big opening image, name & buttons, in the Cartouche treatment: Paper cartouche over the room: copy, actions and an awards ribbon.
• 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.

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

This template uses the Compact layout — a tight priced list with no photography — the density a menu of composed plates actually wants. The compact layout is right for a menu that is a list of stages rather than dishes. It states the sequence, the length and the price, and stops — which for this format is the whole job.

Where a stage needs explanation, the description line carries it. Dietary marks are set per item so that a guest can see, before booking, whether the sequence can be adapted for them.

The layout can change; what does not is that each dish, its description and its price are text on the page, wrapped in Restaurant schema — rather than a PDF or a picture of a card.

Taking the booking

This template has no basket. A restaurant with no walk-ins and a fixed sequence sells reservations, and the entire structure routes there.

The booking form offers only real sittings, collects dietary requirements at the point of reservation, and — with Stripe connected — can take a deposit or hold a card, paid directly into your own account.

The story and visit pages

The story page carries the manifesto: a long narrative, a quote, an interview and a timeline. The gallery page exists because a restaurant like this generates photography constantly and needs somewhere permanent to keep it.

The menu builds itself from a photograph

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. The same structured menu 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.

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.

Ten minutes, then you are open

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 ParadojaAll 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

The address should be yours

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.

The email nobody thinks about, designed properly

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.

That is a real email, produced here by the same renderer the booking flow uses. The buttons above it work.

Yours, ours, and never locked

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

Being on the internet is not being in search

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.

What restaurants ask us