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. It is not retrofitted from a blog or a product catalog. If you have worked on a WordPress, Drupal, or Squarespace site for a performing-arts organization, you will recognize the problem. Those platforms force long detours 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. It covers how Basker is structured, what you can extend, and what your custom theme controls. Understanding these ideas makes the rest of the documentation easier to navigate. It also helps you make better choices when you model 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, including pages, events, posts, the event model, and supporting content types.
- Extending Basker: adding fields, content types, and rules that are not in the built-in model.
- Customising Basker: how a custom theme defines layout, look, and behavior for the live site.
If you are a developer, use the Themes documentation for custom themes and the Partners API documentation for external integrations.