Kresala — a seafood 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.

Kresala is a dark harbour ground with a blue that belongs to cold water rather than a summer sky. Yours might be white tile and morning light, or brass and candles, or something nobody has built yet.

Rather than explain, here is the thing itself: the builder’s Theme controls on one side, the live site on the other, both real. You cannot break it, nothing saves, and no account is required to have a go. Go on.

Every page, as it publishes

6 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 seafood restaurant that grills whole fish has a daily-changing menu and a very specific selling point: this fish, this morning, this boat. The design leads with exactly that — a landed-today board — because it is both the most useful and the most persuasive thing the page can say.

Dark ground, cold blue accent, a wide display face for the fish names. Photography of whole turbot over embers needs a dark page to sit on, and this one is built to disappear behind it.

Everything on the home page, named

Eight blocks, arranged around the day’s catch:

• Hero — Big opening image, name & buttons, in the Landed Today treatment: Oysters by origin and price beside the counter.
• Intro statement — Big opening statement line.
• Feature rows — Alternating image and text rows.
• Menu preview — A few dishes on a sliding rail.
• Ambience — Full-width video or photo mood band.
• Press bar — Press mentions or awards as a ruled band.
• Reviews — Guest quotes with stars.
• Newsletter — Email signup band.
• Call to action — Headline + button band.

The statement block currently reads The boat list is the menu — what landed this morning is what the coals get tonight. — one line you will rewrite in about four seconds.

The menu page, and why it is text

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 catch list that is short, photographic and changes daily. A guest sees today’s fish as a row rather than a scroll.

Weight and market price are the two hard problems on a seafood menu, and portion groups solve both: a whole turbot carries its sizes as chips, each priced, and the price is edited between services when the market moves. Sold-out marks a fish gone at eight o’clock as gone.

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.

Ordering: a delivery app that belongs to you

This is the part worth pressing. Kresala uses the Minimal ordering layout — a clean typographic list with nothing between the guest and the order. Ordering is minimal here — a clean typographic list — because a harbour restaurant’s online sales are usually a short list of prepared items rather than the grill menu itself.

Sizes and preferences are inline choices, the total stays visible, and collection asks only for a name and a number. Payment lands in your own Stripe account at 0% commission from us. Stripe’s standard card-processing fees apply to online payments.

What the guest is asked depends on how they are eating: table number, phone number or address, and never all three.

Story, visit, and the practical pages

The story page carries the boats, the grill and the family — narrative, sourcing, interview, timeline, gallery. The events page handles the seasonal dinners, and the visit page explains a harbour location that a map pin alone cannot.

You will not be retyping the menu

This is the part that saves an afternoon. Take a picture of the menu you already have: the pressed card, the board behind the pass, a PDF from the printer. Back comes the whole menu as data: ordered sections, named dishes, their descriptions and prices, plus dietary and spice marks wherever the card showed them. Check it over — a smudged price or an ambitious accent is a two-second fix — and save.

What arrives is not a picture of a menu — it is real data. One menu then feeds 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 search copy gets the same treatment: a Write with AI button reads the page and drafts its title and description, so those fields are never blank. Nothing is published on your behalf; the draft waits for you.

From nothing to taking reservations, in ten minutes

There is no build phase to wait through. Structure, styling and behaviour are done. Names, dishes and pictures are yours. Reckon on ten minutes to a published site, and reservations working from that same moment. Bookings land in your TableSpark inbox, and the guest gets a confirmation email straight away.

Taking money is a single connection: link Stripe and deposits on tables and payment on orders go straight to your own account. There is no cut for us — 0% commission on every plan. Stripe’s standard card-processing fees apply to online payments. Nobody else charges anything.

1. Pick KresalaThe whole thing is duplicated into your account to edit.
   1 min
2. Change the name and the wordsClick a block, change the words, swap the picture.
   4 min
3. Upload your menuPhotograph the menu; review what the AI read back.
   3 min
4. PublishLive on your address, with reservations working.
   1 min
5. Connect StripeNow you can take deposits on tables and payment on orders — direct to your account.
   1 min

Point your own domain at it

A domain is signage, and signage matters. Nothing about going live depends on owning a domain first; connect yours later and the site simply answers to it.

The plumbing is ours: certificate, secure connection, redirect, and keeping canonical URLs, sitemap and robots pointing at the live address as the domain changes. Own it already? Good. The instruction is a single record, spelled out.

The email after the booking is yours to design

A confirmed booking is not the end of the conversation; it is the start of one. A confirmation is sent the second the booking lands, carrying the time, the covers, your address and contact details, and a self-service cancellation link. The same system sends the reminder before service, the deposit receipt and the cancellation notice.

The whole thing is yours to set, down to the sign-off. Six looks, one accent colour, your logo and cover photograph, the header layout, the sign-off line, and whichever links and social accounts you want on it. Add your domain and the from-line is yours too — the last detail that separates a real restaurant email from a system notification.

What follows is not a screenshot of an email — it is an email, drawn by the module the booking system calls. Change the style or the colour and it redraws.

What you control

• Yours from the first minute: names, headings, body copy, pictures, dishes, prices, opening times, the address, and every colour and typeface.
• Kept for you: everything that has to keep working at 200 dishes, at 390 pixels wide, and after you have changed every colour in the theme.
• Never locked: change the order of anything, remove whatever you do not want, add modules from the full library, and add or delete pages at will.

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 misconfigured robots file, a noindex left in place, canonical tags in conflict, pages with no internal links, a PDF menu, missing Restaurant schema or incomplete verification — any one is enough to keep a live site invisible. You feel it in the margin — guests reach commission-charging platforms first, and demand you should own outright becomes demand you rent.

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