Vesper Table / Independent design study
Vesper Table
A dining room before the dining room.
Live interface preview. Scroll inside to explore, or open the concept above for a full-size view.
- Brief
- Restaurant
- Location concept
- Lower Manhattan, NYC
- Design
- Aubergine, ivory & editorial serif
- Status
- Working front-end demonstration
01 / The brief
Let the atmosphere invite. Let the information answer.
The brief: a small evening restaurant whose personality gets lost between a generic website, a downloaded menu, and an off-brand booking link. Guests need the food, the occasion, and a clear next step.
02 / The response
Slow visual rhythm. Fast practical answers.
Large food photography and generous serif typography establish the room. Dinner and drinks live in the page as readable text. Reservations and private dining are distinct tasks, each with a direct route.
01 / Feature
An actual menu
Dinner and drinks tabs switch between structured menus; no pinch-to-zoom PDF.
02 / Feature
A reservation path
A locally validated party/date/time form demonstrates the handoff without claiming to reserve a real table.
03 / Feature
Private dining
A separate section explains the occasion, group size, and next steps without crowding the main menu.
03 / Infrastructure
A smaller, deliberate stack.
For this type of brief, the presentation can be a small static site, while an existing reservation provider remains the source of truth for availability. The website does not need to own table inventory to express the restaurant’s identity.
What is built in this demonstration
A responsive restaurant page with dinner/drinks switching, anchor navigation, and a reservation demo that returns an explicitly local preview. No requests are transmitted.
The demonstration is static HTML, CSS, and browser JavaScript hosted alongside this portfolio. It needs no database or page-builder runtime to display its pages. The code uses the same shared documentation approach as the other examples.
What production would still require
Connect an approved booking provider, establish real hours and menus, replace illustrative photographs with venue photography, and confirm accessibility and dietary information with the operator.
A client deployment would include owned accounts, access controls, backups, an editing workflow, tested integrations, and a documented handover. A static demo is not a substitute for that operational work.
04 / Cost logic
Remove only what is unnecessary.
A standalone restaurant information site may remove a page-builder subscription while retaining a worthwhile reservation tool. The business case depends on actual website fees, booking fees, and who updates the menu.
A proposal would compare hosting, domain, third-party services, maintenance, and the one-time work before estimating savings.
Read the evaluation method05 / The thread between the work
Different expression.
The same care.
The expressive surface changes, but the structure stays disciplined: one clear primary action, no invented social proof, and content a guest can actually use.
Clear hierarchy. Useful information. Visible boundaries. Technology selected for the job—not imposed on the business.
Discuss something like this