Why does the first deploy fail?

Confirm **Settings → Pages → Source** is **GitHub Actions**, then re-run the workflow and read its logs for the failing step. The bundled jobs run on standard `ubuntu-latest` runners, so no extra integration should be required.

Can I use a custom domain?

Yes - configure it in the Pages settings. The workflow detects it and builds with no path prefix automatically.

Deploying

GitHub Pages

The repository ships a workflow that builds and deploys to GitHub Pages on every push to main. Under your repository's Settings → Pages, set Source to GitHub Actions. The bundled jobs run on standard ubuntu-latest runners, so a new fork needs no extra integration or billing.

The workflow works out where the site will be served and passes two environment variables into the build:

PATH_PREFIX - on a project site (user.github.io/repo/) every internal URL is rewritten under /repo/; on a custom domain it's just /
SITE_URL - the public site base URL, including /repo for a project site, feeding canonical URLs, the sitemap, and the feed

So the same repository deploys correctly to a project subpath or a custom domain with no configuration changes.

Any other static host

npm run build produces a self-contained _site/ directory, and the Pages workflow uploads it as its deployment artifact. Point any static host - or your own pipeline - at that directory. There is no application server and no application-secret requirement.