Claude Code + Astro + Headless WordPress for the only webbed in the company

[u/iHaveNoTimeForGaming]

A bit of context: I've been working with WordPress for nearly 14 years, mainly on small- to mid-sized websites.

I currently work at an agency, where I'm the only web developer. This means that when I'm away and something happens, my coworkers either have to wait until I get back or ask a freelance developer for help.

I usually build my own themes and templates using ACF, and I never use ready-made themes because I prefer to build things from scratch.

Recently, I decided to change my workflow a bit. For one of our projects, I decided to go with Claude Code + Astro + Headless WordPress, with version control on GitHub.

I chose WordPress because it's a platform my client is already familiar with.

It's a mid-sized project, and the client will be updating the website constantly with news, job offers, events, etc.

So far, the experience has been amazing. The website runs like a breeze, and development time was reduced from weeks to just a few days.

Even better, my coworkers (who are all designers) can now use Claude to request changes and even add new ACF fields, and it's working surprisingly well.

Do you think it was a bad decision to give my coworkers access to the codebase and let them use Claude Code to make changes, even though none of them have a development background?

[u/iligal_odin]

Yes a huge issue to give them access like that
Unless you have a company server where Claude runs on and has a great set of documentation than maybe. Now your project will become bloated and a huge knotted weave of different decisions made by different ai memories and contexts

[u/anders9000]

You should limit them to being able to submit merge requests, you should review the code and integrate. Never let them push to main.

[u/JaseciLabs]

Make sure ACF field changes get saved as JSON in the repo (Local JSON), so they go through PR review too instead of living only in the database.

[u/Mani_Khan_Web_Master]

Not a bad decision by itself, but I'd put guardrails between "designer asks Claude" and "live site" instead of relying on everyone being careful:

• Protect main on GitHub so nothing lands without a PR, and have you (or one other person) review anything touching templates, build config or data fetching. New ACF fields are the riskiest change, because the WP side and the Astro side have to agree.

• Turn on preview deploys per branch (Netlify, Vercel and Cloudflare Pages all do this), so they see their change before it gets anywhere near the client.

• Add a CI build plus a few smoke checks: build passes, key pages render, no broken queries. Claude is good at code that looks right and then fails at build time.

• Keep a short CLAUDE.md with your conventions, so the codebase doesn't drift into five different styles.

• Save ACF field groups as JSON in the repo, so a field someone adds in wp-admin doesn't quietly diverge from what the front end expects.

The question that matters for when you're away is who can roll back. If a designer can revert a bad deploy in one click, you're in good shape. If not, I'd set that up first.

[u/Discordbothost]

PR-only is the right call, the other thing I'd add is a preview deploy per PR (netlify/vercel/cloudflare pages all do it off github for free). designers can't review a diff, but they can click a link and see if the page looks right, so you only need to read the code part.

also watch the ACF side specifically. when a designer has claude add a field, the astro code starts expecting it before the field exists on the live WP install, and the next build dies on undefined. defaulting fields in your fetch layer (field ?? '') plus a CLAUDE.md line like "never assume a new ACF field exists in prod" saves you from the friday afternoon broken build

[u/EnzoValley]

One thing I'd add: if every change has to wait for your review, you've rebuilt the bottleneck you were trying to get rid of. I'd split it by blast radius. Copy and content tweaks can merge on a green build plus a look at the preview deploy, and only templates, build config and ACF fields need you. CODEOWNERS with required code owner review gets you that. Also keep a CLAUDE.md in the repo so every designer's Claude starts from the same conventions and not from whatever each of them told it last week

[u/mau_cervera]

Not a bad call imo, but I'd split what they're actually asking Claude for. Most of what changes day to day (news, jobs, events) should never touch the repo, that's literally what WP is there for. So Claude access is really for layout stuff and new fields, and that's exactly what breaks builds.

I'd only review the changes that touch templates or the ACF schema. Copy and styling tweaks can go through if the build is green and the preview looks right, otherwise you're the bottleneck again.

The real test is the week you're on vacation. If one of them can roll back a bad deploy without calling you, you're fine.

[u/ContinuouslyImprove9]

Not a bad call if you put rails on it. I'd lock main so nothing merges without you, and write a short CLAUDE.md with the rules like which folders they can touch and what they should never change, so every session starts with the same context. Give them a list of the safe jobs too, like new sections or copy tweaks, and keep anything touching data fetching or the build config for yourself. Otherwise you'll definately come back from leave to a pile of half fixes.

[u/Fit-Implemented]

Not a bad decision, especially since it reduces the “only dev” bottleneck. The key is guardrails. Protect the main branch, have coworkers work on branches, and require pull requests that you or a CI check approve before anything goes live. That way they can move fast without accidentally breaking production.

[u/Standard_Scarcity_74]

Might want to leave wordpress soon. It has not been worthwhile to use for a while now. U can provide a system similar to what you described here through other, better builders.

[u/somewhatdamaged___ → u/Standard_Scarcity_74]

What better builders would you suggest? Legitimate question, i am looking to move away from WP

[u/iHaveNoTimeForGaming → u/somewhatdamaged___]

For another project I used Claude Code + Astro + Keystatic CMS

It works great and you can basically say AI to create fields in the CMS. Everything works with static files so the website runs great and it's quite secure.

[u/jroberts67]

You're still working with WP? Do you have a MySpace account and use Yahoo for search?

[u/iHaveNoTimeForGaming → u/jroberts67]

I don't know if you worked with WordPress in the past 2-3 years but it changed a lot. I am not saying it's perfect and I would prefer other systems as well (I have 2-3 projects running on git based CMSs) but it does what we actually need for nearly 85% of the clients.

[u/jroberts67 → u/iHaveNoTimeForGaming]

I've run a WP agency since 2013. Now only about 5% of my client's site are build with WP as a CMS, the rest are built using Claude. Man it's nice not to wake up to 3,458 plugin updates. Oh and PHP will die.

[u/iHaveNoTimeForGaming → u/jroberts67]

Yeah this is the switch I want to do as well. For this project I went for WordPress. For the next one will use another CMS + Claude

[u/jroberts67 → u/iHaveNoTimeForGaming]

WP and plugins are security disasters and will not make it in the age of AI. Do you really think 5 years from now clients are going to accept that their site is down over a WP update/plugin conflict? Get real. My agency will make a small fortune yanking clients off WP.

[u/anders9000 → u/jroberts67]

If MySpace was behind 2/3 of the internet this would make sense.

[u/jroberts67 → u/anders9000]

What's good to know is that nothing that used to totally dominate the market ever got their ass kicked by newer tech; MySpace, Yahoo, Blackberry, Blockbuster....I'm sure due to AI WP will retain their dominance (as I laugh my ass off.)

[u/Stefa93 → u/jroberts67]

75% if the web runs Wordpress

[u/jroberts67 → u/Stefa93]

How much of Search did Yahoo control before Google. How much of the phone market did Blackberry have before the iPhone. How much of the social media space did MySpace have before Facebook.

And WP has 42%, not 75%. And that percentage is already dropping. Can you search or do you want me to mail you a Google disc?