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. |
||
|---|---|---|
| .. | ||
| api | ||
| colors | ||
| components | ||
| composables | ||
| constants | ||
| data | ||
| i18n | ||
| layouts | ||
| maps | ||
| packet | ||
| scripts | ||
| stores | ||
| styles | ||
| utils | ||
| index.js | ||
| ProfileLoader.vue | ||
| README.md | ||
library/ (@map) — the shared map template
The other half of the architecture (see ../plugin-designs/README.md):
every map in plugin-designs/<your-map>/ composes the reusable, parameterized pieces that live here.
Fix something here and every map benefits on the next build; break something here and every map
breaks — read components/WARNING.md before touching shared pieces.
| Folder | What lives there |
|---|---|
ProfileLoader.vue |
The root of every bundle: parses profile-config, loads the profile, provides the stores + config |
components/ |
Shared UI — map, legends, controls, popup (PeopleGroupDetail), tables, charts, hints (README) |
composables/ |
Shared logic — map engine (useMapInstance), provider switch, shadow-DOM styles, theming |
stores/ |
Per-instance Pinia stores (ui / map / data) — provided by ProfileLoader, injected by children |
api/ |
Data-source registry (sources.json) + fetch layer — the JAMstack runtime wiring |
colors/ |
Color sets maps opt into via profile-config.colorSet |
i18n/ |
The shared string catalogs (all maps speak the same languages) |
data/ |
Small shared datasets baked at build time (big served data lives in ../data/) |
constants/ |
Shared constants |
scripts/ |
Maintainer pipelines (posters, research) — not part of any bundle |
The rule of thumb (same as WARNING.md): custom code in your app-profile, reusable code here — and things only move from the first to the second once they've earned it.