c8242064e6
Step 2 told an author to create 'exactly four files'. Measured across the 18 shipped bundles, the folder holds 3 to 8 files and NOT ONE has exactly four. all-people-groups is the true minimum at 3 (root .vue + index.js + index.html) and is a fully working, manifest-listed plugin. 9 of 18 carry no .meta.json at all, because the single and prop-table tiers are INFERRED rather than declared. The table now marks each file required or opt-in, and adds the two files real bundles actually use that the doc never mentioned: <name>.instances.json (which is what makes a bundle prop-table / cap-2, per discover.mjs) and src/. Verified the one claim that matters by testing it: moving index.html out of demo-map made the build error and dropped the bundle from the buildable list (18 -> 17); restoring it returned a clean build, byte-identical to HEAD. Capability inference confirmed against the built manifest: all-people-groups type=single, demo-map and doxa-vision-card type=parameterized. |
||
|---|---|---|
| .. | ||
| 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.