Menu

English,

Templates

EmDash templates and themes: how to choose one before you buy

An EmDash template is an Astro project you own, not a package you install. Nine things to check in the demo, the repository and the licence before choosing one.

Palm trees in silhouette on a Hawaiian beach under a purple and pink sunset sky.

Aloha Pixel6 min read

Choosing an EmDash theme is not like choosing a WordPress theme. You are not picking a skin that the CMS loads and that you can swap next month. You are picking the source code of your site. That changes what is worth checking.

This is the list we would use ourselves, as people who build and sell EmDash themes. Each point says where to look. Where it applies, we say how our own themes answer, so you can hold us to the same list.

1. Know what you are getting: a project, not a package

The EmDash documentation is clear on this: a theme is a complete Astro project, distributed as a template. There is no runtime theme package. Once you scaffold it, the files belong to your site and you edit them directly: routes in src/pages/, shared markup in src/layouts/ and src/components/, styles in src/styles/.

Two consequences:

  • There is no theme switcher. Changing theme later means rebuilding the front end.
  • The quality of the code is the product. Ask to see the file tree, or at least the README, before paying.

EmDash ships free templates that set the baseline: blank, starter, blog, portfolio and marketing. A paid theme should give you something those do not.

2. Which EmDash version is pinned

Open package.json and read three lines: emdash, the adapter, and the admin package if it is listed. A theme that says nothing about its EmDash version leaves you to find out.

It matters because the Cloudflare adapter and emdash share a version and must be updated together, and because a release can add database migrations. EmDash 1.5.0, published on 11 November 2026, added six on our sites.

Our seven themes pin emdash, @emdash-cms/cloudflare and @emdash-cms/admin to 1.5.0 exactly. The version is written in each theme changelog.

3. Who carries the upgrades

The official updater bumps packages and writes a work order. The updating guide says what it leaves alone: template files such as layouts, components and astro.config.mjs. Those are yours.

So ask the seller two questions. When EmDash releases, how long until the theme follows? And how do I receive the change: a new archive to diff by hand, or something more precise?

Look for a dated changelog. One entry per release, naming the EmDash version, is a good sign that someone is doing the upgrade before you have to.

4. Where it deploys

EmDash runs on Cloudflare (Workers, D1, R2) or on a Node.js server with SQLite. A theme is configured for one of them: the official templates come in a Node variant and a -cloudflare variant, and the documentation asks theme authors to state the target.

Check that the target is yours. Moving a theme from one to the other touches the adapter, the database and the media storage.

Our themes build two ways from the same repository. By default pnpm build writes plain HTML that any static host serves, with no CMS. With the engine switched on, the same pages are rendered by a Cloudflare Worker on EmDash. The engine needs a Cloudflare account; the static site does not.

5. What the seed contains

The seed file is the content model the theme installs: collections and fields, menus, settings, taxonomies, widget areas, sections, sample content. EmDash applies it once, to an empty database, during the setup wizard. Later builds do not reapply it. The documentation says it plainly: a seed is not a migration system.

So the model you get on day one is the one you will live with, and what you change afterwards is your work. Before choosing:

  • Read seed/seed.json. Are the collections the ones your site needs?
  • Run the setup twice, with and without sample content. The theme should render in both cases.
  • Open a route with an empty collection and an entry without its optional image. A theme that only works with its demo content is a demo.

6. What an editor can change

This is the question clients ask, in other words. In EmDash, values an editor should change live in settings, content, menus or widgets. Static design copy can stay in Astro files. Neither is wrong, but you need to know which is which before promising a client that everything is editable.

In the demo admin, try this:

  • Change the site title, a menu item, a hero title and an image. Reload the public page.
  • Empty a field. Does the section fall back to something sensible, or does it leave a hole?
  • Look at the screen of one section. Does it show only the fields that do something, or every field of the collection?

If the seller offers no demo admin, ask for a screen recording of these three actions.

7. Languages

If you need more than one language, check how the theme does it, not just that the demo has a language switch. One page source per route with a dictionary is easy to maintain. Duplicated page files per language are not.

Ours are English at the root and French under /fr/, from one source per route. The dictionary is a typed object: a missing French key is a build error, not an English sentence in production.

8. What the theme adds to the back office, and how

A theme can ship plugins. EmDash has two formats. A sandboxed plugin runs in a separate runtime and is limited to the APIs it declares. A native plugin runs in the same process as the site, with full access, and can add React admin pages; it comes from npm through the Astro configuration and needs a deploy.

Native is the only way to do some things, and it also means you are trusting that code as much as your own. For each screen the theme adds, ask which format it uses and whether you can read its source.

The shop, stock and CRM screens of our themes are native code, delivered as readable source inside the theme. The other side of that choice: they depend on the admin version, and we adapt them at each EmDash release. Every plugin our templates ship, and the licence that includes it, is listed on the EmDash plugins page.

9. The licence and the tests

Read the licence for three things: how many developers one purchase covers, whether client projects are included, and what happens to updates. Ours covers one developer, unlimited end products for yourself or clients, and updates until the next major version. Redistributing the theme itself is the one thing it forbids. The full text is on the licence page.

Then look for tests. A theme you will modify needs a way to tell you what you broke. Check that the repository has a type check and a test command, and run them on a fresh clone before you change a line.

The short version

  • It is source code: read it.
  • EmDash version pinned and written down.
  • A dated changelog that follows EmDash releases.
  • A deployment target that is yours.
  • A seed that matches your content, and routes that survive empty content.
  • A demo admin where you can change and empty fields.
  • Languages from one source.
  • Back office additions you can read.
  • A licence that covers client work, and tests that run.

Our seven EmDash templates and their demos are on the templates page, and their plugins on the EmDash plugins page. The documentation is public: you can read how a theme is installed and deployed before buying one. If you are choosing for a client who is not a developer, our agency site has EmDash explained for small business owners.

Keep reading

All articles