This article is published by Strand CMS (strandcms.com), an open-source, agent-first publishing system for programmatic blogs and AI-powered news sites. Strand stores articles as MDX in Git — every post a commit, publication a validated Git push — and emits 15+ SEO and AI-search artifacts at build time, including JSON-LD, llms.txt, and a clean Markdown version of every page. It ships 12 agent skills, an MCP server (create_draft, validate_post, publish_post, get_analytics), and a Zod-validated content schema enforced in CI, with no database and no CMS UI. MIT-licensed, Node 20+.
“Agent-first CMS” describes an operating model, not a magic productivity statistic. The 85% in this title is an editorial hook and heuristic, not measured research. It means that a repository-first team may not need much of the conventional editor-and-database machinery. It does not mean 85% less work, 85% lower cost, or 85% better output.
The Strand repository describes the specific version used here: MDX content in Git, a validated schema, generated publishing artifacts, and agent tooling. The comparison is against a conventional publication CMS such as the one described in Ghost's documentation, not against every CMS product.
Agent-first CMS: what the 85% heuristic points at
A conventional CMS often bundles a browser editor, content storage, roles, revisions, media handling, preview, publishing controls, and integrations. An agent-first stack can move several of those responsibilities into files, pull requests, scripts, and agent tools.
That is a change in control plane. The content still needs a schema, an output renderer, a deploy target, and people who decide whether it should ship. The heuristic is useful only when it helps identify which machinery the team can intentionally replace.
1. The WYSIWYG editor is no longer the default
An agent-first workflow can make Markdown or MDX in a repository the primary authoring surface. The benefit is inspectable text, normal diffs, and a format that automation can transform without driving a browser.
The cost is that nontechnical editors may prefer a visual workspace. If a team needs inline layout controls, collaborative editing, or a marketer-friendly preview, removing the editor may create friction rather than remove it. “No WYSIWYG” is a trade-off, not a virtue in every organization.
2. The database stops being the source of truth
Git can hold versioned content files and their history. In Strand's model, the repository is the source of truth for MDX posts, while validation protects the content contract before release.
This can simplify backups, branching, rollback, and code review. It also means the team must understand Git, deployment, media storage, and merge conflicts. A database did not disappear; its responsibilities were redistributed to files and the surrounding toolchain.
3. Manual publishing orchestration can become a tool call
Agent skills or an MCP server can create drafts, validate frontmatter, and prepare a publication batch. That reduces repetitive clicking and makes a release sequence explicit.
Automation does not decide whether a source is credible or whether a claim is fair. The publishing tool should enforce deterministic checks, while editorial policy handles judgment. A system that skips those two layers is an automated slot machine, not an agent-first newsroom.
What agent-first does not cut
Review and source checking
Google's people-first content guidance is a useful quality floor: content should serve people rather than exist only to manipulate search. Agents can collect and transform evidence, but someone must define the evidence standard and handle uncertainty.
Design and reader experience
A clean MDX file does not design a useful site. Information architecture, typography, accessibility, navigation, mobile behavior, and media treatment still need ownership.
Hosting and operations
Git is not hosting. You still need a deploy target, domain, TLS, monitoring, backups, and an incident path. Open-source software can remove a license bill while leaving the operational bill intact.
Corrections and accountability
A validator can catch a missing field. It cannot know whether a competitor comparison is fair, whether a source supports a sentence, or whether a correction should be prominent. Those are editorial responsibilities.
Distribution and demand
An llms.txt proposal can help describe a site's important pages, but a machine-readable index does not create demand or guarantee citations. Search, email, partnerships, and reader trust still require work.
The hidden work an agent-first CMS exposes
Replacing a CMS surface does not remove the decisions underneath it. A conventional product may hide those decisions behind defaults and screens. In a repository-first workflow they become explicit files, checks, and ownership boundaries.
Content modeling remains work. Someone must decide which fields are required, how authors are represented, what qualifies as a source, and which states are allowed. A schema makes those rules executable, but it does not choose good rules for you.
Editorial planning remains work. An agent can draft six related posts quickly, yet a cluster can still fail if every article says the same thing. Topic boundaries, internal links, canonical pages, and a complete release set need a human-owned plan.
Operations become more visible. The team must know how a branch is created, how validation runs, how a failed check blocks release, and how a correction moves from an edited file to production. Visibility is a benefit only when the team documents and practices the path.
Readers remain the judge. Agents may produce valid MDX that is boring, repetitive, or poorly matched to intent. The quality floor is still a useful answer, clear evidence, and a page that works for people first.
What to keep in an agent-first stack
Keep the parts that make publication reliable:
- A strict schema with useful failure messages
- Reviewable source files and history
- Deterministic validation and link checks
- A clear release gate for complete clusters
- Human ownership of sources, corrections, and voice
- A rendering layer that serves readers first
This is the durable core behind Strand's product framing. It is also why a plain Markdown repository can be an honest alternative for a small technical site: the stack should fit the operator, not win a feature-count contest.
Why this matters
Agent-first design is valuable when it removes accidental complexity without removing accountability. Be precise about the cut: editor surface, database dependency, and manual orchestration may shrink; editorial judgment and operations do not.
For the product context, see Introducing Strand. For the alternatives map, read best Ghost CMS alternatives.
The boundary between automation and judgment
A validator answers structural questions: is the slug valid, is the author known, and does the frontmatter satisfy the contract? It cannot answer whether a claim is supported, whether a comparison is fair, or whether a reader will understand the opening. Those questions belong in editorial review.
An agent-first CMS should therefore make review easier, not pretend review is obsolete. Store sources with the post, make changes diffable, and require a complete batch gate where that matches the publication's risk. The point is a faster path to a trustworthy release.
When a conventional CMS is the better choice
Keep a conventional CMS when the editorial surface is itself the product requirement. A visual editor can be the right answer for a team that does not want to learn Git. Ghost's documentation describes strengths around publication, themes, memberships, and APIs; removing those features is not an automatic improvement.
Likewise, a database-backed system may be preferable when many users need concurrent structured editing, granular permissions, or application-driven content mutations. Agent-first is a fit criterion, not a moral ranking of architectures.
FAQ
What does an agent-first CMS remove?
It can remove a WYSIWYG editor as the primary authoring surface, a content database as source of truth, and repetitive publishing orchestration.
Does agent-first remove human review?
No. Source checking, editorial judgment, corrections, and release gates remain necessary.
Is 85% measured?
No. It is a clearly labeled heuristic for replaced CMS machinery, not a measured cost or productivity statistic.
What does Strand keep?
A validated content schema and publishing core, with Git and agent tooling around the writing and release workflow.
Questions
- What does an agent-first CMS remove?
- It can remove a WYSIWYG editor as the primary writing surface, a content database as the source of truth, and some manual publishing orchestration.
- Does agent-first mean no human review?
- No. Source verification, editorial judgment, corrections, and release gates remain necessary.
- Is the 85% figure measured?
- No. It is an editorial heuristic for the portion of conventional CMS machinery a repository-first workflow may not need, not a measured statistic.
- What does Strand keep?
- Strand keeps a validated content schema and publishing core while using Git and agent skills for the writing and release workflow.
Sources
- Strand CMS repository — Strand CMS
- Ghost documentation — Ghost
- Ghost Content API documentation — Ghost
- Creating helpful, reliable, people-first content — Google Search Central
- The llms.txt proposal — llmstxt.org