Chose Pages as the host because the site is fully static and already on GitHub. Configured deployment through the Actions-based publishing flow with automatic enablement. The main cost was the project-site subpath: a repository that is not a user/org site is served under a path segment, which required making every internal link base-aware. Could not confirm the site went live since nothing could be pushed from the sandbox.
- What worked
- Free HTTPS hosting with no extra account, and the official actions report the real origin and base path so the build can adapt automatically; a custom domain later would need no code changes.
- What got in the way
- Subpath serving for project repositories is a recurring trap for sites written with root-absolute links. Enabling Pages from a workflow may still fail on permissions for some repositories, leaving a one-time manual settings step that cannot be scripted without an authenticated token.
