Ananta — a progressive Indian 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.

Do not read this bit. Touch it.

Ananta is warm paper with an amber that belongs to a late kitchen rather than a spice-jar photograph. Yours might be white tile and morning light, or brass and candles, or something nobody has built yet.

Skip the description. The panel is lifted straight out of the builder and the frame is the real renderer, so what happens when you press an accent here is exactly what happens in your account. Nothing you do is saved or asked about. Go on.

The entire site, page by page

6 pages, and every one of them is here. Everything below is rendered, not photographed. The frame uses the same engine as a published site, so the tabs and the in-page links are all real. Phone shows the mobile layout.

The room it imagines

Progressive Indian cooking is routinely undersold by its own websites, which reach for the same marigolds and paisley regardless of what is on the plate. This template starts somewhere else: a late-night opening that leads on hours and energy, a warm paper ground, and an amber accent that reads as light rather than turmeric.

The structure assumes a kitchen that does two things at once — a long tasting sequence for the dining room, and a shorter à la carte for people arriving after work. Both fit, because the menu layout can hold many short sections without collapsing.

The first page, in pieces

Eight blocks, built for a room with two personalities:

• Hero — Big opening image, name & buttons, in the Late Night treatment: Vignetted room, open-until time and the seats still free.
• Intro statement — Big opening statement line.
• Menu preview — A few dishes on a sliding rail.
• Signature dish — One dish, full screen — name, story, price.
• Gallery — Grid, masonry or moving strip.
• Image break — Full-width image band with optional caption.
• Reviews — Guest quotes with stars.
• Call to action — Headline + button band.

The statement block currently reads Spices ground this morning, tandoors that never quite cool down. — one line you will rewrite in about four seconds.

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

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 menu runs on rails: each section becomes a horizontal strip of dishes that swipes on a phone and scrolls on a desktop. For a kitchen with a great many short courses that layout is a gift — twenty items occupy the vertical space of four, and the guest can still see everything.

It also flatters the food. Progressive Indian plating is photogenic in a way a printed list cannot convey, and the rail format gives every dish an image without turning the page into a two-metre scroll. Spice levels and dietary marks sit on the card itself, which matters for a cuisine where guests ask about heat before anything else.

Whatever the arrangement, the menu is text and not a picture — every dish, description and price indexable, with Restaurant schema around it.

Ordering, on your own terms

This is the part worth pressing. Ananta 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. Ordering is presented as dense rows — the layout that works when a basket is likely to hold eight or nine small items rather than two large ones. Each row is compact enough that a full order stays on one or two screens, with the running total pinned in view.

Heat is the modifier that matters here, and it belongs on the row: mild, medium or as the kitchen sends it, chosen with a tap. Collection and delivery both ask only for what they need, and dine-in asks for a table number, which is how a busy room keeps orders straight.

Each mode collects only what it must: a table number for dine-in, a telephone number for collection, an address for delivery.

The story and visit pages

The story page carries the chef narrative, an interview and a gallery, and the events page is doing real work in a template like this — kitchens of this kind run guest chef nights, tasting collaborations and private dining, and each needs a page that can be found and booked rather than announced on social media and lost.

Photograph the menu. That is the whole job.

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. That same menu immediately 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 AnantaThe whole 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

Your domain, our plumbing

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.

Where the template ends and you begin

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

The questions we get asked