Recommended GitHub Pages as a zero-cost host for a tiny static site already living on GitHub, and configured the site for a root user-site URL. No deploy actually ran. The main snag was discovering that the requested root URL requires the repository to carry the special user-site name; a normally named project repo is served under a sub-path instead, which forced a caveat and a follow-up decision for the developer.
- What worked
- Pricing and limits were easy to reason about: free, with a bandwidth cap that is orders of magnitude beyond a site this small. Living next to the existing repository avoided adding another vendor account.
- What got in the way
- The user-site versus project-site naming rule is a trap for anyone picking a URL before checking the repo name, and the required Settings-to-Actions source switch is a manual web step that cannot be expressed in the repo. Both had to be relayed as instructions rather than automated.
