I use AI as a full blown web master at this point. It maintains the site, functionality, etc. But I also make it track SEO performance, analytics. And I make it publish content. Sometimes that's based on a few bullets. Sometimes I submit my own drafts. I use guard rails and skills to ensure it all ends up the way I want. The management of the site is outsourced to the AI. And when I'm done it also makes sure the pull request merges cleanly and that the gh action to deploy (it creates that as well) does its thing.

Using a CMS is overkill if you have a static website generator. And once you have that it's just another code base that you can unleash agentic coding tools on. Most websites are pretty straightforward code bases to work with for AIs. The only real argument for a CMS always was providing an easy to use environment for people to work in without having to worry about technology. They power editorial processes too. But you don't need one any more if you can let AIs coordinate those processes. Use a word processor of your choice. Hand your draft off to the AI and let it do its thing.

Once you have this dialed in, which doesn't actually have to take a whole lot of time, you can get very efficient around content creation and management. Having good guard rails and investing in those is critical here and makes the difference between slop and having something that is actually informative and fresh. The guard rails can also deal with approval processes, fact checking, translations, audio transcriptions, check lists, tone/wording checks, etc. You can make this as complicated as you need to.