Bayt Ikhwan Bistro — a Middle Eastern 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.

Bayt Ikhwan Bistro is bright warm paper with a violet accent that has nothing traditional about it. 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.

The whole template, not a sample of it

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.

What kind of restaurant this is

A Levantine bistro run by chefs with modern training needs a website that reads neither as a heritage restaurant nor as a fine-dining room. The design lands between them: a bright warm ground, a bold contemporary accent, and a hatch-board opening that shows the kitchen working rather than the room posed.

The type is a wide display face over a plain sans, which lets Arabic and English dish names sit together at similar weight without either looking like a translation of the other.

What is on the home page

Nine blocks, arranged around an open kitchen:

• Hero — Big opening image, name & buttons, in the Hatch Board treatment: Blackboard prices beside the service hatch, sold-out lines struck through.
• Marquee strip — Scrolling awards or words.
• Intro statement — Big opening statement line.
• Image break — Full-width image band with optional caption.
• Menu preview — A few dishes on a sliding rail.
• Offer banner — Time-bounded offer that hides itself when it ends.
• Gallery — Grid, masonry or moving strip.
• Reviews — Guest quotes with stars.
• Call to action — Headline + button band.

The statement block currently reads Mezze until the table disappears, then charcoal until you surrender. — one line you will rewrite in about four seconds.

How the menu is set, and why it matters twice

This template uses the Editorial layout — each section opens on its signature plate, then the dishes are set as type in ruled columns, the way a printed card reads. The editorial layout gives each section its own plate and then sets the dishes as ruled type — right for a mezze menu, where the sections are the structure and the dishes are numerous and short.

The description line carries the pantry: the tahini, the pepper, the ferment. Dietary marks matter a great deal on a menu like this and are set per dish, so a vegetarian guest can read the menu rather than interrogate a waiter.

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. Bayt Ikhwan Bistro uses the Classic list ordering layout — the printed-menu look, with dotted leaders running from each dish to its price. A classic priced list with leaders is right for mezze ordering, where the basket fills with many small items and a photograph of each would slow the process down.

Quantities and options are inline, the running total stays on screen, and collection asks only for a name and a number. Payment settles into your own Stripe account at 0% TableSpark commission. 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 family and the pantry — narrative, sourcing, an interview and a timeline — and the reservations page manages a bistro that fills quickly. The visit page handles the practical detail of a room in a busy district.

Send a photograph, get a structured 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. That single menu is what powers 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 Bayt Ikhwan BistroThe full site arrives in your account as a working draft.
   1 min
2. Change the name and the wordsRewrite the words by clicking them; the name carries everywhere.
   4 min
3. Upload your menuSend the menu in as a photograph and check what comes back.
   3 min
4. PublishIt goes live on your address and starts taking bookings.
   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.

After the booking: an email that looks like you

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 is editable — which is nearly everything

• 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.

Findable, not merely online

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