run your own register.

Forking this site is not just permitted — it's the point. The code is MIT: keep the LICENSE file and its copyright line and you are fully compliant. A link back to iusethis.org is appreciated, never required. This is the whole procedure, fork to custom domain.

1 · Fork and make it yours

1. Fork iusethisorg/iusethisorg (an org account is best — governance handoff never requires migrating the repo).
2. Empty articles/ and projects.js; put your own objects in. Scaffold a write-up with make new SLUG=my-object.
3. Set your identity: git config user.name / user.email, and your domain in CNAME (or delete CNAME to use <you>.github.io).
4. Build and preview locally:

make build    # render write-ups + manifest + site pages
make serve    # preview at http://localhost:8000
make check    # strict build — what CI runs

2 · Enable GitHub Pages

1. Repo Settings → Pages → Source: GitHub Actions.
2. Push to main — the workflow (.github/workflows/pages.yml) runs make check and deploys. No generated files are ever committed.

3 · Verify your domain (TXT record)

In GitHub: org/profile Settings → Pages → Add a domain → enter your domain. GitHub shows a TXT record:

Create it, wait for propagation (dig TXT _github-pages-challenge-<account>.yourdomain.org +short), then click Verify. This prevents domain takeover if the Pages site is ever disabled. For iusethis.org itself the name is _github-pages-challenge-iusethisorg.

4 · Point the apex at GitHub Pages

5 · Enforce HTTPS

Back in repo Settings → Pages: once the domain shows a green check and the certificate is issued (usually within an hour of DNS propagating), tick Enforce HTTPS. Done — your register is live.