One page per branch. Every enquiry knows which.
Run every location on one website: a page with many items for the list, a detail URL for each branch, and forms that tag the lead with that location. Your frontend owns the map; mywebcms owns the hours, fees and copy.
List. One page with many items. Every branch is an item with its own slug, hours and address — same schema, different values.
Without a locations model
Five branches, five piles of content.
Separate mini-sites, duplicated Word docs, or a spreadsheet of hours that never matches the live pages. Enquiries arrive with no idea which door someone walked toward.
Copy-paste per location
Hours and fees rewritten by hand on every branch page. One update means three (or thirty) edits.AndheriThanePuneNo shared schema
Each location page drifts: different field names, missing addresses, broken filters on the directory.InconsistentLeads without a place
Contact forms dump into one inbox. Nobody knows which branch to call back — or which one is over capacity.Where from?Map and CMS out of sync
The pin map is hard-coded while the CMS holds yesterday's hours. Visitors trust neither.Two sources of truth
One schema for every location
A page with many items — each item is a branch.
Create a Branches page once. Define fields (name, address, hours, fees, city). Every new location is an item with its own slug, not a new website or a duplicated page.See how pages with many items work
Same fields everywhere
Address, hours, phone, fees, city — optional fields cover differences. No per-branch schema drift.hoursfeescityDirectory from the list API
GET the page slug for every visible branch. Your map or list UI reads JSON — never hard-coded pins.GET /v1/pages/branchesFilter and sort
Mark city or open-now style fields as filters; sort by name or fee. Configured on the schema — not custom code per site.city=sort=nameAdd a branch in admin
New location = new item. Fill the fields, Release, and the list API includes it. No deploy for content.+ New item
A page for every location
Each branch gets its own address and sections.
The item template defines Hero, Facilities, Fees and Enquiry once. Every branch fills its own values. Rename a slug and the old one stays as a redirect so shared links keep working.See how Releases ship changes
Stable detail URLs
Your site routes /branches/thane (or whatever you choose). The API is GET /v1/pages/branches/thane with every field./branches/<slug>Item sections
Hero, gallery, timing, FAQ — the same section kinds as any page, scoped to the item. Design stays in your frontend.HeroFeesEnquiryEnquiry on the branch
A form section on the item template shows the same form on every location page, with the item recorded on the lead.form · itemSlugSlug redirects
Rename Thane to thane-west and the old slug answers with the new one. Bookmarks and ads don't break.Old → new
Leads that know the location
Every enquiry is tagged with its branch.
Forms on item pages send the item with the submission. Filter leads by location, assign an owner at that branch, and export without guessing which door they meant.See how forms and leads work
- Neha S.ThaneVisit enquiryNew
- Omar K.AndheriVisit enquiryContacted
- Priya R.PuneCallbackNew
Item on the lead
pagePath and itemSlug travel in the form context. Admin shows which branch the visitor was on.itemSlug: thaneFilter by location
Work Thane's queue separately from Andheri's. Same statuses and owners as any other lead.ThaneAndheriOne inbox, many branches
Still one website's Forms & Leads — not a CRM per location. Access stays per module for the team.One websiteExport the filter
CSV of the current branch filter or selection. WhatsApp and CRM delivery aren't built yet..csv
Who updates the hours
Local teams edit. Design stays locked.
Give a branch manager Editor on Content — they change hours and fees in Development. A Release (with approval if you want) puts it live. They never touch API keys or the map code.See how team access works
Edit one branch
Items check out independently. Updating Thane never locks Andheri.Per-item checkoutRelease to publish
Production stays read-only until someone merges. Staging keywords belong to Releases — same flow as any page.v3v4Access per module
Content Editor for hours; Leads Viewer for that inbox; Developer settings nowhere in sight.ContentLeadsOne website, many locations
Still one tenant — not a CMS login per branch. Isolation is between websites, not between items of the same page.Shared website
FAQ
Questions about branches.
Items vs websites, maps, leads by location, and who edits hours.
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.