Milpa Norte — a Mexican restaurant website template UK

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.

This is yours already. Prove it.

Milpa Norte is limewashed paper with an orange that belongs to a market crate in November. Yours might be white tile and morning light, or brass and candles, or something nobody has built yet.

This is the product, not a picture of it. Left, the live site. Right, the builder’s own Theme panel. Everything you press takes effect immediately, nothing persists, and there is no sign-in wall in front of it. Go on.

Now walk the whole thing

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.

Who this was drawn for

A Mexican kitchen in Britain has a specific argument to make — that the technique travels even when the produce cannot — and the website has to make it early. The opening is a week on the road: where the produce came from, what the kitchen did with it, when the room is open.

The palette is limewashed rather than saturated, which is the right register for British light, and the geometric type keeps the page from reaching for folkloric cues that would undercut the argument.

Pulling the home page apart

Nine blocks, arranged around a supply chain:

• Hero — Big opening image, name & buttons, in the Week on the Road treatment: The week of pitches as a ruled timetable beside the name.
• Marquee strip — Scrolling awards or words.
• Intro statement — Big opening statement line.
• Numbers — Headline stats.
• 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 Corn nixtamalised nightly, salsas ground in stone, fire doing the talking. — one line you will rewrite in about four seconds.

The menu page, and why it is text

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 sets the dishes as ruled type — right for a menu where the story of each ingredient matters as much as the dish name.

Descriptions carry the farm, the county and the technique, which is exactly the specificity that makes the argument. Heat is set per dish, and dietary marks travel with it. All of it is structured, indexable text.

Any of the layouts leaves the substance intact: real text for every dish, description and price, marked up as Restaurant data rather than published as an image.

The ordering page: same habit, different economics

This is the part worth pressing. Milpa Norte uses the Roomy rows ordering layout — the basket sits beside the menu rather than beneath it, so a table watches the bill build as they choose. The split layout keeps the basket beside the menu, which suits shared ordering — several plates for a table, built together, with the total visible throughout.

Options are inline chips on each row, and on a phone the basket becomes a pinned bar. Everything settles into your own Stripe account and TableSpark takes 0%. 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 where the supply chain becomes an argument: narrative, a sourcing block naming farms and counties, an interview, a timeline and a gallery. The reservations page handles a room that books out, and the visit page covers a London address that needs explaining.

Upload your menu. The AI does the typing.

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. Everything downstream reads from it: 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 Milpa NorteThe 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.

After the booking: an email that looks like you

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.

Built to be found, not just to be live

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.

Common questions