Terra — a seasonal kitchen

A restaurant that takes its own reservations. Six tables, split lunch and dinner services, and a menu that changes without anybody editing a page.
The businessRestaurant
They arrive asking"Can I get a table on Saturday?"
Switched onTable reservations · Menu in the CMS · Private-dining form
Needs the planBusiness

A visitor arriving at a restaurant site is asking one question, and it is not what the chef trained in. Terra answers it in the first screen and then earns the rest of the attention afterwards.

The six tables are real booking resources with combination rules, so two twos become a four when a four asks. Lunch and dinner are separate services with separate hours. The menu is a content type grouped by course — the kitchen edits Thursday's dish, and the page it appears on is never touched.

terra-kitchen shown at its home page

What you would change: the photographs, the dishes, the number of tables and the hours. What you would not: any of the arithmetic underneath it.

Open this one in the editor

A designer holding a fabric sample up to the light against a wall of drawings in a studio

Every one of these was somebody’s Tuesday afternoon.

Twelve starting points
True of all twelve

You are copying a site, not a wireframe.

Whichever one you pick, it lands in your account with its pages, its brand tokens, its content and every module the design depends on already configured. Nothing is shared with the original — change the prices on day one and no other site moves.

Pages, navigation, footer and 404Colours, typefaces and spacing as tokensBookings, products, forms and content entriesYours to export, or to hand to a client

Change the words.
Keep the machinery.

Or start from an empty page and build it yourself — by hand, or by describing it to an agent.

A working site the same afternoonSwap starting points before you publishCancel and take the site with you