Klippeholm — a New Nordic 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.

Klippeholm is a dark room with a teal that belongs to cold water. 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

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

An island restaurant has a season, a ferry and a larder, and all three belong on the first screen. The bake-times opening handles the practicalities — when things come out of the oven, when the room is open — and the rest of the page handles the argument.

A dark ground with a cold teal accent is the honest palette for a Nordic coast, and the wide display face keeps short Danish dish names legible without turning them into decoration.

The home page, section by section

Eight blocks, arranged around a season:

• Hero — Big opening image, name & buttons, in the Bake Times treatment: What comes out of the oven, and when.
• Intro statement — Big opening statement line.
• Menu preview — A few dishes on a sliding rail.
• Signature dish — One dish, full screen — name, story, price.
• Image break — Full-width image band with optional caption.
• Gallery — Grid, masonry or moving strip.
• Reviews — Guest quotes with stars.
• Call to action — Headline + button band.

The statement block currently reads Short seasons, long memories — preserved, fermented, and served in their own time. — one line you will rewrite in about four seconds.

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

This template uses the Plate layout — every section leads on one photographed dish and lists the rest as type — imagery where it persuades, type where it informs. The plated layout gives each section its signature dish as an image and the rest as type — the right balance for a menu where a few preparations carry the argument and the others support it.

A preserving kitchen’s menu is full of dates and processes, and the description field carries them: the year it was picked, the length of the ferment, the island it came from. All indexable text rather than a photographed card.

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.

Take the order yourself

This is the part worth pressing. Klippeholm 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 — is right for pantry goods: preserves, ferments, vinegars, a hamper. The description sells them; a photograph of a jar does not.

Quantities and sizes are inline, the total stays visible, and payment lands in your own Stripe account with no commission taken by TableSpark. Stripe’s standard card-processing fees apply to online payments.

Each mode collects only what it must: a table number for dine-in, a telephone number for collection, an address for delivery.

Where the restaurant explains itself

The story page carries the island, the larder and the seasons — narrative, sourcing, interview, timeline, gallery. The visit page does real work explaining a location that involves a ferry and a season.

Photograph the menu. That is the whole job.

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.

Publish today, take bookings tonight

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 KlippeholmThe 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 name over the door

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.

What lands in the guest’s inbox

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.

Live is not the same as findable

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