Atelier Larix — an Alpine 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.

This is yours already. Prove it.

Atelier Larix is near-black with a green that reads as pine at dusk. 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.

Every page, as it publishes

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.

Who this was drawn for

Alpine fine dining has a particular restraint to it — few ingredients, precise technique, a short season — and the design mirrors that rather than reaching for cosy chalet cues. Near-black ground, a single pine green, wide margins, and photography that is allowed to be cold.

The opening is a chronicle: the season, the sitting, the sequence. It reads like the first page of a notebook, which suits a kitchen that changes its menu with the mountain rather than with a marketing calendar.

Everything on the home page, named

Nine blocks, arranged with as little decoration as possible:

• Hero — Big opening image, name & buttons, in the Chronicle treatment: Newspaper masthead, ruled meta row, three columns and a wide band.
• Pull quote — A large standout quotation.
• Feature rows — Alternating image and text rows.
• Menu preview — A few dishes on a sliding rail.
• Sourcing — The growers and makers behind the menu.
• Ambience — Full-width video or photo mood band.
• Reviews — Guest quotes with stars.
• Reservation form — Live availability slot picker, saved to your Inbox.
• FAQ — Accordion of questions.

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 sequence — which is how a seasonal tasting menu should be read: as an order of events, not a catalogue.

Section subtitles carry the season and the altitude; descriptions carry the forager, the herb, the age of the cheese. Because it is structured text rather than an image, all of that specificity is available to a guest and to a search engine.

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.

Ordering that works like the apps — without the commission

This is the part worth pressing. Atelier Larix uses the Minimal ordering layout — a clean typographic list with nothing between the guest and the order. The minimal ordering layout — a clean typographic list — fits what a mountain restaurant actually sells online: preserves, bread, a hamper, a voucher. It does not pretend to be a supermarket.

Quantities, inline choices and a running total behave as they do everywhere else, and payment goes into your own Stripe account with no 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 behind the menu

The story page is written for a restaurant that is also a place: the building, the valley, the seasons, the people. Narrative, sourcing, interview, timeline and a gallery page for the landscape photography that inevitably accumulates.

You will not be retyping the menu

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. One menu then feeds 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.

Ten minutes to live — and taking bookings

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 Atelier LarixThe 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

Run it on your own domain

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.

Findable, not merely online

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