BUILD · THE CMS CORE
Every Praxis site runs EmDash, Cloudflare's own CMS, and EmDash's core runs unmodified. Its screens for content, media, comments, menus, redirects, users, plugins and settings come first in your admin, as EmDash made them. Around them, Praxis adds the copilot on every screen, the Composer for pages, and the rooms of the experience layer. These screens are EmDash's work. This page shows what each one does, and what changes when it runs on Praxis.
EmDash's screens come first in your admin's rail, in EmDash's own order: 43 screens behind the sign-in, as of October 2026, each known to the copilot by its plain name. Praxis's nine rooms follow them.
Content and content types
Media
Menus, widgets, sections and bylines
Edit menus directly. They are the same menus the Navigation room builds, and the copilot changes menus through Navigation, where a live header preview and a publish card wait. The copilot can also copy a menu for another language once you approve its card.
Widget areas, and the widgets in them.
EmDash's library of reusable sections. Sections that arrive with a migration join it.
Author records, and the fields each one carries.
Redirects and the 404 log
Users and roles
Plugins and the registry
Settings, backups and site export
The site's name and address, formats, and social links. On Praxis, renaming the site is passed on to your account.
The title separator, the default social image, Google and Bing verification, robots.txt, and an AI-training opt-out. On Praxis, the robots.txt box is set aside whenever a Praxis bot policy exists.
Passkeys. On Praxis, sign-in itself is managed through your Praxis account, and an emailed sign-in link is refused: "Sign-in is managed through your Praxis account."
Who may sign up by their email domain, and personal tokens, which read published content and drafts within their scopes and your role.
Email setup with test sends, backup settings, and the index of where each file is used. Taking or downloading a backup from that screen is not available yet.
Export the site as one transfer archive.
In a sentence: "Change the tagline" · "Let anyone with an address at our company's domain sign up".
Screen by screen
| Screen | What EmDash gives | On Praxis, and what the copilot may do |
|---|---|---|
| Dashboard | Your site's figures | Titled Praxis; the welcome popup skipped for customers arriving from their account |
| Pages, Posts | Lists, filters, bulk actions | "Add New" opens the Composer; a Composer page cannot be saved from EmDash's editor; publish, unpublish, trash and schedule wait for approval |
| Other collections, Calendar | Records in your own types; the publication calendar | Unchanged; scheduling waits for approval |
| Media | Folders, crop, focal point | Old preview links sent on to the working file; uploads, deletions and repairs wait for approval |
| Comments | The moderation queue | Moderation, bulk acts and deletion wait for approval |
| Menus | Direct menu editing | The same menus as Navigation; the copilot reads here, writes through Navigation, and copies a menu for another language after approval |
| Redirects | Rules and the 404 summary | Run first on every request, with 301 to 308, 410, 451 and patterns; every rule change waits for approval |
| Widgets, Sections, Bylines, Byline Schema | Widget areas, reusable sections, author records | Imported sections join the library; most writes wait for approval |
| Content Types and Relations | Schemas, fields, relations | Schema changes wait for approval |
| Users | The site's users | Roles managed in your Praxis account's Team; every change waits for approval |
| Plugins, Registry | Install and manage plugins | No installs or updates; no new powers for any plugin through the copilot; secret settings stay on screen; every plugin change waits for approval |
| Import | EmDash's WordPress wizard | Still there, beside the Migration room |
| Settings | General, Social, SEO, Security, email domains, tokens, Email, Backups, Media usage, Site transfer | Renames passed to the account; robots set aside under a Praxis policy; sign-in through the account; read-only tokens; settings changes wait for approval |
| Categories and Tags | Their rows in EmDash's menu | Moved to Site › Taxonomies, their one home |
When it publishes, schedules, uploads, moderates, redirects, changes a schema, a user, a plugin, a setting or a backup on EmDash's screens, it stops at a card first.
The copilot refuses a plugin's request for more.
The copilot refuses a plugin's secret settings, which are entered on the plugin's own screen.
EmDash's editor cannot save one, and EmDash's own Publish button applies the same publishing check as the Composer and the copilot.
Sign-in runs through your Praxis account, and "Open admin" passes you in at your own role.
A personal token reads published content and drafts within its scopes and your role.
Yes. EmDash's screens come first in your admin, as EmDash made them, and Praxis's rooms follow.
Yes, for content not built in the Composer, such as the records in your own collections. New pages and posts start in the Composer.
To Site › Taxonomies, with any groupings of your own.
EmDash's own wizard remains, and Praxis adds the Migration room our engineers use, with review, before and after, and every loss named.
No. Admins can manage the installed plugins on the Plugins screen. When the copilot changes one, it asks first, and it never grants a plugin new powers.
Settings › Site transfer exports the site as one transfer archive. Your measurement data has its own exports, on Privacy & Data.
Every AI action on your site goes through one governed gate.
Its core runs unmodified, as the published package. Everything Praxis changes on a screen, it changes from its own code around EmDash.
Comments