CMS Architecture for Events Companies

Why events companies need structured content

Events websites juggle a lot of moving parts: speakers confirm late, schedules shift, sponsors have logo requirements, and venues change. A structured CMS lets you update one piece — say, a speaker's bio — and have it cascade to every page where that speaker appears.

Recommended collections

Events

The top-level collection representing each event (conference, workshop, gala, webinar):

• Name (PlainText, required) — event title, e.g., "DesignOps Summit 2025".
• Slug (PlainText) — URL-friendly identifier.
• Description (RichText) — full event overview with agenda highlights and logistics.
• Short description (PlainText) — for cards and social sharing. Help text: "2-3 sentences summarizing the event."
• Featured image (Image, required) — hero image and social card.
• Start date (DateTime, required) — event start date and time.
• End date (DateTime, required) — event end date and time. Help text: "For single-day events, set this to the same day as start date."
• Venue (Reference) — link to the Venues collection.
• Event type (Option) — conference, workshop, webinar, gala, meetup, hackathon.
• Registration URL (Link) — external ticketing or registration page. Help text: "Link to Eventbrite, Luma, or your registration platform."
• Registration deadline (DateTime) — early bird or final cutoff.
• Price (PlainText) — ticket price or range, e.g., "$99 - $499" or "Free".
• Status (Option) — upcoming, live, completed, cancelled.
• Speakers (MultiReference) — link to Speakers collection.
• Sponsors (MultiReference) — link to Sponsors collection.
• Featured (Switch) — pin to homepage or events landing page.
• Recap video URL (Link) — post-event video link.
• Recap body (RichText) — post-event writeup.

Speakers

People presenting at your events:

• Name (PlainText, required) — full name, used as the primary field.
• Photo (Image, required) — professional headshot.
• Title (PlainText) — job title, e.g., "VP of Design".
• Company (PlainText) — employer or organization.
• Bio (RichText) — speaker biography.
• Topic (PlainText) — primary speaking topic or talk title.
• LinkedIn (Link) — profile link.
• Twitter (Link) — profile link.
• Website (Link) — personal or company site.
• Keynote (Switch) — flag keynote speakers for special treatment in the design. Help text: "Keynote speakers are displayed prominently."

Venues

Where events take place:

• Name (PlainText, required) — venue name, e.g., "Moscone Center".
• Address (PlainText, required)
• City (PlainText)
• Description (RichText) — directions, parking, transit info.
• Photo (Image) — venue exterior or interior.
• Capacity (Number) — maximum attendees.
• Website (Link)
• Map coordinates (PlainText) — latitude/longitude for embedded maps.

Sponsors

Organizations sponsoring your events:

• Name (PlainText, required)
• Logo (Image, required)
• Tier (Option) — platinum, gold, silver, bronze, community. Help text: "Sponsor tier determines logo size and placement."
• Website (Link)
• Description (PlainText) — one-line sponsor summary.
• Order (Number) — display order within their tier.

Event Photos

Post-event gallery, structured as a companion collection:

• Event (Reference, required) — link back to the event.
• Image (Image, required)
• Caption (PlainText)
• Photographer credit (PlainText)
• Order (Number) — gallery sort order.

Schedule / Sessions

A companion collection for detailed event agendas:

• Event (Reference, required) — link back to the parent event.
• Title (PlainText, required) — session title, e.g., "Opening Keynote" or "Lunch Break".
• Start time (DateTime, required) — session start.
• End time (DateTime, required) — session end.
• Speaker (Reference) — link to Speakers (null for breaks/lunch).
• Room (PlainText) — room name or number.
• Track (Option) — design, engineering, leadership, general.
• Description (PlainText) — session abstract.
• Session type (Option) — keynote, talk, panel, workshop, break, networking.
• Order (Number) — fallback sort order.

Key relationships

• Events -> Speakers (multi-reference) — each event features multiple speakers.
• Events -> Venue (single reference) — each event takes place at one venue.
• Events -> Sponsors (multi-reference) — each event has multiple sponsors.
• Events -> Sessions (companion collection) — sessions reference back to the event, enabling detailed schedules.
• Events -> Event Photos (companion collection) — post-event galleries.
• Sessions -> Speaker (single reference) — each session has one primary speaker.

Handling recurring events

If you run the same event annually (e.g., "DesignOps Summit 2024" and "DesignOps Summit 2025"), create separate items for each year. Include the year in the title. This keeps past events as an archive and lets you link to recaps, photos, and speakers from previous years.

For truly recurring small events (weekly meetups), consider a "Series" field (Option or Reference) to group them, and archive items older than 90 days to keep your CMS manageable.

Tips for events CMS

1. Date ranges, not single dates — always use separate Start date and End date DateTime fields. Multi-day events and same-day events both work with this pattern. See Date Fields.
2. Registration links are external — use a Link field, not a built-in form. Most events use Eventbrite, Luma, or Tito. See Link Fields.
3. Sponsors need tiers — an Option field for tier (platinum, gold, silver) lets you size logos differently in the design.
4. Past events are content — do not delete completed events. Add recap text, videos, and photos after the event to build an archive that demonstrates your track record.
5. Sessions need their own collection — do not try to put a full schedule inside a RichText field on the event. A companion Sessions collection enables filtering by track, speaker, and time.