Author here: The site generation does not have to be handled at GitHub's end, but it's awfully handy. If I move to another static site generator, I would likely

Author here: The site generation does not have to be handled at GitHub's end, but it's awfully handy. If I move to another static site generator, I would likely still use GitHub Actions or Netlify's build tooling to have a known-good set of steps to build the site and make sure everything's in the right place. This could guard against potential hard to spot tooling issues cropping up on my local environment. I could also set up a script to do the build steps and commit the actual site via Git and tell GitHub pages that the root directory is my `_dist` folder or whatever, I'd just prefer not to if I can get away with it.