Collection
The shape
- title
- text
- author
- text
- post
- rich text
Collections, entries and fields are all there is. This page shows how far they go: nested content, relations, translations and 27 fieldtypes.
{from 'birkly' get 'the model'}
Everything on this page is built from these three. An editor changing a post and an AI reading it are looking at the same objects.
The shape
The data
The markup
{for each entry in 'blog'}
<h2>{'title'}</h2>
<p>by {'author'}</p>
{'post'}
{endfor}
What visitors see
In the docs: Collections · What is Birkly
{from 'birkly' get 'structure'}
Two primitives, collections and entries, cover one-off pages, shared site parts and long lists alike. A few tools on top keep larger sites tidy.
parent → child
Comments on a post, reviews on a product, variants of an item. Child entries belong to their parent and are managed from its entry editor.
{for each entry in 'comments'
of 'blog'.current}
entry ↔ entry
Link entries across collections, like an article to its author in a team collection. Templates print titles or links in one line.
{relation_links('author')}
tidy admin
Folders for your collections, up to three levels deep, with labels and emoji icons. Also available in templates and the API.
shared parts
Headers, footers and announcement bars are entries too. Place them on any page with one element.
<birkly-region collection="site_elements"
entry="header">
In the docs: Content model · Sub-collections · Collection groups
{for each entry in 'fieldtypes'}
Every field in a collection has a type. It decides what editors see in the admin, what gets stored, and what your template receives.
¶ContentEditor
⧉DynamicItems
{dynamicitems_html('blocks')}Every field also has a display name, an API name and a required switch. Plugins can add their own fieldtypes. In the docs: Field types · Content editor · Dynamic items
{from 'birkly' get 'the admin'}
This is where your team works every day: writing entries, linking content, translating it and deciding who can change what.
An Author entry can contain a Posts sub-collection, for content that truly belongs to a parent. Need a looser cross-reference instead? The Relation fieldtype handles that.
Give an editor exactly the collections they need. The same role system is what an AI connection inherits further down this page.
Translations live in the content model, side by side in the admin. No plugin to activate, no schema to migrate, no content duplicated by hand.
Define fields once and every entry inherits them. Change the schema later and existing entries adapt instead of breaking.
In the docs: Content overview · Entry editor · Media library
{from 'birkly' get 'languages'}
No plugin, no duplicated entries. Switch a collection to multi-language and every entry carries its translations.
Editors see each language in its own tab of the same entry.
Show the right content and copy per language.
{if current.language = 'de'}…{endif}
One attribute turns a select into a language switch that remembers the choice.
<select data-birkly-language-select>
Each team member picks their own admin language, separate from the site’s languages.
In the docs: Multilingual templating · Admin vs site language
{for each entry in 'shapes' ordered by ambition}
Each site below is just collections with fields. Some collections sit inside others. Plugins add what content alone can’t, like checkout or logins.
A single collection. The simplest Birkly site.
Projects link to clients with a relation field.
Articles live inside sections, versions inside articles.
Products get a price field from the Commerce plugin.
Events plus RSVPs and tickets from the Events plugin.
Members sign up; their posts and likes live inside their profile.
A full walkthrough with example entries is on the front page, and the step-by-step build is in Getting started.