A halal Padang restaurant's website, chosen from three complete looks, built for office buyers ordering through WhatsApp.

The owner chose Coklat on 3 November, after four rounds of revisions and a photoshoot.

Preview
Promo · VideoThe look the owner chose, on the owner's own photographs, every action ending in WhatsApp

Project facts

Role
Designer: wireframes, Figma designs, client feedback, copy
Timeline
5 weeks, 1 Oct to 3 Nov 2026
Built with
  • Claude Code
Stack
  • Astro 7
  • Tailwind CSS 4
  • TypeScript
  • three.js
  • Static files
01

Why

Sari Rendang is a rumah makan Padang with two outlets in South Jakarta, halal-certified by BPJPH. It had no website. Its Instagram bio linked a link page, its old business cards printed an address that was never built, and its awnings, flyers, VIP card and posts carried at least nine phone numbers between them. A buyer could not tell which number answered.

The food, the rooms and the service sit above street level, while the old identity used three logo treatments and about six colour stories. The site's job is to be the one source of truth: the dated price list, two outlets with their own WhatsApp lines, the hours, the halal certificate, in Indonesian and English.

Halfway through, the owner's team asked for a site that sells to businesses ("lebih buat b2b"), in a more formal register. The home page now leads with nasi box for offices, then the VIP rooms, then dining in.

The owner had not chosen a look yet, so the site was built three times over: A Coklat on the brown of their logo plate, B Batu on the slate their food is photographed on, C Merah on the red of their Instagram.

The same first screen in Coklat: their logo, "Satu meja, banyak hidangan" and a nasi box button over a spread of dishes
01Coklat takes the brown of their logo plate
The same first screen in Batu: two photographs laid like cards, the nasi box price pinned on
02Batu takes the slate their food is photographed on
The same first screen in Merah: a fish head curry in a ring, like an Instagram story
03Merah sets their Instagram red over charcoal
04 · VideoThree looks share one body of content, and every action ends in WhatsApp
02

How It Works

  1. A first visit opens on batik. Their logo builds on a whole cloth of batik tanah liek, the Minang batik, while the page loads underneath; the cloth draws apart and the logo lands in the hero. Any touch or key ends it, and it never runs past five seconds.
  2. The services, in the buyer's order. Nasi box with its starting price, the VIP rooms, dining in.
  3. The whole menu as text. 145 dishes in 16 categories from the price list of 3 May 2026, tax included, Signature and Pedas marked, with jump links that follow the reading.
  4. An outlet, then WhatsApp. Every reservation or order button asks which outlet first, then opens that outlet's own WhatsApp line with the message written in the visitor's language.
  5. Forms that show what they send. The catering form writes its WhatsApp message beside itself as it fills, so a buyer sees every word before it leaves.

The site speaks Indonesian first, with an English twin under translated addresses at /en/; the language switch keeps the visitor on the same page. Each outlet's card carries its front, its hours, its rooms (small stills from the restaurant's company video), its facilities and a map drawn from OpenStreetMap in the concept's own colours; Google's map loads only when asked for, so no request leaves the site on load. A line of copy never carries a typed price or date: it quotes the price list, and the page fills in the starting price and the list's date itself.

The services as the rows of a printed menu: a gold numeral 01, a photograph of nasi box dishes, 23 options from Rp 27.700 a box, tax included
05Nasi box leads, priced, tax included
The menu's price list with dotted leaders, a category per block and jump links along the top
06All 145 dishes are text, never a picture of a menu
07 · VideoThe batik strip goes to the menu through the site's own transition
08 · VideoThe message builds beside the form as it fills
Two outlet cards, Pondok Indah and Wolter Monginsidi: each front, address, hours, WhatsApp number and facilities
09Each outlet answers on its own line
03

Under the Hood

The site is plain static files, built by Astro, so it runs on the shared hosting the restaurant buys with no server code. Facts live in one place (src/data, checked at build time: 145 dishes, two outlets, a WhatsApp line each) and every line of copy in another, one blueprint per page with Indonesian and English side by side. Each concept is a theme on one token contract, and where it differs, its own home page and menu.

System map: a visitor, plain files on any host, the pages built from src/data, the opening in a worker, WhatsApp on the outlet's line, and no database
10Plain files serve every page, WhatsApp takes every order, and nothing is stored

Life of one catering request:

  1. The form. Eight fields, four of them required: name, WhatsApp number, outlet and need.
  2. Checked. The browser stops a send with a required field empty and focuses it.
  3. Written. The message builds beside the form as it fills, greeting first.
  4. Sent. The icon turns once and a line says "Membuka WhatsApp".
  5. WhatsApp. wa.me opens in a new tab with the outlet's number and the message ready.
  6. Kept nowhere. The page stores nothing; the request lives in the chat.

The opening is the one heavy part, and it is kept off the main thread: three.js draws the cloth inside a Web Worker on an OffscreenCanvas, on a first visit by a capable device only. Everywhere else a CSS layer plays the same cloth, and a test keeps the two in step.

Sitemap: six pages and a 404 in two languages, the header and footer on every page, and the six places the site hands off to
11Seven pages run in two languages, and every outlet keeps its own line
Flows: six paths from arrival to an answer, four of them ending in WhatsApp
12Every path that asks for an outlet ends in WhatsApp
04

How It Was Built

Two weeks, 1 to 14 October 2026, in 20 commits, every one co-authored by Claude Code (Claude Opus 5.5). The project's rules file holds what every session starts from: the brand rule, the writing rules (no em dash, never an invented fact) and the motion rules learned from bugs. The copy, in both languages, was drafted with Claude Code from 2 October and edited in review; the preview went up on Vercel on 12 October.

Decision 01

Three Whole Sites From One Body of Content

Discovery needed three looks the owner could use, not three pictures. The content is written once and each concept is a theme on one set of roles (bg-surface, text-ink, rounded-button), never colours. Cost: the shared pages had to carry three very different looks, and every check runs per concept: 412 contrast pairs.

Decision 02

The Client's Brand, Not a Rebrand

A first design layer followed an earlier rebrand proposal and was thrown away on day one. The palette is sampled from their Instagram and logo plate, and their logo, known only from WhatsApp copies, was remade as a vector. Cost: a logo that stays a remake until the original arrives, and red in the palette, the category's most common colour.

Decision 03

Every Action Ends in WhatsApp, and Says So

The restaurant runs on WhatsApp, one line per outlet. Buttons say what they do ("Pesan nasi box"), ask for the outlet, and open WhatsApp with the message written. Cost: no booking confirmation on the site, and a form that depends on WhatsApp; nothing is stored, so nothing can leak.

Decision 04

Dark, Textured Grounds

After the reviews of 11 October, every ground became dark and textured: suede on the browns, slate on the stone, drawn in code as soft WebP tiles. Cost: contrast proved on every texture's lightest and darkest patch, and a finer grain that aliased into a grid had to go.

Decision 05

Facts Filled From Public Sources, Never Made Up

Facts the owner had not sent were filled from the best public source and recorded: hours from the outlets' Google listings, the halal certificate checked in BPJPH's registry and linked. Cost: a list for the owner to confirm before launch, and copy that says less than it could.

05

Design Details

Motion is native CSS on opacity and transforms, scroll-driven where it follows the scroll, and token-driven per concept: Coklat slow and soft (a base of 320 ms), Batu quick (220 ms), Merah with a damped spring that overshoots by about 5%. Batik answers the pointer in small places: a flower opens under a navigation link, a line of cecek runs under a text link or a dish row, and two corners draw in around a dish card's photograph.

The opening has two layers: a three.js scene inside a worker for a first visit by a capable device, and a cloth drawn in CSS everywhere else, laid out alike and checked by a test. Nothing moves on its own for more than five seconds, and reduced motion keeps the fades and drops the movement; under it the opening rests on its finished frame.

13 · VideoA first visit opens on Minang batik, in 3D off the main thread
14 · VideoEach concept dyes the cloth in its own colours
15 · VideoRendang cooks down as the section rises
16 · VideoBatu moves quickly: the index follows the reading
17 · VideoBatik answers the pointer, and lets go
18 · VideoOn a phone, the menu carries both outlets
Coklat's palette: four tones, each with its roles and values
19Every colour is set by its role, in four tones
Coklat's type: Fraunces for display and body, Jost in spaced capitals for labels
20Two families carry every role on a fluid scale
Coklat's components in their states: buttons, the outlet picker, dish rows, fields, the dropdown, the calendar
21Every component appears in its states, photographed from the live pages
06

The Owner Chose Coklat

4Rounds of revisions with the owner
50Photographs from the owner's shoot
42Dishes with their own picture
12Link-preview posters, per page and language

On 3 November the owner chose Coklat, and the preview now presents only that. Batu and Merah stay in the code. The build ran five weeks in the end, 1 October to 3 November 2026, in 34 commits, every one co-authored by Claude Code (Claude Opus 5.5).

The first screen today: their logo and "Satu meja, banyak hidangan" beside a close photograph of rice, gulai and rendang on one plate
22Coklat today: the plate is from the owner's photoshoot of 3 November
The rounds

Four Rounds With the Owner

The owner's side sent four rounds of changes.

  1. 23 October. The nasi box and nasi bungkus become one entry each on the Menu, GrabFood joins GoFood, and both move to where they are seen.
  2. 28 October. Hemat and Reguler tiers, buffet catering from 50 guests, the outlets as they are now, and no nasi box prices on Events & Catering.
  3. 2 and 3 November. The Menu's bar jumps because of its two columns, the photo above "Kenapa rendang?" should be rendang, and there are more bugs, with no list. The whole site gets audited.
  4. 3 November. Opening hours, four dish descriptions, one Aneka Jus in place of seventeen lines, and the photoshoot: 50 of its 56 photographs go into the site, 42 dishes get their own picture.

The owner chose Coklat the same day and called this the last round before launch.

The Menu in October: two page columns of categories side by side
23Before: two page columns, so the lit link went back and forth
The Menu now: one category to a row, Ayam with its photograph held at the side and its dishes beside it
24After: one order, the jump links keep up
Decision 06

Hide the Two Looks Not Chosen, Keep Them

Batu and Merah left the owner's preview and stayed in the code, at their own addresses, out of search engines. Cost: the contrast check still covers every look, and a change to a shared page can still break one nobody is looking at.

Decision 07

An Audit, Because the Report Had No List

The third round said there were many more bugs without naming them. So the site was walked with real pointer and touch input at the sizes of the screens the owner's team uses: a small Windows monitor and an Android phone. Then every page ran in WebKit and Firefox too, with the newer CSS switched off to stand in for older browsers. Cost: the fixes answer what the audit found, not what they saw, and their list is still to compare. A real iPhone remains untested.

07

What Changed on the Page

  1. The whole menu as text, in one reading order. 145 dishes in 16 categories from the price list of 3 May 2026, tax included, Signature and Pedas marked. Each category holds its name and photo at the side while its dishes pass, and the jump links follow the reading.
  2. Nasi box by tier. One large photo of what comes in a box, then Hemat from Rp 27.700 and Reguler from Rp 42.400, each worked out from the price list.
  3. Forms that show what they send. The catering form writes its WhatsApp message beside itself as it fills, and its first line changes with what the buyer needs: a nasi box order or a buffet.

Each outlet's card carries its front, its hours, its rooms, its facilities, its GoFood and GrabFood links under the apps' own logos, and a map drawn from OpenStreetMap in the site's colours; Google's map loads only when asked for, so no request leaves the site on load.

The services as the rows of a printed menu: a gold numeral 01, the photoshoot's nasi box, 23 options from Rp 27.700 a box, tax included
25Nasi box leads, priced, tax included
The outlet picker open over the first screen: Pondok Indah and Wolter Monginsidi, each with its hours
26Every order button asks for an outlet first
27 · VideoThe menu reads straight down, one category to a row
28 · VideoTwo tiers, each priced from its lowest box
29 · VideoThe batik strip goes to the menu through the site's own transition
30 · VideoThe message builds beside the form as it fills
Two outlet cards, Pondok Indah and Wolter Monginsidi: each front, address, hours, WhatsApp number and facilities
31Each outlet answers on its own line
Catering prasmanan on Events & Catering: its terms in three lines, a button, and a spread of dishes
32Buffet catering came in with the second round
08

The Same Map, in the Chosen Look

Each look is a theme on one token contract, and one setting, selectedConcept, decides which look the site renders; choosing Coklat was a one-line change.

System map: a visitor, plain files on any host, the pages built from src/data in the chosen look, the opening in a worker, WhatsApp on the outlet's line, and no database
33The same map today: the chosen look, the owner's photoshoot, 12 link posters
Sitemap: six pages and a 404 in two languages, the header and footer on every page, and the six places the site hands off to
34The looks not chosen stay at their own addresses, out of search engines
Flows: six paths from arrival to an answer, four of them ending in WhatsApp
35Delivery now takes GoFood or GrabFood, on the same paths
09

The Opening, Rebuilt

The opening was rebuilt on the last day, after the first cloth read as "so rough, not soft like fabric". It now falls from its rail, hangs in long folds that drift, and parts with a curved edge and deepening pleats. The hanging batik on the inner pages went the same way: sixteen sliding strips became one length of cloth bent by a small WebGL shader, swinging from its rail under the pointer.

36 · VideoBefore: the same cloth, stiffer
37 · VideoNow: the cloth falls, hangs and parts like fabric
38 · VideoOne length of cloth, swinging from its rail
39 · VideoThe owner's rendang, then the pot cooking down
40 · Video42 dishes now show their own plate
41 · VideoThe Signature dishes lean toward the hand
42 · VideoOn a phone, the menu carries both outlets
10

One Poster per Page, per Language

Every page sends its own title and description in its own language, with its canonical address, its hreflang pair and a link preview made for that page. The previews are designed, not captured from the page: a script lays each poster out as its own web page and renders it in Chrome, so it uses the site's own fonts and batik. A build needs none of this and no network.

A shared link is often the first thing a buyer sees, so each page in each language has its own poster: their plates crowded across the batik cloth with its border and corner flowers, their logo, and the page's own title from its blueprint, its second line in gold italics. Lokasi lays the outlet photographs on the cloth like prints. The plates are cut from their photographs, and the script finds each plate's white rim itself, so a new photo needs no measuring.

Link preview for the home page: the rendang large among other plates on batik, "Satu meja, banyak hidangan"
43Beranda: rendang first, the dish the restaurant is named after
Link preview for the Menu page: "Menu dan harga" beside fried chicken and other plates on batik
44Menu
Link preview for Lokasi: the two outlet fronts laid like prints on batik
45Lokasi lays the outlets' fronts like prints
Link preview for Events & Catering: "Kami yang memasak, Anda yang menjamu" beside the nasi box photograph on batik
46Events & Catering
Link preview for the home page in English: the same table, "One table, many dishes"
47The English page sends its own
Link preview for Tentang Kami: "Masakan Padang, disiapkan dengan sabar" beside a plate of balado on a banana leaf
48Tentang Kami
Link preview for Kontak: "Ada yang bisa kami bantu?" beside fried chicken and other plates
49Kontak
11

Outcome

145Dishes on the menu, as text
3Complete looks built, one chosen
2Outlets, a WhatsApp line each
100Lighthouse accessibility, every page
99 to 100Lighthouse performance, desktop
0Layout shift on every page
412Contrast pairs passing WCAG AA
173Unit tests passing

The owner chose Coklat and called the fourth round the last before launch. The site runs at its preview address in that look, on the owner's photographs, and waits for its domain and hosting: it is not live yet. Every check the project runs passes: 173 unit tests, 412 contrast pairs, 2,863 internal links and assets in the production build, no em dash in 435 files, and no placeholder left in the content check. On that build, Lighthouse scores accessibility, best practices and SEO at 100 on all 13 pages, desktop performance at 99 to 100 and mobile performance at 86 to 100, with no layout shift on any page.

What it does not have yet: a launch, the owner's original logo file, a test on a real iPhone, and the owner's check of the closing hours and some dish lines.

In October the site was in preview with the owner, three concepts awaiting a choice. The checks then: 161 unit tests, 412 contrast pairs, every internal link in each build, no em dash in 428 files, and on the production builds Lighthouse at 100 for accessibility, best practices and SEO on all 39 pages, desktop performance at 99 to 100, mobile performance at 84 to 99. The link to BPJPH's certificate check was 23 px tall in two concepts, the one control under 24 px.

12

Gallery

The home page on a phone in Coklat: the logo, the headline and the nasi box button
50On a phone, the first screen ends on the nasi box button
The home page on a phone in Batu: the logo and the headline on slate, a red nasi box button
51On a phone, Batu pins the nasi box price to its photographs
The home page on a phone in Merah: the headline in yellow on red, round buttons and shortcuts
52On a phone, Merah adds round shortcuts, like Instagram highlights
Batu's services as a bento: nasi box large with its photograph, the VIP rooms and dining in beside it
53Batu sets the services as a bento
Merah's services in three rings of text around photographs: nasi box, the VIP rooms, dining in
54Merah sets them in rings
Merah's four Signature dishes in circles on red, each with its price on a badge
55Merah prices each Signature dish on a badge
Batu's menu: a price list with an index at the side
56Batu's menu keeps its index at the side
Merah's menu: each category on its own round card
57Merah's menu puts each category on a card
The menu on a phone: a row of category links under the header, then Lauk dan nasi and its first dishes with their prices
58On a phone, the category links stay along the top
Tentang Kami's halal section: Halal, tanpa ragu, the BPJPH certificate number and a link to check it
59The halal certificate links to BPJPH's own check
The 404 page: their logo on a band of batik and the way back
60Even the 404 carries the batik
Batu's palette: four tones, three of slate and one of red, each with its roles and values
61Batu keeps to three slates and a red
Merah's palette: three tones, charcoal, red and near black, each with its roles and values
62Merah works in charcoal and red
The chosen site

Coklat After the Photoshoot

The home page on a phone: the logo, the headline and the nasi box button over the plate
63On a phone, the first screen ends on the nasi box button
A category on a phone: its name first, then its photograph, then its dishes, the jump links along the top
64On a phone, a category opens with its name, then its photo
The nasi box on a phone: the large photograph, then Hemat and Reguler
65The tiers hold on a phone
The phone menu open: the pages, then both outlets with their hours and lines
66The phone menu carries both outlets
The first dishes on slate: Rendang, Ayam Pop Original, Kepala Kakap Gulai and Sate Padang Lidah with their prices
67Four Signature dishes open the food
The rendang photograph as a band across the page
68The third round asked for rendang above Kenapa rendang?
The Menu's first screen: the title, GoFood and GrabFood under their own logos per outlet, and the hanging batik
69Delivery sits at the top of the Menu, per outlet
The form filled for a buffet, with the whole WhatsApp message written beside it
70The whole message, ready before WhatsApp opens
The large nasi box photo beside Aneka Nasi Box and Aneka Nasi Bungkus, each with Hemat and Reguler
71The owner asked for one large photo of what comes in a box

Keep browsing

More AI Engineering

All projects
  • Rigor RoomA landing page for Ravenry's three-day insights masterclass, where every block of evidence builds toward one amber decision.
  • Ravenry × SWDAThe launch page for a Ravenry and SWDA study: the real covers fan open, the findings unfold, and one form hands over both documents.
  • Ravenry Company ProfileRavenry's 44-page company profile, rewritten as one page with its own address: the cover's sun, stair and hand, and 19 case files.