- The Goal and Isaiah 40:3 lead the README, byte-for-byte as written on the public repo (driver-web-edits.patch), so the next export keeps them. - Each of the 5 capabilities and 5 deployment methods is now a one-line summary, its picture, and a collapsed "More about…" dropdown. 16 dropdowns, none open by default, so a reader can scroll the pictures and summaries. - WordPress / Disciple Tools and desktop say what is true in plain words: we got a JAMstack map running there; proven, not yet a production feature; the Research Gallery could become a strong desktop app. Their cards match. - The agent-swarm section explains the problem in plain words (one shared library and one build means one bad change breaks every map), with a git glossary and the commands folded away. - Get it running now includes your own free Mapbox token (the public copy ships without one), and a dropdown on changing the studio itself. - The diagram has eight plugin nodes, main at the centre behind a padlocked merge-queue ring, and a plain-language "How main is protected" strip. |
||
|---|---|---|
| .. | ||
| architecture | ||
| assets | ||
| contributing | ||
| readme-images | ||
| screenshots | ||
| CONTRIBUTING.md | ||
| develop-a-plugin-and-see-it-live.md | ||
| explanation.md | ||
| how-to.md | ||
| README-embed-example.md | ||
| README-SECTION-3-cli-commands.md | ||
| README.md | ||
| reference-capability-exemplars.md | ||
| reference-library-index.md | ||
| reference.md | ||
| tutorial.md | ||
| vendored-font-noto-serif-devanagari.md | ||
| why.md | ||
documentation/ — 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.
Working on the repo:
- develop-a-plugin-and-see-it-live.md — ★ the golden path: zero to a plugin live, in 6 steps.
- README-SECTION-3-cli-commands.md — every command, per deployment method, with prerequisites.
- reference-capability-exemplars.md — which bundle is at which capability tier (generated).
- reference-library-index.md — the reusable
library/pieces you can import (generated). - CONTRIBUTING.md and contributing/ — how to contribute, and the bar for
library/.
Nothing on the simple path is longer than a few minutes; everything complex lives in
architecture/, linked from where you'd need it.