Problem
A restaurant's menu is usually published as a PDF or a photograph of a printed card. It is unreadable on a phone, invisible to a search engine, and out of date within a season, because updating it means exporting and uploading a new file. Hours and location drift across whichever listings were edited most recently.
Our role
Design and build: the content structure, the pages, and the metadata.
Approach
The menu is content, not an attachment: sections and items with their own records, rendered as pages that can be read, searched, and linked to. TanStack Start handles routing and rendering, with React and TypeScript above Supabase.
Metadata and structured data are treated as part of the build rather than an afterthought, so the business and its menu can be described to search engines in a form they understand. A change to a dish is an edit, not a new file, which is the difference between a menu that stays accurate and one that does not.
Outcome
The site is built around structured menu content with search-oriented metadata. Whether the details currently presented are the restaurant's real menu, hours, and status is not something this page asserts.
Notes
No business details, prices, or menu data are reproduced here, and ordering is not part of what this project claims to do.