Handbook

Product repo ↔ handbook deploy shell

Four private handbook pairs share one pattern — product Markdown in the * repo, Firebase deploy wiring in the *w shell with kitchensink + product submodules.

The collision

Engineers edit the wrong tree (flsw instead of fl), or deploy without bumping the product submodule pointer — handbook shows stale docs.

How to choose

1) Is the change product documentation or API behavior? → edit ff, lcdl, fl, or fp. 2) Is the change only Firebase/hosting/generator wiring? → edit ffw, flw, flsw, or fpw. 3) Ready to publish? → bump submodule in *w, build generator, deploy-websites.sh --only . 4) Did kitchensink CSS/components change too? → propagate ks first (sync-kitchensink-and-rebuild.sh).

Using several at once

ff+ffw (fleet-2f1d3), lcdl+flw (lcdl-542d8), fl+flsw (lenses-d0fdb), fp+fpw (forge-platform-1541d). Each shell submodules kitchensink/ and the matching product repo.

Terms covered

Examples from chat / plan.md

LCDL task operator docs changed in forge-lcdl/docs → commit lcdl → cd flw → git submodule update --remote forge-lcdl → build-site.py → ./deploy-websites.sh --only forge-lcdl-website

Fleet admin API doc fix in forge-fleet/ → separate commit in ffw bumping forge-fleet submodule only after ff push.

Bridge page handbook-deploy-pairs — read when multiple abbreviations appear in one sentence.