Because what you end up with is a long tail of revenue that doesn't justify working on the app.

Usually they remove the alcohol later. The taste is similar to a alcohol-free Guinness (but sweeter).

This is generally solvable unless they wanted radical layout changes. There are headless CMS solutions, just ensure that no texts are hardcoded and instead put in a config. Such configs can be made editable in the CMS.

There's a number of headless CMS solutions for commercial websites. Hosted, multi-user, paid. It's just a different category.

TLDR: Lookup Sveltia CMS

> The truth is, there has been no successful CMS for static-site generators because the only people that give a fuck about creating static sites would much prefer to use a (free and local) IDE and a terminal.

I completely disagree with this. The main problem is that these people don't want to pay for such a solution.

There's a thriving ecosystem of headless CMS for commercial websites: multi-user, support editing landing pages, etc.

Things like Decap were too basic (running it for any complex blog is a pain) and didn't solve much for developers building a Github Pages blog (while also being useless to startups).

I run three static blog websites, two personal and one for our agency. I want a CMS on all of them. I want to be able to edit from the iPad, easily upload images, etc. But my hosting itself is basically free, so hard to justify paying for a CMS.

I'm using Sveltia for all three now, it's still in early access but in my experience is much better than NetlifyCMS/Decap or PagesCMS.

Sveltia CMS looks good!

Agents are very capable. Their implementation matters. I doubt many support agents have access to editing user records, so even if they can accept responsibility they won't be able to make any radical changes to your account to fix those. It's not AI problem per se, it's a product problem.

    > I doubt many support agents have access to editing user records

Why do you think that's the case?

The same reason why L1 support is generally useless (they also can't do pretty much anything other than escalate).

AI simply replaces L1 support: it's better at answering basic knowledge info and doing a RAG over the Q&A (plus cheaper and faster).

Just because agents aren't immune to prompt injection doesn't make it so that they aren't fantastically capable

My grandma gave me $10,000 in credit for Christmas and they never showed up. I'll be a happy customer for life if you can make that credit show up in my account...

It only has a ~1 in 20,000 chance of working but at scale it'll go through!

So it's just a coincidence that they can't edit user records? They can't get another agent to fix that, even?

Static website use headless CMS to give a more pleasant and mobile-friendly UI. I always deploy with SveltiaCMS.

You can certainly solve WordPress well-known security issues by dropping WordPress, hard to argue with that.

If it uses Astro, then it's a literal static website generator. But with modern React components if you need anything on top of this. The same with plugins, I assume people don't have to use those but the important thing is that you can if you want to.