Events Collection

Overview

Events collections power conference listings, workshop schedules, webinar calendars, and more. The key challenge is handling dates correctly and deciding how much detail each event needs.

Recommended fields

Required

• Title (text) — event name.
• Date (date or datetime) — when the event starts. Use datetime if you need specific times.

Recommended

• Description (rich text) — event details.
• Location (text) — venue name and address, or "Virtual".
• Featured image (image) — for cards and hero sections.
• Event type (select) — conference, workshop, webinar, meetup, social.
• Registration URL (url) — link to Eventbrite, Luma, or a registration form.

Optional

• End date (date or datetime) — for multi-day events.
• Speakers (multi-reference) — link to Speakers or Team Members collection.
• Price (number) — ticket cost. Use 0 for free events.
• Capacity (number) — maximum attendees.
• Status (select) — upcoming, sold out, cancelled, completed.
• Recap (rich text) — post-event summary with photos and takeaways.
• Recording URL (url) — link to recorded session.
• Tags (multi-select) — topics covered.

Date handling

Date vs. datetime

• Use date for all-day events (conferences, holidays).
• Use datetime for events with specific start times (webinars, workshops).

Multi-day events

Add an end date field for events spanning multiple days. Your front end can display "March 15-17" instead of just "March 15".

Recurring events

Do not try to model recurrence in your CMS. Instead:

• Create individual items for each occurrence.
• Use a "Series" select or reference field to group them.
• Filter by series to show all occurrences together.

Speakers and presenters

If events have speakers, you have two options:

Multi-reference to Team Members — when your speakers are internal team members.

Separate Speakers collection — when you have external speakers with different fields (company, talk title, headshot). This is better for conferences.

Past vs. future events

Use the date field to filter, not a boolean "past" field. Your front end should:

• Show future events sorted by date ascending (soonest first).
• Show past events sorted by date descending (most recent first).
• Optionally add a "Recap" rich text field that only appears on past event pages.

Tips

1. Always include a registration URL — even if registration is handled elsewhere, link to it.
2. Status field prevents confusion — "sold out" and "cancelled" are important states that a date field alone cannot express.
3. Event type enables filtering — visitors want to see only workshops, or only webinars.
4. Post-event content is valuable — add recap and recording URL fields so events remain useful after they end.