Casa Nebbiolo — a wine country 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.

Press something. It is your restaurant now.

Casa Nebbiolo is near-black with a terracotta accent, the colours of a cellar with one lamp in it. Yours might be white tile and morning light, or brass and candles, or something nobody has built yet.

This is the product, not a picture of it. Left, the live site. Right, the builder’s own Theme panel. Everything you press takes effect immediately, nothing persists, and there is no sign-in wall in front of it. 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.

Why it looks like this

A restaurant in a wine region sells two things, and most restaurant websites only handle one. This design gives the cellar equal standing: a menu structure for the food and a drinks structure for the list, each with its own layout rather than the wine being appended as an afterthought.

The opening is a carte — the menu itself, set as type, at size. In a region where guests arrive knowing what they want to eat and needing to know what you have to drink with it, leading with the card is the confident move.

Everything on the home page, named

Nine blocks, split between the kitchen and the cellar:

• Hero — Big opening image, name & buttons, in the Carte treatment: A printed menu card laid over a darkened room.
• Pull quote — A large standout quotation.
• Menu preview — A few dishes on a sliding rail.
• Sourcing — The growers and makers behind the menu.
• Numbers — Headline stats.
• Press bar — Press mentions or awards as a ruled band.
• Gallery — Grid, masonry or moving strip.
• Reservation form — Live availability slot picker, saved to your Inbox.
• Call to action — Headline + button band.

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 — sections listed, then opened in turn — is right for a regional menu organised traditionally, where the guest already knows the structure and is scanning within it.

The description line carries the producer, the valley and the age, which in wine country is exactly the specificity guests search for. All of it is real text rather than a PDF, so a search for a producer can land on your 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.

Ordering that works like the apps — without the commission

This is the part worth pressing. Casa Nebbiolo 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. The photo-tile ordering layout works here because what is sold online is usually wine and pantry goods, where the bottle is the picture and the label does the selling.

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

The form adapts to the mode. Eating in? A table number. Collecting? A phone number. Delivery? An address. Nothing more is demanded.

Story, visit, and the practical pages

The story page carries the region, the family and the cellar — narrative, sourcing, interview, timeline. The gallery page holds the vineyard and room photography, and the visit page explains a rural location and its seasons.

Send a photograph, get a structured menu

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 Casa NebbioloThe whole thing is duplicated into your account to edit.
   1 min
2. Change the name and the wordsClick a block, change the words, swap the picture.
   4 min
3. Upload your menuPhotograph the menu; review what the AI read back.
   3 min
4. PublishLive on your address, with reservations working.
   1 min
5. Connect StripeNow you can take deposits on tables and payment on orders — direct to your account.
   1 min

Point your own domain at it

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.

The email after the booking is yours to design

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.

What follows is not a screenshot of an email — it is an email, drawn by the module the booking system calls. Change the style or the colour and it redraws.

What is editable — which is nearly everything

• 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.

The difference between published and discovered

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.

Questions before you start