Dhara Studio — a modern Indian tasting menu 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.

Dhara Studio is warm paper with a saffron amber that reads as spice light rather than gold leaf. 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.

Why it looks like this

A studio kitchen serving one menu to twenty covers is closer to a workshop than a restaurant, and the design says so: a single clear proposition on the first screen — one sequence, one price — and no attempt to look like a dining room it is not.

The warm paper ground is a deliberate departure from the near-black that tasting menus default to. Indian plating is colourful, and a pale page lets that colour carry rather than fighting it with a dark surround.

What is on the home page

Eight blocks, arranged around one proposition:

• Hero — Big opening image, name & buttons, in the One Bowl, One Price treatment: Three priced bowls across a ruled sheet above the photo band.
• Announcement — Slim notice bar at the top.
• Signature dish — One dish, full screen — name, story, price.
• Menu preview — A few dishes on a sliding rail.
• Values — Three guiding values.
• Text + image — A paragraph beside a photo.
• Reviews — Guest quotes with stars.
• Call to action — Headline + button band.

The menu page, and why it is text

This template uses the Accordion layout — sections sit collapsed on one screen and open in place, so a long menu never becomes a long scroll. The accordion works well for a long sequence of short courses: named, collapsed, opened only where the guest is curious. Twenty-two courses fit on a screen and a half rather than requiring a minute of scrolling.

The description line is where a modern Indian kitchen does its explaining — the region, the technique, the reinvention. That text is indexable, which matters when guests search for a regional dish name rather than for a restaurant.

Whichever layout you choose, the point is the same: every dish, description and price is real text in the page with Restaurant schema around it, not a PDF and not a photograph of a laminated sheet.

The ordering page: same habit, different economics

This is the part worth pressing. Dhara Studio uses the Dense rows ordering layout — compact rows that keep a large order visible while it is being built, with the running total pinned in view. The dense-row ordering layout suits a retail list — chutneys, spice blends, gift boxes — where the description does more selling than a photograph would.

Quantities and options are inline, the running total stays on screen, and payment goes into your own Stripe account. TableSpark takes 0% at every plan level. 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.

The pages guests read before they come

The story page is written for a chef with a thesis: narrative, quote, interview, timeline and gallery. The events page holds the guest sittings and collaborations, each as a findable page rather than a social post that disappears in a week.

You will not be retyping the menu

The worst job in setting up a restaurant site is typing the menu. You do not have to. Send in the menu you hand to guests — card, board, PDF, ten pages if it runs that long. What returns is not a scan but a structured menu: every section, every dish, every price, with dietary and spice marks read off the page where they were printed. Nothing saves until you have looked at it — every field is editable on the review screen.

And because it is data rather than a photograph, it can do work. 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.

Search titles and descriptions are drafted the same way: press Write with AI and it writes from the page in front of you. You still approve every line of it before it goes anywhere.

Ten minutes to live — and taking bookings

The waiting is the part that has been removed. Consider it a fully fitted kitchen waiting for your knives. Ten minutes to live, and the booking form does not need setting up: it is already answering. The booking appears in your inbox; the guest gets a confirmation before they have put their phone down.

One Stripe connection turns the site into something that collects money: deposits on tables, payment on orders, paid direct. Our commission is 0% at every plan level. Stripe’s standard card-processing fees apply to online payments. That is the only deduction.

1. Pick Dhara StudioThe complete site lands in your account, ready to edit.
   1 min
2. Change the name and the wordsClick, type, replace a photograph. The name updates site-wide.
   4 min
3. Upload your menuUpload a picture of the card; the AI does the sections and prices.
   3 min
4. PublishPublished, on your own address, with the booking form answering.
   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

Nobody prints someone else’s name on their menu, and a web address is no different. You start on a TableSpark address so you can publish today, and move the site onto your own domain whenever you are ready — the one on your menus, your napkins and your Google listing.

You do not touch a certificate or a redirect rule. TableSpark issues and renews the SSL, points the bare domain at your chosen host, and keeps the search signals consistent. If the domain is already yours, nothing needs buying; you are told precisely which DNS record to point where.

The email after the booking is yours to design

Most guests will see this email more often than they see your home page. On booking, an email goes out on your behalf with everything the guest needs — when, how many, where, how to reach you, and a one-click way to give the table back. Reminder emails, deposit receipts and cancellation notices are cut from the same cloth.

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. Once your domain is connected the email leaves from your address as well, not a generic one.

Not a mock-up: the frame runs the actual guest-email renderer. Press a template or an accent and watch it change.

What you change, and what stays

• Yours from the first minute: the restaurant’s name, the copy on every page, the photography, the dishes and prices, the opening hours and address, and the theme itself.
• Kept for you: the load-bearing decisions: long-menu layout, mobile ordering behaviour, responsive stacking, and colour contrast that does not collapse when you change the palette.
• Never locked: restructure any page, delete sections outright, add new modules, and create or remove pages. None of it is locked.

Findable, not merely online

A live link proves the page exists. It does not prove Google can read it. Sites sit at a perfectly good address and never appear in search — because of a leftover noindex, canonicals that disagree, pages nothing links to, a menu trapped in a PDF, absent restaurant schema, or verification never finished. What follows is expensive: searches for your name, your dishes or your street send guests to marketplaces that take a cut of the booking you would have had for free.

None of it is left for you to assemble. Rankings and indexing are Google’s decision and no honest supplier promises either — but the configuration that makes them possible is done.

Questions before you start