Why a restaurant website needs a menu that actually changes
Most restaurant website templates treat the menu like a static image — a PDF embed or a page you have to rebuild every time a dish changes. Fine-dining menus change constantly: seasonal courses, sourcing swaps, a dish that sells out.
I built Pass — 12 Seats around that problem. The menu is structured as editable course entries (name, ingredients, price, photo) inside Framer's own property controls, so a restaurant owner or their designer can update a dish without touching code. Seven pages total — home, menu, reservations, private dining, chef, journal, visit — with reservation buttons built to connect to Resy, Tock, or OpenTable rather than bundling booking software nobody asked for.
Launching on Product Hunt tomorrow. Curious whether other template builders have run into the same "content that looks static but isn't" problem in other niches — hotels, clinics, anything with a changing price list.

p/many-displays
p/slotify-2
p/runevr
p/google-cloud-platform
p/producthunt
p/airuncode
p/ai-context-flow
p/aperture-7
p/kodlo
p/raycast
p/lasso-11
p/kuc-kuc
p/dino-kids
p/offiai
p/supabase
p/jev
p/murror
p/reso
p/dex-by-exmergo
p/htmldrag
Replies
Be the first to reply
Have a question or a thought to share? Add a comment above to start the conversation.