Brüderhaus — a modern German 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.

Brüderhaus is a near-black room with a green that reads as a bottle rather than a leaf. Yours might be white tile and morning light, or brass and candles, or something nobody has built yet.

Rather than explain, here is the thing itself: the builder’s Theme controls on one side, the live site on the other, both real. You cannot break it, nothing saves, and no account is required to have a go. Go on.

Now walk the whole thing

6 pages, and every one of them is here. What follows is the site itself rather than pictures of it. The same engine that publishes a live restaurant is drawing it here, links and all. The Phone toggle shows the small-screen version.

Who this was drawn for

A German kitchen operating outside Germany is doing translation work on every plate, and the website has to hold both halves — the technique and the place. The design does it with restraint: a dark, filmic ground, a single cool accent, and photography given room to establish a mood before any copy arrives.

The opening is a waiting list, which is an unusual and honest hero for a small room with more demand than covers. It states the position plainly and gives the guest something to do about it, rather than pretending a table is always available.

Pulling the home page apart

Nine blocks, all editable modules:

• Hero — Big opening image, name & buttons, in the Waiting List treatment: Live waiting-list card over the brunch table.
• Announcement — Slim notice bar at the top.
• Signature dish — One dish, full screen — name, story, price.
• Text + image — A paragraph beside a photo.
• Menu preview — A few dishes on a sliding rail.
• Values — Three guiding values.
• Reviews — Guest quotes with stars.
• Call to action — Headline + button band.

The menu page, and why it is text

This template uses the Compact layout — a tight priced list with no photography — the density a menu of composed plates actually wants. A compact carte is the right density for a menu that is deliberately short. The whole offering sits on a screen and a half, which is the correct impression for a kitchen doing a few things exactly.

The description line carries the German name and the explanation together, which is the practical solution for dishes whose names mean nothing to local guests. Both are indexable text, so a search for either version finds the page.

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.

The ordering page: same habit, different economics

This is the part worth pressing. Brüderhaus uses the Photo tiles ordering layout — every dish is a tile with an image, a price and an add button that becomes a quantity stepper. Photo tiles work here because the online list is short and visual — the bread, the charcuterie, the cakes. Each tile carries an image, a price and an add button that becomes a stepper.

Choices are chips on the tile rather than a modal, the basket stays visible with a running total, and collection asks only for a name and a phone number. Payment lands in your own Stripe account, and TableSpark takes 0%. 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 carries the two-country narrative properly — where the recipes come from, why they are cooked here, who cooks them. There is a timeline, an interview and a gallery, and the reservations page manages a room that runs on bookings alone.

Upload your menu. The AI does the typing.

The worst job in setting up a restaurant site is typing the menu. You do not have to. Send in the menu you hand to guests — card, board, PDF, ten pages if it runs that long. What returns is not a scan but a structured menu: every section, every dish, every price, with dietary and spice marks read off the page where they were printed. Nothing saves until you have looked at it — every field is editable on the review screen.

And because it is data rather than a photograph, it can do work. That single menu is what powers 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.

Search titles and descriptions are drafted the same way: press Write with AI and it writes from the page in front of you. You still approve every line of it before it goes anywhere.

Ten minutes to live — and taking bookings

The waiting is the part that has been removed. Consider it a fully fitted kitchen waiting for your knives. Ten minutes to live, and the booking form does not need setting up: it is already answering. The booking appears in your inbox; the guest gets a confirmation before they have put their phone down.

One Stripe connection turns the site into something that collects money: deposits on tables, payment on orders, paid direct. Our commission is 0% at every plan level. Stripe’s standard card-processing fees apply to online payments. That is the only deduction.

1. Pick BrüderhausThe full site arrives in your account as a working draft.
   1 min
2. Change the name and the wordsRewrite the words by clicking them; the name carries everywhere.
   4 min
3. Upload your menuSend the menu in as a photograph and check what comes back.
   3 min
4. PublishIt goes live on your address and starts taking bookings.
   1 min
5. Connect StripeNow you can take deposits on tables and payment on orders — direct to your account.
   1 min

Moving it onto your own domain

Nobody prints someone else’s name on their menu, and a web address is no different. You start on a TableSpark address so you can publish today, and move the site onto your own domain whenever you are ready — the one on your menus, your napkins and your Google listing.

You do not touch a certificate or a redirect rule. TableSpark issues and renews the SSL, points the bare domain at your chosen host, and keeps the search signals consistent. If the domain is already yours, nothing needs buying; you are told precisely which DNS record to point where.

Every booking sends an email — in your colours

Most guests will see this email more often than they see your home page. On booking, an email goes out on your behalf with everything the guest needs — when, how many, where, how to reach you, and a one-click way to give the table back. Reminder emails, deposit receipts and cancellation notices are cut from the same cloth.

And the email is yours to design, not ours. Six templates, your accent colour, your logo, a cover photograph, the header layout, a sign-off in your own voice, your links and your social accounts. Once your domain is connected the email leaves from your address as well, not a generic one.

Not a mock-up: the frame runs the actual guest-email renderer. Press a template or an accent and watch it change.

What you change, and what stays

• Yours from the first minute: the restaurant’s name, the copy on every page, the photography, the dishes and prices, the opening hours and address, and the theme itself.
• Kept for you: the load-bearing decisions: long-menu layout, mobile ordering behaviour, responsive stacking, and colour contrast that does not collapse when you change the palette.
• Never locked: restructure any page, delete sections outright, add new modules, and create or remove pages. None of it is locked.

Built to be found, not just to be live

A live link proves the page exists. It does not prove Google can read it. Sites sit at a perfectly good address and never appear in search — because of a leftover noindex, canonicals that disagree, pages nothing links to, a menu trapped in a PDF, absent restaurant schema, or verification never finished. What follows is expensive: searches for your name, your dishes or your street send guests to marketplaces that take a cut of the booking you would have had for free.

None of it is left for you to assemble. Rankings and indexing are Google’s decision and no honest supplier promises either — but the configuration that makes them possible is done.

Common questions