AnvilWiki template update log (v2.37.0): the CLI now speaks Chinese — apply-template asks your interface language on interactive runs (or pass --lang zh), while scripted/non-interactive runs stay byte-identical. The fifth full-project code review landed in the same release: 10 confirmed findings fixed — consent event/storage literals now pinned by a contract test (a one-sided rename silently killed ad loading), a silent shell-$ expansion in cover frontmatter splicing eliminated, dead code and duplicate truth-sources (order field, t(), llms.txt enum) removed. 24 suites / 390 tests. Forks: merge upstream and pnpm install as usual. This bar tracks template releases — details & full changelog on GitHub Releases.
Learning Manual Development Manual Templates Highlights GitHub Demo
AnvilWiki
Esc Close · ↵ Search
Powered by Pagefind
中文

Development Manual

For customizers and contributors: the change map, categories & locales, theme & homepage copy, feature switches, CI & security, syncing upstream or contributing back, and running ops through AI (GSC API setup, anvilwiki-ops CLI + MCP).

9 lessons

  1. 1 Read the Map First: What to Change, What to Leave Alone Three layers — code (rarely touched), config (once per game), content (daily). A 30-second decision tree for any change, plus six Astro gotchas (5→7 re-verified).
  2. 2 Add Categories and Add Languages Step-by-step recipes for adding a navigation category (three-place consistency) and adding a language (scaffold plus translation prompts). A lookup manual.
  3. 3 The Feature-Toggle Table: Ads, Comments, Analytics All optional features share one toggle mechanism — empty variable = nothing rendered. The full variable table, where they go, and the advanced wrangler.toml route.
  4. 4 Verify Your Changes: The Checklist and the Gates The post-change, pre-commit checklist: seven local commands, the eight CI gates, the six pipelines, and the safety and performance baselines.
  5. 5 Sync Upstream: Bringing Official Updates In Three commands to merge official updates, the conflict mantra, and the semver promises that decide whether you upgrade.
  6. 6 Contribute Back: Returning the Good Parts Five steps to contribute to AnvilWiki (issue first, branch, self-verify, PR, tests and docs), plus PR-ing your own site onto the official showcase wall.
  7. 7 Run Ops with AI: GSC setup, metrics & MCP GSC API setup in five minutes (Google Group relay), CF token into .env, then doctor, metrics and evidence-ranked insights — with MCP, every write lands as a PR.
  8. 8 The Content Pipeline: Keyword CSV to Draft PR Paste a keyword CSV into Actions; the pipeline builds drafts, runs all eight gates, and opens a draft PR only on all-green. No AI keys in CI; a human merges.
  9. 9 Multi-Site Management: One Toolkit, N Sites From site two: register in sites.toml (credentials never enter), inspect with one command via --all and --site; submit refuses --all. AI referrals read as trends.