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
..
app-wrapper-material	UPG-100: lead with Prayer Resources, map second	2026-09-23 20:33:00 +00:00
pane-wrapper	Brand-neutral shared VerticalTabsLayout with lazy nested-element hosting; fix cap-5 prayer tab leaf path; neutralize library identifiers; add Forgejo CI build-gate workflow	2026-09-19 17:24:30 +00:00
README.md	Move internal files out of the repo; fix five dead links; a fuller delegation diagram	2026-09-25 05:14:10 +00:00
StackLayout.vue	Rename the output folder to dx-maps	2026-09-25 19:26:14 +00:00
VerticalTabsLayout.vue	VerticalTabsLayout mirrors for right-to-left, and the gallery sets its direction	2026-09-25 04:41:01 +00:00

README.md

layouts/ — app wrappers

Each folder here is an app wrapper: a host shell that composes doxa-maps plugin-designs (the independently-built custom elements) into one application.

  layouts/<wrapper>/          ← the HOST page (not a bundle)
  ┌──────────┬──────────────────────────────┐
  │ sidebar  │  mounts an app-profile here    │
  │ (nav.js) │  ┌──────────────┐              │
  │  ├ item  │  │ <doxa-map>    │  ← a         │
  │  ├ section│ │  (a bundle)   │    micro-    │
  │  └ folder │ └──────────────┘    frontend  │
  └──────────┴──────────────────────────────┘

app-profile = a self-contained custom element (the micro-frontend). app wrapper = the host that mounts them and provides nav/chrome. A wrapper is a host page, not a bundle-in-a-bundle.
Wrappers today: app-wrapper-material/, pane-wrapper/.
Icons are inline SVG only (no CDN) — an F-Droid/offline hard requirement.

Sidebar contract, target filtering, sidebar modes, staging: ../documentation/architecture/app-wrappers.md.