Altopiano — a mountain 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.

Altopiano is warm plaster with a terracotta that belongs to a bread oven. 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.

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 room it imagines

A restaurant an hour from anywhere has to answer a different question than a city one: not “why you” but “why the drive”. The design answers it structurally, leading with what comes out of the oven and following immediately with the practical detail a guest planning a journey needs.

The palette is plaster and terracotta, warm and unhurried, and the type is a soft serif with a plain sans. It reads as a converted building rather than a design project, which is exactly what a mountain restaurant is selling.

The home page, section by section

Eight blocks, arranged for someone deciding whether to drive:

• Hero — Big opening image, name & buttons, in the Oven Poster treatment: Flat accent field, oven temperature, six pizzas on one line.
• Pull quote — A large standout quotation.
• Menu preview — A few dishes on a sliding rail.
• Seasonal calendar — What each month or season brings.
• Gallery — Grid, masonry or moving strip.
• Numbers — Headline stats.
• 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.

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

This template uses the Rails layout — each section becomes a horizontal strip that swipes on a phone, so twenty dishes take the room of four. The menu runs on rails, giving each section a swipeable strip of dishes. For a kitchen with a short, deep menu that changes with the season it shows everything at once without a long scroll.

Seasonality is the argument here, and the section subtitle is where it goes — the month, the altitude, what is available. Set menus sit alongside as their own block, which is how a tasting menu and a shorter carte should appear together.

Whatever the arrangement, the menu is text and not a picture — every dish, description and price indexable, with Restaurant schema around it.

Ordering, on your own terms

This is the part worth pressing. Altopiano uses the Chip bar ordering layout — sections become filter chips across the top, so a short menu is ordered from in three taps. The chip-bar ordering layout — sections as filters across the top — suits a restaurant whose online sales are a curated few things rather than the whole menu: the bread, the preserves, a hamper.

It behaves like everything else in the library: quantities, inline options, a visible total, and payment into your own Stripe account with 0% taken by us. Stripe’s standard card-processing fees apply to online payments.

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.

Where the restaurant explains itself

The story page carries the building, the family and the valley — narrative, timeline, interview, gallery. The events page handles the cookery days and seasonal dinners a destination restaurant runs, and the visit page does the real work of explaining a road that a map alone cannot.

The typing is already done

Nobody starts a website looking forward to retyping ninety dishes. Point a phone at whatever your menu currently lives on and send it over. The AI turns it into sections, dishes, descriptions and prices, and picks up the dietary marks and heat levels it can see. Read it back, adjust anything the photograph fumbled, and that is the menu built.

A photograph of a menu is decoration; a structured menu is infrastructure. From there the same data runs 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.

And the fields nobody enjoys writing — the search title and description — are drafted by a Write with AI button that reads the page first. The AI writes the first version; you decide whether it is the last.

Ten minutes, then you are open

You are not commissioning a website; you are moving into one. The site works from the first second — it simply has the wrong name on the door. Ten minutes covers it for most kitchens — and the second it is live, the booking form is taking reservations. It lands in the inbox with the party size and the time, and the guest is confirmed by email at once.

Attach your own Stripe account and the site can charge for orders and hold deposits on tables — the funds are yours from the start. We take 0%. Not on the first order, not on the thousandth. Stripe’s standard card-processing fees apply to online payments.

1. Pick AltopianoThe whole site copies into your account, menu and all.
   1 min
2. Change the name and the wordsClick any block and type. The restaurant name propagates everywhere.
   4 min
3. Upload your menuPhotograph it and let the AI build the sections, dishes and prices.
   3 min
4. PublishYou are live on your address. Bookings work immediately.
   1 min
5. Connect StripeNow you can take deposits on tables and payment on orders — direct to your account.
   1 min

Your domain, our plumbing

The web address is something guests read aloud, so it should sound like you. You can be live before lunch on a TableSpark address and on your own domain by the weekend, with no rebuild in between.

Everything fiddly about a domain — SSL, renewals, bare-domain redirects, canonical URLs surviving the move — is managed on your behalf. Already own the name? Keep it — you get the exact record to update, in plain English.

The email nobody thinks about, designed properly

The email that follows a booking is read more carefully than any page on the site. As soon as a table is confirmed, the guest gets an email in your name carrying the date, the time, the number of covers, your address, your phone number and a way to cancel cleanly. Reminders, receipts and cancellations follow the same treatment, so nothing looks bolted on.

It carries your restaurant, not our branding. Pick one of six templates, then set the accent, the logo, a cover image, how the header sits, the sign-off line, your links and your social marks. When your domain is connected the mail is sent from your own address, which is also what keeps it out of a promotions tab.

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: every word and every image, the menu and what it costs, the hours you keep, where you are, and the colours and fonts the site is built from.
• Kept for you: the difficult engineering — long-menu behaviour, the basket on a small screen, how blocks stack when the window narrows, and legibility surviving a palette change.
• Never locked: reorder, remove or add any block on any page, add whole pages, and throw away anything you do not need. This is a starting point, not a cage.

Being on the internet is not being in search

Being published and being findable are two different things, and only one of them happens automatically. The usual culprits are mundane: a robots rule nobody removed, two canonicals pointing different ways, orphaned pages, the menu published as a PDF, no structured restaurant data, search verification half done. The cost lands on the restaurant — guests searching your name, your menu or your street reach directories and commission-charging marketplaces first, and you end up paying for the traffic you should already own.

All of that is finished before you arrive. Search results are not something anyone can promise you. A correctly configured site is, and that is what this is.

What restaurants ask us