Comment by claytonjy
19 hours ago
Yeah this sounds pretty reasonable really, like instead of using a CMS directly they’re having Claude file PRs to make the same changes. As someone who likes static sites and change control, it actually sounds like an improvement.
Despite my own personal preference for static sites, marketing using a CMS under their own control to make content updates seems vastly more reasonable than vibe coding open ended PRs as a codebase they don't understand gradually grows in complexity over time.
They could even use one of many headless CMSs combined with a static generator. Claude Code in the hands of non-technical users deploying to prod regularly seems like one of the worst possible ways to do it (except for the "cool" value telling people about it).
At my company the internal devs don't even have access to wherever the company site is hosted, it's a WordPress CMS and marketing can make updates safely with a couple clicks and zero day-to-day development oversight required. IT just helps keep the box updated but otherwise it's entirely their own thing.
If as a developer all you want your job to be is checking ai generated PRs then this is a great step!