Waldstück — a modern Austrian 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.

Do not read this bit. Touch it.

Waldstück is bone paper with a forest green that reads as parkland rather than as a logo. Yours might be white tile and morning light, or brass and candles, or something nobody has built yet.

Skip the description. The panel is lifted straight out of the builder and the frame is the real renderer, so what happens when you press an accent here is exactly what happens in your account. Nothing you do is saved or asked about. 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 this design is for

A grand European dining room has to look established without looking dated, which is a harder brief than it sounds. The design solves it with an old-style serif on bone paper and a single forest green — a palette that could be a hundred years old or five, and reads as neither retro nor trendy.

The opening is a salon plaque: the name engraved rather than photographed, with the hours and the route to a table beneath. It is the most formal hero in the library and exactly right for this kind of room.

The home page, block by block

Nine blocks, arranged with formality:

• Hero — Big opening image, name & buttons, in the Salon Plaque treatment: Portrait portal on a dark band, awards row and chef signature beneath.
• Intro statement — Big opening statement line.
• Scroll story — Numbered chapters beside a pinned photo.
• Signature dish — One dish, full screen — name, story, price.
• Numbers — Headline stats.
• Text + image — A paragraph beside a photo.
• Reviews — Guest quotes with stars.
• Reservation form — Live availability slot picker, saved to your Inbox.
• Newsletter — Email signup band.

The statement block currently reads A mountain house kitchen — wood fire, larder walls, and whatever the valley sent up. — one line you will rewrite in about four seconds.

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

This template uses the Accordion layout — sections sit collapsed on one screen and open in place, so a long menu never becomes a long scroll. The accordion suits a large menu with many sections — a full carte, a vegetarian menu, a lunch menu, a cheese trolley — where the guest needs the structure visible before choosing where to look.

Descriptions carry the technique and the producer; set menus have their own block with courses named and the price stated once. Every value is a field, so changing a price updates every page that shows it.

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.

Taking the booking

This template routes to reservations rather than a basket, which suits a dining room that sells tables. The booking form offers only the sittings your service hours define and collects dietary requirements and occasion alongside the party size.

Everything arrives in your TableSpark inbox with the booking, and the guest is confirmed by email in your own branding immediately, with a link to release the table if plans change.

The story and visit pages

The story page has room for a long institutional history: narrative, timeline, interview, sourcing and a gallery. The events page carries the private dining and seasonal occasions that a room of this size runs constantly.

The menu builds itself from a photograph

Start with the job everyone puts off. Photograph your menu — the printed card, the chalkboard, the laminated takeaway sheet — and upload it. It comes back as a real menu — sections in order, dishes, descriptions, prices, dietary marks and spice levels, all filled in. It lands in front of you for approval first, with every value editable.

The important part: this is structured data, not an image of a menu. 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.

Every page carries a Write with AI button for the search title and description — it reads the page you are on and writes the first draft. Read it, sharpen it, publish it. The order matters.

Publish today, take bookings tonight

There is no kick-off call and no staging link to approve. Everything is designed and wired — you are changing the words and the photographs. Ten minutes, give or take, and it is live — with the reservation form answering immediately. Both sides get told at once — the booking in your inbox, the confirmation in theirs.

Money is one connection away. Link your Stripe account and the site can take deposits on bookings and payment on orders, paid directly to you. No per-order fee, no revenue share, 0% commission on any plan. Stripe’s standard card-processing fees apply to online payments.

1. Pick WaldstückAll 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

Your domain, our plumbing

The address on your napkins should be the address that loads. Start on a TableSpark address, then bring your own domain across — the site does not change, only the name it answers to.

The certificate, its renewal, the secure connection and the redirects are managed here, along with the canonical and sitemap signals that make a domain move safe. Bring your own, and the setup screen tells you the one value to paste and where.

The email nobody thinks about, designed properly

A confirmation email is the only piece of your restaurant a guest keeps in their pocket for a week. The guest is emailed straight away with the particulars — date, time, party size, address, phone — and a link to release the table themselves. Service reminders, deposit receipts and cancellations all travel on the same design.

You are not stuck with our house style. Choose from six styles and make the rest yours: accent colour, logo, cover photograph, header layout, sign-off, links and social accounts. Connect the domain and the sender address becomes yours, which is what makes it read as genuinely from you.

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: all copy, all imagery, the entire menu with its prices, hours, address, and the colour and type choices underneath.
• Kept for you: the engineering underneath: long menus, small screens, reflowing sections, and contrast that survives your colour choices.
• Never locked: rearrange every page, drop blocks you dislike, pull in new ones, and add or delete pages entirely. The structure is a suggestion.

Being on the internet is not being in search

Publishing a page and being present in search are separate achievements. A site can be live at a working link and still be missing from Google: a stray noindex, conflicting canonicals, orphaned pages, a menu locked inside a PDF, missing structured restaurant data or unfinished search verification will each do it. That gap gets filled by directories and marketplaces, which are delighted to charge you for guests who were already looking for you by name.

That groundwork is already laid here. Neither rankings nor indexing can be guaranteed by anyone — but the setup that so often prevents them is complete here.

The questions we get asked