Event instances
Add the individual dated occurrences of an event — what audiences see as showtimes
An event instance is a single dated occurrence of an event — what audiences see as a showtime. One event can have many event instances: a production with a four-week run has roughly 30 instances; a one-off concert has one. The terms "performance" and "event instance" mean the same thing in Basker; the canonical product term is event instance.
Event instances live underneath an event. The event holds the editorial detail — synopsis, creative team, programming context — and each instance holds the date, time, and any per-night specifics.
What an event instance contains
The instance editor has six tabs: Instance Detail, Content, Booking, Theme Settings, Custom Attributes, and SEO. The Instance Detail tab carries the core fields:
- Event (required) — the parent event the instance belongs to.
- Title and Description — optional overrides for special performances such as opening nights, captioned performances, or post-show talks.
- Venue, Duration, Company — optional overrides for tour dates, runouts, or co-productions.
- Start Date (required) and Timezone — the showtime.
- Season, Series, Works — optional overrides; instances inherit these from their event by default.
The right-hand sidebar carries:
- Slug with a Generate from title toggle.
- Main Image — uploaded or picked from the media library.
- Hide Event Instance? — hides the instance from the public site without deleting it.
- Hide Start Time? — hides the start time on the public site (useful when a time isn't being announced yet).
By default an instance inherits everything from its parent event. You only fill in the fields that need to differ.
Add an event instance
Open the parent event
Open the event you want to add an instance to. Switch to the Instances tab where its existing instances are listed. Or open the Event Instances area under Event Model in the main sidebar to start a fresh instance from there.
Start a new instance
Click to create a new instance. On the Instance Detail tab, pick the parent Event if it isn't already set.
Set the date and time
Fill in Start Date and pick its Timezone. These are the only required fields — most instances need nothing more, since they inherit everything else from the event.
Set any overrides
Override the Title for special performances. Override the Venue for tour dates or runouts. Override the Company, Season, Series, or Works if the instance differs from the event's defaults.
Add a main image, hide rules, and content
Use the sidebar to set a per-instance Main Image if it differs from the event's. Toggle Hide Event Instance? or Hide Start Time? if you need to. Use the Content tab to add per-instance content blocks the theme renders.
Save
Click Save. The instance appears in any listings your theme generates from upcoming-event data.
Recurring instances
For a production with many instances on a regular pattern, add the first instance and then duplicate it to seed each subsequent date. Adjust the date on each duplicate.