Restaurant websites have one job: get people to the table. Most bury the menu in a PDF that won't open on a phone, and send reservations to a third-party widget that feels nothing like the restaurant.
The idea
Make the website feel like walking in: warm, editorial and a little moody. Then keep "Reserve a table" one tap away on every screen.
What I designed and built
Editorial hero: "Fire, smoke, and the season on a plate." A serif headline over a dark, ember-toned palette.
A real menu, not a PDF: seasonal sections (small plates, from the fire, desserts) that update from a CMS in minutes.
Two-tap reservations: date, party size, time. The key details (hours, address, private events) sit right beside it.
Private dining capture: a separate enquiry flow for larger groups, often a restaurant's most profitable bookings.
Mobile first: menus and booking designed for someone deciding where to eat on their phone.
Why it matters for a real restaurant
More direct bookings, a menu the team can update without a developer, and a brand that matches the room.
Stack
Next.js, Tailwind, a headless CMS for menus, and reservation integration hooks (e.g. OpenTable/Resy-style embeds or a custom form).