#[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.
#gRegorBut that requires keeping WordPress around on the server?
#[tantek]making the whole site MediaWiki eventually is worth considering but larger scope than necessary for redesign
#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.
#[tantek]like I'd prefer to keep the design of the blog posts
#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
#[mattl]Oh sure. Does the server you’re running this on do its own LetsEncrypt?
#[tantek]wait why does GH actions require to keep a toolchain up to date with the latest versions of node/whatever? I thought GH did that for you?
#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.
#[tantek]I mean that's what my shared web host does 🙃
#[mattl]I think I’m going to write something in PHP
#[mattl]The time difference between 7.3 and 8.4 is about a decade. In node terms that would be about 8 months.
#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
#[mattl]I’m sure Dreamhost keeps older versions of PHP around too.
#aaronpkdreamhost has actually been getting pretty aggressive about forcing php updates lately
#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.
#jimwand don't be fooled by the version numbers, PHP doesn't adhere to semantic versioning. things change/break in minor releases.
#[mattl]My use case is to keep using WordPress but I can see people may not want to.
#jimwi assumed the goal was to not have to run/use wordpress any more.
#aaronpkthe goal for the microformats blog is to decommission wordpress
#[tantek]our blog needs are much simpler than what WordPress of today provides
#[tantek]and so we don't need the full software maintenance responsibilities
#[mattl]So you’re okay writing Markdown and basic HTML and have that shoved into a template?
#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