The content model
The content types Basker ships with and how they relate to each other
Basker comes with a curated set of content types designed for performing-arts and live-events organisations. This page explains what each one is for and how they fit together — useful both as a reference and as the starting point for thinking about how to model your own content.
The two big content areas
Basker's content divides roughly into two areas:
- The website — pages, blog posts, forms, smart collections, announcements. This is the editorial and structural side: standalone pages, navigation, content blocks, marketing.
- The event model — events, event instances, people, venues, seasons, series, works, organizations. This is the productions side: a connected model of who's performing, what's being performed, when, and where.
Both areas share the same platform features (drafts, versioning, translation, SEO) and can reference each other freely — a page can list events, a post can credit people, an event can link to a programme PDF stored in your media library.
The website side
| Content type | What it is | Lives at |
|---|---|---|
| Pages | Standalone pages (About, Contact, landing pages) | Pages |
| Posts | Editorial entries inside one or more blogs | Blog |
| Authors | People who write posts | Authors |
| Categories and tags | Taxonomy for posts | Categories and tags |
| Smart collections | Dynamic listings — "upcoming events", "recent reviews" | Smart collections |
| Reusable sections | Content built once and embedded on many pages | Reusable sections |
| Blueprints | Preset arrangements for new content | Blueprints |
| Announcements | Site-wide banners scoped to where you choose | Site-wide announcements |
| Forms | Structured forms with submissions | Forms |
The event model
The event model is one of Basker's core differentiators. Instead of forcing live-events organisations to rebuild this structure with custom fields, Basker ships it as native concepts:
| Content type | What it is | Lives at |
|---|---|---|
| Events | The top-level production or show record | Create events |
| Event instances | The dated occurrences (one per night of a run) | Event instances |
| People | Cast, creative team, contributors | People |
| Venues | Where events happen | Venues |
| Seasons and series | Grouping for programming context | Seasons and series |
| Works | Productions, pieces, repertoire performed | Works |
| Organizations | Producing companies, sponsors, partners | Organizations |
Event-model records relate to each other through links: an event has a venue, a season, possibly a series, a list of works, a list of participants drawn from people and organizations. The same record can be linked from many places — one venue underpins every event happening there, one person can appear in every event they're part of.
Supporting content
| Content type | What it is | Lives at |
|---|---|---|
| Media | Images uploaded to your site | Media library |
| Files | Non-image uploads (PDFs, downloads) | Files |
| Custom data | Fields and types you define yourself | Custom data |
| Domains, redirects, settings | Operational records for the site itself | Site settings |
What every content type shares
Most content types in Basker share a baseline of platform features:
- Drafts and publishing — see Drafts and preview.
- Versioning — see Versioning and history.
- Translation — see Languages and translation.
- SEO — see SEO.
- Visibility controls — see Visibility.
These work the same way across content types. Once you've learned the publishing workflow on pages, the same workflow applies to events, posts, and almost everything else.
When the built-in model isn't enough
When you need fields or content types that aren't in the built-in model, see Extending Basker.