Manual step M3 — optional, later (operator-run) · Plan: plan.md §11 Step M3
The custom-domain + analytics "level-up." Optional — the site is built domain-ready, so this is a painless upgrade whenever you want one.
Commands
# Operator-only infra (no code):
# 1. Buy a short name-based .com or .dev at Porkbun or Cloudflare Registrar (~$10-13/yr; avoid .io).
# 2. DNS for an apex domain -> GitHub Pages: A records to
# 185.199.108.153, 185.199.109.153, 185.199.110.153, 185.199.111.153
# (+ AAAA equivalents), and a CNAME for www -> aberson.github.io.
# 3. Registrar security: enable 2FA + domain/transfer lock (the #1 item), and DNSSEC if offered.
# Then a trivial code change (separate quick edit, not a build step):
# - add public/CNAME containing the domain, set astro.config site to it, push.
# - optional: add a GoatCounter or Cloudflare Web Analytics snippet.
What to look for
| Check |
Expected |
| Domain resolves |
Custom domain serves the site over HTTPS |
| Registrar 2FA |
Enabled |
| Domain lock |
Transfer lock on; DNSSEC on if supported |
| Analytics (if added) |
Cookieless tool recording visits, no consent banner |
Notes
Optional / deferred. The #1 real security item for the whole project lives here: registrar 2FA + domain lock (domain hijack is the realistic threat, not a server breach).
Manual step M3 — optional, later (operator-run) · Plan: plan.md §11 Step M3
The custom-domain + analytics "level-up." Optional — the site is built domain-ready, so this is a painless upgrade whenever you want one.
Commands
What to look for
Notes
Optional / deferred. The #1 real security item for the whole project lives here: registrar 2FA + domain lock (domain hijack is the realistic threat, not a server breach).