Exactly, GitHub Pages has two publishing methods:

1. From a branch (traditionally gh-pages), where the generated HTML files are stored in that branch.
2. From a GitHub Actions workflow, where the documentation is generated during the workflow and then deployed directly to GitHub Pages. With this approach, you don't have to maintain a gh-pages branch yourself—the workflow builds the documentation and publishes it for you.

Since you're new to GitHub, I'd actually recommend starting with the first option because it's easier to understand. Once you're comfortable with GitHub Actions, you can automate the entire process.

And yes, you can absolutely make this part of your release process. For examp…