Without a menu model
Prices in three places, none of them right.
Hard-coded menu pages, a PDF that never matches the site, and booking forms that forget which dish or table someone meant.
Copy-paste per dish
Details rewritten by hand on every dish page. One update means a deploy — or many manual edits.TikkaDalLassiNo shared schema
Each dish page drifts: different field names, missing media, filters the list page can't use.InconsistentLeads without a menu item
Contact forms dump into one inbox. Nobody knows which dish to follow up on.Which dish?Booking widget bolted on
A third-party form or sheet for tables while the CMS holds yesterday's prices. Two sources of truth.Two tools
One schema for the menu
A page with many items — when dishes need their own page.
Create a Menu page once if every dish needs a detail URL. For a simple list, a Repeater on a Menu section is enough. Define fields (title, price, category, veg). New dishes are items or repeater rows — not a redeploy.See how pages with many items work
Same fields everywhere
Title, price, category, veg — optional fields cover differences. No per-dish schema drift.pricecategoryvegDirectory from the list API
GET the page slug for every visible dish. Your cards read JSON — never hard-coded dishes.GET /v1/pages/menuFilter and sort
Mark category or veg as filters; sort by price. Configured on the schema — not custom code per site.category=sort=priceAdd a dish in admin
New menu item = new item. Fill the fields, Release, and the list API includes it. No deploy for content.+ New item
A page for every dish (when you need it)
Each dish can get its own address and sections.
Use item pages only when a dish needs its own URL. The template defines Hero, Details and Booking once. Rename a slug and the old one stays as a redirect.See how Releases ship changes
Stable detail URLs
Your site routes /menu/paneer-tikka. The API is GET /v1/pages/menu/paneer-tikka with every field./menu/<slug>Item sections
Hero, details, allergens, booking — the same section kinds as any page, scoped to the item. Design stays in your frontend.HeroDetailsBookingForm on the dish
A form section on the item template shows the same form on every dish page, with the item recorded on the lead.form · itemSlugSlug redirects
Rename a dish URL and the old slug answers with the new one. Bookmarks and ads don't break.Old → new
Leads that know the booking
Every table request can carry its context.
Forms on item pages send the item with the submission. Filter leads by dish or page path, assign an owner, and export without guessing.See how forms and leads work
- Neha S.Paneer tikkaTable bookingNew
- Omar K.Dal makhaniTable bookingContacted
- Priya R.Mango lassiCallbackNew
Item on the lead
pagePath and itemSlug travel in the form context. Admin shows which dish the visitor was on.itemSlug: paneer-tikkaFilter by dish
Work one dish's queue separately from another's. Same statuses and owners as any other lead.TikkaDalOne inbox, many dishes
Still one website's Forms & Leads — not a CRM per dish. Access stays per module for the team.One websiteExport the filter
CSV of the current dish filter or selection. WhatsApp and CRM delivery aren't built yet..csv
Who updates the prices
The restaurant edits. Design stays locked.
Give an editor Content access — they change price and description in Development. A Release (with approval if you want) puts it live. They never touch API keys or the frontend.See how team access works
Edit one dish
Items check out independently. Updating Paneer tikka never locks Dal makhani.Per-item checkoutRelease to publish
Production stays read-only until someone merges. Same flow as any page — not an industry-only publish button.v3v4Access per module
Content Editor for dishes; Leads Viewer for enquiries; Developer settings nowhere in sight.ContentLeadsSame platform, menu schema
Nothing is hardcoded for restaurants. Hotels and clinics use the same building blocks with different fields.Configurable
FAQ
Questions about restaurant sites.
Menus as items or repeaters, bookings, and who edits prices.
Get started
Build your next client site on mywebcms.
Start from a screenshot, give your client one simple place to run it, and ship it on any stack you like.
- Two steps to your first website:
- 1Create your workspace
- 2Add a client website
Everything that comes with mywebcms
Tap any feature to learn more.