|
Some checks are pending
build-gate / build (push) Waiting to run
contain:paint was removed earlier for the scroll bug, but LAYOUT containment also makes .vtl-content the containing block for every position:fixed descendant, so all modal scrims hosted in the shell resolved inset:0 to the CONTENT PANE: measured, a fixed inset:0 probe read x=256 w=1184 on a 1440 viewport -- the 256px nav rail stayed clickable behind an open modal. Visibly almost right, interactively wrong. The perf rationale for keeping it does not hold: a nav collapse changes this element's own width, and a width change re-lays-out the subtree with or without containment. Verified: fixed probe now 0,0 1440x900; check:scrim-viewport PASS (3 scrims cover the viewport in the shell); check:fits-screen PASS (scroll/zoom/reachability contract intact); nav collapse round-trips. |
||
|---|---|---|
| .. | ||
| api | ||
| colors | ||
| components | ||
| composables | ||
| constants | ||
| data | ||
| i18n | ||
| layouts | ||
| maps | ||
| 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.