Kaimar — a Nikkei restaurant website template

Press something. It is your restaurant now.

Kaimar opens as a dark room lit by one clay-red lamp, because that is the kitchen it was drawn for. 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.

Now walk the whole thing

Six pages, and every one of them is here. Nothing below is a screenshot. The frame renders the template 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 see how the same design reflows — particularly on the ordering page, which is the point of this one.

The room this design is for

Nikkei kitchens are counter kitchens. The fish arrives whole, the leche de tigre is mixed to order, and the room runs on the rhythm of people arriving without a booking. The design answers that with a street-counter opening rather than a magazine cover: the hero is a Queue & Takeaway board — hours, the address, tonight’s dish and two actions, set over a photograph of the counter itself. A guest standing outside with a phone gets the four facts they need before the page has finished loading.

That decision runs through everything after it. The palette is a dark room lit by one warm lamp, so photographs of raw fish and charcoal look like they were taken in the restaurant rather than in a studio. The type pairs a wide display face for the shouted words with a plain workhorse for the reading, which is what a menu of forty short dish names actually needs.

The home page, section by section

Six blocks do the work, and each one is a builder module you can reorder, edit or delete:

• Queue & Takeaway hero — the board: opening hours, the street address, tonight’s signature and the two things a hungry reader wants to press.
• Moving strip — dish names travelling across the page under the hero. It costs one line of text and gives the page a pulse.
• Statement — the one sentence that says what the kitchen is: Lima meets Tokyo: soy in the leche de tigre, ají in the tare.
• Overlapping text and photo — the "why here" paragraph with the room photograph pulled under the copy card.
• Signature rail — four dishes with photographs and prices on a sliding strip; it takes as much room as one dish, and swipes on a phone.
• Offer card and moving call to action — the lunch plate, then a marquee CTA that carries the booking button.

The menu page: a printed menu a search engine can read

The menu uses the Editorial layout — each section opens on its signature plate, then the dishes are set as type in two ruled columns, the way a printed card reads. That matters twice over. For the guest, a long menu stops being an endless scroll of cards. For Google, every dish, description and price is real text in the page with Restaurant schema around it, not a PDF or a photograph of a laminated sheet.

Dietary marks (V, VG, GF, DF), a one-to-three chilli spice scale, "Chef’s pick" badges, sold-out lines and size options all come from the menu editor — set a portion group and the price reads From £12 with the sizes as chips underneath. Change a price once, and it changes on the menu page, the signature rail, the ordering page and the structured data at the same time.

Ordering: a delivery app that belongs to you

This is the part worth pressing. Open the frame below, switch to Phone, and add something to the basket.

The ordering page reads like the delivery apps your guests already know — because that is the interaction they have been trained on — except the restaurant keeps the relationship and the money. Your sections run down a rail on the left. Tapping one swaps the dish list beside it without losing your place. Dishes are photo tiles in this template; each has a round add button that grows into a quantity stepper the moment something is in the basket. Required choices — three or six oysters, the portion, the spice level — appear as inline chips on the row, so choosing costs one tap and never opens a modal.

And the basket never leaves the screen. On a phone it is a bar pinned to the bottom with the item count, a running total and Place order; on a laptop it becomes a panel beside the menu that follows the scroll, so a table of four watches the bill build as they choose. Dine-in asks for a table number, collection asks for a phone number, delivery asks for an address — and each one only asks for what it actually needs.

The story and visit pages

The story page opens on a collage hero and runs through the chef, the "why here" paragraph, a pull quote, a three-question interview, a milestone timeline and a masonry gallery — enough structure that a real kitchen has somewhere to put its actual history instead of one thin paragraph. The visit page carries the practicalities: what to know before coming, how to find the door, the contact block, a map, the questions people always ask, and a newsletter sign-up. Reservations get their own page with a booking form that only offers valid dates and times, computed from your service hours.

Upload your menu. The AI does the typing.

This is the part that saves an afternoon. Photograph your menu — the printed card, the chalkboard, the laminated takeaway sheet — and upload it. TableSpark reads it and builds the structured menu for you: sections in the right order, dish names, descriptions, prices, and the dietary and spice marks where it can see them. You review it, fix anything the camera got wrong, and it is done.

What arrives is not a picture of a menu — it is real data. That same menu immediately drives the menu page, the ordering page, the signature rail on the home page and the Restaurant structured data a search engine reads. Change a price once afterwards and all four change together.

The writing gets the same treatment. Each page has a Write with AI button that drafts the search title and description from what is actually on that page, so the pages that decide whether Google shows you are not left empty. Always your last word — the draft appears in the field for you to edit before anything publishes.

Ten minutes to live — and taking bookings

There is no build phase to wait through. The template is already a finished site; the work is making it yours. Most restaurants go from opening the builder to a published site on their own address inside ten minutes, and the reservation form is answering from the moment it publishes — bookings land in your TableSpark inbox, and the guest gets a confirmation email straight away.

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. TableSpark takes 0% commission at every plan level; Stripe’s standard card-processing fees apply, and nothing else does.

1. Pick KaimarThe whole six-page site copies into your account, menu and all.
   1 min
2. Change the name and the wordsClick any block and type. The restaurant name propagates everywhere.
   4 min
3. Upload your menuPhotograph it and let the AI build the sections, dishes and prices.
   3 min
4. PublishYou are live on your address. Bookings work immediately.
   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. You start on a TableSpark address so you can publish today, and you can move the site onto your own domain whenever you are ready — the one on your menus, your napkins and your Google listing.

TableSpark manages the technical side: the certificate, the secure connection, the redirect from the bare domain to the one you chose, and keeping the search engines pointed at the right address so the move does not cost you what you have already earned. Bring a domain you already own, and we will tell you exactly which record to change.

Every booking sends an email — in your colours

A confirmed booking is not the end of the conversation; it is the start of one. The moment a guest books, TableSpark sends them a confirmation on your behalf: the date, the time, the party size, where you are, how to reach you, and a link to release the table if their plans change. Reminders before service, deposit receipts and cancellation notices come from the same place.

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. Connect your domain and it sends from your address too — so what lands in a guest’s inbox looks like it came from the restaurant, because it did.

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.

What you change, and what stays

• 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: add, delete or reorder any section on any page. Add pages. Delete the ones you do not want. The template is the starting line.

Built to be found, not just to be live

Putting a page online is not the same as delivering a restaurant site that search engines can reliably discover and understand. 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. The cost lands on the restaurant — guests searching your name, your menu or your street reach directories and commission-charging marketplaces first, and you end up paying for the traffic you should already own.

This template ships with that work done. No one can promise rankings or guaranteed indexing — but nothing here is left for you to hire a technician to assemble.

Questions before you start