The source ZIP contains repository files. GitHub release assets and externally linked downloads remain separate. For an editable host, start with a fork.
Fork the repositoryOpen the project on GitHub and create a fork under your account. Use YOUR-USERNAME.github.io for a root-domain Pages site.
Review your host settingsThe publisher currently uses an empty base path for the root domain. In scripts/host-project-pages.cjs, review the Pages origin, repository owner, raw-file and release links, branding and main-site links for your fork. A different repository name or custom domain needs matching path and routing changes.
Enable GitHub PagesIn your fork, open Settings → Pages → Build and deployment and choose GitHub Actions as the source. If GitHub asks you to enable workflows in the fork, review and enable the existing workflow.
Run the publishing workflowOpen Actions → Deploy WWB HOST → Run workflow, select your default branch and run it. The existing .github/workflows/pages.yml builds and checks the static output before deployment.
Open your published addressAfter a successful deployment, use the address shown by GitHub Pages. With the original repository name, the usual address is https://YOUR-USERNAME.github.io/. Check navigation and exact download links before sharing it.
The source archive can be large. Use the project’s publisher to build its selected Pages output and retain download mappings; do not upload the entire download archive as a Pages site. Follow GitHub’s published size limits and preserve each bundled project’s license and attribution.
