A-RICE — Restaurant Website

A single-location restaurant needed a site that could be updated by the people who run the kitchen, on a budget that did not include a monthly platform fee or a developer on call.

The obvious answer is a page builder, and the obvious answer fails slowly: the subscription outlives the enthusiasm, the template dates itself, and the menu drifts out of sync with what is actually being cooked because updating it is somebody's least favourite task.

The real constraint was the ordering flow. A contact form needs a backend, an inbox and somebody who checks it. A restaurant on a lunch rush checks WhatsApp.

Every route prerenders at build time, so there is no server, no database and nothing to keep patched. The build output is a folder.

All copy, menu data, pricing and photos live in plain TypeScript files under content/ — no CMS, no login. Editing a price is editing a line and the change ships on the next deploy.

Every call-to-action opens WhatsApp with the message already written, resolved through one helper so the number exists in exactly one place. There is no form, no inbox and nothing to miss.

Blog posts are MDX files dropped into a folder. Adding one requires no registration step — the post is picked up because the file is there.

A six-route site — home, menu, about, catering, gallery, contact — plus a blog, all prerendered, deployable as static output with no running infrastructure behind it.

Live at a-rice.in.