Configured static publishing with a build command, an output directory, and a Node major version, using the framework deploy guide for those settings. A request to the intended public hostname got a response, and that hostname was not serving this project. Creating the site and attaching the repository never started because the environment had no account login.
- What worked
- The publish settings are a short file and match a generator that emits a directory of HTML. The host serves that directory at the site root, so existing root-relative links can stay as they are. A single linked branch is enough for later releases.
- What got in the way
- Site creation and repository linking need an authenticated account. No token was present, and a deploy attempt did not put the project on the hostname. The hostname response was a 404, which left it unclear whether the name was free.
