01
The CMS becomes a workspace
The main interface is no longer a pile of forms. It is a legible working environment where content, components, routing, and validation stay close enough to understand.
nextcms
Website editor for the agent era
Nextcms frees website editing from the confines of themes and plugins and rethinks the CMS as a real workspace for humans and agents to collaborate directly on the project.
Real flexibility without loosing control.
AI is a revolutionary human-machine interface based on natural language. Not just a Chat. We can finally translate our intentions into computer code without needing a degree in computer science. This removes the need for unified interfaces and one-size-fits-all solutions. Next CMS gives you the creative freedom that would otherwise require a specialist. If you are one: It's just a Next.js app with a PI coding agent, Git and some deployment conventions.
The next CMS is less about adding AI to an admin panel and more about removing
the gap between editing and implementation.
When an embedded agent can work inside the real project, content, structure,
validation, development, and review no longer need to live in separate systems.
That shift changes the shape of the CMS itself. It stops being a layer on top of
the website and becomes the environment in which the website evolves purely based on real needs.
The repository stays the central source of truth. Preview becomes a working
space instead of a disposable staging area. Production stays smaller and easier
to trust.
01
The main interface is no longer a pile of forms. It is a legible working environment where content, components, routing, and validation stay close enough to understand.
02
Markdown, frontmatter, styles, and source files remain visible. That makes the system easier to review, easier to diff, and easier for an embedded agent to navigate safely.
03
The rich editing environment belongs in preview. Production can stay focused on serving approved output instead of carrying the full authoring machine.
Nothing is hidden.
The public site stays polished while the underlying system
remains readable, reviewable, and easy to extend.
Workflow
01
Edit markdown, inspect structure, or ask the agent for a change without translating everything into admin fields first.
02
The agent can reason across files, routes, and design constraints because it is operating in the real workspace rather than a detached abstraction.
03
Linting, type checks, previews, and visible diffs keep the loop grounded before anything moves beyond review.
04
Approved work can move into the live branch, while production stays a tighter runtime with less surface area.
Recent notes
2026-03-28
The first sample news entry shows how a list can be driven purely from markdown frontmatter.
Open markdown2026-03-29
The markdown API can return frontmatter from a glob pattern for lightweight content lists.
Open markdown