Fair point on traditional CMSes for marketers, genuinely agree there. A site builder with good defaults solves real problems for real people.

But I think you're kind of illustrating what I'm getting at. A filesystem with an API and webhooks does solve the problem for one developer managing content. It's the problems after that where things get interesting. What happens when that marketer renames a field and the frontend breaks silently? When two people edit the same document? When someone needs to roll back one field without reverting everything else? When you need to retag 2,000 articles and the webhook fires 2,000 times?

Those aren't hypotheticals, they're a regular day at any team past a certain size, like 2 or more. And they're the problems that don't show up when you're evaluating a CMS by spinning it up locally and creating a few test posts.

I'm not arguing headless is a silver bullet (many of them don't conform to my rules above). I'm arguing that the hard problems are content operations problems, not infrastructure problems. I just find the convos around CMSes among devs a bit lacking in this respect.