ba55689f2f
Step 6 told an author that surfacing a plugin means adding a TAB_DEFS entry and a NAV_MODEL row. That overstates the work. The cap-5 SPA reads the built manifest at runtime and auto-discovers every bundle that is neither curated nor on the NOT_EXPERIMENTAL exclusion list, placing it in the Experimental folder with its label and description from the manifest. Verified in a browser rather than from the comment that claims it: the rail rendered 11 rows - 6 curated, then 5 auto-discovered (all-people-groups, country-posters, demo-map, doxa-vision-card, stack-demo), each carrying the flask marker. The manual edit is still documented, reframed as what it actually is: optional promotion OUT of Experimental into the curated teaching order. Also recorded the one-row-per-bundle rule and the fail-soft behaviour, and corrected the closing summary, which omitted the new mount step and implied surfacing was manual work. |
||
|---|---|---|
| .. | ||
| architecture | ||
| assets | ||
| readme-images | ||
| screenshots | ||
| develop-a-plugin-and-see-it-live.md | ||
| explanation.md | ||
| how-to.md | ||
| README-embed-example.md | ||
| README-longform.md | ||
| README-SECTION-3-cli-commands.md | ||
| README.md | ||
| reference-capability-exemplars.md | ||
| reference-library-index.md | ||
| reference.md | ||
| slide-deck-outline.md | ||
| tutorial.md | ||
| why.md | ||
docs/ — pick your path
"what is this?" "teach me" "how do I …?" "look it up" "all the detail"
│ │ │ │ │
why.md ──────────► tutorial.md ────► how-to.md ────► reference.md ───► architecture/
(2 min, 1 diagram) (first map) (task recipes) (tables) (contracts)
- why.md — the problem and the "map islands" idea. Start here.
- tutorial.md — build your first map, no jargon.
- how-to.md — recipes: embed, iframe, SPA, colors, CDN, mobile, tokens.
- reference.md — config fields, build scripts, the
profile-configcontract. - explanation.md — the model in 15 lines.
- architecture/ — the deep end: full contracts, the per-file catalog.
- README-embed-example.md — the drop-in README used when this bundler is embedded inside a host repo.
Nothing on the simple path is longer than a few minutes; everything complex lives in
architecture/, linked from where you'd need it.