a876e5e97b
- ShareButton resolves its link from where the bundle is hosted (profile-config.shareUrl -> embedBaseUrl -> window.MAP_EMBED_BASE_URL -> the bundle's own script URL); profiles pass tree-relative embed pages, so links work in the playground, on doxa.life and on any CDN - Generated leaf pages try token endpoints in order (override -> configured absolute URL -> same-origin) and only then offer the paste-once box; build config points at the canonical https://doxa.life/api/maps/token - Dev playground extracted from vite.config.js into internal/playground/{discover,render,dev-plugin}.mjs; serves /assets/* like the built site so data-driven maps initialise; passes assetsBase + shareUrl to every element; header ladder with a Start-here primer and the five kinds of mounting files (single-element, preset-element, multi-view-element, composite-element, app-shell) - New gates: smoke:playground (every element boots, with status text + data diagnostics), smoke:share (Share URL resolves and reopens the same map), sync:dropin (mirror public/ into a host checkout, never credentials), deploy:dev (build + sync) - MapToolbar + ShareButton on every map profile; UPG-100 composite (map + prayer lists) on the pane layout; shared --map-radius token consumed by the legend components - docs/reference.md: profile types table, profile-config assetsBase/shareUrl/embedBaseUrl, gates |
||
|---|---|---|
| .. | ||
| architecture | ||
| assets | ||
| explanation.md | ||
| how-to.md | ||
| README-embed-example.md | ||
| README.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.