Skip to content

Working with Content

Use the EmDash admin to take an entry from its first draft to a published page. The editor keeps draft changes separate from the version visitors can see, so saving and publishing are two distinct actions.

Open /_emdash/admin on your site and sign in. Select a collection, such as Posts or Pages, in the sidebar.

The collection page lists its entries. From here you can:

  • select Add New to create an entry;
  • search by the entry title, slug, and fields marked as searchable;
  • filter by publishing state, author, byline, date, and locale;
  • move between pages of entries and choose whether a page shows 20, 50, or 100;
  • select entries for bulk publishing, returning to draft, or moving to Trash; and
  • open Trash to restore or permanently delete an entry.

The fields and publishing features available in the editor depend on the collection’s content model. For example, a collection may support revisions, previews, taxonomies, or search.

  1. Select Add New on the collection page.

  2. Complete the required fields. If the collection has a title field, EmDash uses it to suggest a slug. You can edit the slug before publishing.

  3. Add the body and any supporting fields, such as an excerpt, featured image, byline, categories, or tags.

  4. Select Save draft. The first save creates the entry as a draft and opens its permanent editor URL.

  5. Review the draft. If the collection supports previews, select Preview to see the rendered page before publishing.

  6. Select Publish now, then confirm. The saved draft becomes the live version that public content queries return.

The entry has a stable content ID and a separate slug. The ID continues to identify the same entry if its slug changes. Templates normally use the URL-facing identifier returned by getEmDashCollection(); the querying content guide explains both values.

On screens 1024px and wider, the settings panel sits beside the page. Select Hide settings at the end of the editor’s bar to give the page the full width, and Show settings to bring the panel back. Each browser remembers the choice. A hidden panel opens on its own for image and gallery settings, and when Save is blocked by an invalid field inside it. On smaller screens, the same button opens the panel over the page.

Portable Text fields provide a block editor for headings, paragraphs, quotations, lists, links, images, videos, galleries, code blocks, tables, HTML blocks, and reusable sections. Installed plugins may add more blocks.

Use the toolbar to format the selected text. To insert a block, select the add-block control beside a paragraph or type / and search for a block by name. Image and gallery blocks open the same media picker used by image fields.

To create a link with a multi-word label, type the label first, select the whole label, then choose Add link in the toolbar and enter the destination. If you add a link at an empty caret and then type its label, the link ends at the first space you type. Text after that space is not linked.

You can also drag image and video files into the editor or paste a copied image or screenshot. Each file uploads to the Media Library and appears between the surrounding blocks when the upload finishes. If an upload fails, the reason appears where the file would have gone.

When you select an image block, a toolbar appears above it. Use it to replace the image, edit its alt text, align it, add a link or a caption, or delete the block. The Alt text button is highlighted once the image has a description, and hovering it shows the description. Alt text that is only a Media Library image’s file name doesn’t count. To caption the image, select Add caption and type in the field that opens under the image, then press Enter to keep writing below it. The caption field stays hidden while an image has no caption. From a selected image, Tab moves to the caption and then the toolbar.

Image settings in the toolbar opens every setting for that use of the image, including its display size and optional tooltip. Edit asset there opens the underlying Media Library item, where changing or replacing the asset can affect other entries that use it. See Media Library for that distinction.

Type /video, then choose a video from the Media Library or upload one in the picker that opens. The video block is added once you choose a video. You can also drop a video file anywhere in the text.

The video plays in the editor as it will on your site, at the width of the text.

Hover over a video, or select it, to show Replace video, Add caption, and Delete video in its corner. Add caption opens a caption field under the video; press Enter there to keep writing below it. From a selected video, Tab moves to the player, where Space plays it, then to the caption and the three buttons. Escape returns to the block.

Uploads follow the Media Library’s size limit, maxUploadSize, which is 50 MiB unless you raise it.

An HTML block holds code the other blocks can’t express, such as an embed, a signup form or a small widget. Its tabs are HTML, CSS, JS and Preview. Each code tab is a code editor where Tab indents; press Escape to return to the surrounding text. The CSS and JS tabs are optional: you can also paste a whole snippet, with its <style> and <script> elements, into the HTML tab.

Preview shows the block as your site renders it. When you open an entry, a block that runs JavaScript waits until you select Run preview, so a broken script can’t freeze the editor.

The block’s menu sets how your site renders it:

  • Isolated frame runs the block’s HTML, CSS and JavaScript in a sandboxed frame that grows with its content. The frame can’t read your site’s cookies, storage or pages, and your site’s styles don’t reach it. Relative links resolve from your site’s root. After a visitor clicks inside the frame, it can open other pages in the visitor’s tab or a new one. New HTML blocks use this mode, but blocks pasted from another website or browser tab don’t. Don’t size content to the frame’s viewport, as with height: 100vh: the frame grows to fit it, which makes the content taller again, until the frame reaches 20,000 pixels.
  • Inline puts the HTML into the page, where it uses your site’s styles. Your site keeps text formatting, links, lists, tables, images and iframes, and removes other markup, such as scripts, <style> elements, style attributes, media and form controls. Iframes from sites other than YouTube and Vimeo are emptied. An inline block has no CSS or JS tab.

Search engines may not treat text inside an isolated frame as part of the page. Put text that matters for search in paragraphs or an inline block.

An iframe block shows a page from another site, such as a video, a map or a form. Type /iframe, then paste the site’s embed code or a link into the Code tab. YouTube and Vimeo links become their players, and any other https link is embedded as it is. Preview shows the embedded page. When you open an entry, a saved block waits until you select Load preview, so the admin doesn’t load other sites’ pages until you ask. Iframe blocks pasted from another website or browser tab arrive empty.

Only https pages can be embedded, and the block keeps only the parts of an embed code it needs: the address, the title, the size, full-screen support and the permissions players use. Some sites refuse to appear inside another site’s page; their preview stays blank or shows an error from that site.

An embed code that runs a script instead of an iframe, such as some social media posts, belongs in an HTML block.

After the first save, the editor autosaves changes two seconds after you stop typing. On tablet and desktop, the toolbar’s Save control appears while changes are unsaved, shows Saving… while the request is in progress, and disappears after a successful save. There is no persistent Saved label. A screen-reader-only status announces Saving… and Saved. An autosave replaces the version before it when that version is also an autosave, so a run of autosaves leaves one version in revision history. The new version keeps the names of everyone who edited the one it replaced.

On a phone, entries with drafts and revision history offer Show settings > Save draft even after autosave finishes. To retain the autosaved version in history, wait for autosave before using this action. On tablet and desktop, the toolbar’s Save action is only offered while there are unsaved changes. Both actions retain the preceding draft revision, and autosave never replaces the version they save. Autosave also never replaces a version EmDash creates itself, such as the draft that unpublishing an entry leaves.

If a save fails, the editor keeps the unsaved fields in place, shows a dismissible error banner below the editor header, and displays an error toast. Dismissing the banner does not save the data. Retry with the toolbar’s Save control when it appears, or on a phone use Show settings > Save draft when available. Keep the page open until a successful retry clears the banner and the saving control settles. If you must leave first, copy the unsaved work elsewhere.

For a published entry, saving changes updates its draft only. Visitors continue to receive the previous live revision. Use Preview draft to check the pending version, Live View to check the public version, and Publish changes when the draft is ready to replace it.

Changing the slug of a published entry follows the same draft flow. The public URL changes when you publish the draft, not when autosave runs.

Several people can edit an entry at the same time. Each person sees the others’ changes as they type, and everyone’s edits save together. Co-editing works in collections with revision support, on sites that turn on coEditing. It’s off by default. In the cases listed under Single-editor mode, the editor takes an edit lock instead.

Each translation is edited on its own, so people working on different locales of an entry don’t see each other.

  • The editor bar shows each other person who has the entry open as a circle with their photo, or their initials if they have none: up to three, then a count such as +2. Hover over or focus a circle to see the person’s name and the field they’re editing, or Viewing when they aren’t in a field. Select a circle to go to that person’s field, or select the count to list everyone.
  • The names of the people in a field appear at the end of its label row, in their colors.
  • In rich text, each person’s cursor and selection appear in their color. Their name shows at the cursor for a couple of seconds after it moves, and while you hover over it.

EmDash saves everyone’s edits together two seconds after the latest change, and at least every 10 seconds while people keep typing. Your Save button shows Saved once a save holds all of your own edits. Other people’s typing doesn’t change it.

Save keeps the current point in revision history, as it does when you edit alone. Each version in Revisions names everyone who edited it.

  • In rich text, undo reverts only your own edits. Other fields use the browser’s undo.
  • If you leave the entry before a save holds your edits, the editor asks you to confirm. Links within the admin first wait up to three seconds for the save.
  • If a save is refused, for example by a validation rule, everyone with the entry open sees the error. EmDash tries again after the next change.
  • Changes saved another way, such as through the REST API, MCP, the CLI, the visual editor or a plugin, appear in open editors within a second.
  • SEO settings, the author, the publication date, taxonomy terms, bylines and reference fields save separately from the rest of the entry. When two people change the same SEO setting, the author or the date, the later save is kept. Taxonomy terms, bylines and reference fields keep what each person adds and removes. Other people see the new value once they leave that field.

If your connection drops, keep typing. The editor reconnects on its own, then merges and saves your edits. After five seconds without a connection, the Save button shows Offline. Select it to see what happens to your edits until you reconnect. A shorter drop shows nothing.

While the editor is offline, Preview and the actions in Publish while others edit are disabled. Your offline edits exist only in that browser tab, so closing it loses them.

If no one was connected to the entry for an hour before you reconnect, your offline edits can’t merge. The editor saves them as a recovery revision instead, and tells you so.

Publishing, scheduling, unpublishing, discarding changes, restoring a version and moving the entry to Trash first save everyone’s edits, then run. Each action needs the same permission as when you edit alone.

  • Publishing makes everyone’s edits live as they were at that moment. Edits made after it are pending changes, which Publish changes makes live.
  • Other people with the entry open see a message such as Ana changed this entry.
  • Restore and Discard changes replace the fields they change. Text that anyone types into those fields while the action runs is lost, and no version holds it.
  • If the save before an action fails, the action doesn’t run, and the editor shows the error.
  • Preview opens its tab at once and loads the page once your edits are saved. If they can’t be saved, a tab that Preview opened closes, and the editor shows Preview opens once your edits are saved.
  • A Contributor can edit their own entry only while it’s a draft. Once it’s published or scheduled, their editor turns read-only.
  • When someone moves the entry to Trash, the other editors show it read-only, with a notice that it was moved to Trash or deleted. An editor with edits that weren’t saved yet keeps them instead, as Recovery revisions describes.

Rich text merges: when several people type in it at once, everyone’s text is kept. Other changes follow these rules:

  • Bylines, and reference fields that link several entries, keep what each person adds and removes. When two people change the same byline’s role at the same time, the later change is kept.
  • Every other field, including the title, the slug, block and repeater fields, and fields that plugins add, holds one value. When two people change one at the same time, one of the changes is kept, the same for everyone.
  • Turn into, dragging, deleting, wrapping a block in a list or quote, joining it with the block next to it, and indenting it all replace the block. Text that someone else types inside that block at the same moment is lost.
  • Text you type offline inside content that someone else deleted is lost.
  • When a script or another tool changes a field that someone in the editor changed since the last save, the editor’s value is kept and saved over it. Plugin writes, CLI and MCP updates, and REST updates without skipRevision create a version, so the replaced value stays in Revisions.

If you can view drafts but can’t edit the entry, such as an Author or Contributor opening someone else’s draft, the editor is read-only and shows others’ changes as they type. Others see you as Viewing.

An entry also opens read-only while the entry is already open in 25 tabs or in 5 of yours, and while the server is busy, for example because it’s restarting. The Save button shows Joining…, and the editor keeps trying until it joins. After a server stops unexpectedly, joining can take up to a minute.

In single-editor mode, the editor works as it does for one person, with an edit lock. It uses single-editor mode when:

  • the collection doesn’t support revisions;
  • co-editing is off, or the site’s host can’t run it;
  • the browser can’t open co-editing connections, for example because a proxy or network blocks WebSockets;
  • the entry is larger than 1 MB, or its rich text has formatting the editor can’t show;
  • the tab was opened before co-editing was available on the site, until you reload it;
  • you already have the entry open in a tab that uses single-editor mode; or
  • the site is partway through deploying a new EmDash version.

After a browser’s first three co-editing connections fail, it uses single-editor mode for every entry until the browser session ends.

When a tab in single-editor mode opens an entry that others are co-editing, EmDash shows People are editing this entry together. Select Join to edit with them, or Open read-only. When the browser can’t open co-editing connections, Join isn’t offered, and the entry opens read-only.

A recovery revision holds edits that EmDash couldn’t merge or save. It appears in Revisions with the other versions, and never becomes the draft or the published version. To use one, open it and select Restore. Restoring saves its fields as your edit and checks them as any save does.

EmDash saves a recovery revision in these cases:

  • The editor has to start again from a fresh copy of the entry while it holds unsaved edits, such as after you reconnect too late to merge. A message says that your unsaved edits are in a recovery revision.
  • EmDash is upgraded, or a collection, plugin or taxonomy definition changes, such as when someone adds a field. Within 15 minutes, open editors save their unsaved edits this way and reload the admin.
  • Edits stay unsaved for an hour after everyone leaves the entry, for example because every save failed validation.

When your edits can’t be saved at all, the editor keeps them in the tab, and the Save button shows Not saved with a message that says why. This happens when you lose edit access, when the entry is moved to Trash or deleted, or when the recovery revision itself can’t be saved. Select Copy my edits to copy the entry’s text and rich text fields as plain text, including lists and tables, then select Reload. Block, repeater, media and reference fields and the slug aren’t copied.

When an entry opens in single-editor mode, the editor takes an edit lock for that entry and locale. If another person already has it open in single-editor mode, EmDash identifies the lock holder and offers two choices:

  • Open read-only shows the entry without accepting edits, so you cannot type work that will be discarded.
  • Take over gives you the entry. The other person keeps what they typed, but within two minutes their editor reports that their changes are no longer being saved.

When the entry can’t be co-edited, their next save is refused. Otherwise, Take over removes their lock and opens the entry for co-editing, and their saves still reach the entry until their editor reports the change.

The lock is renewed while the entry is open and released when you leave the editor or close the tab. If the browser or computer closes without releasing it, the lock expires seven minutes after its last renewal.

Locks are independent for each locale, so two people can edit different translations of the same entry. A script, API client, or MCP client is also refused while another editor holds the lock unless it uses the documented override. While people co-edit an entry, it has no lock, so these writes land and appear in the editor. See Entry edit lock for the complete API behavior and Content lifecycle and bylines for the MCP tools.

An administrator can turn locking off for a collection under Content Types, then the collection, then Edit locking.

Publishing and scheduling use separate controls:

  • Publish now makes a new draft live after confirmation.
  • Publish changes makes pending changes to a published entry live after confirmation.
  • Schedule sets when a new entry or pending changes become live.
  • Change schedule updates an existing schedule.
  • Remove schedule cancels an existing schedule.
  • Unpublish removes the live revision from public queries, cancels any schedule, and keeps an editable draft.

In collections with revision support, the publish confirmation names everyone who edited the entry since the published version, or everyone who edited it when no version is published.

To schedule an entry, save it first, select Schedule below the publishing summary, and choose a future date and time. The editor displays the time zone used for the schedule. Until that time, the current live revision stays public; for a new entry, nothing is public yet.

Scheduling is available by default. A collection can disable creating or changing schedules with no-scheduling in its supports settings through a seed file, the schema API, or MCP. The Content Type editor has no checkbox for this flag. Existing schedules still run and can be removed.

Node.js deployments run the scheduled-publishing sweep automatically at the start of every minute, so an entry scheduled for a whole minute goes live at that minute. A schedule with seconds, which only the API and MCP can set, can go live up to a minute late. Cloudflare Workers require a Cron Trigger. The Cloudflare starter templates include it; existing deployments can follow Scheduled publishing to verify the trigger.

The calendar shows what was published and what is scheduled across your collections. Contributors and higher roles can open Calendar from the sidebar or the command palette. When something is scheduled, the dashboard’s Scheduled count also links to it.

The calendar has two views:

  • Month shows the month’s weeks at the height of the window. Each entry is one line with its title and, when there is room, its time. Hover over or focus an entry to see its full title, state, time, and collection. When a day has more entries than fit, select +N more to list them all.
  • Agenda lists the month by day, with each entry’s time. In the current month, days before today start collapsed unless one of them has an overdue entry, and a red line marks the present.

On a phone or another narrow screen, the calendar opens in Agenda, and Month shows a date picker with dots on the days that have entries. Select a day to list its entries.

Select an entry to open its details in a side panel, or Ctrl-click (Cmd-click on macOS) to open it in the editor in a new tab. The panel shows the entry’s state, time, collection, locale and translations, bylines, and when it was last edited. From the panel you can open the entry in the editor, preview scheduled changes, or view a published entry on the site. If you can publish the entry (Authors for their own entries, and Editors and higher roles for any entry), you can also reschedule it (unless its collection has no-scheduling), remove its schedule, or publish an overdue entry now. On a wide screen the panel sits beside the calendar; select another entry to switch to it, or select empty space to close it. On a phone, the panel opens as a sheet at the bottom of the screen; swipe it down to close it.

Use Filter to narrow both views by collection and state, and by locale on multilingual sites. The filters, the view, the month, and the open entry are kept in the page URL, so you can bookmark or share it.

Entries are placed on days in the site’s time zone, which the calendar names beside the month. If your browser uses a different time zone, the calendar says so, and the side panel and entry tooltips also show each time in your own time zone.

The calendar shows:

  • published entries on the date they were published;
  • scheduled entries on their scheduled date; and
  • scheduled changes to a published entry on their scheduled date, marked Update. Once the changes go live, the entry appears only on its original publication date.

A schedule that is more than two minutes past its time is marked Overdue. This usually means the scheduled-publishing sweep is not running; see Publish or schedule changes.

The calendar leaves out drafts without a schedule, entries in Trash, and collections hidden from the sidebar. The dashboard’s Scheduled count covers every month and includes hidden collections, so it can be higher than what the calendar shows for one month.

The calendar loads at most 1,000 entries for a month, including the days from neighboring months that the grid shows. When there are more, it says on which day the loaded entries end and marks the later days as not loaded.

Collections with revision support show Revisions in the settings panel. Expand it to see the entry’s saved versions, grouped by day. Each version shows its time and everyone who edited it since the version before it, such as “Ana, Ben, and 1 other person”. Current version marks the version in the editor, and Published marks the version visitors see. The list shows the 20 newest versions; select Show older versions to see the rest.

Select a version to show it in the editor, read-only:

  • Added text is highlighted and removed text is struck through, in the color of the person who edited the version, or in a neutral color when several people edited it. The dot next to the names in the list shows that color.
  • The version’s entry in the list describes each change, such as “Changed the title” or “Edited “Most teams plan posts in…””. Select a change to scroll to it.
  • Turn off Show changes to read the version without highlights.

Save and Publish pause while a version is open, and your unsaved edits stay in the editor. Select the × in the bar (Back to editing) or press Esc to return to them. On a phone, or while the settings panel is hidden, use the arrows in the bar at the bottom of the editor to step between versions.

To use a version again, select Restore in that bar. Restoring copies the version into a new draft at the top of the list. Your previous draft stays in the list, and visitors keep seeing the published version until you publish. If the entry is scheduled, the restored version goes live at the scheduled time.

A version whose content matches an earlier one is marked “Restored from” with that version’s date. A version that matches the current one shows Same as current version in place of Restore.

When internationalization is enabled, the Translations panel shows the configured locales for the current entry.

  1. Open the source entry and find Translations in the settings panel.

  2. Select Translate for a locale that does not yet have an entry.

  3. Edit the copied title, slug, body, and other translatable fields.

  4. Select Save, then publish or schedule the translation when it is ready.

Each translation has its own slug, publishing state, schedule, and revision history. Use the locale selector on the collection page to view one language at a time.

Open an entry’s actions or select one or more rows on the collection page, then choose Move to Trash. Trashed entries stop appearing in ordinary content queries but remain available on the collection’s Trash tab.

From Trash, select Restore to return an entry to the collection. A restored entry comes back as a draft with no schedule. Publish it to make it public.

Choose which entries the admin navigation shows and which sections the editor’s settings panel shows, and in what order, under Settings > Sidebars. You can also open the page with Customize sidebar at the bottom of the settings panel, or with the pencil at the bottom of the navigation.

  • The Navigation tab lists the navigation entries by group. Turn off an entry’s switch to hide it, and drag an entry to move it within its group or folder. Dashboard always stays first.
  • The Editor sidebar tab lists the settings panel’s sections. The order applies to every collection and to new entries, and a collection skips sections it does not use. Publish can move but cannot be hidden.
  • To move an entry with the keyboard, focus its drag handle and press Alt+Up or Alt+Down.
  • Reset restores the current tab’s default order and shows every entry again.

The layout is saved to your account, so it applies in every browser you sign in from, and it does not change anyone else’s sidebars. Hiding an entry only removes its link from your navigation. The page still opens from its URL.

The REST API and EmDash CLI support the same draft and publishing workflow. Collection fields belong inside the request’s data object. An update saves a draft revision; publishing is a separate action. Pass the latest _rev value when updating or publishing so the server rejects a stale write instead of replacing newer work.

Use the content lifecycle reference for state transitions, permissions, conflicts, and hooks. The REST API reference defines request and response bodies, and the CLI reference covers equivalent terminal commands.

Continue with Querying Content to render published entries in an Astro site, or Media Library to add and manage reusable files.