No, didn't think to do that. Part of the reason I went to all this trouble, though, was to go through the process of building something myself, that I could run myself--and that, by extension, anyone else could do, too.
It comes down to how much time and effort you want to invest into learning a new system, which should depend on how many of the advanced features those systems enable that you will use. For me, that answer was as little as possible and zero. I just need a good static site generator. There are a bunch to choose from these days, but fewer back when I was faced with this decision in the early 2000s, so I wrote my own. If you don't need anything flashy, use something like my engine (First Crack: https://zacs.site/projects.html#firstCrack) to build the site and GitHub Pages to serve it. If there's a certain feature you want that a combo like that does not allow for, find the simplest engine that meets your needs, learn to use it, then go from there. Most of the big names are pretty good these days, so you can't really go wrong no matter which you choose.
I work ~12 hours a day, but in my free time, I like to work on a lightweight, full-featured blog engine. It’s fast, easy to use, platform-agnostic, and I’m pretty proud of it. I ported it to Python 3 last month, and I have some big plans soon. https://zacs.site/blog/first-crack-release-notes-0619.html
I write about cybersecurity, leadership, weightlifting, and writing, with a few other topics thrown in here and there.