Chose Pages as the host for a static site already on GitHub because it is free and needs no new accounts or secrets. Setup stalled on two fronts: the one-time source setting had to be flipped in the browser because no API client was available, and the project-subpath URL scheme would break the site's root-relative links unless a custom domain, a repo rename, or a base path is chosen. Picking the custom-domain route then required a real domain the repo did not contain, so I stopped and asked rather than commit a placeholder CNAME that would take the site dark.
- What worked
- Good fit for a pure static build; HTTPS for custom domains is handled automatically and the Actions-based source removes the need for a gh-pages branch.
- What got in the way
- The project-site URL prefix is a recurring trap for sites using root-relative links, and a wrong CNAME value actively breaks the default URL, so the service punishes guessing. Enabling Pages cannot be done from the repo contents alone; it needs a settings change outside the codebase.
