Feuillage — a French-Japanese 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.

Nothing here is precious. Try it.

Feuillage is warm paper with a vermilion accent used once per screen. 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. None of this is an image. The frame runs the real renderer — the one that publishes live restaurants — so each tab is the actual page and the links go where they say. Press Phone and watch it reflow.

The kitchen behind the layout

A French-Japanese kitchen is doing precision work in both directions, and a design that leans hard into either language misrepresents it. This one stays neutral and warm — paper ground, one vermilion, a wide display face — and lets the plating carry the cultural information.

The opening is an izakaya board, which is a deliberately informal choice for a serious kitchen. It signals a room you can eat in rather than perform in, which for a restaurant of this kind is often the harder message to land.

The home page, section by section

Eight blocks, arranged to look approachable:

• Hero — Big opening image, name & buttons, in the Izakaya treatment: Lantern-lit frontage with the last-order time and counter seats.
• Intro statement — Big opening statement line.
• Menu preview — A few dishes on a sliding rail.
• Signature dish — One dish, full screen — name, story, price.
• Gallery — Grid, masonry or moving strip.
• Image break — Full-width image band with optional caption.
• Reviews — Guest quotes with stars.
• Call to action — Headline + button band.

The statement block currently reads Counter seats, charcoal smoke, and the discipline of doing few things completely. — one line you will rewrite in about four seconds.

The menu page — the most important page you own

This template uses the Rails layout — each section becomes a horizontal strip that swipes on a phone, so twenty dishes take the room of four. The rail layout gives each section a swipeable strip, which suits a menu of many small plates: everything visible, every dish able to carry a photograph, no endless scroll.

Descriptions carry the technique and the provenance in whichever language the guest reads, and the header can offer a second language switch. Both versions are indexable text.

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.

Ordering, on your own terms

This is the part worth pressing. Feuillage 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 are right for small plates: guests order more when they can see, and a grid handles thirty items without becoming a wall.

Options sit as chips on the tile, the basket bar stays pinned with a count and a total, and Payment lands in your own Stripe account and TableSpark takes 0%. Stripe’s standard card-processing fees apply to online payments.

Dine-in wants a table number and nothing else; collection wants a number to ring; delivery wants somewhere to go. No mode asks for the others’ fields.

The story and visit pages

The story page carries the two-discipline narrative, the sourcing and the chef — with an interview, a timeline and a gallery. The events page holds the guest chef nights and wine dinners a room like this runs.

Photograph the menu. That is the whole job.

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. That same menu immediately drives 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.

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 FeuillageEverything copies across — pages, blocks, menu, the lot.
   1 min
2. Change the name and the wordsEvery block is edited in place. Change the name once.
   4 min
3. Upload your menuA photograph of the menu becomes a structured menu.
   3 min
4. PublishLive. The reservation form starts working immediately.
   1 min
5. Connect StripeNow you can take deposits on tables and payment on orders — direct to your account.
   1 min

The address should be yours

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.

What lands in the guest’s inbox

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.

Below is the actual renderer, the one that sends after a confirmed booking. Press any of the styles or colours and it rebuilds in front of you.

The line between the design and your restaurant

• 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