Corey PettyandClaude Opus 4.8 dc89328b56 Migrate site to Quartz 5 ...

Follows the official v5 migration: branch from upstream/v5, run
`quartz create` (non-interactively, via -t/-X/-s/-b/-l), then restore this
site's customisations on top.

Config moves from TypeScript to YAML. The port was small - the only
deviations from upstream defaults were pageTitle and baseUrl, so
quartz.config.yaml is the generated default with those two changed and
markdownLinkResolution kept at "shortest". quartz.layout.ts is gone
entirely; layout position is now a per-plugin property, and 44 built-in
components resolve as community plugins via quartz.lock.json.

Carried over from v4: content (verified byte-identical, 194 files, no
additions and no losses), serverless/inline-comments-worker, docs-internal,
custom static HTML and images, AGENTS.md/CLAUDE.md, and the .gitnexus /
.dev.vars / .wrangler ignore rules.

Deliberately not carried over:
- quartz/components/InlineComments.* - becomes a standalone v5 plugin, see
  docs-internal/inline-comments-v5-plugin-migration.md
- quartz/plugins/transformers/tikz.ts - custom transformer, used by exactly
  one content file; needs its own port and should not block this
- quartz.config.ts / quartz.layout.ts - superseded by quartz.config.yaml

The deploy workflow gains the mandatory `npx quartz plugin install` step and
a plugin cache keyed on quartz.lock.json, but is deliberately left on
workflow_dispatch only. GitHub Pages has a single production deployment, so
a push trigger here would immediately replace the live v4 site; the push
trigger is commented out until cutover.

Verified: build succeeds, 194 files parsed, 360 pages emitted, no content
from ignored paths leaked into the output.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>

2026-07-20 12:15:05 -04:00

..

inline-comments-worker

Migrate site to Quartz 5

2026-07-20 12:15:05 -04:00