Blog — building in the open
Design decisions, MCP workflows, templating milestones, and honest write-ups as we build toward 1.0.
What is shipping, what is mid-flight, and what is not built yet. Written so you can tell which is which before committing anything real to it.
Open source projects that never answer this question tend to answer it badly later. Here is where the line sits, why we drew it there, and what would have to go wrong for it to move.
A blog, a shop, a social feed, an event site, documentation and a portfolio — modelled with the same collections, entries and fields. Where the plugins pick up, and where they do not.
Template syntax is usually optimised for the person typing it. We optimised for everyone who reads it afterwards — including the ones that are not human.
Adopting a CMS normally means rebuilding your site first. Birkly attaches to the site you already have — and this is how the two connection modes actually differ.
AI systems are already answering questions about your product. Right now they are inferring the answers from your marketing copy. The Agent Guide lets you state them instead.
Every CMS we tried asked us to give something up: our content, our stack, or our sanity. Birkly is what we built instead — and this is the argument it rests on.
Most CMSs let AI write straight into published content and call the Approve button oversight. We put agent writes in the same review queue as public form submissions — and this is what that actually changes.
Collections, entries and fields are the whole content model — plus one more idea that does most of the work. Why sub-collections beat reference fields for anything that owns something else.
The least fashionable decision we made is the one we are most confident about. On boring technology, code that still runs in ten years, and why the qualities that help a junior developer also help an AI agent.