Consume shared Antora UI bundle from wincon-antora-ui release

The UI bundle source this repo carried has been extracted into
wintermeyer/wincon-antora-ui. That repo builds and publishes
ui-bundle.zip to a `latest` release on every main push; both this
book and learn-ruby-on-rails-book now pull the bundle from that
URL, so the chrome stays in lockstep without copy-paste.

Changes here:

- antora-playbook.yml / antora-local-playbook.yml replaced the
  `./ui-bundle/build/ui-bundle.zip` reference with the release
  URL at github.com/wintermeyer/wincon-antora-ui. Both gain
  `ui.supplemental_files: ./ui-supplemental` so Antora overlays
  per-book header/footer-content.hbs on top of the bundle defaults.
- scripts/fetch-partials.sh now writes under ui-supplemental/
  (gitignored). The Phoenix nav gets data-book-current="phoenix"
  stamped in.
- scripts/deploy.sh loses the `npm run build` inside ui-bundle/
  — the bundle is ready-made — plus a comment clarifying what
  `antora --fetch` does now that the UI comes from a URL.
- The vendored ui-bundle/ directory is removed.
- README rewritten; the contributing flow is now "edit the shared
  UI bundle repo and push" rather than "edit this repo's ui-bundle
  subtree".

Builds pre/post are visually identical (both books already used a
byte-identical copy of this bundle); the value is in the delete.

Author: wintermeyer

.gitignore

@@ -7,3 +7,5 @@ sandbox/*
 /docs-site
 .vscode
 /ignore/
+# Generated at deploy time by scripts/fetch-partials.sh.
+/ui-supplemental/

README.md

@@ -1,79 +1,82 @@
 # Elixir, Phoenix and Ash Beginner's Guide
 
 Content is authored in AsciiDoc under `modules/ROOT/pages/` and rendered
-by [Antora](https://antora.org). The visual style matches
-[wintermeyer-consulting.de](https://wintermeyer-consulting.de) and is
-produced by a custom Tailwind CSS v4 UI bundle that lives in
-`ui-bundle/`.
+by [Antora](https://antora.org). The visual chrome (Tailwind v4 theme,
+sidebars, pagination, TOC) comes from the shared UI bundle at
+[`wintermeyer/wincon-antora-ui`](https://github.com/wintermeyer/wincon-antora-ui),
+which is also used by the Rails book at `/rails/book/`.
 
 ## Build
 
-The site build is two steps: first build the UI bundle, then run Antora.
-
 ```sh
-# 1. Build the UI bundle (produces ui-bundle/build/ui-bundle.zip)
-cd ui-bundle
-npm install
-npm run build
-cd ..
-
-# 2. Render the site against the local source (build/site/)
-npx antora --fetch antora-local-playbook.yml
+npm install                                          # installs Antora
+npx antora --fetch antora-local-playbook.yml         # renders build/site/
 ```
 
-Open `build/site/index.html` in a browser to preview.
+`--fetch` refreshes both the content source and the UI bundle
+(pulled from the `latest` release of wincon-antora-ui). Open
+`build/site/index.html` to preview.
 
-To render the production playbook (pulls content from the remote repo
-instead of the working directory), swap step 2 for:
+To render against the main branch on GitHub instead of the local
+working copy:
 
 ```sh
 npx antora --fetch antora-playbook.yml
 ```
 
-## UI bundle development
-
-Work on the chrome and styles lives in `ui-bundle/src/`:
+## UI bundle changes
 
-- `css/site.css` — Tailwind v4 source (`@theme` tokens, `@custom-variant
-  dark`, and `@apply`-scoped rules for Antora's class surface)
-- `partials/header-content.hbs`, `partials/footer-content.hbs` — the
-  wincon-matching top nav and four-column footer. These are the
-  *committed fallbacks*; the real canonical versions live in
-  [wincon/priv/static/partials/](https://github.com/wintermeyer/wincon/tree/main/priv/static/partials)
-  and are pulled in by `scripts/fetch-partials.sh` at deploy time
-  (with `data-book-current="phoenix"` stamped into the nav).
-- `partials/*.hbs`, `layouts/*.hbs`, `helpers/*.js`, `js/site.js`,
-  `img/*.svg` — carried from the Antora default UI so Antora's internal
-  plumbing and sidebar JS keep working
+Edit `src/` in
+[wintermeyer/wincon-antora-ui](https://github.com/wintermeyer/wincon-antora-ui)
+and push to main. A GitHub Actions workflow rebuilds `ui-bundle.zip`
+and re-uploads it to the `latest` release in ~30 seconds. The next
+deploy of this book (or of the Rails book) picks it up.
 
-For a tight iteration loop:
+For a tight local loop while editing the bundle, point this repo's
+playbook at the UI bundle checkout:
 
-```sh
-cd ui-bundle
-npm run dev      # Tailwind CLI in watch mode
-# then, in another shell, rebuild the bundle + site on demand
-npm run build && cd .. && npx antora --fetch antora-local-playbook.yml
+```yaml
+ui:
+  bundle:
+    url: /path/to/wincon-antora-ui/build/ui-bundle.zip
+    snapshot: true
 ```
 
-Dark mode follows the OS `prefers-color-scheme`; there is no toggle.
+## Per-book chrome override
+
+`scripts/fetch-partials.sh` pulls the canonical nav + footer from
+[`wincon/priv/static/partials/`](https://github.com/wintermeyer/wincon/tree/main/priv/static/partials),
+stamps `data-book-current="phoenix"` into the nav, and drops the files
+into `ui-supplemental/partials/`. Antora's `ui.supplemental_files`
+overlay then overrides the default `header-content.hbs` and
+`footer-content.hbs` shipped with the UI bundle. The `ui-supplemental/`
+directory is gitignored — it's generated at every deploy.
 
 ## Deployment
 
-Pushing to `main` triggers `.github/workflows/deploy.yml`, which runs on
-a self-hosted runner (label `eliph`) on bremen2. The runner checks the
-repo out, runs `scripts/deploy.sh`, and publishes the rendered site to
-`/var/www/elixir-phoenix-ash/releases/<timestamp>/`. An atomic symlink
-swap makes `/var/www/elixir-phoenix-ash/current/` point at the new
-release. The last five releases are kept.
-
-`scripts/deploy.sh` calls `scripts/fetch-partials.sh` first, which
-pulls the canonical nav/footer HTML from wincon (production → GitHub
-raw fallback) and overwrites `ui-bundle/src/partials/{header,footer}-content.hbs`
-before the UI bundle is built. A fetch failure is non-fatal: the
-committed copies are used as-is.
-
-Nginx serves the site under
-<https://wintermeyer-consulting.de/phoenix/book/> via two location
-blocks on the `wintermeyer-consulting.de` vhost (one for pages, one for
-`antora-assets/`). The old domain <https://elixir-phoenix-ash.com>
-returns a path-preserving 301 to the new location.
+Pushing to `main` triggers `.github/workflows/deploy.yml`, which runs
+on the self-hosted runner (label `eliph`) on bremen2. The runner
+checks the repo out, runs `scripts/deploy.sh`, and publishes the
+rendered site to `/var/www/elixir-phoenix-ash/releases/<timestamp>/`.
+An atomic symlink swap makes `/var/www/elixir-phoenix-ash/current/`
+point at the new release. The last five releases are kept.
+
+`scripts/deploy.sh`:
+
+1. Activates mise (Node 20 pinned in `.tool-versions`).
+2. Calls `scripts/fetch-partials.sh` to pull the canonical nav/footer.
+3. Runs `npm ci` and `npx antora --fetch antora-playbook.yml`.
+4. Copies `build/site/` into the new release dir and swaps the
+   `current` symlink.
+5. Prunes old releases (keeps last 5).
+
+A fetch failure in step 2 is non-fatal: Antora silently falls back to
+the UI bundle's default partials (with an empty `data-book-current`).
+
+## Nginx
+
+The site is served under <https://wintermeyer-consulting.de/phoenix/book/>
+via two location blocks on the `wintermeyer-consulting.de` vhost (one
+for pages, one for `antora-assets/`). The old domain
+<https://elixir-phoenix-ash.com> returns a path-preserving 301 to the
+new location.

antora-local-playbook.yml

@@ -12,8 +12,9 @@ content:
 
 ui:
   bundle:
-    url: ./ui-bundle/build/ui-bundle.zip
+    url: https://github.com/wintermeyer/wincon-antora-ui/releases/download/latest/ui-bundle.zip
     snapshot: true
+  supplemental_files: ./ui-supplemental
   output_dir: antora-assets
 runtime:
   fetch: true

antora-playbook.yml

@@ -11,8 +11,9 @@ content:
 
 ui:
   bundle:
-    url: ./ui-bundle/build/ui-bundle.zip
+    url: https://github.com/wintermeyer/wincon-antora-ui/releases/download/latest/ui-bundle.zip
     snapshot: true
+  supplemental_files: ./ui-supplemental
   output_dir: antora-assets
 runtime:
   fetch: true

scripts/deploy.sh

@@ -38,13 +38,14 @@ log "Repo: ${REPO_DIR}"
 log "Fetching latest nav + footer partials from wincon..."
 ./scripts/fetch-partials.sh
 
-log "Building UI bundle..."
-( cd "${REPO_DIR}/ui-bundle" && npm ci --no-audit --no-fund && npm run build )
-
 log "Installing Antora..."
 ( cd "${REPO_DIR}" && npm ci --no-audit --no-fund )
 
 log "Rendering site..."
+# --fetch refreshes both the content source (this repo) and the UI
+# bundle (wincon-antora-ui/releases/latest/ui-bundle.zip). The UI
+# bundle's snapshot:true in the playbook tells Antora not to cache
+# across runs, so a fresh bundle is always pulled.
 ( cd "${REPO_DIR}" && npx antora --fetch antora-playbook.yml )
 
 if [ ! -d "${REPO_DIR}/build/site/book" ]; then

scripts/fetch-partials.sh

@@ -1,15 +1,18 @@
 #!/usr/bin/env bash
-# Fetch the canonical nav + footer partials from wincon and overwrite
-# the Antora UI-bundle header-content.hbs / footer-content.hbs before
-# the UI bundle is built.
+# Fetch the canonical nav + footer partials from wincon and write them
+# into ./ui-supplemental/partials/ so Antora overrides the default
+# header-content.hbs / footer-content.hbs from the shared UI bundle
+# (wintermeyer/wincon-antora-ui) with book-specific content.
 #
 # Source of truth: https://wintermeyer-consulting.de/partials/
 # (served from wincon/priv/static/partials/).
 #
 # Falls back to the GitHub raw URL when production is unreachable.
 #
-# On fetch failure, keeps the committed .hbs files so deploys never
-# break on a transient network issue.
+# On total failure the supplemental files are left at whatever state
+# the previous run put them in (or absent on first deploy), so Antora
+# silently falls back to the bundle defaults. Deploys never break on
+# a transient wincon outage.
 
 set -u
 
@@ -19,7 +22,8 @@ BOOK_CURRENT="phoenix"
 
 cd "$(dirname "$0")/.."
 
-PARTIALS_DIR="ui-bundle/src/partials"
+PARTIALS_DIR="ui-supplemental/partials"
+mkdir -p "${PARTIALS_DIR}"
 
 try_fetch() {
   local source_name="$1"