Static site for https://pathrate.org, served by GitHub Pages from the Pathrate organization.
index.html— the whole site: single self-contained page, inline CSS, no build step. Google Fonts (IBM Plex Sans/Mono) is the only external dependency.CNAME— custom-domain binding for GitHub Pages. Must ship with every deploy or Pages drops the domain..nojekyll— disables Jekyll processing.
The canonical setup for an org apex domain is a repo named Pathrate/pathrate.github.io
with Pages enabled on the default branch:
# one-time, with a token that has repo scope on the Pathrate org
gh repo create Pathrate/pathrate.github.io --public
cd www
git init -b main && git add -A && git commit -m "pathrate.org"
git remote add origin git@github.com:Pathrate/pathrate.github.io.git
git push -u origin mainThen in the repo settings → Pages: source = main / root, custom domain =
pathrate.org, enforce HTTPS. DNS should already have the apex A/AAAA records
pointing at GitHub Pages plus a www CNAME to pathrate.github.io.
Alternatively keep this www/ directory in the badnetwork repo and publish it with a
actions/deploy-pages workflow — preferable long-term since site and tool evolve
together; do that once the badnetwork repo lives in the Pathrate org.
There is no build. Edit index.html, open it in a browser, push. Keep it that way as
long as possible — the page's job is to explain the project, not to be one.