docs: canonical URL is https://jonbogaty.com/pkgs/

CLAUDE.md

@@ -9,7 +9,7 @@ domain: technical
 
 Unified package repository for every `jbcom/*` project. Ships Homebrew,
 Scoop, and Chocolatey packages from one git tree plus an auto-generated
-Astro static site at <https://jbcom.github.io/pkgs/>.
+Astro static site at <https://jonbogaty.com/pkgs/>.
 
 ## Critical rules
 
@@ -71,7 +71,7 @@ Upstream projects write manifests here on every tagged release:
   commit manifests here.
 
 The Astro site rebuilds automatically on every push to `main`, so
-new packages appear on <https://jbcom.github.io/pkgs/> within minutes
+new packages appear on <https://jonbogaty.com/pkgs/> within minutes
 of the upstream release landing here.
 
 ## What jbcom/pkgs is NOT

README.md

@@ -2,7 +2,7 @@
 
 Unified package repository for every `jbcom/*` project — Homebrew,
 Scoop, and Chocolatey from one git tree. Public package index at
-<https://jbcom.github.io/pkgs/>.
+<https://jonbogaty.com/pkgs/>.
 
 ## Install
 
@@ -142,7 +142,7 @@ PY
 
 `deploy.yml` runs on every push to `main` using `withastro/action@v6`.
 The built site is deployed to GitHub Pages at
-<https://jbcom.github.io/pkgs/>.
+<https://jonbogaty.com/pkgs/>.
 
 ## License
 

astro.config.mjs

@@ -8,10 +8,11 @@ import { ViteToml } from "vite-plugin-toml";
 import tailwindcss from "@tailwindcss/vite";
 
 // jbcom/pkgs — package index site
-// Served at https://jbcom.github.io/pkgs per Astro's GitHub Pages guide.
+// Served at https://jonbogaty.com/pkgs/ via GitHub Pages custom-domain
+// routing. jbcom.github.io/pkgs/ 301-redirects here automatically.
 
 export default defineConfig({
-  site: "https://jbcom.github.io",
+  site: "https://jonbogaty.com",
   base: "/pkgs",
   integrations: [
     vue(),

docs/ARCHITECTURE.md

@@ -82,17 +82,21 @@ tap git tree directly.
 - **Deployed** via `withastro/action@v6` (auto-detects pnpm) to GitHub
   Pages with base path `/pkgs`
 
-## Why not subpath under custom domain (jonbogaty.com/pkgs)?
+## Site serves at jonbogaty.com/pkgs/
 
-Astro's official GitHub Pages guide only supports either:
+The operator's apex domain `jonbogaty.com` already CNAMEs to
+`jbcom.github.io`, so GitHub Pages transparently serves `/pkgs/` at
+`https://jonbogaty.com/pkgs/`. `jbcom.github.io/pkgs/` 301-redirects
+to the canonical URL.
 
-- Project page (`jbcom.github.io/pkgs`) with `base: '/pkgs'`
-- Custom domain with `site: 'https://custom.tld'` and **no base**
+Astro's `astro.config.mjs` uses `site: 'https://jonbogaty.com'` +
+`base: '/pkgs'` — this feeds correct absolute URLs into sitemap and OG
+metadata while internal routing stays subpath-relative.
 
-Serving `jonbogaty.com/pkgs` requires an external reverse proxy
-(Cloudflare Worker, Netlify rewrite, Caddy) that maps that path to
-`jbcom.github.io/pkgs/`. That's a future-operator decision; the repo
-itself is deployed at `jbcom.github.io/pkgs` today.
+No CNAME file is needed in `public/` because the apex-domain CNAME is
+configured repo-wide (pages settings), not per-repo via file. Adding a
+`public/CNAME` would *break* the `/pkgs` base path by treating the
+repo as apex-mode.
 
 ## Dependencies
 

docs/DEPLOYMENT.md

@@ -11,7 +11,7 @@ domain: ops
 
 | Env | URL | Trigger |
 |-----|-----|---------|
-| Production | <https://jbcom.github.io/pkgs/> | Push to `main` |
+| Production | <https://jonbogaty.com/pkgs/> | Push to `main` |
 | Preview | Local (`pnpm dev`) | `localhost:4321/pkgs/` |
 
 There is no staging environment. Previews happen locally.
@@ -53,20 +53,23 @@ Or:
 
 - GitHub Pages build status: <https://github.com/jbcom/pkgs/deployments>
 - Workflow runs: <https://github.com/jbcom/pkgs/actions>
-- Site health: manual check at <https://jbcom.github.io/pkgs/>
+- Site health: manual check at <https://jonbogaty.com/pkgs/>
 
 No uptime SLA. If the site is down for more than an hour during a
 release window, escalate via the upstream project's issue tracker.
 
 ## DNS / custom domain
 
-Currently served on the GitHub-issued subdomain
-(`jbcom.github.io/pkgs`). To serve `jonbogaty.com/pkgs` in the future:
+The operator's apex `jonbogaty.com` already CNAMEs to
+`jbcom.github.io`. GitHub Pages transparently serves every `jbcom/*`
+repo's pages subpath at the matching URL on the apex, so this repo
+is live at `https://jonbogaty.com/pkgs/` with no additional config.
 
-1. Configure Cloudflare (or equivalent CDN) to proxy
-   `jonbogaty.com/pkgs/*` → `jbcom.github.io/pkgs/*`
-2. Do NOT add a `public/CNAME` file — per Astro docs, that converts
-   the site to apex-domain mode and breaks the `/pkgs` base path
+`jbcom.github.io/pkgs/` 301-redirects to the apex, so operators
+following the GitHub URL end up in the right place.
+
+Do NOT add a `public/CNAME` file. That converts this repo to
+apex-domain mode and would break the `/pkgs` base path.
 
 ## Broken-build triage
 

docs/STATE.md

@@ -29,8 +29,6 @@ publish from `jbcom/radioactive-ralph`.
   the seeded manifests
 - A non-Go publishing workflow template for `jbcom/paranoid-passwd`
   and other CMake/C projects (no GoReleaser equivalent)
-- Reverse-proxy setup for `jonbogaty.com/pkgs` → `jbcom.github.io/pkgs`
-  (optional; current deploy works at the GitHub-issued subdomain)
 
 ## Active owners