Photo menu, reservation form, location, WhatsApp ordering — every restaurant website Vibecoding scaffolds ships with the things diners actually use, not the marketing fluff your old web designer added.
Breakfast, lunch, drinks, specials — each section editable from the admin. Upload photos, set prices, mark items as veg / non-veg / chef's special. Out-of-stock toggles instantly.
Tap an item, pre-filled message opens in WhatsApp with name and price. Cuts the friction of forms-and-payments for low-ticket orders. Falls back to a contact form if you don't use WhatsApp Business.
Diners fill date, time, party size. You get a WhatsApp alert with their phone number. Confirm or decline by replying. Saved in the CRM so repeat diners get recognised.
Pin your exact location, with directions button. Hours block beside it — open / closed status updates live based on the schedule you set.
Drag-and-drop image library. Photos of the space, the food, events. Stored on your own Supabase storage bucket — you own the assets.
Embed a feed of your latest 5-star reviews. Auto-refresh weekly. Drives social proof above the fold without you copy-pasting quotes.
Or your own version of it. The closer to a real brief, the better the first build.
“Build me a website for my restaurant Coffee & Co. in Bangalore. I serve breakfast, lunch, and coffee. I want a photo menu split into sections, a reservation form that pings my WhatsApp at +91 98765 43210, and a Google Maps pin to MG Road. Use earthy browns and forest green.”
All editable in chat. Add or remove pages any time.
Yes — every menu item is in your Supabase database. Add, remove, change prices, mark out-of-stock from the admin panel. No deploys, no developer.
Yes. We use the wa.me deep link with the message pre-filled. On desktop it opens WhatsApp Web. On phones it jumps straight into the chat with your number.
For pre-paid orders, we wire Razorpay (India) or Stripe (global) — the customer pays from the menu and you get a confirmation email + WhatsApp alert. For pay-at-counter or pay-on-delivery, the WhatsApp button is usually enough.
Yes — set time-based visibility on each section, or build separate pages (/lunch, /dinner) that share the same item database. Whichever feels right for your operation.
Yes — each location gets its own page with its own menu, hours, and reservation form, but they all share one admin and one CRM. Useful for small chains.