[mattl]I think GitHub actions can just build the site from WordPress and output HTML to a repo. I think I can also add http://WordPress.com support too.
gRegorOh, I think I get it. We could run matt's archiver one time, replace the homepage with static HTML, remove WordPress. Then next time we write a blog post we can do it manually, or consider the full site MW option.
aaronpkplease be mindful that even github actions is not zero admin tax, you still have to keep the toolchain up to date with the latest versions of node/whatever
jimwyou wouldn't want that, new versions of node (or whatever) could break whatever code it is that you're running the action. if the SSG were written in PHP, you wouldn't want GH to just blindly update from PHP 7.3 to 8.4.
aaronpk[tantek]: i mean you have to make sure your code that is running in the github action works with the latest version of the environment it's running
jimwthere are existing SSGs in PHP. if your WP-to-11ty thing is dumping out Markdown files of the old content, it might just be a matter of writing some templates and logic to make sure the URLs get generated the same.
jimwPHP had a long period of kind of stagnant development that made the upgrade treadmill seem like it wasn't happening, but it is on a more regular cadence of releases now that involve deprecations.
The_DecryptorSSGs like Zola or Hugo don't depend on any specific runtime environment or toolkit, can just pin a specific binary version and use it indefinitely
[tantek][mattl] best I can do for you is writing basic HTML because that's literally what we asked of folks writing http://microformats.org blog posts in the past