Back to Case Files
BNR-CF-09Restaurant · Web·Hospitality·Sousse, Tunisia·2026

Babke

A kebab and plates restaurant in Sousse. The site is in build: a menu the kitchen edits itself, a plate flow that matches how orders are actually assembled, and a direct path from browsing to ordering.

// pre-launch · babke.tn not yet deployed
Signal pending// awaiting capture
Capture queued · BNR-CF-09

BUILD

Status

.TN

Target

FR

Locale

Babke serves kebabs and composed plates in Sousse. The engagement covers the full digital front of house: a menu that reads as well on a phone at the counter as it does on a laptop, a plate builder that mirrors how the kitchen actually assembles an order, and a route from browsing to a placed order that never asks the customer to create an account.

The build follows the same architecture as the rest of our Tunisian hospitality work: a Next.js App Router application in TypeScript, content modelled as typed data so the kitchen can change a price or retire a plate by editing one file, and a French-first interface sized for the local market.

The site is in development and has not been deployed. This record carries a live capture and a link once babke.tn is published.

// challenge

The Challenge

A counter-service kebab house sells speed and consistency, and neither survives a menu PDF. Orders arrive by phone and in person, the plate combinations change with what is prepped, and customers decide in under a minute on a phone. The site has to hold a menu that changes often, make a composed plate legible without a checkout wizard, and stay fast on the mid-range Android hardware that dominates the local market.

// solution

What We Built

A Next.js App Router build in TypeScript with Tailwind, with the menu and plate options modelled as a single typed data module so the kitchen changes one file and the page, the structured data and the order flow all follow. Ordering targets the channel customers already use rather than a card checkout, and the interface is French-first with type sizes and tap targets set for phone use at a counter.

// outcome

The Outcome

The build is in progress against babke.tn. When it ships, Babke will have a menu it can edit itself, a plate flow that matches the kitchen, and a single address to put on its packaging and its Instagram bio.

Engineering log
[01]

Menu as typed data

Every plate, kebab, side and price lives in one typed module, so a change propagates to the page, the structured data and the order flow at once with no CMS to administer.

[02]

Plate configurator

A composed plate is built the way the kitchen assembles it, base then protein then sides then sauces, rather than being flattened into a list of fixed combinations the customer has to decode.

[03]

Account-free ordering

The order path targets the channel customers in Sousse already use, so nobody is asked to register or enter card details to send an order to the counter.

[04]

Phone-first interface

Type scale, tap targets and image weight are set for mid-range Android on a mobile connection, which is the hardware the majority of the local audience actually browses on.

Stack
Framework
Next.jsReactTypeScript
Styling & infra
Tailwind CSSVercel
Launching soon

Site in deployment

Babke is being engineered against babke.tn and will be published there. Tell us what you are building — BreakNRoot ships production software for startups and enterprises worldwide.

Adjacent records
>_ BREAKNROOT//SYSTEM.ONLINE