Astro × Claude: When Claude Code Is Your CMS

Traditional CMS thinking starts with a dashboard: log in, edit fields, click publish.

I do not want that stack for most agency and marketing sites. I want content and code in Git, preview deploys before anything goes live, and an assistant that can change a headline or a component without switching tools.

That workflow is what I argued for in AI as Your CMS. Astro × Claude is the template I ship so other people can start there instead of wiring it from scratch.

The problem with “just use a CMS”

For a brochure site, portfolio, or blog, a traditional CMS solves yesterday’s constraint: non-developers needed a safe way to publish without touching code.

July 2026 made the cost of that attack surface hard to ignore. wp2shell, a pre-auth remote code execution chain in WordPress Core, was disclosed mid-month and actively exploited within days. A lot of site owners are now patching in a hurry, or finally asking whether a brochure site needs PHP, MySQL, and an admin login on the public internet at all. I have argued WordPress is a weak default for new marketing sites; moments like this accelerate the switch.

In 2026, that constraint is weaker. You can describe a change in plain English. An agent edits Markdown and Astro files. CI builds. A preview goes up. You review the diff and merge. Rollback is git revert, not a database restore.

What you avoid:

• An admin login on the public internet
• Plugin debt and dashboard lock-in
• Content trapped in MySQL while the real design lives in components
• Paying for a CMS so someone can change a paragraph once a month

What you keep: ownership of the repo, static-site performance, and a stack that still makes sense when the brief grows.

What Astro × Claude actually is

Astro × Claude is a production-ready Astro 7 agency template with Claude Code wired in as the CMS and a junior developer you supervise.

The pitch on the site is blunt: Claude is your CMS and your dev team.

You open Claude Code in the project root and describe what you want. Claude reads CLAUDE.md, follows project skills, edits files, runs checks, commits, and pushes. GitHub Actions deploys. No admin panel.

It is not a prompt-to-app toy. It is a real codebase you own: the same model I prefer over instant site makers.

What Claude can do in the repo

Three jobs, same interface:

1. Edit content: blog posts, standalone pages, frontmatter, tags. Content collections are schema-checked at build time.
2. Update site code: components, layouts, styles, navigation. Not just copy fields.
3. Add features: a contact page, a newsletter block, a tags index. Scaffold, check, ship.

The loop is simple:

You prompt → Claude edits → astro check runs → commit to main → the site rebuilds and deploys.

Skills cover content updates, feature work, and deploy. Hooks block writes to dist/ and workflow files, and re-run checks after relevant edits. That is the difference between “AI that once rewrote half your theme” and a workflow you can leave running without babysitting every keystroke.

Who it is for

• Agencies and freelancers who want one starter for client marketing sites
• Teams who already use Claude Code (or are ready to)
• Anyone who wants Git as the CMS and Astro as the site framework
• People tired of WordPress or headless CMS overhead for a twelve-page site

It is not for teams that need a multi-editor visual admin with roles, localisation workflows, and a content API shared by five apps. Those briefs still earn a real CMS. Most agency brochure sites do not.

What you get for $39

The agency license is a one-time purchase. One license covers unlimited client and internal projects for your business. You get private repo access after checkout: clone and ship.

Included:

• Astro 7, TypeScript, Tailwind CSS 4
• Dark agency-grade design system as a starting point, not a prison
• Content collections for blog and pages
• Claude skills, hooks, and CLAUDE.md
• GitHub Actions CI: deploy to GitHub Pages, Netlify, or Vercel
• Prompt examples so you are not inventing the workflow on day one

Live demo: astro-x-claude.netlify.app. Buy: astro-x-claude.netlify.app/buy.

Why I built it this way

I kept recommending the same stack: Astro for marketing sites, Git for content, Claude for edits. Clients and other developers kept asking for a starting point that already had the agent layer, not another blank theme.

So I packaged the workflow I already use: content in the repo, Claude as the interface, CI as the publish button. The design is opinionated enough to look finished and flexible enough to rebrand in an afternoon, preferably by asking Claude to do it.

If you only take one idea from this post: the repo is the CMS. Claude is how you talk to it. Astro × Claude is one concrete way to start.

If you want help adapting this model to a client site, or you want the template and a second pair of eyes on the first deploy, get in touch.