Nah, no CI workflow, I generate locally. Creating the site was just pip install pelican; git init . ; pelican-quickstart; vim pelicanconf.py # to set the th

Nah, no CI workflow, I generate locally. Creating the site was just pip install pelican; git init . ; pelican-quickstart; vim pelicanconf.py # to set the theme Then to publish: pelican . && git add -A && git commit -m "post title" && git push (I have a shortcut for this, of course) But I think you overestimate the time to "setup the CI workflow" actually takes. It's just a text file where you put the commands above, so it can run on the server instead of your machine. There's no black magic to it. > I don't have to worry about a build pipeline at all. Of course you do; it's just that your build pipeline runs every time someone accesses your site. > I'm not aiming this at you, but in general I'd love to see how newer engineers would tackle things like deployment if they couldn't rely on some SaaS offering. I've done that too. I created a bare git repo on the server, with a post-receive hook that checkouts "master" and runs the static site generator. Then I had Nginx serve the directory.