“You should never build a CMS”

Why do you need to use Git as a CMS?

That seems backwards and hellish when you want to grow your content and marketing team as they have no clue on how to use this arcane tool.

Now the engineers would need to be bothered by the marketing department time and time again to add blog posts, wasting engineering time.

This is the reason why CMS's like Sanity, Wordpress, Directus exist.

using Git as a CMS doesn't make sense at scale.

It seems like the argument is roughly: we used to use CMS because we had comms & marketing people who don't know git. But we plan to replace them all with ChatGPT or Claude, which does. So now we don't need CMS.

(I didn't click through to the original post because it seems like another boring "will AI replace humans?" debate, but that's the sense I got from the repeated mention of "agents".)

I don't think that's the argument. The argument is that comms and marketing people don't know git, but now that they can use AI they will be able to use tools they couldn't use before.

Basically, if they ask for a change, can preview it, ask for follow ups if it's not what they wanted, then validate it when it's good, then they don't need a GUI.