The Visual CMS for Astro
Astro doesn't ship with a CMS. Pagesmith is one. Edit pages and blog posts in a visual editor, publish in one click, and keep a real Astro codebase you own — no headless CMS to wire up, no rebuilds to manage.
Why Astro Needs a CMS
Astro is one of the best frameworks for fast, content-driven sites — but it has no built-in content management. Out of the box, editing content means editing code. That's fine for a solo developer and a wall for everyone else.
Content lives in code
Pages and posts are Markdown, MDX, and .astro files in the repository. Changing a headline means opening an editor, editing a file, and committing to git.
Every edit means a rebuild
Astro is static, so published changes need a rebuild and redeploy. Wiring a headless CMS to trigger that automatically means webhooks, build hooks, and CI to maintain.
Non-developers are locked out
Marketers, writers, and clients can't update an Astro site without a git workflow and a local dev environment. The people who own the content can't publish it.
Pagesmith Is a Visual CMS for Astro
Pagesmith generates a real Astro project and puts a visual editor on top of it. The CMS and the site are one system — nothing to connect, nothing to configure.
Edit pages visually
Update headings, copy, images, and sections in a visual editor. No Markdown syntax, no hunting through .astro files — click the content and change it.
A real article editor
Blog posts are backed by Astro content collections with proper frontmatter and schemas. Write and publish articles in a dedicated editor — type-safe content, standard Astro workflow.
Publish in one click
Hit publish and Pagesmith rebuilds the static site and deploys it to Cloudflare's edge for you. No git commits, no CI, no webhooks — the rebuild step disappears.
Non-developers can run it
Hand the site to a marketer, writer, or client. They edit and publish themselves — no git, no local setup — while the codebase underneath stays clean, standard Astro.
Nothing to wire up
No separate CMS to connect, no content types to model, no API keys, no build hooks. Skip the Sanity or Contentful setup entirely — the content layer is already built in.
Your Astro code, no lock-in
It's still a standard Astro repo — package.json, astro.config.mjs, components, content collections. Export it, push to GitHub, or hand it to a developer. The code is yours.
Ways to Add a CMS to Astro
There are a few ways to manage content on an Astro site. Here's how the common approaches compare — and where Pagesmith fits.
| Approach | Visual editing | No rebuild wiring | Non-dev friendly | Own the Astro code | Setup effort |
|---|---|---|---|---|---|
| Markdown in the repo | No | No — you rebuild | No | Yes | None (but code-only) |
| Headless CMS Sanity, Contentful, Storyblok | Yes | No — webhooks + CI | Yes | Yes | Heavy |
| Git-based CMS Decap, TinaCMS, Keystatic | Basic | No — still rebuilds | Partly (git underneath) | Yes | Medium |
| Pagesmith | Yes | Yes — handled | Yes | Yes | None — built in |
Headless and git-based CMSs are great fits for existing Astro codebases. Pagesmith is for teams who want the Astro site and the CMS generated together, with no integration to maintain.
From Description to a Managed Astro Site
Describe your site
Tell Pagesmith what you're building. It generates a production-ready Astro project — designed pages, layouts, content collections, and SEO — in minutes.
Edit visually or in plain English
Change pages and posts in the visual CMS, or ask the AI agent to make edits to the .astro source. Non-developers manage content; developers can still open the code.
Publish to the edge
One click publishes. Pagesmith rebuilds and deploys the static Astro site to Cloudflare's global edge — or export the repo and host it anywhere you like.
An Astro Site with a CMS Built In
Describe what you need and get a production-ready Astro site you can edit visually and publish in one click. Free to start, no headless CMS required.
No credit card required. No vendor lock-in. Export your Astro code anytime.
Frequently Asked Questions
Does Astro have a built-in CMS?
No. Astro is a static site framework — content lives in Markdown, MDX, or .astro files inside the codebase, and editing it means changing code and rebuilding the site. To get a content management interface you either connect an external headless CMS or add a git-based CMS layer. Pagesmith gives an Astro site a visual CMS out of the box, so you can edit and publish without touching code.
What is the best CMS for Astro?
It depends on your team. Headless CMSs like Sanity, Contentful, and Storyblok are powerful but require setup, content modeling, and rebuild/webhook wiring. Git-based options like Decap, TinaCMS, and Keystatic edit Markdown inside the repo. Pagesmith takes a different approach: it generates the Astro site and provides a visual CMS on top of it, so non-developers can edit and publish without touching code, while you keep a standard Astro codebase you can export at any time.
Can I use a headless CMS with Astro?
Yes. Astro connects to headless CMSs such as Sanity, Contentful, Storyblok, and WordPress through their APIs. The tradeoff is setup: you model content types, connect the API, map fields to components, and configure rebuilds (usually via webhooks) so published changes go live. Pagesmith removes that plumbing — the CMS and the Astro site are one system, so there is nothing to wire up.
How does Pagesmith's Astro CMS work?
Pagesmith generates a real Astro project and layers a visual editor over it. You edit pages and blog posts — backed by Astro content collections — in the browser, and publish in one click. Pagesmith rebuilds the static site and deploys it to Cloudflare's edge for you, so there are no git commits, CI pipelines, or webhooks to manage. You can also ask the AI agent to make changes, or export the Astro code and edit it by hand.
Do I have to rebuild my Astro site to publish content?
With a traditional Astro plus headless CMS setup, a content change triggers a rebuild and redeploy that you have to configure. With Pagesmith, publishing is one click and the rebuild and edge deploy are handled for you — you never touch CI or webhooks.
Can non-developers edit an Astro site with Pagesmith?
Yes — that is the point of a visual CMS. Marketers, writers, and clients edit pages and posts in a visual editor and publish themselves, with no Markdown, git, or local development environment required, while the underlying site stays a clean Astro codebase.
Can I still edit the Astro code directly?
Yes. Pagesmith sites are standard Astro projects. You can edit through the visual CMS, ask the AI agent to change the .astro source, or export the full repository and hand-code it. All three workflows operate on the same project.
Is my content or code locked in?
No. Every Pagesmith site is a complete Astro repository — package.json, astro.config.mjs, components, layouts, and content collections. Export it any time and host it anywhere. There is no proprietary content format and no lock-in.