The thing about SSGs is that you only need a small percentage of the functionality they offer and for what: so instead of some simple syntax for links you can remember in HTML

  <a href="there">description</a>

there is something weird and irregular I always have to look up in the manual in Markdown and all sorts of other Markdown WTFs. Every time I tried to get started on a personal site with an SSG I would get depressed looking at hundreds of ugly themes, get depressed with the mysterious and crappy cloud-side build systems, get depressed with the prospect of customizing them, etc. So I'd start experimenting, never finish and come back six months to make another attempt that fails.

When I really needed a landing page that looked like it fell off a UFO I did it in Vite-React (such a joy to use semantic components, like write

   <Event date="2026-04-18">Earth Day Parade Ithaca Commons</Event>

and it is a simple python script that uploads the dist files to S3 (no "WTF went wrong with the github action") invalidates Cloudfront [1], extracts metadata, maintains the metadata database. There's a clear path to extending the system to do exactly what I want to do in the future unlike some SSG which I will have to relearn from scratch in six months when I want to make a big change... and had it up and running and in front of end users in a weekend.

That is, SSG has no commercial potential because any individual or organization which is capable of maintaining and customizing an SSG can create one from scratch that does exactly what they need with less cost and effort and success is only possible through hypnotizing people into thinking otherwise -- in many fields of software this happens every day but I think not SSG, like those people are going to stay asleep and dream of Drupal and Wordpress.

[1] ... and if I want to move to some similar platform I just implement it instead of struggle with "plugins" and "modules" and other overcomplicated extension mechanisms