WotWP Blog

Can I still edit my own site after it moves?

A blank white card taped to a blue background with a strip of kraft tape labeled YOURS, with a plain wooden pencil resting across it

The short answer

Yes. After a move from WordPress to EmDash you still sign in to an admin panel in your browser and change your own pages, posts and images, with drafts, revisions you can read and undo, scheduled publishing, preview links and passkey sign-in. What changes is the layout: EmDash edits your content, not your page design, so a new layout is a change to the site's templates, made by whoever looks after the site.

  • Everyday editing stays in your hands. Write, save a draft, preview it, publish or schedule it, and undo it later. The live page does not change until you publish.
  • You decide who signs in and what they can do. Passkeys replace passwords, and five roles let a helper write drafts without being able to publish.
  • The layout is the part that moves out of your hands. There is no page builder and no theme screen. There is also no WordPress plugin update screen to keep up with.
  • AI assistants are optional, and they get only the access you give them. An assistant can draft for you inside the same roles a person would have.

If you move with us, we invite you to the editor when your site goes live and email you a short guide to your first edit.

What editing looks like day to day

Editing an EmDash site works much like editing in WordPress: you open the admin panel, pick Pages or Posts from the sidebar, open an entry and type. The difference is that saving and publishing never happen by accident. "The editor keeps draft changes separate from the version visitors can see, so saving and publishing are two distinct actions" (EmDash docs).

Here is a normal edit, start to finish.

  1. Open the page you want to change. The page list has search and filters by state, author and date, so a site with 200 pages is still quick to find your way around.
  2. Type your change. The rich-text editor handles headings, lists, links, images, videos, tables and more. Type / to add a block, or drag an image straight into the text.
  3. Let it save. After the first save, "the editor autosaves changes two seconds after you stop typing" (EmDash docs). On a page that is already live, saving only updates the draft: "Visitors continue to receive the previous live revision."
  4. Preview it. Preview draft shows the page as it will look. You can also send a preview link to someone who has no login, such as a business partner. EmDash's preview links are "secure, time-limited URLs" that show one draft and stop working when they expire (EmDash docs).
  5. Publish it, or schedule it. Publish changes makes the draft live. Schedule picks a future date and time, and the editor shows which time zone it uses.
  6. Check the calendar. Since EmDash 1.1 in October 2026 (EmDash 1.1), a publishing calendar "shows what was published and what is scheduled across your collections", in a month view or an agenda list that works on a phone (EmDash docs).

Undoing a change

Every saved version stays in a revisions list, and since EmDash 1.3 you can read what changed without decoding anything. The release notes put the old problem plainly: before 1.3, "the Revisions panel showed changes as raw JSON, and didn't say who made them" (EmDash 1.3). Now you select a version and it opens in the editor, read-only. "Added text is highlighted and removed text is struck through, in the color of the person who saved the version," and the list describes each change in words, such as "Changed the title" (EmDash docs).

Going back is one button. "Restoring copies the version into a new draft at the top of the list," and visitors keep seeing the published version until you publish (same source). Nothing you restore goes live by surprise. A page you delete goes to the trash first, and you can restore it from there.

Two people editing the same page is handled too. Opening a page takes an edit lock, so a second person sees who has it open and can choose Open read-only or Take over. Neither of you silently overwrites the other.

Editing on the page itself

EmDash also lets you change some things by clicking them on your live site while you are signed in. A small toolbar appears on public pages for signed-in editors, and the EmDash 1.3 release says "Visual editing lets you edit rich text directly on the site" (EmDash 1.3). It works on the parts of a page the site's templates mark as editable. On the sites we build today, that is each entry's title and featured image. The rest of the text you change in the editor, which is where most people do their writing anyway.

Where things you know from wp-admin live now

What you do in wp-admin today

Where it is in EmDash

Edit a page or post

Pages or Posts in the sidebar, then the rich-text editor

Save a draft

Save, plus autosave two seconds after you stop typing

Preview before publishing

Preview draft, or a time-limited preview link you can share

Schedule a post

Schedule in the editor, and the publishing calendar

Restore an older version

Revisions, with added and removed text marked, then Restore

Upload images and set alt text

The media library, or drag the file into the editor

Edit the SEO title and meta description

The SEO panel on each entry

Edit a menu

Menus, for menus your site's templates display

Add a user

Users, then Invite User with a role

Update plugins and the theme

Nothing to update. There is no WordPress core, theme or plugin left to patch

Change a page's layout or design

A template change, made by whoever looks after the site

Two rows need a word. The SEO panel holds the "SEO Title", "Meta Description", "Canonical URL" and a switch to hide a page from search engines, much like the Yoast or Rank Math box you may be used to (EmDash docs). Menus work the same way they do in WordPress, with one limit: "Adding a menu item or widget in the admin only changes the public site when an Astro component queries and renders that menu or widget area" (EmDash docs). In plain terms, you can edit the menus your site shows, but a brand-new menu in a new place on the page is a template change.

Who can sign in, and what they can do

You sign in with a passkey, and you decide who else gets in and with which role. "EmDash uses passkey authentication as its primary login method," and passkeys "don't require passwords, and work across devices through your browser or password manager" (EmDash docs). A passkey is the fingerprint, face or PIN check your phone or laptop already uses, so there is no admin password to forget, share or have stolen.

A few things worth knowing on day one:

  • Add a second device. Each person can register up to 10 passkeys. The docs' own tip is to "Register passkeys on multiple devices (e.g., laptop and phone) to ensure you always have a way to log in."
  • Email is the backup. On a site with email set up, a sign-in link can be sent instead. It works once and expires after 15 minutes.
  • Invites are links. An admin invites a person by email with a role. "Invite links are single-use and expire after 7 days."

The five roles, in EmDash's own words (EmDash docs):

Role

What it can do

Who it suits

Subscriber

"Read published content (no draft access)"

Rarely needed on a business site

Contributor

"Create content and edit own drafts (needs approval to publish)"

A freelance writer, or an AI assistant

Author

"Create/edit/publish own content"

A staff member who writes their own posts

Editor

"Manage all content"

An office or marketing manager

Admin

"Full access including settings"

The site owner

The server enforces the roles. "Hiding a navigation item is not the security boundary," the docs say, and "The server checks permissions for each action" (EmDash docs).

What changes from wp-admin

The part that changes is design. "EmDash manages structured content; it is not a visual page builder" (EmDash docs). Structured content means each page is made of named fields, such as a title, a body, an excerpt and a featured image, and the site's templates decide how those fields are laid out. The docs put the split in one line: the admin "manages data and configuration. Astro pages and components still define the public layout" (EmDash docs). Astro is the framework EmDash is built on, the code that draws your pages.

In practice:

  • Words, images, posts, pages, menus and SEO fields are yours to change, any time, without asking anyone.
  • A new layout, a new section type or a new color scheme is a template change. It is made in the site's templates by whoever builds and looks after the site, not in the editor.
  • There is no theme or plugin screen to manage. Once the whole site has moved, there is no WordPress core, theme or plugin left for you to patch. You lose the freedom to install something on a whim, and you lose the update chores that came with it.

If your WordPress site was built in Elementor or Divi, this is the biggest adjustment. Our guide to what survives a move away from Elementor and other page builders covers what happens to builder layouts.

Using an AI assistant to edit, if you want to

You never have to use AI on an EmDash site, and when you do, the assistant gets no more access than a person with the same role. EmDash includes a built-in connection for AI assistants, called an MCP server, that "lets AI assistants work directly with your site's content. You can ask Claude, ChatGPT, or other tools to draft posts, update pages, manage media, search your content, and more" (EmDash AI tools guide). This is the practical meaning of bringing your WordPress site into the AI era on EmDash and Astro: an assistant can do the typing, and you keep the publish button.

The limits are set by the role the assistant signs in with. From the same guide:

Role

What the AI can do

Admin

"Everything, including schema changes and updating site settings"

Editor

"Manage all content, media, bylines, taxonomies, and menus. View schema and read settings."

Author

"Create content; edit and publish owned content; upload media and manage owned media."

Contributor

"Create draft content, edit owned drafts, and upload media, without publishing."

When you connect an assistant, EmDash shows a consent page listing the permissions it asked for, and you can clear any it does not need. "The resulting token is limited to the permissions you keep selected and the permissions allowed by your EmDash role, so granting fewer permissions never increases what the client can do" (same source).

The guide's advice is the sensible default: "Ask the AI to create content as a draft, review it in the admin panel, then ask the AI to publish it – or publish it yourself." It also suggests asking the assistant to "Compare the live and draft versions of this post" before anything goes live. And it is honest about the limit: "complex formatting is best done in the admin editor." If you would like help connecting one, we set it up with you.

Who should stay on WordPress

If you rearrange your own page layouts every week in a page builder, and that is the part of the site you enjoy, stay on WordPress. On EmDash you are in charge of the words and pictures, and a layout change becomes a request.

Stay put as well if:

  • You like installing plugins and trying new themes yourself. WordPress gives you more of that freedom, along with the upkeep.
  • Your daily work happens inside a plugin, such as a store, a member area, an online course or a complex booking system. Those sites are not a fit for a move yet.
  • The site works, costs you little, and editing it does not bother you. Being able to edit is not a reason to move on its own.

Our guide to whether your site is a good candidate to move has five questions to settle it, and the fit guide gives the short version. For the bigger picture, see EmDash vs WordPress: what changes for a small business site, or start with what EmDash is.

How editing is handed over when we move your site

When your site goes live, an invitation comes from your site's own address, separately from our emails, and its button opens the EmDash editor. You accept it and choose how you sign in. We also email you a short guide to your first edit: open a page you know well, change a sentence, save it, and look at the page on your site. If anything works differently from those steps, you reply and we help.

If you would rather have someone walk you and your team through the editor, editor training is a $149 add-on, listed with the rest on our pricing. The conversion itself starts at $790 for up to 25 pages. Before launch, we check every URL, redirect, form, title, description, canonical and schema against your live site, and your WordPress site stays live until you approve the new one.

To see whether your site is a good fit and what it would cost, check your site for free.

Frequently asked questions

Can I still edit my website after leaving WordPress for EmDash?

Yes. You sign in to an admin panel in your browser and edit your own pages, posts, images, menus and SEO fields, with drafts, previews, revisions and scheduled publishing. The live page stays as it is until you publish. What you do not edit there is the layout, which lives in the site's templates.

Is the EmDash editor hard to learn if I know WordPress?

Most of it will feel familiar. You pick Pages or Posts, open an entry, type, save and publish, and the rich-text editor adds blocks when you type a slash. The new habits are passkey sign-in, the separate Save and Publish steps, and asking for layout changes instead of making them in a page builder.

Can I undo a change on an EmDash site?

Yes. Every saved version stays in the revisions list, with added text highlighted and removed text struck through. Restoring a version copies it into a new draft, and visitors keep seeing the published page until you publish again. A deleted page goes to the trash first, so you can bring it back.

Can I schedule posts on EmDash?

Yes. Save the entry, choose Schedule and pick a future date and time, and the editor shows the time zone it uses. Since EmDash 1.1 there is also a publishing calendar with a month view and an agenda list, so you can see what went out and what is coming up.

Can I give my office manager or a writer access?

Yes. An admin invites each person by email with one of five roles. A writer can be a Contributor, who writes drafts but cannot publish. An office manager can be an Editor, who manages all content. Invite links work once and expire after seven days, and each person signs in with their own passkey.

Can I change my site's design myself on EmDash?

Not the way a page builder works. EmDash edits structured content, and the page layout lives in the site's templates. You change words, images, posts, menus and SEO fields yourself. A new layout or color scheme is a template change, made by whoever looks after the site.

Do I have to use AI to edit an EmDash site?

No. EmDash works the same whether or not you use AI. If you want help, you can connect an assistant such as Claude or ChatGPT, and it gets only the access of the role and permissions you approve. A Contributor-level assistant can write drafts but cannot publish them.