Model any content. Edit it in one calm admin.

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'}

Collections define shape. Entries hold data. Templates render it.

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.

Collection

The shape

title
text
author
text
post
rich text

Entry

The data

title
Why we removed the build step
author
Mara Lindqvist
post
Every dependency is a promise…

Template

The markup

{for each entry in 'blog'}
  <h2>{'title'}</h2>
  <p>by {'author'}</p>
  {'post'}
{endfor}

Page

What visitors see

Why we removed the build step by Mara Lindqvist Every dependency is a promise someone else has to keep.

{from 'birkly' get 'structure'}

Model real structure, not just pages.

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

Sub-collections

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

Relations

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

Collection groups

Folders for your collections, up to three levels deep, with labels and emoji icons. Also available in templates and the API.

shared parts

Site elements

Headers, footers and announcement bars are entries too. Place them on any page with one element.

<birkly-region collection="site_elements"
  entry="header">

{for each entry in 'fieldtypes'}

27 fieldtypes. Two of them change how you build pages.

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

A real page editor, inside one field.

  • Tables and responsive CSS grids, with a layout studio for widths, spans and spacing
  • Previews with your own site’s CSS while you write
  • Ready-made blocks: callout, quote, call-to-action button
  • Saves clean, portable HTML. Switch to the HTML tab any time

⧉DynamicItems

Build each entry from the blocks it needs.

  • Editors add blocks one by one, each with its own fieldtype
  • Order and mix can differ from entry to entry
  • Made for page sections, FAQs, feature lists, headers and footers
  • One tag renders them all: {dynamicitems_html('blocks')}

Text & writing

  • Textone line
  • Textareaplain paragraphs
  • ContentEditorrich text, layout
  • Markdownwrite and preview
  • Codesnippets, JSON

Media

  • Fileone image or PDF
  • Galleryordered images
  • oEmbedYouTube, Vimeo

Numbers & time

  • Numbermin, max, decimals
  • Rangevalue on a scale
  • Dateday only
  • DateTimeday and time
  • Timetime of day

Choices

  • Selectone option
  • MultiSelectseveral options
  • Radioone, as buttons
  • Checkboxyes or no
  • Toggleon or off
  • Tagsfree keywords

Links & contact

  • URLweb address
  • Emailvalidated
  • Phonevalidated
  • Passwordhashed, never shown

Structure

  • Relationlink to other entries
  • DynamicItemsrepeating blocks
  • Maplatitude, longitude
  • Colorhex value

{from 'birkly' get 'the admin'}

One admin to write, translate and organise everything.

This is where your team works every day: writing entries, linking content, translating it and deciding who can change what.

Creating a new entry in the Birkly admin

Sub-collections, alongside references

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.

Roles and permissions

Give an editor exactly the collections they need. The same role system is what an AI connection inherits further down this page.

Multi-language everywhere

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.

Schema first, content second

Define fields once and every entry inherits them. Change the schema later and existing entries adapt instead of breaking.

{from 'birkly' get 'languages'}

Multi-language, built into the content model.

No plugin, no duplicated entries. Switch a collection to multi-language and every entry carries its translations.

Side by side

Editors see each language in its own tab of the same entry.

In templates

Show the right content and copy per language.

{if current.language = 'de'}…{endif}

Visitor switch

One attribute turns a select into a language switch that remembers the choice.

<select data-birkly-language-select>

Admin language

Each team member picks their own admin language, separate from the site’s languages.

{for each entry in 'shapes' ordered by ambition}

Same three primitives. Six very different sites.

Each site below is just collections with fields. Some collections sit inside others. Plugins add what content alone can’t, like checkout or logins.

posts collection articles sub-collection, lives inside the one above title field price field added by a plugin

Blog

core only
  • poststitleauthorposttag

A single collection. The simplest Birkly site.

Portfolio

core only
  • projectstitlegalleryclient ↗
  • clientsnamelogo
  • servicesnametext

Projects link to clients with a relation field.

Documentation

core only
  • sectionstitle
  • articlestitlebody
  • versionsnumberchanges
  • faqquestionanswer

Articles live inside sections, versions inside articles.

Online shop

Commerce plugin
  • productsnamephotosprice
  • variantssizecolourstock

Products get a price field from the Commerce plugin.

Event site

Events plugin
  • eventstitledateplacetickets
  • speakersnamephoto

Events plus RSVPs and tickets from the Events plugin.

Social feed

User Management plugin
  • profilesnameavatarlogin
  • poststextimage
  • likesby ↗

Members sign up; their posts and likes live inside their profile.

NextAI that works within your rules