Most content systems were built for a person sitting at an editor. Strand CMS starts from a different premise: the writing, the SEO, the structured data, the scheduling, and the publishing can all be done by an agent working against a well-defined contract.
What we kept, and what we threw out
A modern CMS is mostly machinery for human editors - a WYSIWYG editor, roles and permissions, members and subscriptions, newsletters, a theme marketplace. The genuinely valuable part is small: a validated content schema and a publishing-quality core that produces sitemaps, JSON-LD, canonical tags, and feeds.
Strand CMS keeps that core and throws out the rest. The editor becomes a set of agent skills. The database becomes Git. Every article is a commit; publishing is a pull request.
The schema is the contract
Because an agent writes the post, the schema matters more, not less. Frontmatter is validated on commit, so a malformed article literally cannot merge. That validation is the same check an agent runs to correct itself before opening a PR.
SEO is the floor; AI search is the reason
Strand emits sitemaps, JSON-LD, RSS, and robots like any good CMS - and then goes further,
with llms.txt and a clean Markdown rendering of every page so AI search engines ingest
your content instead of your hydrated DOM.
Try it
One command scaffolds a running publication, wired for an agent to take over. The whole thing is open source.
Questions
- What is Strand CMS?
- An open-source publishing system for programmatic blogs and news sites. Articles are MDX files in Git, written by AI agents, with SEO and AI-search built into the core.
- How is it different from Ghost or WordPress?
- No database, no WYSIWYG editor, no plugin marketplace. The editor is replaced by agents writing against a strict schema; the database is replaced by Git.
Sources