What is Basker?
An introduction to Basker — what it is, who it's for, and what's covered in this documentation
Basker is a content platform built specifically for performing-arts and live-events organisations. It combines a flexible content management system, a first-class event model, integrations with the major ticketing platforms, and a custom-theme system for the public-facing site — all in one place.
If you produce, present, or programme live events — opera, theatre, music, dance, festivals, comedy, lectures, exhibitions — Basker is built to handle the structure of your work. Productions, performances, casts and creative teams, venues, seasons and series, sponsors and partners are all native concepts, not custom data you have to bolt on.
This documentation is for the people who use Basker day-to-day:
- Site editors maintaining content across pages, events, blog posts, and media.
- Theme integrators working with a custom theme to render the live site.
- Site administrators managing users, permissions, integrations, and settings.
For developer-level documentation about building themes, integrating with the API, or extending Basker as a developer, see basker.dev.
How to use these docs
The sidebar groups topics by area. The natural reading order is:
- Get started with Basker — orientation, quick-start, plans, and the changelog.
- Core concepts — how Basker works, the content model, how to extend and customise.
- The remaining sections — task-oriented documentation for each part of the product.
Use the search at the top of the sidebar to jump straight to a topic, or browse the cards below for the most common starting points.