Nam Fon — a seasonal Thai 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.

Nam Fon is a dark room with an amber accent pitched at the hour before service. Yours might be white tile and morning light, or brass and candles, or something nobody has built yet.

There is no demo video and no sales call. What you see on the right is the actual Theme panel from the builder, wired to the actual site renderer on the left. Press a colour. It will not ask you to register and it will not remember what you did. Go on.

The entire site, page by page

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 seasonal Thai kitchen is doing something that most guests do not associate with Thai food, and the design has to establish that quickly. The opening leads with tonight — the hour, the sitting, what is being cooked — rather than with a generic hero, because seasonality is a claim best made specifically.

The dark ground with an amber accent reads as a room at dusk. It gives the plating photography a warm surround and lets short dish names sit at display size without looking sparse.

The first page, in pieces

Eight blocks, arranged around tonight:

• Hero — Big opening image, name & buttons, in the Sunset Tonight treatment: Sunset time, weather and free terrace tables above the city.
• Marquee strip — Scrolling awards or words.
• Signature dish — One dish, full screen — name, story, price.
• Gallery — Grid, masonry or moving strip.
• Sourcing — The growers and makers behind the menu.
• Pull quote — A large standout quotation.
• Reviews — Guest quotes with stars.
• Reservation form — Live availability slot picker, saved to your Inbox.
• Call to action — Headline + button band.

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 suits a seasonal menu of many short courses: each section a swipeable strip, everything visible without a long scroll, and every dish able to carry the photograph that explains it.

Section subtitles carry the season and the region; descriptions carry the ingredient and the technique. Heat is set per dish rather than assumed, which for a Thai menu is the single most useful piece of structured data on the page.

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.

Take the order yourself

This is the part worth pressing. Nam Fon uses the Classic list ordering layout — the printed-menu look, with dotted leaders running from each dish to its price. The classic priced list is right for a kitchen selling composed plates. It reads like the printed menu, scans quickly, and does not pretend to be something it is not.

The basket behaves properly regardless: quantities, inline options, a total that stays in view, and payment into your own Stripe account with no commission taken by us. Stripe’s standard card-processing fees apply to online payments.

Each mode collects only what it must: a table number for dine-in, a telephone number for collection, an address for delivery.

The rest of the site

The story page is where a seasonal kitchen explains its calendar: narrative, sourcing, interview, timeline and gallery. The events page carries the seasonal dinners and collaborations, each findable long after the announcement.

Photograph the menu. That is the whole job.

Here is the hour you were dreading, deleted. Photograph the card, the board or the takeaway sheet — up to ten pages at a time — and hand it to TableSpark. It is read into proper fields — section, dish, description, price, dietary marks, spice level — rather than pasted in as a lump of text. Then you read it through, correct whatever the lens misread, and save.

It behaves like data, because it is data. From there the same data runs 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.

For the search snippet, a Write with AI button drafts the title and description out of the page itself. It is a draft, not a decision: edit it, then publish.

Ten minutes, then you are open

Nothing here needs to be built, because it already is. The hard parts are finished; the personal parts are not, and only you can do those. Most restaurants go from opening the builder to a published site on their own address inside ten minutes, and the reservation form answers from the moment it publishes. You see it in the inbox, they see a confirmation in theirs, both within seconds.

Add your Stripe account and the same site takes booking deposits and order payments, with the money landing in your account rather than ours. TableSpark takes 0% commission at every plan level. Stripe’s standard card-processing fees apply to online payments. Nothing else is deducted.

1. Pick Nam FonEverything 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

Your name over the door

An address is branding that people type. The TableSpark address gets you live in minutes; your own domain takes over the moment you want it to, with nothing rebuilt.

TableSpark manages the technical side: the certificate, the secure connection, the redirect from the bare domain to the one you chose, and keeping search engines pointed at the right address so the move does not cost you what you have already earned. An existing domain works fine. You get one instruction, not a documentation site.

What lands in the guest’s inbox

What lands in the inbox after a booking is doing more work than most restaurants realise. The confirmation goes out immediately: date and time, party size, the address and phone number, and a link that releases the table if something changes. It also carries the reminder the day before, the deposit receipt and any cancellation.

The design is not a TableSpark email with your name in it — it is your email. Six templates to choose between, then colour, logo, cover image, header style, sign-off wording, links and socials are all yours to set. Hook up the domain and even the sender is you.

The frame below is the real thing: it is drawn by the same renderer the booking system uses, not a picture of one. Press a style or a colour and watch it change.

The line between the design and your restaurant

• Yours from the first minute: the name over the door, all the words, every photograph, the menu, the prices, your hours and address, and the whole palette and type system.
• Kept for you: the mechanics — how a very long menu paginates, how ordering behaves on a phone, how every block reflows, and how text stays readable against any background you pick.
• Never locked: reorder or delete any section, add any module, and add or remove pages. The template is where you begin, not where you must stay.

What it takes to actually be found

Any tool can put a page on the internet. Fewer can make sure a search engine understands what is on it. It fails quietly: noindex directives nobody noticed, conflicting canonical URLs, orphan pages, menus buried in PDFs, no structured data about the restaurant, and search verification that was never completed. The bill arrives as dependence — guests looking for your kitchen land on a directory or a marketplace that charges you for the introduction.

This is packaged into the site rather than sold separately. There is no promise of a position or of being indexed, because nobody can make one. There is a promise that you will not be hiring someone to fix the basics.

The questions we get asked