e3df4677d3
Some checks are pending
build-gate / build (push) Waiting to run
With every composition tree open, the rail was too long to find your way around. Each composite now carries a chevron and starts folded, so the rail first reads as the 35 plugins by capability, each composite saying how many parts it has. Open one and you see its direct parts; a part that is itself a composite folds again, so doxa-maps-spa opens to its tabs and each tab opens to what it is made of, one level at a time. Choosing a composite also opens it; only the chevron closes it. The same child folds independently wherever it appears. VerticalTabsLayout gains two optional row fields: `branch` makes a row foldable, `ancestors` hides a row until every branch above it is open. Rows are wrapped so the chevron can sit beside the tab rather than inside it. doxa-maps-spa sets neither field and renders unchanged. |
||
|---|---|---|
| .. | ||
| app-wrapper-material | ||
| pane-wrapper | ||
| README.md | ||
| StackLayout.vue | ||
| VerticalTabsLayout.vue | ||
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.