Overview
Build custom Basker themes — architecture, blocks, templates, Liquid, and deployment
This section is for developers building custom themes for Basker. A theme defines how content renders on the live site — layouts, templates, blocks, typography, navigation, and the editor controls site editors use to configure the look and feel.
You don't need to know anything about Basker's internals to build a theme — themes are a self-contained surface with a Liquid contract, a manifest, and a set of conventions for files and folders. The pages below walk through that surface from the ground up.
What's covered
Tutorial
Build a starter-shaped theme from scratch, end to end — directory, layout, templates, blocks, settings, calendar, upload, and preview.
Architecture
Directory structure, the theme manifest, the rendering lifecycle, and the data your templates work with.
Building
Layouts, templates, blocks, and theme settings — the four building units.
Template references
The shape of every record passed to your templates — pages, posts, events, people, venues, and more.
Liquid reference
Custom tags, filters, and field types layered on top of standard Liquid.
Deployment
Upload, version, and roll back themes. Plus the pre-deploy checklist.
When to come back here
Theme development is iterative. Most developers visit this section in three phases:
- First theme — work through Getting started and Architecture, then build a thin theme that renders pages and events from your site's content.
- Filling in features — read Building and Template references when you need a specific block type, override a template, or add theme settings.
- Shipping — Deployment and Troubleshooting, then back to the editor docs to verify the final result.
For the editor-side perspective on theme management — installing, switching, configuring themes from the admin — see Themes in the user docs.