Events | Basker Help Center

Events are designed to help you easily build out the main event pages on your website. This could be a theatre production, exhibition, literacy or gig; an Event page is the main landing page for users to find out important event and booking information, and serves as an entry point into the ticketing path via a booking button or browse a list of Event Instances, which could be performances, cinema screenings, and concerts.

You can start creating events directly from the Dashboard or within the Events section.

1. Event Detail

Found under the "Event Detail" tab:

Title (title):
- What it is: The official name of the event. This is a required field and will be used as the main identifier for the event in the admin interface and often on the website.
- How to use: Provide a clear and concise title. This field is localized, allowing for different titles in multiple languages.
Description (description):
- What it is: A more detailed explanation of the event. This can include a summary, highlights, or any other relevant information.
- How to use: Write a short, comprehensive description. This field is optional and also localized.

2. Venue, Duration, and Company

Venue (venue):
- What it is: The physical or virtual location where the event will take place.
- How to use: Select a venue from your Venues collection. This creates a relationship between the event and a predefined venue. Only one venue can be selected. However, if you want to create an single Event page for an event with performances with a different venue (e.g. a neighborhood concert), you can specify the venue on a per Event Instance basis.
Duration (duration):
- What it is: The length of the event in minutes.
- How to use: Enter a numerical value for the event's duration. This field is optional and not localized. The minimum value is 0.
Company (company):
- What it is: The organization or entity primarily responsible for or presenting the event.
- How to use: Select an organization from your Organizations collection. This links the event to a specific company. Only one company can be selected.

3. Dates and Times

Start Date (startDate):
- What it is: The exact date and time the event begins. This is usually the start date and time for the first event instance.
- How to use: Use the date-time picker to select the start date and time. The picker allows selection of both day and time, with time intervals of 10 minutes. The timezone for this date is also stored -- make sure the event is using the correct timezone.
End Date (endDate):
- What it is: The exact date and time the event ends (i.e. the end date and time for the last event instance)
- How to use: Use the date-time picker. This field is optional. It includes validation (validateEndDate) to ensure the end date is not before the start date.

*All dates and times are stored as UTC in Basker and requires the timezone for dates and times to display correctly on your website. For custom themes, developers can use startDateLocalAsUTC and endDateLocalAsUTC so they do not need todo any timezone conversion (i.e. just display the time given!)

4. Seasons, Series, and Works

Relate your events to broader contexts like seasons, series, or works.

Season (season):
- What it is: Associates the event with a specific season (e.g., "25/2 Season").
- How to use: Select a season from your Seasons collection. An event can belong to one season. Optional.
Series (series):
- What it is: Links the event to one or more series (e.g., "Guest Speaker Series," "Film Noir Festival").
- How to use: Select one or more series from your Series collection. An event can be part of multiple series. Optional.
Work (work):
- What it is: Connects the event to a specific creative work being presented or featured (e.g., a particular play, symphony, or film).
- How to use: Select a work from your Works collection. Optional.

5. Participants

List individuals or organizations involved in the event and their roles.

Participants (participants):
- What it is: Allows you to create groups of participants (e.g. Cast and Creatives)
- How to use:
  - For each group of participants (e.g., "Cast," "Organizers," "Speakers"), you can specify a Group Name (group). These groups are called Participant Groups.
  - Within each Participant Group, you can add multiple Participants (participantGroup), where each entry consists of:
    Participant (participant): A relationship to either a People or Organizations record.
    Role (role): A text field to describe their role within that group (e.g., "Lead Actor," "Keynote Speaker").

6. Hero

The Hero section is a prominent visual area at the top of the event page.

Type (type):
- What it is: Controls the visual prominence and layout of the Hero section.
- How to use: Select from four options:
  - High Impact: A large, visually striking hero, usually with a full-width background image or video. Requires a media item.
  - Medium Impact: A balanced hero section that is prominent but less dominant than High Impact. Requires a media item.
  - Low Impact: A more subdued hero, often just a title and text without a large background media.
  - None: Hides the hero section completely.
Title Override (richText):
- What it is: Allows you to provide a custom, richly formatted title for the hero section.
- How to use: Use the rich text editor to create a custom title. If left empty, the event's main Title will be used by default. This field is hidden if the Type is set to "None".
Prefix Text (prefix):
- What it is: Optional text that appears before the main hero title.
- How to use: Useful for adding a subtitle or a short introductory phrase. This field is hidden if the Type is set to "None".
Suffix Text (suffix):
- What it is: Optional text that appears after the main hero title.
- How to use: Can be used for additional context or a tagline. This field is hidden if the Type is set to "None".
Buttons (LinkGroupField):
- What it is: Allows you to add one or two call-to-action buttons within the hero section.
- How to use: Configure the text and link for each button. This field is hidden if the Type is set to "None".
Media (media):
- What it is: The background image or video for the hero section.
- How to use: Upload or select a media file. This field is required and only visible when the Type is set to "High Impact" or "Medium Impact".

7. Content

Similar to Pages, Events can have rich content and visual styling. Content blocks appear below the Event Hero.

Content Blocks (blocks - in "Content" tab):
- What it is: The main descriptive content for the event, built using the Basker block editor.
- How to use: Add and configure various content blocks (text, images, etc.) to provide detailed information about the event. See Blocks.

8. Media

Main Image (image - in sidebar):
- What it is: A primary representative image for the event, similar to the one for Pages. Used for previews, listings, etc.
- How to use: Upload a single image. This field allows for a display preview in the admin interface.
Media (media - in "Media" tab):
- What it is: Allows you to associate multiple images or other media files with the event.
- How to use: Upload or select files from your Media collection. These might be used in a gallery on the event page or for promotional materials.

9. Event Instances

Found under the "Instances" tab, this section manages the specific occurrences or showtimes for an event.

What it is: While an Event defines the overall production (e.g., "The Spring Concert"), an Event Instance represents a single, bookable occurrence of that event (e.g., "The Spring Concert on May 25th at 7 PM"). Each instance can have its own unique details, such as a specific venue, ticketing information, or on-sale date. This allows for granular control over complex event schedules, like a touring production that performs at different venues.
How to use: The "Instances" tab displays a list of all Event Instances linked to the event. From this list, you can view key details for each instance, such as its title and ticketing system ID. You can also create new instances directly from this tab, making it easy to build out a full schedule of performances or screenings.

10. Page URL and Template

Slug (slug):
- What it is: The URL-friendly identifier (or handle) for the event.
- How to use: Typically auto-generated from the title, can "unlocked" and edited. Must be unique per tenant.
Template (template):
- What it is: This setting determines the overall design or layout used for the event page. Your website developer can create multiple templates, allowing you to choose different looks for different types of events (e.g., a standard event page vs. a festival main page).
- How to use: In most cases, this will be pre-selected for you. If your developer has provided multiple options, you can select the appropriate template from the dropdown list.

11. Theme Settings

Found under the "Theme" tab, these settings allow you to fine-tune the appearance of your event page. This tab is only available for custom themes.

What it is: Your website's theme controls the overall look and feel of your pages. "Theme Settings" are special options created by your website developer that let you customize how a specific event page looks. The available settings are based on the selected template.
How to use: The options available here will depend entirely on your active theme. For example, you might find settings to change the page's color scheme, adjust the layout of certain sections, or toggle specific visual elements on or off.

Important: Theme Settings are for visual adjustments only. Since these settings are tied to a specific theme and template, they will be lost if you change either. For essential data (like ticketing data), always use Custom Attributes.

12. Custom Attributes

Found under the "Attributes" tab, this section provides a powerful way to add extra, structured information to your event.

What it is: Custom Attributes are like custom data fields for your event, allowing you to store specific pieces of information that aren't covered by the standard fields. While developers can set up complex attributes, you can also create and manage them yourself without any code. Unlike Theme Settings, which are purely for visual changes, Custom Attributes store core data that stays with the event regardless of which theme or template you are using.
How to use: You can manually add data, such as a film's Director and Rating for a festival. More powerfully, if you have connected a ticketing system (like Spektrix or Tessitura) via the Apps section, you can configure attributes to automatically sync data from that system. This allows you to pull in and display information from third-party sources without manual entry, keeping your event details up-to-date automatically.

13. Version Control and Workflow

Events benefit from the same robust versioning as Pages:

Drafts & Autosave: Work is saved automatically (every 375ms) and can be explicitly saved as a draft.
Scheduled Publishing: Publish events at a future date and time.
Validation: Drafts are validated before publishing.
Version History: Up to 30 versions (depending on your plan) of each event are stored, allowing for review and rollbacks.

14. Permissions

In Users & Permissions you can can control access by the following permissions:

View Events: events:view
Create Events: events:manage
Update/Edit Events: events:manage
Delete Events: events:delete