Quillay — a foraging 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.

Take it for a drive.

Quillay is warm paper with a green that belongs to a hillside after rain. Yours might be white tile and morning light, or brass and candles, or something nobody has built yet.

So do not read about it. The panel on the right is the real Theme tab out of the builder, and the frame beside it is the real site — the same renderer that publishes a live restaurant. Nothing is a mock-up, nothing you touch is permanent, and nobody is asking you to sign in first. Go on.

The whole template, not a sample of it

5 pages, and every one of them is here. This is the live site, not a gallery. Every tab renders through the engine that publishes real restaurants, and the links inside it work. Try the Phone view.

Why it looks like this

A foraging kitchen has the hardest menu-maintenance problem in the industry: the ingredient list changes weekly and sometimes daily, and any website built on fixed copy is wrong within a fortnight. This design starts from that reality with a larder opening — what came in this week, and from where.

The palette is warm paper and a hillside green, and the type is a soft serif over a plain sans. It reads as a field notebook rather than a restaurant brochure, which is the correct impression for a kitchen whose menu is a record of a place.

What is on the home page

Eight blocks, arranged around a changing larder:

• Hero — Big opening image, name & buttons, in the This Week’s Larder treatment: Crops and the farms they came from, with distances.
• Pull quote — A large standout quotation.
• Menu preview — A few dishes on a sliding rail.
• Seasonal calendar — What each month or season brings.
• Numbers — Headline stats.
• Gallery — Grid, masonry or moving strip.
• 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.

The menu page, and why it is text

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 with the rest as type, which is the balance a foraging menu needs: photographs of the ingredients that need showing, and type for everything else.

The section subtitle carries the week and the territory; the description carries the species, the altitude and the gatherer. Because the menu is structured data rather than a designed image, rewriting it weekly costs minutes rather than a design job.

The important part survives any layout: dishes, descriptions and prices are indexable text carrying Restaurant structured data, not an image a crawler has to guess at.

The ordering page: same habit, different economics

This is the part worth pressing. Quillay uses the Dense rows ordering layout — compact rows that keep a large order visible while it is being built, with the running total pinned in view. The ordering page runs as dense rows, which suits selling preserves, ferments and pantry goods — a list where the description matters more than a photograph.

Quantities and sizes are inline, the total stays on screen, and Payment goes into your own Stripe account. TableSpark takes no commission on any of it. 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 is where this kind of restaurant lives: a narrative about the territory, a sourcing block naming gatherers and communities, an interview, a timeline and a gallery of the landscape as much as the plate.

Upload your menu. The AI does the typing.

The tedious part comes first, and it is barely a part at all. Upload the menu exactly as it exists today, whether that is a printed card, a photograph of a board or an old PDF. Sections keep their order, dishes keep their descriptions, prices land in the price field, and dietary and spice marks come across where they were legible. You are the proofreader, not the typist.

That structure is the reason the rest of the site works. Everything downstream reads from it: 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.

The title and description a search result shows are drafted for you too, by a Write with AI button that works from the page’s own content. You edit before it ships, every time.

How long this actually takes

Most of the work was done before you arrived. The design, the layouts and the plumbing are all in place; what is missing is your restaurant. From opening the builder to a live site is usually about ten minutes, at which point guests can already book a table. Your inbox catches the booking; an automatic email catches the guest.

The money side is a single step: connect Stripe, and deposits and payments go directly into your account. Nothing is skimmed at any plan level — 0% commission. Stripe’s standard card-processing fees apply to online payments.

1. Pick QuillayThe 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

Run it on your own domain

A restaurant’s address is part of its name. Publishing does not wait for a domain. Start on ours, move to yours — the same site, a different name over the door.

The technical work is ours: issuing and renewing the certificate, securing the connection, redirecting the bare domain, and keeping the search engines aimed at the live address through the change. You can keep the domain you have had for a decade — the change at your registrar is a single record.

The email after the booking is yours to design

Something arrives in their inbox with your name on it. That is worth designing. It arrives at once, with the booking details, your address, your phone number and a link the guest can use to cancel without phoning. Everything after the booking — the reminder, the receipt, the cancellation — comes from here too.

What the guest sees is your identity, not our template. Six templates; your colour; your logo; a cover shot; a left, centred or banded header; your sign-off; your links; your social accounts. Your domain, once connected, becomes the sending address as well as the web address.

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

What you control

• Yours from the first minute: the restaurant name, every line of copy, all photography, the menu and its prices, opening hours, address, and the colours and typefaces in the Theme tab.
• Kept for you: the layout logic — how the menu reads at 200 dishes, how the basket behaves on a phone, how sections stack on a small screen, and how the whole thing stays legible when you switch to a light palette.
• Never locked: move sections, delete them, add new ones from the module library, create pages, remove pages. Nothing here is fixed.

Built to be found, not just to be live

Getting a page online is easy. Getting it discovered, read and understood is the actual work. Live and invisible is a common combination — caused by stray robots directives, canonical conflicts, unlinked pages, PDF menus, missing schema, or verification that stalled halfway. The restaurant ends up buying back its own customers, because the people searching for it are meeting someone else’s page.

You inherit it finished. Nobody can sell you a ranking or guarantee indexing. This sells you the groundwork that makes both possible.

Things worth knowing first