Calendars

Calendars group your events. Each one has its own colour and field layout, so you can model very different kinds of events — concerts, workshops, markets — in the same install.

Creating a calendar

Go to Owl → Calendars → New calendar. Give it a name and handle, pick a colour (used in calendar views, the control panel and ICS feeds), then save.

Field layouts

Each calendar has its own field layout, designed with Craft’s standard field-layout designer. Add any custom fields your events need — a location, a ticket price note, a lineup Matrix, an image — and they’ll appear on every event in that calendar, exactly like entry types.

Querying calendars

Calendars are available in Twig through the Owl variable:

{# All calendars #}
{% set calendars = craft.owl.calendars() %}

{% for calendar in calendars %}
  {{ calendar.name }}
{% endfor %}

{# A single calendar by handle #}
{% set concerts = craft.owl.calendar('concerts') %}

Calendars & project config

Calendar definitions (name, handle, colour, field layout) are stored in Craft’s project config, so they version-control cleanly and deploy across environments. Event content lives in the database, like any other element.

Ticketing per calendar

With Owl Pro, you can enable ticketing on a calendar so its occurrences can be sold as tickets through Craft Commerce. See Commerce ticketing.

More in Site Features

Pairs well with Owl

The bigger pieces a client asks for by name. Events, bookings, memberships, courses, reviews, a support desk, job listings and the rest.