How this knowledge base is authored and maintained. The repo is the source of
truth, not the wiki UI.
Every page lives as Markdown under docs/wiki/ in the main repo. The folder
structure maps 1:1 to the wiki's page tree:
| Repo path | Wiki path |
|---|---|
docs/wiki/home.md |
/home (the landing page) |
docs/wiki/hub/jobs.md |
/hub/jobs |
docs/wiki/playbooks/deploy-release.md |
/playbooks/deploy-release |
docs/wiki/_meta/capture-log.md |
/_meta/capture-log (unpublished — the decision trail) |
Edit the Markdown, then run the importer to push changes to the wiki.
The importer is scratchpad/wiki_import.py (a small GraphQL client). It is
idempotent — create-or-update — so it's safe to re-run anytime.
export WIKI_TOKEN='<the key>'python3 wiki_import.py — it walks docs/wiki/**/*.md, parses frontmatter, andA future upgrade is Wiki.js Git storage (auto-sync from the repo). Until then,
the importer is the sync mechanism.
Every page must follow these — they're what make the KB trustworthy:
title, description, published: true, tags: [...],editor: markdown, date.file:line for claims about behavior. Documenting is auditing./hub/jobs), not relative (hub-jobs.md).`docs/ARCHITECTURE.md`), not links.ai_bar / .kcc-* are internal only)docs/wiki/<section>/<slug>.md with the frontmatter above.home.md (and any related pages).Keep both current: when a risk is fixed, move it to the register's "Resolved" log and
tick the roadmap item.
The wiki logo is the GoBuild app mark (slate-900 rounded square + orange-400
hexagon), stored at docs/wiki/_assets/gobuild-mark.svg and set via Wiki.js
site.updateConfig(logoUrl=<data-URI>). See the Brand & UI guide.