Astro gives you control over the frontend. ApostropheCMS provides the structured content, editorial tools, and true in-context editing behind it.
Not every Astro project needs one. Astro content collections and files can be a simple, effective choice when developers manage the content and updates naturally belong in the development workflow.
A CMS becomes more useful when content needs to be managed by a broader team, updated independently of code changes, reused across the site, translated, scheduled, or assembled into new pages. When nontechnical users are editors, the value of the CMS quickly increases.
ApostropheCMS adds that content-management layer without replacing Astro as the frontend.
You can keep the architecture and developer experience that made you choose Astro while giving the rest of your team the tools they need to manage the site.
Give content teams a dedicated editing experience instead of routing every copy change, image update, or new page through a developer and deployment workflow.
Developers still define the available components and content structure. Editors manage the content within those boundaries.
Continue using Astro for frontend components, styling, and custom frontend behavior.
ApostropheCMS supplies structured content and editing capabilities without imposing a proprietary frontend framework or replacing your Astro application.
Define structured pages, reusable content types, relationships, widgets, and editable page areas in ApostropheCMS.
Your Astro components decide how that content is presented, whether it appears on one page or is reused across many experiences.
Introduce media management, drafts, versions, previews, scheduled publishing, localization, permissions, and other CMS fundamentals without turning them into features your product team must build and maintain.
An ApostropheCMS and Astro implementation combines two connected projects with clearly divided responsibilities. They can live together in a monorepo or be maintained separately, depending on how your team prefers to work.
ApostropheCMS defines and stores:
Your Astro project remains responsible for:
The ApostropheCMS Astro integration:
ApostropheCMS lets editors manage content in the context of the Astro-rendered page rather than working from a disconnected form or a side-by-side approximation.
Developers determine which components editors can use, what fields each component contains, and which layout or style options are available. Editors can then add, arrange, and update content while seeing how it works within the actual page.
ApostropheCMS area fields define the regions where editors can add and organize content. Each widget placed in an area is rendered by the corresponding component in your Astro project. This gives editors meaningful flexibility without giving them unrestricted control over the frontend.
Some document fields and content relationships open in focused editing dialogs when that interaction is more appropriate. Editors still manage the content through ApostropheCMS while the Astro application controls how it appears on the site.
Create pages, reusable content types, relationships, widgets, and editable areas. Developers define the model while editors use it to create and maintain content.
Manage drafts, document versions, previews, scheduled publishing, media, and day-to-day updates without moving content changes through the codebase.
Support localization and translation, as well as user roles, permissions, and SSO as more people, regions, and teams become involved.
ApostropheCMS Community Edition is open source under the MIT License, with no user or content limits. Self-host it, extend it through its module system, and integrate it with the systems your application already uses.
Hybrid Apostrophe + Astro projects support both dynamic and static build styles. Gain the advantages of static builds for production while retaining the friendly editing experience of a dynamic site. ApostropheCMS runs side by side with Astro as a Node.js application. Your Astro frontend can be deployed separately, or right in the same container with Apostrophe.
For statically generated pages, published content must be incorporated into a new build before it appears on the public site. Server-rendered implementations can retrieve current content when a request is handled. The right model depends on how frequently content changes, how quickly updates need to appear, traffic levels and how you want to operate the editing and production environments.
ApostropheCMS supplies the content and editing foundation without taking that architectural decision away from your team.
You should not need a lengthy implementation to understand whether ApostropheCMS works for your Astro project.
Michelin uses ApostropheCMS and Astro as part of a digital platform supporting more than 350 websites across 36 languages, eight brands, and nine business lines.
The architecture allowed Michelin to modernize its frontend without forcing content teams to abandon the editorial environment they depended on. Astro controls the frontend experience while ApostropheCMS provides the shared content, editing, and multisite foundation behind it.
ApostropheCMS's visual editor continues to provide a user-friendly interface, enabling non-technical teams to manage content effectively without interfering with the headless architecture.
CTO, Consumer Experience Factory at Michelin
No. Your Astro project remains responsible for frontend components, styling, and frontend behavior.
ApostropheCMS provides the structured content and editing interface. The official integration maps Apostrophe page and widget types to the Astro components that render them.
Only while editing. Your public-facing site can be a static build, or the exact same dynamic Node.js application that serves the editing experience. The chocie is up to you.
Yes. We provide a full solution for static site builds, alongside a dynamic site for content editing. Astro developers also have the option of a dynamic site for use cases not well-served by a static build.
Editors can manage supported areas and widgets in the context of the Astro-rendered page. They can see how content works within the page as they update it.
Developers still control the available components, fields, styles, and frontend behavior. Some fields and relationships are managed in dedicated editing dialogs rather than directly inline.
Yes. Astro allows teams to use supported frontend frameworks such as React, Vue, Svelte, and Solid where needed.
ApostropheCMS integrates with the Astro project and does not require you to replace the frontend framework components you use within Astro.
Yes. ApostropheCMS Community Edition is available under the MIT License and includes the core CMS, editing, localization, SSO, media, SEO, and content-management capabilities needed to build an Astro website.
Paid editions add capabilities for teams with more advanced operational and multisite requirements.
Yes. The Astro frontend and ApostropheCMS application remain separate projects, connected through the official integration.
The amount of work depends on the existing project's component structure, content model, routes, and current content sources.
Keep the frontend components you chose Astro for. Add the structured content and editorial experience your project needs as it grows.
