Course pages the institute can edit. Enquiries that know the batch.
A coaching or institute website is a page with many items for courses, detail URLs for each programme, and forms that tag the lead with that course. Your frontend owns the design; mywebcms owns the words, fees and schedules.
List. One Courses page. Every programme is an item with the same fields — title, fees, duration, mode — and its own slug.
Without a courses model
Every programme, a separate mess.
Hard-coded course pages, fees in a sheet that never matches the site, and enquiry forms that forget which programme someone opened.
Copy-paste per course
Details rewritten by hand on every course page. One update means a deploy — or many manual edits.EnglishIELTSDataNo shared schema
Each course page drifts: different field names, missing media, filters the list page can't use.InconsistentLeads without a programme
Contact forms dump into one inbox. Nobody knows which course to follow up on.Which course?Admission form bolted on
A third-party form or sheet for admissions while the CMS holds yesterday's fees. Two sources of truth.Two tools
One schema for every course
A page with many items — each item is a course.
Create a Courses page once. Define fields (title, fees, duration, mode, featured). Every new programme 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
Title, fees, duration, mode, featured — optional fields cover differences. No per-course schema drift.feesdurationmodeDirectory from the list API
GET the page slug for every visible course. Your cards read JSON — never hard-coded courses.GET /v1/pages/coursesFilter and sort
Mark mode or featured as filters; sort by fees. Configured on the schema — not custom code per site.mode=sort=feesAdd a course in admin
New programme = new item. Fill the fields, Release, and the list API includes it. No deploy for content.+ New item
A page for every course
Each programme gets its own address and sections.
The item template defines Hero, Syllabus, Faculty and Enquiry once. Every course fills its own values. Rename a slug and the old one stays as a redirect.See how Releases ship changes
Stable detail URLs
Your site routes /courses/spoken-english. The API is GET /v1/pages/courses/spoken-english with every field./courses/<slug>Item sections
Hero, syllabus, faculty, FAQ — the same section kinds as any page, scoped to the item. Design stays in your frontend.HeroSyllabusEnquiryForm on the course
A form section on the item template shows the same form on every course page, with the item recorded on the lead.form · itemSlugSlug redirects
Rename a course URL and the old slug answers with the new one. Bookmarks and ads don't break.Old → new
Leads that know the course
Every admission enquiry is tagged with its programme.
Forms on item pages send the item with the submission. Filter leads by course, assign an owner, and export without guessing which batch they meant.See how forms and leads work
- Neha S.Spoken EnglishAdmission enquiryNew
- Omar K.IELTS preparationAdmission enquiryContacted
- Priya R.Data scienceCallbackNew
Item on the lead
pagePath and itemSlug travel in the form context. Admin shows which course the visitor was on.itemSlug: spoken-englishFilter by course
Work one course's queue separately from another's. Same statuses and owners as any other lead.EnglishIELTSOne inbox, many courses
Still one website's Forms & Leads — not a CRM per course. Access stays per module for the team.One websiteExport the filter
CSV of the current course filter or selection. WhatsApp and CRM delivery aren't built yet..csv
Who updates the fees
The institute edits. Design stays locked.
Give an editor Content access — they change fees and syllabus 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 course
Items check out independently. Updating Spoken English never locks IELTS.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 courses; Leads Viewer for enquiries; Developer settings nowhere in sight.ContentLeadsSame platform, courses schema
Nothing is hardcoded for institutes. Travel and clinics use the same building blocks with different fields.Configurable
FAQ
Questions about institute sites.
Courses as items, admission enquiries, LMS tools, and who edits fees.
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.