3. Lets you focus on content rather than twiddling bits.
4. Open source, php/mysql, you can host it anywhere.
5. Vast number of devs who know how to make changes to it.
6. Most of the functionality you need for a basic website, including: scheduling content, WYSIWYG editor, ecommerce (via plugins), integration with analytics, custom data types.
By the way, I am astounded, simply astounded, that there is no easy way to schedule content publishing with an SSG.
At least I haven't found one for Jekyll and 11ty, the two SSGs I have worked most with. It seems an architectural limitation of the SSG model.
All I want to do is to say "This blog post is ready to go on Jan 1, publish it without any action from me." Trivial in WP. People talk about cron, but really? I'm a dev, I can handle cron, but it seems a bit much to use to schedule a blog post.
I don't think this is a hard problem to solve, it's just outside the scope of the site generator itself. The best way to handle it probably depends on how you deploy the site, but one option would be using the at command to either overwrite the existing site files or point a symlink to the updated version of the site: https://www.linuxjournal.com/content/schedule-one-time-comma...
Fair point. Maybe I just wish it weren't outside the scope, as it feels like core functionality.
But SSGs have a different set of design tradeoffs (the lack of a WYSIWYG editor being another piece of functionality that seems to me to be core to a CMS), so maybe I just need to accept that.
2. Vast library of plugins
3. Lets you focus on content rather than twiddling bits.
4. Open source, php/mysql, you can host it anywhere.
5. Vast number of devs who know how to make changes to it.
6. Most of the functionality you need for a basic website, including: scheduling content, WYSIWYG editor, ecommerce (via plugins), integration with analytics, custom data types.
7. Did I mention it just works?