You're seeing Seahawk's original 2015 colors and logo. Thousands of WordPress sites maintained since.

Book a call Free rebuild
Home/Development/Astro CMS: How to Choose a CMS for Your Astro Site
Guide

Astro CMS: How to Choose a CMS for Your Astro Site

Published November 21, 2026 9 min read

Astro has no admin screen, so an "Astro CMS" is whatever you choose as the place content is written. There are four routes: Markdown files in the project's content collections, a Git-based CMS that edits those files for you, a headless CMS that Astro reads through an API, or EmDash, a full CMS built for Astro. The right one depends on who edits the site, how often, and how quickly changes need to go live.

We run seahawkmedia.com on Astro and build Astro and EmDash sites for clients, so this guide is the decision we walk teams through. If you are new to Astro itself, start with our plain-English guide, What Is Astro?

How content gets into an Astro site

Astro renders pages from data. That data can be read when the site is built (the default, producing static HTML) or when a page is requested (on-demand rendering, which needs an adapter for your host). Every CMS option below is a different answer to two questions: where does the content live, and when does Astro read it?

Option 1: Content collections and Markdown

The simplest Astro CMS is no CMS. Content lives in Markdown or MDX files in the project, grouped into content collections. You define each collection and its fields in src/content.config.ts, and Astro checks every file against that schema when it builds:

import { defineCollection, z } from 'astro:content';
import { glob } from 'astro/loaders';

const blog = defineCollection({
  loader: glob({ pattern: '**/*.md', base: './src/content/blog' }),
  schema: z.object({
    title: z.string(),
    description: z.string(),
    pubDate: z.coerce.date(),
  }),
});

export const collections = { blog };

If a post is missing its title or has a bad date, the build fails with a clear error instead of publishing a broken page. Content is versioned in Git with the code, costs nothing to host, and can never go down separately from the site.

Good for: developer-run blogs, documentation, and brochure sites that change a few times a year. Not good for: non-technical editors who need a login, a media library, and a publish button.

Option 2: A Git-based CMS

A Git-based CMS puts an editing interface on top of the same Markdown files. Editors log in, fill in forms or a rich-text editor, upload images, and press save. The CMS commits the change to your repository, and your host rebuilds and deploys the site. Common choices include Keystatic, TinaCMS, Decap CMS, and CloudCannon. Each has its own approach to visual editing, authentication, and hosting, so check how editors sign in and whether they need a Git account.

Good for: small teams that want a friendly editor while keeping content in the repository and hosting simple. Watch for: each save triggers a build, so changes take as long to go live as the build takes; large media libraries do not belong in Git; and workflows such as approvals and scheduling vary by product.

Option 3: A headless CMS

A headless CMS stores content in its own database and serves it through an API. Astro fetches it at build time, usually through a content loader so it gets the same schema checks as local files, or at request time for pages rendered on demand. Editors work in the CMS; developers build the templates in Astro.

WordPress as a headless source

If your team already knows WordPress, keep it as the editor and let Astro render the site. Astro reads posts, pages, and custom fields through the WordPress REST API or WPGraphQL. Editors keep their workflow, the public site becomes fast static HTML, and WordPress can sit behind a login where visitors never reach it. The trade-offs are two systems to host and that page-builder layouts do not render on the Astro side. Our headless WordPress guide walks through the setup.

Sanity

Sanity is a hosted content platform with a customizable editing studio built in React. Developers shape the studio around the content, and it offers an official Astro integration and visual editing tools. It suits teams with structured content and the developer time to configure the studio well.

Contentful

Contentful is a hosted, API-first platform with strong content modeling, localization, and environments for testing changes. It suits organizations that deliver the same content to several sites or apps. Editors work in forms rather than on the page, so set up previews early.

Storyblok

Storyblok is a hosted headless CMS built around reusable components and a visual editor that shows changes on the real page as editors type. It has an official Astro SDK, which makes it a common choice for marketing teams that want visual editing on an Astro site.

Other headless platforms such as Strapi, Payload, Directus, and Hygraph work with Astro in the same way. The pattern does not change: Astro reads an API, and the quality of the editing experience depends on the CMS and on how carefully the content model and previews are built.

Option 4: EmDash, the CMS built for Astro

EmDash is an open-source, MIT-licensed CMS written in TypeScript, built specifically for Astro. It started at Cloudflare and reached a stable 1.0 in September 2026. Editors get a WordPress-style admin with posts, pages, media, menus, taxonomies, drafts, revisions, and scheduling. Content types are defined in the admin, each one a real database table, and EmDash generates TypeScript types from them for your Astro templates.

The difference from a headless CMS is that the CMS and the website are one project rather than two systems joined by an API. Plugins from its registry run in an isolated sandbox with only the permissions they declare, and every site ships with an MCP server so AI tools can draft and edit content under the same roles as your team. It runs on Cloudflare Workers with D1 and R2, or on a Node.js server with SQLite, PostgreSQL, or libSQL. The ecosystem is young, so check that the integrations you need exist. Our EmDash page covers when we recommend it, and our stack page shows how EmDash, Astro, and WordPress combine.

The options compared

OptionWhere content livesHow editors workHow changes go liveGood for
Content collectionsMarkdown files in GitIn a code editorCommit, then rebuildDeveloper-run blogs, docs, brochure sites
Git-based CMSMarkdown files in GitA web editor that commits for themSave, then rebuildSmall teams with occasional edits
Headless WordPressWordPress databaseThe WordPress adminWebhook rebuild, or on-demand pagesTeams that already know WordPress
Sanity, Contentful, StoryblokThe vendor's cloudThe vendor's editorWebhook rebuild, or on-demand pagesStructured or multi-channel content, visual editing
EmDashEmDash's database, in the same projectA WordPress-style adminPages render from the databaseNew content sites, TypeScript teams, AI-assisted publishing

How editing and previews work

This is where Astro CMS setups succeed or frustrate editors, so plan it before you pick a platform.

Publishing on a static site

On a pre-built site, a change in the CMS is not live until the site rebuilds. Most headless and Git-based CMSs send a webhook to your host when content is published, which starts a build and deploy. For a small site that takes a minute or two. For a site with tens of thousands of pages, build time becomes a real constraint, and you may render some sections on demand instead.

Previewing drafts

Editors need to see a draft on the real design before publishing. The usual pattern is a preview route in Astro that renders on demand (with export const prerender = false), fetches draft content with a preview token, and stays out of search results. Storyblok, Sanity, and TinaCMS go further with visual editors that update the page as editors type. EmDash avoids the separate preview chain because the admin and the templates are in one project.

Media

Decide where images live. Headless platforms usually host media and serve resized versions from their own image service. With Markdown, images sit in the project and Astro's image tools optimize them at build time. Large libraries belong in object storage, not in Git.

How to choose a CMS for an Astro site

  1. Who edits, and how often? Developers only: content collections. Occasional non-technical edits: a Git-based CMS. Daily publishing by an editorial team: a headless CMS or EmDash.
  2. Do you already have a CMS? If your content and editors are in WordPress, headless WordPress is the shortest path. If you run Contentful or Sanity for other channels, reuse it.
  3. How structured is the content? Many related content types point to a headless CMS or EmDash. A blog and a few pages do not need one.
  4. How fast must changes go live? If minutes matter on a large site, plan on-demand rendering or a CMS like EmDash that renders from its database.
  5. Who runs it? Every extra system is another login, bill, and set of updates. Choose the smallest setup that meets the editors' needs.
  6. Will AI tools publish content? If agents will draft or update content, look at how the CMS grants them permissions. EmDash's MCP server is designed for this.

For brochure sites, our WordPress vs Astro guide often settles the question before a CMS is needed at all. When you are ready to build, our guide to building an Astro website covers the project from setup to launch.

Where Seahawk fits

Em Workers builds EmDash and Astro sites for small businesses, including the content model, editor setup, and training. For enterprise headless projects, Seahawk VIP builds Astro front ends on WordPress, EmDash, and other headless platforms. Web hosts that want to offer EmDash and Astro to their own customers can use Em Region, our fleet modernization and care platform for web hosts.

Frequently asked questions

Does Astro have a built-in CMS?

No. Astro builds and renders pages but has no admin screen or login for editors. It does have content collections, which let you keep Markdown and data files in the project with a schema that Astro checks on every build. For a web editor, add a Git-based CMS, a headless CMS, or EmDash, which was built specifically for Astro.

What is the best CMS for Astro?

It depends on your editors. Developers are often happiest with Markdown in content collections. Small teams with occasional edits do well with a Git-based CMS. Teams that already use WordPress can run it headless. Structured or multi-channel content suits Sanity, Contentful, or Storyblok. New content sites that want a full admin in the same project suit EmDash.

Can I use WordPress as a CMS for an Astro site?

Yes. WordPress works as a headless CMS: editors keep using the WordPress admin, and Astro reads content through the REST API or WPGraphQL and publishes fast pages. It is a common way to modernize a site without retraining editors. Plan for two systems to host and maintain, and rebuild page-builder layouts as Astro components.

How do editors preview changes on an Astro site?

With a headless CMS, you add a preview route in Astro that renders on demand, fetches draft content with a preview token, and is kept out of search results. Some platforms, including Storyblok, Sanity, and TinaCMS, offer visual editors that update the page live. With EmDash, the admin and templates are in one project, so previews use the real design.

Do content changes require a rebuild?

On a pre-built static site, yes: the CMS sends a webhook, the host rebuilds, and the change goes live when the deploy finishes. On small sites that is quick. For large sites or content that must update instantly, render those pages on demand, or use a CMS such as EmDash whose pages render from its database.

Is EmDash a headless CMS?

Not in the usual sense. A headless CMS is a separate system that your site reads through an API. EmDash is a full CMS for Astro: the admin, the database, and the Astro templates are one TypeScript project. It does offer a REST API and an MCP server, so other tools and AI agents can read and write content too.

Em Workers

EmDash and Astro sites at revolutionary pricing.

Lightning-fast, secure websites delivered on EmDash and Astro. For the AI-curious bunch.