History

doxa-maps-88655c70 1cf4e89dab Some checks are pending build-gate / build (push) Waiting to run Details Resolve a composite's child bundles against the tree root, not a guessed depth Driver-reported console text: Could not load <doxa-research-map> from ../../doxa-research-map/doxa-research-map.js A composite declares children as src: '../../<bundle>/<bundle>.js'. That literal is right from a one-deep leaf and wrong from a two-deep one, and the generator emits both: .../research-map-plus-grid/index.html ../../ -> /doxa-maps/ 200 .../research-map-plus-grid/default/index.html ../../ -> /doxa-maps/rmpg/ 404 So the path encoded an assumption about the host's depth that the host does not control and cannot see. It survived because every gate exercised the shallow leaf, which is genuinely fine. StackLayout now derives the tree root from the document's own pathname (up to and including the /doxa-maps/ segment) and rebuilds the path from there -- depth-independent by construction, so a third leaf depth cannot reintroduce it. Absolute, protocol-relative and root-relative srcs pass through untouched, and a missing /doxa-maps/ segment returns the original string, so this can only fix a path, never break a working one. Measured, both leaves, real browser with live data: one-deep mapEl=true mapH=792 canvasH=856 0 4xx two-deep mapEl=true mapH=792 canvasH=856 0 4xx (was 404, map absent) Also carries source that had been left behind by its own built output: the cities/gospel legend bounding (shipped in `5008a6f` as output only) and the per-profile config carrier in generate-tree.mjs, plus a new fits-screen clause that wheels inside every column rather than one.		2026-09-23 19:34:28 +00:00
..
app-wrapper-material	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
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	consolidate docs into documentation/ and deployment shells into deployment/	2026-09-21 23:23:23 +00:00
StackLayout.vue	Resolve a composite's child bundles against the tree root, not a guessed depth	2026-09-23 19:34:28 +00:00
VerticalTabsLayout.vue	Match the tab radius to the rest of the app, and open on the tab you were last on	2026-09-23 01:03:15 +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.