Template references
Per-collection field references for every content type Basker passes to your templates
This section is a per-collection reference. For each content type Basker exposes to templates, you'll find:
- The template filename Basker looks for.
- The shape of the document object passed to the template (
page,event,post, etc.). - Common patterns for rendering each collection.
Use it when you need to know which fields are available on a record, or when you're starting a new template for a collection you haven't worked with yet.
Templates by content type
Page
Standalone content pages with hierarchy, navigation, and blocks.
Post
Editorial blog entries with author and category.
Event
Productions, runs, and shows with dates, venue, and creative team.
Season
Programming-cycle groupings of events.
Series
Curated event groupings — festivals, recital series, themed weekends.
Work
The piece, production, or repertoire performed at events.
Person
Artists, conductors, designers, contributors.
Venue
Reusable venue records, with capacity and accessibility detail.
Organization
Co-producers, partners, sponsors, presenters.
Blog
The container for editorial posts.
Author
Reusable author records linked to posts.
Smart collection
Dynamic listings driven by a rule.
Category
Primary post groupings within a blog.
Tag
Free-form post labels.
404 / Not found
The page rendered when a URL doesn't match any record.
Runtime routing notes
Most content types use a base Liquid template such as templates/page.liquid, templates/post.liquid, or templates/event.liquid. Some pages are route-specific instead of normal collection defaults:
- Event detail pages use
templates/event.liquid; event-instance detail pages usetemplates/instance.liquid. - Event instance listing routes can use
templates/instances.liquid. - Smart collections use
templates/collection.liquid, even though the docs call the objectsmart-collection. - Category and tag pages are wired by dedicated routes as
templates/categoryandtemplates/tags. - 404 pages are rendered by custom not-found middleware using
templates/404.liquidwhen present.
Related
- Templates — how to write a template using these references.
- Template context — the global functions and variables available alongside the per-collection document.