EmDash CMS is a content management system built for websites made with Astro. The admin panel runs inside the same application as the public site, and your content lives in a database you configure. Templates written as Astro components decide how that content looks. EmDash is not a visual page builder: editors fill in fields, and templates decide where each field appears (why EmDash).

This article explains the moving parts in plain words, walks through one editing session with a made-up example, and sets out who owns what after handover. If you are weighing a move away from WordPress, read the companion piece on when to convert WordPress to EmDash afterwards.

Three parts: database, templates and runtime

It helps to picture an EmDash site as three layers.

  • Database. Holds your collections, entries, drafts and revisions. It is the source of truth for text and structured data. Media files are stored separately.
  • Templates. Astro components that read content and turn it into HTML. A field only reaches the public site when a template uses it.
  • Runtime. The server or platform that runs the application. EmDash supports Node hosting, and Cloudflare documents an official setup that runs the app on Workers with D1 for the content database and R2 for media (Cloudflare guide). Neither option is a maintenance-free static folder. Updates, access control and monitoring stay part of owning the site, and running costs depend on your provider and traffic.

How quickly a change becomes visible depends on how each page is built. Server-rendered pages ask the database for the current published content on the next request, so a change should appear on the next page load unless a cache in front of the site is still serving the older copy. Prerendered pages are generated during a build and need a rebuild before visitors see the change. Developers choose this per page. As an owner, know which model your most important pages use and how a rebuild or cache purge is triggered.

Collections give content its shape

A collection defines one kind of content and the form editors see for it. Each collection has a slug, and so does each field. Choose slugs deliberately: the admin lets you change labels later, but not slugs. Drafts, revisions, preview, routing and SEO features are switched on per collection, so one collection can allow preview while another does not. Admin users with the right permissions can add collections and fields from the panel, but a new field does not design or render anything by itself. It appears on the public site only after a developer updates the templates (collections).

A hypothetical content model for a service company

The table below is a design proposal for an imaginary cleaning company. It is not a client site and not a default EmDash template.

FieldWhat editors doWhat developers implement
NameType the service namePage heading, URL handling, title on the services listing
SummaryWrite one or two sentencesCard text on the listing, source for the meta description
BodyWrite the full description with headings and listsRich-text rendering and typography rules
ImageUpload a photo and select itMedia storage, image sizes, alt text handling, a fallback when empty
Contact CTAChoose the button label and the form it points toThe button component and the form behavior behind it

Suppose you later want a Pricing tier field. An admin with permission can add it to the Services collection in minutes. Nothing changes on the public site until a developer decides where the tier appears and updates the template. Treat schema changes and rendering changes as two separate jobs. The same split applies to the contact button. It points at a form, and where that form delivers, whether email or a CRM, is behavior that needs its own testing.

Walking through one edit

Here is the documented flow (working with content) applied to a made-up entry in the Services collection:

  1. Sign in to the admin panel at /_emdash/admin.
  2. Open Services and choose Add New.
  3. Complete the required fields. For this example: Name “Office cleaning”, Summary “Weekday evening cleaning for offices up to 500 square metres, with a fixed monthly price.”, a Body with a short “What is included” section, the image office-cleaning.jpg with alt text, and the CTA label “Request a quote” pointing at the quote form.
  4. Save draft. Pending edits differ from the public version, so visitors see nothing yet.
  5. Preview, if preview is enabled for the collection and the developer has implemented it.
  6. Choose Publish now, then confirm when the admin asks you to.
  7. Check the public result yourself. Open the services listing in a fresh window and look for the “Office cleaning” card with its summary. Open the page: the heading, image and “Request a quote” button should be there, and the button should lead to the quote form. If the page is prerendered, wait for or trigger the rebuild. If a cache sits in front of the site, you may need to wait or purge it.

Which of these actions you can take depends on your role permissions and on which features are enabled for that collection.

Responsibilities and limits

  • Editing can still affect layout. An oversized image, a very long title or unusual formatting in the body can make a page look wrong. Preview helps you catch this. It is not a guarantee.
  • Schema and rendering are different jobs. Adding a field or collection can be an admin task. Showing it to visitors, or adding a new page type, is template work for a developer.
  • Forms and integrations need their own tests. Submitting a test entry and checking it arrives is part of launch, not an optional extra.
  • Revisions are not backups. Revisions let you restore an earlier version of one entry. Recovery of the whole site needs a complete database backup suited to your database adapter, media backed up separately, matching application code and configuration, and the secret keys stored safely. The JSON export EmDash produces is for inspection and custom tooling and cannot be restored by EmDash (backups).

Who benefits, and when it is not the right fit

EmDash suits businesses with repeatable content types such as services, locations or articles, and a working relationship with a developer who maintains the templates. It suits teams who want editors working in forms rather than arranging layouts by hand.

It is a poor fit when the team wants to drag and drop freely on every page, when there is no developer available for template changes, or when the site depends on functionality that would have to be rebuilt. The companion article covers that last case in detail.

A short handover checklist

Ask your developer for these before you sign off:

  • A list of collections, what each is for, and which features are enabled on each.
  • Which pages are server-rendered and which are prerendered, and how a rebuild or cache purge is triggered.
  • The admin roles, who can publish, and who can change collections and fields.
  • Where database and media backups live, how recovery works, and where secret keys are kept.
  • Proof that each form delivers to the right inbox or system.
  • Who to contact for template changes and how long they usually take.

A useful next step

Take one content type on your current site and write its field list in the same table format as above, with a column for who edits it. Then write one sample entry the way the example above does. That gives a developer a starting brief for scoping an EmDash build. The full scope also depends on design, integrations and hosting. When you are ready, see our EmDash CMS development service.

Change note

2026-11-10: Rewritten to explain the database, template and runtime layers, add a hypothetical service-company content model with a sample entry, document the draft-to-publish steps including the publish confirmation, and separate admin schema changes from developer template work. Facts checked against the linked sources as of 2026-11-10. Documentation may change in later versions.

Sources