Baram — a Korean 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.

Go on — change something.

Baram is a dark room with an ember orange that sits exactly where the grill would. 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.

Open it properly

5 pages, and every one of them is here. Not screenshots. The frame is running the publishing renderer, so the navigation inside it works and every tab is a real page. Switch to Phone to see how it behaves on a handset.

The room it imagines

A Korean dining room with grills at the table has a physical format that a website rarely conveys, so this design opens with it: the grills, the seatings, the way the room works. A guest understands what kind of evening they are booking before they read a word of the menu.

The ground is dark with an ember accent, which flatters both the grill photography and the jang-heavy plating. The serif-and-sans pairing keeps Korean dish names legible at small sizes, which matters on a menu with many short names.

The first page, in pieces

Eight blocks, built around the grill:

• Hero — Big opening image, name & buttons, in the Table Grills treatment: Charcoal photograph with sets and free grills along the base.
• Intro statement — Big opening statement line.
• Feature rows — Alternating image and text rows.
• Menu preview — A few dishes on a sliding rail.
• Press bar — Press mentions or awards as a ruled band.
• Ambience — Full-width video or photo mood band.
• Reviews — Guest quotes with stars.
• Newsletter — Email signup band.
• Call to action — Headline + button band.

The statement block currently reads Fermentation does the slow work; the charcoal grill does the fast part at your table. — one line you will rewrite in about four seconds.

A menu that reads like a card and indexes like a page

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 a signature photograph and lists the rest as type — right for a menu where the grill items need showing and the banchan do not.

The pantry is the argument in a kitchen like this, and the description field carries it: the age of the jang, the ferment, the province. Structured, indexable, and consistent everywhere the menu appears.

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. Baram uses the Delivery app ordering layout — sections run down a rail on the left, the dish list swaps beside them without losing your place, and the basket follows the scroll. The full delivery-app layout is correct for a Korean kitchen with a takeaway trade: a section rail, dishes beside it, and a basket that follows the scroll. It is exactly the interaction guests use on the marketplace apps.

The difference is the economics. There is no commission from TableSpark at any plan level, the order lands in your own inbox, the guest record is yours, and the page sits on your own domain so the next order comes back to you rather than to a platform.

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 pantry and the chef — narrative, sourcing, interview, timeline, gallery. The visit page handles a room where the format needs explaining before arrival.

The menu builds itself from a photograph

Nobody starts a website looking forward to retyping ninety dishes. Point a phone at whatever your menu currently lives on and send it over. The AI turns it into sections, dishes, descriptions and prices, and picks up the dietary marks and heat levels it can see. Read it back, adjust anything the photograph fumbled, and that is the menu built.

A photograph of a menu is decoration; a structured menu is infrastructure. The same structured menu 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.

And the fields nobody enjoys writing — the search title and description — are drafted by a Write with AI button that reads the page first. The AI writes the first version; you decide whether it is the last.

Publish today, take bookings tonight

You are not commissioning a website; you are moving into one. The site works from the first second — it simply has the wrong name on the door. Ten minutes covers it for most kitchens — and the second it is live, the booking form is taking reservations. It lands in the inbox with the party size and the time, and the guest is confirmed by email at once.

Attach your own Stripe account and the site can charge for orders and hold deposits on tables — the funds are yours from the start. We take 0%. Not on the first order, not on the thousandth. Stripe’s standard card-processing fees apply to online payments.

1. Pick BaramAll the pages and the demo menu copy into your account.
   1 min
2. Change the name and the wordsType over anything. The restaurant name updates throughout.
   4 min
3. Upload your menuThe menu is built from a photograph rather than typed.
   3 min
4. PublishPublished — and the booking form answers from that moment.
   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 web address is something guests read aloud, so it should sound like you. You can be live before lunch on a TableSpark address and on your own domain by the weekend, with no rebuild in between.

Everything fiddly about a domain — SSL, renewals, bare-domain redirects, canonical URLs surviving the move — is managed on your behalf. Already own the name? Keep it — you get the exact record to update, in plain English.

What lands in the guest’s inbox

The email that follows a booking is read more carefully than any page on the site. As soon as a table is confirmed, the guest gets an email in your name carrying the date, the time, the number of covers, your address, your phone number and a way to cancel cleanly. Reminders, receipts and cancellations follow the same treatment, so nothing looks bolted on.

It carries your restaurant, not our branding. Pick one of six templates, then set the accent, the logo, a cover image, how the header sits, the sign-off line, your links and your social marks. When your domain is connected the mail is sent from your own address, which is also what keeps it out of a promotions tab.

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.

Yours, ours, and never locked

• Yours from the first minute: every word and every image, the menu and what it costs, the hours you keep, where you are, and the colours and fonts the site is built from.
• Kept for you: the difficult engineering — long-menu behaviour, the basket on a small screen, how blocks stack when the window narrows, and legibility surviving a palette change.
• Never locked: reorder, remove or add any block on any page, add whole pages, and throw away anything you do not need. This is a starting point, not a cage.

Being on the internet is not being in search

Being published and being findable are two different things, and only one of them happens automatically. The usual culprits are mundane: a robots rule nobody removed, two canonicals pointing different ways, orphaned pages, the menu published as a PDF, no structured restaurant data, search verification half done. 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.

All of that is finished before you arrive. Search results are not something anyone can promise you. A correctly configured site is, and that is what this is.

Before you begin