Restaurant Anselm — a modern European 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.

Nothing here is precious. Try it.

Restaurant Anselm is a dark room with a green accent pitched somewhere between bottle and pine. Yours might be white tile and morning light, or brass and candles, or something nobody has built yet.

The controls beside the frame are not an illustration of the Theme tab — they are the Theme tab, driving the same engine that publishes real restaurants. Press whatever you like; nothing is stored and nothing is signed up for. Go on.

The entire site, page by page

5 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 room this design is for

A city restaurant that serves breakfast, lunch, aperitivo and dinner has four businesses in one room, and most restaurant websites show only the last of them. This design opens by naming all four, with the hours for each, so a guest arriving at eleven in the morning knows they are welcome.

The palette is a dark room with a single green, and the type is a high-contrast serif over a plain sans. It is a formal-looking page carrying an informal offer, which is the right way round for a room that wants to be used all day.

The home page, section by section

Eight blocks, arranged as a day:

• Hero — Big opening image, name & buttons, in the A Day in Four Parts treatment: The day split into four ruled slots above the room band.
• Marquee strip — Scrolling awards or words.
• Signature dish — One dish, full screen — name, story, price.
• Gallery — Grid, masonry or moving strip.
• Pull quote — A large standout quotation.
• Sourcing — The growers and makers behind the menu.
• Reviews — Guest quotes with stars.
• Reservation form — Live availability slot picker, saved to your Inbox.
• Call to action — Headline + button band.

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

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 every menu first — breakfast, lunch, dinner, the bar — then opens each in turn. For a room with four services that structure is the only one that stays legible.

Each menu carries its own hours in the section subtitle, which answers the question guests actually ask. Descriptions carry the technique and the producer, and every price is a field rather than typography.

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 ordering page, and who keeps the money

This is the part worth pressing. Restaurant Anselm uses the Delivery app ordering layout — sections run down a rail on the left, the dish list swaps beside them without losing your place, and the basket follows the scroll. The full delivery-app layout is here because an all-day room does real takeaway trade at lunch: a section rail, dishes beside it, and a basket that follows the scroll.

It is on your own domain, the order lands in your own inbox, the guest record is yours, and TableSpark takes 0% — which over a year of lunch trade is the difference between a marketing cost and a margin.

Dine-in wants a table number and nothing else; collection wants a number to ring; delivery wants somewhere to go. No mode asks for the others’ fields.

The rest of the site

The story page carries the room, the chef and the sourcing, with a timeline, an interview and a gallery. The visit page handles the practicalities of a room used differently at four times of day.

The menu builds itself from a photograph

Here is the hour you were dreading, deleted. Photograph the card, the board or the takeaway sheet — up to ten pages at a time — and hand it to TableSpark. It is read into proper fields — section, dish, description, price, dietary marks, spice level — rather than pasted in as a lump of text. Then you read it through, correct whatever the lens misread, and save.

It behaves like data, because it is data. The same structured menu drives 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.

For the search snippet, a Write with AI button drafts the title and description out of the page itself. It is a draft, not a decision: edit it, then publish.

Live in ten minutes, booking in eleven

Nothing here needs to be built, because it already is. The hard parts are finished; the personal parts are not, and only you can do those. Most restaurants go from opening the builder to a published site on their own address inside ten minutes, and the reservation form answers from the moment it publishes. You see it in the inbox, they see a confirmation in theirs, both within seconds.

Add your Stripe account and the same site takes booking deposits and order payments, with the money landing in your account rather than ours. TableSpark takes 0% commission at every plan level. Stripe’s standard card-processing fees apply to online payments. Nothing else is deducted.

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

Your name over the door

An address is branding that people type. The TableSpark address gets you live in minutes; your own domain takes over the moment you want it to, with nothing rebuilt.

TableSpark manages the technical side: the certificate, the secure connection, the redirect from the bare domain to the one you chose, and keeping search engines pointed at the right address so the move does not cost you what you have already earned. An existing domain works fine. You get one instruction, not a documentation site.

The email nobody thinks about, designed properly

What lands in the inbox after a booking is doing more work than most restaurants realise. The confirmation goes out immediately: date and time, party size, the address and phone number, and a link that releases the table if something changes. It also carries the reminder the day before, the deposit receipt and any cancellation.

The design is not a TableSpark email with your name in it — it is your email. Six templates to choose between, then colour, logo, cover image, header style, sign-off wording, links and socials are all yours to set. Hook up the domain and even the sender is you.

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

Where the template ends and you begin

• Yours from the first minute: the name over the door, all the words, every photograph, the menu, the prices, your hours and address, and the whole palette and type system.
• Kept for you: the mechanics — how a very long menu paginates, how ordering behaves on a phone, how every block reflows, and how text stays readable against any background you pick.
• Never locked: reorder or delete any section, add any module, and add or remove pages. The template is where you begin, not where you must stay.

What it takes to actually be found

Any tool can put a page on the internet. Fewer can make sure a search engine understands what is on it. It fails quietly: noindex directives nobody noticed, conflicting canonical URLs, orphan pages, menus buried in PDFs, no structured data about the restaurant, and search verification that was never completed. The bill arrives as dependence — guests looking for your kitchen land on a directory or a marketplace that charges you for the introduction.

This is packaged into the site rather than sold separately. There is no promise of a position or of being indexed, because nobody can make one. There is a promise that you will not be hiring someone to fix the basics.

Before you begin