Control Panel

The Control Panel (often abbreviated CP) is Statamic’s web-based administration interface. It’s where content editors create and update entries, manage assets, and work with Taxonomies. It’s also where developers configure Collections, edit Blueprints, manage users and roles, and set up global site configuration. By default it lives at /cp.

The WordPress equivalent is the Dashboard — the /wp-admin/ interface. The two systems serve the same purpose, but the design philosophy behind each reflects how the underlying CMS works. WordPress’s admin grew organically over two decades and carries the complexity that comes with that history. Statamic’s CP was designed more deliberately and has a cleaner, more modern interface. Editors who are comfortable with contemporary web apps tend to find it intuitive.

One practical difference: Statamic’s CP is optional in a way WordPress’s admin isn’t. Because content is stored as flat files, a developer can bypass the CP entirely and work directly in the filesystem — editing Markdown files in a text editor, managing Blueprints as YAML files, and committing everything to version control. That’s not how most editorial teams want to work, but it means the CP is a convenience layer rather than the only access path to content.

The CP includes a live preview feature that lets editors see how content looks in a template before publishing. It supports user roles and permissions so you can give editors access only to the collections and features they need. There’s also a built-in asset manager for uploaded files and images, with support for image manipulation and focal point cropping.

Statamic’s CP is built with Laravel on the backend and Vue.js on the frontend. That combination makes it fast and extensible. The add-on ecosystem includes CP customizations — custom widgets, additional navigation items, and custom tools that appear in the admin interface. If your WordPress setup relied on admin customizations (custom menu pages, dashboard widgets), those can generally be replicated in Statamic through its add-on system.

For teams migrating from WordPress, the CP transition is usually smooth. The core concepts — editing content, managing media, configuring settings — are the same. The interface just looks different and, for most users, feels cleaner to use.