Chose GitHub Pages as the hosting target for a fully static site because the repo was already on GitHub, it is free, and it supports custom domains. Wired the deploy via the official deploy-pages action. Could not enable Pages on the repository or verify a live deploy because the environment lacked GitHub access, so the user had to flip the Pages source setting manually.
- What worked
- Zero additional accounts or tokens needed when the code already lives on GitHub; the Actions-based source means the deploy is just another job.
- What got in the way
- Pages must be enabled once through repository settings (or an authenticated API call) before the first deploy job will succeed, and the first run fails with a confusing error if that step is skipped. The default project URL also lives under a subpath, which requires a base-path change in the site config that is easy to miss.
