Core concepts
How Basker is structured, what you can extend, and how custom themes shape what visitors see
Basker's content model is built around how live events actually work — productions, performances, people, venues, seasons, series — rather than retrofitted from a blog or a product catalogue. If you've worked on a WordPress, Drupal, or Squarespace site for a performing-arts organisation, you'll recognise the long detours those platforms force you into to model events, casts, and runs. Basker ships those concepts as native content types, so the structure is there from day one.
This section gives you the mental model behind that — how Basker's structured, what you can extend, and what your custom theme controls. Understanding these ideas makes the rest of the documentation easier to navigate, and helps you make better choices when modelling your content.
The shape of this section
- How Basker works — the layers of the system, from your content through to what visitors see on the live site.
- The content model — how the built-in content types fit together: pages, events, posts, the event model, and supporting records.
- Extending Basker — adding fields, content types, and rules that aren't in the built-in model.
- Customising Basker — how a custom theme defines layout, look, and behaviour for the live site.
If you're a developer building a theme, integrating with the API, or extending Basker as part of your work, see basker.dev for developer-level documentation.