History

doxa-maps-88655c70 09014f8a03 Some checks are pending Deploy to GitHub Pages / build (push) Waiting to run Details Deploy to GitHub Pages / deploy (push) Blocked by required conditions Details Rename the output folder to dx-maps Driver decision: no embeddable URL carries "doxa" in its folder. The tree's name is one line in vite.doxa-maps-build-config.json ("name": "dx-maps"); everything else follows it. - __DOXA_TREE_NAME__ (the vite define rega landed, from MFE_NAME = internal/_tree-name.mjs) bakes the name into the bundles for the runtime code that must recognise the tree in a URL. StackLayout.vue's resolveBundleSrc anchored on a literal /doxa-maps/ and would have broken every composite's nested bundles on a renamed tree; it now anchors on the define. The Research Gallery's dev fallback uses it (one reader: rega's define, not a second one). - The native shells follow via internal/sync-app-shells.mjs: capacitor webDir public/dx-maps, Tauri frontendDist ../../public/dx-maps (its window url is tree-relative since the one-folder landing). - The WordPress contract test reads the name from config instead of carrying three literals. - check:locale-reachable extracted detectLocale alone and died with "localeFromUrl is not defined" after `09d03c60` factored a helper out; it now follows the calls it makes (already red on main). - generate-tree removes its temp asset pool even when it crashes (a failed build leaked ~50 MB into /tmp each time; measured on a full disk). - Capability exemplars regenerated for the new paths. Proof: rm -rf public && bun run build -> public/ = README.md + dx-maps/; the 25 built bundles carry zero 'doxa-maps/' paths (scanned); check:sri, check:drop, check:parse, check:public-hygiene PASS. Tag names (doxa-* -> dx-*) are the next, separate landing.		2026-09-25 19:26:14 +00:00
..
architecture	Research Gallery: embed on someone else's page, in both modes	2026-09-24 19:03:37 +00:00
assets	consolidate docs into documentation/ and deployment shells into deployment/	2026-09-21 23:23:23 +00:00
contributing	README: lead with the objectives, showcase the Research Gallery, teach the agent swarm	2026-09-24 18:34:02 +00:00
readme-images	README: the Experimental shelf, with Wall of People Groups and the Prayer Walk Planner	2026-09-25 11:22:52 +00:00
screenshots	consolidate docs into documentation/ and deployment shells into deployment/	2026-09-21 23:23:23 +00:00
CONTRIBUTING.md	README: lead with the objectives, showcase the Research Gallery, teach the agent swarm	2026-09-24 18:34:02 +00:00
develop-a-plugin-and-see-it-live.md	Golden path: a six-step table first, the incident notes in a log at the bottom	2026-09-25 03:29:39 +00:00
explanation.md	consolidate docs into documentation/ and deployment shells into deployment/	2026-09-21 23:23:23 +00:00
how-to.md	Land the swarm's work: no iframes anywhere, a tree that keeps its shape, deeper facets	2026-09-22 14:51:52 +00:00
README-embed-example.md	consolidate docs into documentation/ and deployment shells into deployment/	2026-09-21 23:23:23 +00:00
README-SECTION-3-cli-commands.md	Integrate main into bundler-2/work	2026-09-25 18:21:45 +00:00
README.md	README: lead with the objectives, showcase the Research Gallery, teach the agent swarm	2026-09-24 18:34:02 +00:00
reference-capability-exemplars.md	Rename the output folder to dx-maps	2026-09-25 19:26:14 +00:00
reference-library-index.md	Merge main into bundler-1/work (regenerate the tree, re-hash)	2026-09-24 05:33:32 +00:00
reference.md	Reference: the "I want to…" table first, wrong facts fixed, history to a log	2026-09-25 03:48:26 +00:00
tutorial.md	Docs: every build line a reader copies now carries BUILD_ALLOW=1	2026-09-25 03:07:52 +00:00
vendored-font-noto-serif-devanagari.md	Move the vendored font's README out of the served folder	2026-09-24 04:15:26 +00:00
why.md	consolidate docs into documentation/ and deployment shells into deployment/	2026-09-21 23:23:23 +00:00

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

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.