Event pages your team can edit. Registrations that know the night.
An events website is a page with many items for listings, detail URLs for each event, and forms that tag the lead with that event. Your frontend owns the design; mywebcms owns the words, dates and registration copy. No dedicated SEO cluster yet — claims stay on items and leads.
List. One Events page. Every listing is an item with the same fields — title, date, venue, price — and its own slug.
Without an events model
Every night, a separate mess.
Hard-coded event pages, dates in a sheet that never matches the site, and registration forms that forget which night someone opened.
Copy-paste per event
Details rewritten by hand on every event page. One update means a deploy — or many manual edits.MeetupPitchWorkshopNo shared schema
Each event page drifts: different field names, missing media, filters the list page can't use.InconsistentLeads without a listing
Contact forms dump into one inbox. Nobody knows which event to follow up on.Which event?Ticketing bolted on
A third-party form or sheet for signups while the CMS holds yesterday's dates. Two sources of truth.Two tools
One schema for every event
A page with many items — each item is an event.
Create an Events page once. Define fields (title, date, venue, price, featured). Every new listing 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, date, venue, price, featured — optional fields cover differences. No per-event schema drift.datevenuepriceDirectory from the list API
GET the page slug for every visible event. Your cards read JSON — never hard-coded events.GET /v1/pages/eventsFilter and sort
Mark venue or featured as filters; sort by date. Configured on the schema — not custom code per site.venue=sort=dateAdd a event in admin
New listing = new item. Fill the fields, Release, and the list API includes it. No deploy for content.+ New item
A page for every event
Each listing gets its own address and sections.
The item template defines Hero, Agenda, Speakers and Register once. Every event 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 /events/design-meetup. The API is GET /v1/pages/events/design-meetup with every field./events/<slug>Item sections
Hero, agenda, speakers, FAQ — the same section kinds as any page, scoped to the item. Design stays in your frontend.HeroAgendaRegisterForm on the event
A form section on the item template shows the same form on every event page, with the item recorded on the lead.form · itemSlugSlug redirects
Rename a event URL and the old slug answers with the new one. Bookmarks and ads don't break.Old → new
Leads that know the event
Every registration is tagged with its listing.
Forms on item pages send the item with the submission. Filter leads by event, assign an owner, and export without guessing which night they meant.See how forms and leads work
- Neha S.Design meetupRegistrationNew
- Omar K.Pitch nightRegistrationContacted
- Priya R.Founders workshopCallbackNew
Item on the lead
pagePath and itemSlug travel in the form context. Admin shows which event the visitor was on.itemSlug: design-meetupFilter by event
Work one event's queue separately from another's. Same statuses and owners as any other lead.MeetupPitchOne inbox, many events
Still one website's Forms & Leads — not a CRM per event. Access stays per module for the team.One websiteExport the filter
CSV of the current event filter or selection. WhatsApp and CRM delivery aren't built yet..csv
Who updates the dates
The organisers edit. Design stays locked.
Give an editor Content access — they change date and venue 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 event
Items check out independently. Updating Design meetup never locks Pitch night.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 events; Leads Viewer for enquiries; Developer settings nowhere in sight.ContentLeadsSame platform, events schema
Nothing is hardcoded for events. Travel and clinics use the same building blocks with different fields.Configurable
FAQ
Questions about event sites.
Listings as items, registrations, ticketing tools, and who edits dates.
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.