Website publishing (sti.forgesdlc.com)

The handbook HTML for Forge STI is produced by forge-sti-website, not this repository. Canonical Markdown remains in forge-sti; the website repo embeds forge-sti as a git submodule and runs forge-autodoc via:

pip install markdown
python3 generator/build-site.py

Firebase project forge-sti-handbook backs Hosting (see forge-sti-website/README.md).

Publish pipeline

1. Commit and push changes in forge-sti (this repo).
2. In forge-sti-website, bump the forge-sti submodule (git submodule update --remote forge-sti or pin SHA).
3. From forge-sti-website: python3 generator/build-site.py emits HTML under website/.
4. Deploy from the Code workspace root:

./deploy-websites.sh --only forge-sti-website

Navigation metadata

The generated handbook groups pages by nested folders under docs/ and uses per-file YAML frontmatter consumed by Kitchen Sink forge-autodoc. No separate site.yml is required.

Submodule mirror (local dev)

If you cannot wait on remote SHA, mirror scoped subtrees only — never delete the submodule .git/:

rsync -a --delete forge-sti/docs/ forge-sti-website/forge-sti/docs/
rsync -a --delete forge-sti/schemas/ forge-sti-website/forge-sti/schemas/
cp forge-sti/README.md forge-sti-website/forge-sti/README.md

See workspace rule forge-sti-handbook.mdc.

Dual-wiki ownership

See Dual-wiki architecture for normative repo boundaries.