Wordpress has:
* the ability to schedule posts
* a ton of plugins
* a lot of people who know how to use it
* a reasonable WYSIWYG interface
As far as I know, most SSGs fall down on one or more of those dimensions.
* the ability to schedule posts
* a ton of plugins
* a lot of people who know how to use it
* a reasonable WYSIWYG interface
As far as I know, most SSGs fall down on one or more of those dimensions.
jekyll serve --watch --incrementalI don't see much of a difference between `jekyll serve` and the e.g. `service nginx start && service php-fpm start && service mariadb start` that would be needed to run WordPress. In fact I don't run my WIP Jekyll site on the same machine that I edit from. Mine is available only on my personal mesh VPN, but it could easily be available publicly if I wanted it to be.
Live Preview means, then, that you need to:
- have a web-based editor behind secure auth,
- create an environment resembling CI to rebuild the site on demand,
- trigger rebuilds when a user modifies the content stored on the server,
- make the new build available in a draft environment
- …where it doesn't affect the live site,
- …only grant access to collaborators,
- …without breaking assets, links in the pages, CORS, or CSP.