No dashboard
A CTXR site has no admin panel. Not a minimal one, not a hidden one: none. The agent is the interface, and it works on the files directly.
The choice
An admin panel is the defining feature of a content management system and its largest liability: a second application in front of the content, with a login to attack, sessions to steal, forms that must mirror every field, and its own idea of the content that drifts from the templates.
CTXR removed it. What remains is the files, rules about how they may change, and one public gate through which changes arrive. That gate is the MCP — a protocol any assistant can speak, not an interface.
What it buys
Nothing to log in to, so nothing to break into. No login page, no session, no password database, no plugin ecosystem to keep patched. See Security without logins.
One truth. The agent reads the same files the site renders. No admin-side model can disagree with the template.
Management in your own words. “Move the summer closure notice above the opening hours and make it less formal” is not a feature a panel offers; an agent works from what you mean. See How you manage your site.
Nothing to learn, nothing to age. Panels need training and documentation, and go out of fashion.
What it costs
A dependency on a capable assistant. Someone who may not, or cannot, use one — a policy at a public body, a strict work environment — needs another way in. CTXR’s answer is a principle: new kinds of users get new clients, never new doors. That client exists: the edit client on /edit, which CTXR can switch on, speaking to the same MCP with the same key and rules — a client, not a panel, and never a second entrance with its own login.
What replaces the panel’s other jobs
| Panel job | CTXR answer |
|---|---|
| Explain the site | /admin, readable by any agent |
| List drafts, report refusals | the MCP, in plain language |
| Activity log | the journal |
| Map of the site | the machine views |
It is all data, and an agent reads it.