Why CMSless
For twenty years we've managed websites through admin panels: forms about content instead of content, fields instead of ideas, plugins instead of possibilities. CMSless removes the panel and puts AI in every step of the pipeline — from the first idea to the final code review.
A CMS exists to solve one problem: non-developers need to change websites, and code used to be the barrier. So we built layers of abstraction — page builders, field groups, template hierarchies — that let people edit content without touching code.
The price was steep. Every CMS draws a line between what you can change (the fields someone predicted you'd need) and what you can't (everything else). Want a new section type? File a ticket. Want the layout to breathe differently on this one page? Not without a developer. The CMS didn't remove the barrier — it moved it, and charged rent on both sides.
AI dissolves the barrier itself. When software can read, write, and review production code, the safest interface for changing a website is no longer a form — it's a conversation with something that understands the whole system.
Most tools add an "AI assistant" to an old workflow. CMSless is the workflow. Four stages, each one AI-native:
01 — Ideas
You don't open an editor; you say what you're trying to achieve. "We're launching in Norway next month." The AI proposes the pages, copy, and structure that follow from the goal — and asks what it doesn't know instead of guessing.
02 — Understanding
Before changing anything, CMSless studies the codebase, the design-system docs, the existing tone of voice, and the git history. A junior developer takes weeks to learn a project's conventions; the AI does it on every request, fresh, in seconds.
03 — Development
Changes are written as Blade components, routes, and migrations — following the project's own conventions, covered by tests, formatted by Pint. Nothing is stored as an opaque blob in a CMS database. Your site's single source of truth is its repository.
04 — Code review
Every diff is reviewed by AI before it ships: correctness, accessibility, contrast, responsive behavior, performance, and consistency with the design system. Failing tests block the change. This is the step no human-run CMS workflow ever had — review on every single edit.
CMSless isn't built in a vacuum. It runs on Laravel — the framework that has quietly become the most AI-ready ecosystem in web development.
The Laravel AI SDK gives CMSless first-party access to models, agents, and tools. Laravel Boost hands the AI deep, structured knowledge of the application — its routes, schema, and docs — so understanding isn't guesswork. And Laravel MCP lets the application itself expose tools the AI can call safely.
Around that core sits everything a production change needs: Pest for tests that gate every edit, Pint for consistent formatting, Eloquent and migrations for structured data, and a deployment story from Laravel Cloud to Forge. The AI isn't improvising infrastructure — it's operating a mature framework the way an expert developer would.
Models, agents, and tool-calling as a first-party citizen
Deep application context: routes, schema, docs, conventions
The app exposes safe, typed tools for the AI to use
Every change tested and formatted before it ships
Every CMS has a ceiling: the set of things its data model and plugin catalog anticipated. CMSless has no ceiling, because its output is code. A new page type, a pricing calculator, a members-only area, an integration nobody has built a plugin for — if it can be written in Laravel, it can be asked for in chat.
That's the quiet inversion at the heart of CMSless: the CMS asked "which of our features do you want to use?" CMSless asks "what do you want to exist?"
This page — the one you're reading — was written, designed, reviewed, and deployed exactly that way.