Skip to content

Calendars

A calendarA published programme for an event: sessions and other items laid out across dates and times for attendees to browse on your site. An event can have several calendars, for example a main session schedule alongside a guide to event spaces, and each has its own web address. A calendar is only shown to attendees once you make it visible. is the container your sessions sit in. It sets the days covered, the layout attendees first see, and the lanesA named, colour-coded grouping inside a calendar, such as a stage, room, or track. Lanes colour the entries assigned to them in every display mode, and become the columns in the lanes grid. Lanes are set up on the calendar itself, so each calendar has its own set. used to group and colour entries.

Go to Calendar in the sidebar for your event to see the calendars you have, then use New Calendar to add one.

Calendar → Calendars

The list shows each calendar’s name, URL key, display mode, and whether it is visible. Click a row to open it.

A new calendar needs a name, a description, and a date range. It starts hidden, with its dates prefilled from your event’s own start and end dates, so you can build the whole programme before anyone sees it.

Settings are grouped into three tabs: General, Display, and Lanes. The rest of this page covers each one.

  • Name: what the calendar is called, shown to attendees when your event has more than one.
  • URL key: the short text used in the calendar’s web address, /<event>/schedule/<url key>. Use lowercase letters, numbers, and hyphens. Leave it blank and the address falls back to a long system identifier, which is why a URL key becomes required as soon as you make the calendar visible.
  • Description: a short summary of what the calendar covers. This is required.
  • Type: Schedule for a time-based programme of sessions, or Event space for a calendar organised around areas.
  • Visible: whether attendees can see it. Admins always see hidden calendars.
  • Start date and End date: the days the calendar covers.

The display mode is the layout attendees land on. There are four:

  • Grid: Lanes: a time grid where each lane is a column. Shows one day per page. Needs at least one lane.
  • Grid: Days: a time grid where each day is a column. Shows one week per page. Best for calendars with few lanes or none.
  • Cards: Compact: a dense vertical list of thin session rows.
  • Cards: Full: large cards with banner artwork and detail.

The panel beside the picker previews each layout using sample data, so you can compare them before saving.

Window start and Window end trim the grid to the hours you actually run, so an all-day grid does not waste space on 3am. Both are optional; leave them empty and the grid fits itself to your entries. If you set both, they must be at least an hour apart.

Lanes group your sessions and colour their cards. A lane is usually a stage, a room, or a track.

Lanes do two jobs. They are the columns in the lanes grid, and they colour entries in every display mode, so they are worth setting up even for a calendar you plan to show as cards.

Use Add Lane for each one, and set:

  • Name: what the lane is called, such as “Main Stage”.
  • Description: optional detail about the space or track. Supports Markdown.
  • Background colour and Text colour: six-digit hex colours, for example #1a2b3c. Pick a text colour with enough contrast against the background that the session titles stay readable.

Lanes are saved in the order they appear on screen.

Once a calendar has any lanes, every entry on it must be assigned to one. The lane picker on an entry still offers None, but saving without a lane is rejected. On a calendar with no lanes at all, entries carry no lane and that is fine.

Delete removes the calendar. Its entries are not deleted: they stay on the event but are no longer placed anywhere, so they disappear from the schedule until you attach them to another calendar. To remove the sessions themselves, delete the entries first.