Event Groups and Series
Three ways to group Events that share a brand or a story, and what each one publishes
A series, a group, and a group series are wrappers around Events. They organise what buyers browse; they never sell anything themselves.
A festival with a music night, a workshop day, and a screening needs a group. A conference that returns yearly needs a series.
Three wrappers, one rule
| Wrapper | What it is for | Membership | Public page |
|---|---|---|---|
| EventSeries | Editions of one property over time | Events, in a fixed order | Series page with edition list and totals |
| EventGroup | A branded umbrella for different Events | Events, any order | Portal with its own theme, pages, and subdomain |
| EventGroupSeries | A family of related groups | EventGroups | Index of its groups |
None is ticketable: a wrapper has no Pass, price, or schedule, so buyers always land on an Event.
A wrapper never supplies business defaults to its members. Joining a group copies no currency, venue, tax state, or Pass; those come from the Organization and the Event, which is why a group can hold Events that look nothing alike.
Artwork is the one thing that flows down, and only on the Event's own page. An Event with no cover or poster of its own shows its EventGroup's, and an Event with neither falls back to its EventSeries'. Discovery cards do not borrow collection artwork.
Topics work the same way: each wrapper carries its own tags and nothing inherits. EventGroupSeries carries none at all.
Creating and publishing
All three start as drafts, created with a name, an optional summary and description, a visibility, and an optional slug.
Publishing is a small gate: name and summary must both be non-empty.
Publishing an EventGroup also assigns a subdomain equal to its slug, such as vidyut-festival.ulsav.com. If that label is already taken, a fresh random suffix is appended instead. Only a published, non-private wrapper is publicly resolvable; a private one returns "not found".
Membership
Membership is replaced, not patched: send the complete list and anything left out detaches. An empty list clears the wrapper.
Every member must belong to the same Organization. A duplicate ID is rejected, and an Event from elsewhere returns an invalid-membership error rather than being skipped.
EventSeries ordering is stricter: the ordering call must list exactly the current member IDs in order, so a half-finished drag cannot scramble the public page.
Repeating a series
Two shortcuts exist for a returning series, and they behave differently.
Fork copies one member Event into a new draft edition. Only scalar fields travel: name, summary, description, category, timezone, participation mode, team settings, venue text, capacity, visibility, fulfillment mode, and dates. Passes, Sessions, artwork, topics, FAQs, and sponsors are not copied, so a fork never inherits prices.
Repeat creates up to 52 editions from a published source Event. By default it copies active Passes with prices, shifts sale windows and Sessions by each edition's date change, and remaps selected-Session Pass scope onto the copies; both copies can be switched off per request. Artwork is not copied, so the editions show the series cover.
Each repeated edition lands published, unlisted, and sales paused: announced without being bookable. A name pattern can use {date} and {n}, so "Vidyut Classical {date}" fills itself in.
The group portal
An EventGroup owns a small website for its members. All three pieces stay editable after publication.
| Piece | Limits |
|---|---|
| Theme | The same styling catalogue as an Event |
| Navigation | Up to 8 links: Event list, content page, or external https address |
| Content pages | Up to 20 pages, up to 40 blocks each |
Six block kinds exist: heading, paragraph, image, call to action, event list, and FAQ. No block carries raw HTML, CSS, or JavaScript. A navigation link must name a content page that exists after the edit, so it cannot point at a page you are deleting.
The portal serves on the group's subdomain and on any verified custom domain targeting the group. A domain aimed at an Event or EventSeries serves the market instead.
What the public sees
Series and group pages list only members that are published, non-private, and still scheduled. A postponed or cancelled Event drops off the list while its own page stays reachable.
The series page also reports how many editions exist and how many are showing, so an empty year reads as empty rather than broken.
Edge cases
| Situation | Result |
|---|---|
| Add an Event from another Organization | Rejected as invalid membership |
| Send a partial member list | Prior members not listed detach |
| Order a series without every member ID | Rejected; the order must be complete |
| Repeat from a draft Event | Rejected; the source must be published |
| Delete a published wrapper | Refused; only drafts can be deleted |
Related
- Events — the ticketable thing these wrappers group
- Visibility — what published, unlisted, and private mean
- Domains — pointing a hostname at a group portal
- Roles — authority that can be scoped to a series or group