Skip to content

Expand the EmDash CMS guide from stub to full guide - #14428

Open
danielmlr wants to merge 1 commit into
withastro:mainfrom
danielmlr:add/emdash-cms-guide
Open

Expand the EmDash CMS guide from stub to full guide#14428
danielmlr wants to merge 1 commit into
withastro:mainfrom
danielmlr:add/emdash-cms-guide

Conversation

@danielmlr

@danielmlr danielmlr commented Aug 19, 2026

Copy link
Copy Markdown
Contributor

Description (required)

This replaces the EmDash stub page with a full CMS guide. It follows the structure of the Keystatic guide, the other CMS that runs inside the Astro project.

The guide covers adding EmDash to an existing Astro project: installing the packages, registering the integrations, adding the live collections loader, completing the setup wizard, creating a post, and rendering content with getEmDashCollection() and getEmDashEntry(). It closes with a short deployment section and the existing official resources.

Every step and code block was run against a fresh Astro project (Astro 7.2.3, emdash 0.34.0, Node 26): install, setup wizard, post creation, and both rendering examples, including the not-found redirect.

Two details in the guide come from that verification rather than from the EmDash docs:

  • A note that pnpm blocks the native build scripts of better-sqlite3 and esbuild by default, with pnpm approve-builds as the fix. Without the approval, the SQLite driver fails at runtime.
  • A note to complete the setup wizard before testing your own pages. Until setup is complete, queries return empty results, so the guide puts the wizard before the rendering steps.

The single-entry example checks only if (!post) and redirects, without a separate error branch. In the current EmDash release, getEmDashEntry() sets error for an unknown slug as well, so the error-then-404 pattern from the EmDash docs turns every unknown URL into a 500.

References

@astrobot-houston

astrobot-houston commented Aug 19, 2026

Copy link
Copy Markdown
Contributor

Lunaria Status Overview

🌕 This pull request will trigger status changes.

Learn more

By default, every PR changing files present in the Lunaria configuration's files property will be considered and trigger status changes accordingly.

You can change this by adding one of the keywords present in the ignoreKeywords property in your Lunaria configuration file in the PR's title (ignoring all files) or by including a tracker directive in the merged commit's description.

Tracked Files

File Note
en/guides/cms/emdash.mdx Source changed, localizations will be marked as outdated.
Warnings reference
Icon Description
🔄️ The source for this localization has been updated since the creation of this pull request, make sure all changes in the source have been applied.

@danielmlr
danielmlr force-pushed the add/emdash-cms-guide branch from 3d8e7fe to 6c3a98a Compare August 19, 2026 13:47
@github-actions

github-actions Bot commented Aug 19, 2026

Copy link
Copy Markdown

Preview deployment

✅ Deployment complete!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants