Sappadu
A restaurant site built as a menu you can actually read — grouped by course, with veg marks, portion sizes and heat levels where the photos usually go.
- Design direction
- Menu-first · dense · scannable
- Typefaces
- Prata · Karla
- Pages included
- 5
- Palette
Design decisions
Each of these came out of researching how this trade actually sells, not from a style preference.
- 01
The menu is the site's centre of gravity — dense rows grouped by course, readable in one pass, with no photo grid burying the food behind taps.
- 02
Veg and non-veg marks are a structural field on every item, matching Indian labelling convention rather than decorating the card.
- 03
Portion size is stated per dish, with half / full / family variants where the kitchen offers them, so a table can order accurately.
- 04
Heat is marked 1 to 3 and the copy commits to it — a 3 is described as genuinely hot rather than hedged.
- 05
Row cards and a dark, warm palette at 0.9 density: built to be read on a phone at the table or on the way over.
Pages included
Every one is a real, working route. Open any of them.
How it’s built
The specifics matter because they determine what the site costs to run, how fast it is, and whether you can move it later.
- Stack
- Next.js 16 App Router, React 19, TypeScript, Tailwind CSS v4
- Rendering
- Fully static export — every route is prerendered HTML, independently crawlable
- JavaScript
- No animation or UI library. Design tokens applied as scoped CSS custom properties
- Accessibility
- Semantic landmarks, labelled controls, visible focus, prefers-reduced-motion honoured
- Hosting
- Deploys to any static host including cPanel shared hosting — no Node runtime required
Suited to
- Restaurants and messes with a large, changing menu
- Cloud kitchens taking orders by phone and WhatsApp
- Kitchens doing function catering alongside daily service
- Anywhere portion size and heat genuinely affect the order
What it doesn’t include
Stated up front rather than discovered later.
- No live table booking or delivery-partner integration. Orders route to WhatsApp and phone, which is how most independent kitchens work.
- FSSAI licence number is required before going live.
- Availability is static sample data; a live deployment needs a simple daily sold-out toggle.
- Built on RootPro's theme engine: 5 routes, with this theme's own palette, typefaces, card anatomy and layout variants.
Want Sappadu for your shop?
Message us on WhatsApp. Tell us what you stock and roughly how many products, and we’ll come back with a timeline and a price.