History

doxa-maps-88655c70 5567134978 shoot the plugin-studio element and stop captioning the product SPA as the studio README drew the two cap-5 products apart in prose and even warned that captioning a studio shot as the product SPA is a documented mistake — then filled its plugin-studio slot with cap5-doxa-maps-spa.png. Both cap-5 figures showed the same app and no plugin-studio screenshot existed anywhere in the repo. A slot filled with the wrong real image looks exactly like a correct one; nothing 404s. So the fix is to shoot the missing artifact, not re-caption around the gap. Both cap-5 slots now use generated, freshness-gated images. Also adds check:shot-fidelity. The shot run reported 13x OK while every emoji rendered as a tofu box: this machine has no emoji font. Measured rather than assumed — the DOM carries 27 correct codepoints, so the markup is right and the defect belongs to the shot machine. Reports by default because installing a font is a Driver call; --strict blocks once one is present.		2026-09-21 10:59:28 +00:00
..
architecture	point docs at library/layouts and fix the stale bunx and provider-ladder claims	2026-09-21 10:43:11 +00:00
assets	README: lead with the SPA-composition trinity + visual proof (desktop & mobile)	2026-09-16 00:17:45 +00:00
readme-images	shoot the plugin-studio element and stop captioning the product SPA as the studio	2026-09-21 10:59:28 +00:00
screenshots	README: distinguish the two cap-5 apps (product SPA vs developer studio) and add current capability screenshots	2026-09-20 05:00:01 +00:00
develop-a-plugin-and-see-it-live.md	carry the push buffer flag in the golden path, not only the runbook	2026-09-21 07:34:05 +00:00
explanation.md	Complete app-profiles->plugin-designs sweep across comments/docs; build green; layouts kept at root (load-bearing)	2026-09-17 18:18:19 +00:00
how-to.md	point docs at library/layouts and fix the stale bunx and provider-ladder claims	2026-09-21 10:43:11 +00:00
README-embed-example.md	docs: simple README template for the embedded (in-host) copy	2026-09-11 18:50:31 +00:00
README-longform.md	point docs at library/layouts and fix the stale bunx and provider-ladder claims	2026-09-21 10:43:11 +00:00
README-SECTION-3-cli-commands.md	gate the docs' quoted scripts block against package.json	2026-09-21 10:47:51 +00:00
README.md	docs: close retest gaps — engine-swap recipe (provider param), instances.json recipe + schema, adopt embed-example into router	2026-09-11 18:50:31 +00:00
reference-library-index.md	generate the library menu and gate it against library drift	2026-09-21 07:25:18 +00:00
reference.md	gate the docs' quoted scripts block against package.json	2026-09-21 10:47:51 +00:00
slide-deck-outline.md	Plugin gallery: one generator for the dev server and the build	2026-09-16 20:04:18 -05:00
tutorial.md	point the tutorial at the studio folder and separate build from publish	2026-09-21 07:38:50 +00:00
why.md	README: lead with the story — one sign-up site is the bottleneck, the map embeds on every partner team's site, Training-for-Trainers roles, the share-button campaign, private CRM for the team list	2026-09-16 12:34:59 -05:00

README.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-config contract.
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.