Doctor pages the clinic can edit. Appointments that know the doctor.
A clinic website is a page with many items for doctors, detail URLs for each profile, and forms that tag the lead with that doctor. Your frontend owns the design; mywebcms owns the words, specialties and timings.
List. One Doctors page. Every profile is an item with the same fields — name, specialty, days, fee — and its own slug.
Without a doctors model
Every profile, a separate mess.
Hard-coded doctor pages, timings in a sheet that never matches the site, and enquiry forms that forget which doctor someone opened.
Copy-paste per doctor
Details rewritten by hand on every doctor page. One update means a deploy — or many manual edits.MehtaRaoIyerNo shared schema
Each doctor page drifts: different field names, missing media, filters the list page can't use.InconsistentLeads without a profile
Contact forms dump into one inbox. Nobody knows which doctor to follow up on.Which doctor?Booking tool bolted on
A third-party form or sheet for appointments while the CMS holds yesterday's timings. Two sources of truth.Two tools
One schema for every doctor
A page with many items — each item is a doctor.
Create a Doctors page once. Define fields (name, specialty, days, fee, photo). Every new profile is an item with its own slug, not a new site or a duplicated page.See how pages with many items work
Same fields everywhere
Name, specialty, days, fee, featured — optional fields cover differences. No per-doctor schema drift.specialtydaysfeeDirectory from the list API
GET the page slug for every visible doctor. Your cards read JSON — never hard-coded doctors.GET /v1/pages/doctorsFilter and sort
Mark specialty or featured as filters; sort by fee. Configured on the schema — not custom code per site.specialty=sort=feeAdd a doctor in admin
New profile = new item. Fill the fields, Release, and the list API includes it. No deploy for content.+ New item
A page for every doctor
Each profile gets its own address and sections.
The item template defines Hero, Bio, Timings and Enquiry once. Every doctor fills their own values. Rename a slug and the old one stays as a redirect.See how Releases ship changes
Stable detail URLs
Your site routes /doctors/dr-mehta. The API is GET /v1/pages/doctors/dr-mehta with every field./doctors/<slug>Item sections
Hero, bio, timings, FAQ — the same section kinds as any page, scoped to the item. Design stays in your frontend.HeroBioEnquiryForm on the doctor
A form section on the item template shows the same form on every doctor page, with the item recorded on the lead.form · itemSlugSlug redirects
Rename a doctor URL and the old slug answers with the new one. Bookmarks and ads don't break.Old → new
Leads that know the doctor
Every appointment request is tagged with its doctor.
Forms on item pages send the item with the submission. Filter leads by doctor, assign an owner, and export without guessing who they meant.See how forms and leads work
- Neha S.Dr. MehtaAppointment requestNew
- Omar K.Dr. RaoAppointment requestContacted
- Priya R.Dr. IyerCallbackNew
Item on the lead
pagePath and itemSlug travel in the form context. Admin shows which doctor the visitor was on.itemSlug: dr-mehtaFilter by doctor
Work one doctor's queue separately from another's. Same statuses and owners as any other lead.MehtaRaoOne inbox, many doctors
Still one website's Forms & Leads — not a CRM per doctor. Access stays per module for the team.One websiteExport the filter
CSV of the current doctor filter or selection. WhatsApp and CRM delivery aren't built yet..csv
Who updates the timings
The clinic edits. Design stays locked.
Give an editor Content access — they change timings and fees 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 doctor
Items check out independently. Updating Dr. Mehta never locks Dr. Rao.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 doctors; Leads Viewer for enquiries; Developer settings nowhere in sight.ContentLeadsSame platform, doctors schema
Nothing is hardcoded for clinics. Travel and hotels use the same building blocks with different fields.Configurable
FAQ
Questions about clinic sites.
Doctors as items, appointment enquiries, EMR tools, and who edits timings.
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.