Maré Alta — a Brazilian 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.

This is yours already. Prove it.

Maré Alta is a bright warm paper with a lime accent, the palette of a market in the morning. 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. What follows is the site itself rather than pictures of it. The same engine that publishes a live restaurant is drawing it here, links and all. The Phone toggle shows the small-screen version.

Who this was drawn for

Contemporary Brazilian cooking is largely about produce and proximity — a garden, a market, a coast — and the design leans light rather than dark to say so. A pale warm ground makes vegetable photography look alive in a way a near-black page never will.

The opening is a plat du jour: today’s dish, the hours, the way in. For a kitchen whose menu is decided by what arrived that morning, it is the only hero that stays true.

Everything on the home page, named

Nine blocks, arranged for a menu decided that morning:

• Hero — Big opening image, name & buttons, in the Plat du jour treatment: Today's three dishes on a surface panel beside the photograph.
• Signature dish — One dish, full screen — name, story, price.
• Marquee strip — Scrolling awards or words.
• FAQ — Accordion of questions.
• Gallery — Grid, masonry or moving strip.
• Numbers — Headline stats.
• Reviews — Guest quotes with stars.
• Call to action — Headline + button band.

How the menu is set, and why it matters twice

This template uses the Compact layout — a tight priced list with no photography — the density a menu of composed plates actually wants. A compact list is right for a short daily menu — the whole offering visible at once, edited in a couple of minutes, with no photographs that will be wrong by Thursday.

The section subtitle carries the day and the market; descriptions carry the grower and the variety. Because it is text rather than an image, guests searching for an ingredient or a producer can arrive on your menu page directly.

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. Maré Alta 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, assembled together, with the total in view throughout.

Options and sizes are inline chips on each row, and the basket becomes a pinned bar on a phone. Payment goes to your own Stripe account with 0% taken by 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.

The pages behind the menu

The story page carries the garden and the market — narrative, sourcing with named growers, an interview, a timeline and a gallery. The reservations page manages a small room where every cover counts.

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

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.

From nothing to taking reservations, in ten minutes

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 Maré AltaThe 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

Moving it onto 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.

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

Questions before you start