334b3d6fa1
STAGED, NOT FLIPPED. SET_FILL_MODE in GiCenteredSetMap is 'fit' — today's behaviour, unchanged — with the alternative named beside it so the ruling is one line and a rebuild. 'fit' is not a placeholder: it is the honest mode for a page that cannot zoom, so the POSTER should keep it whatever the screen chooses. The binding constraint is recorded there because it is not obvious from the numbers: separation can never fall below twice the pin floor (5.2), and an 18.5-unit band therefore holds at most three rows, so no minSep reaches ring 2's 658 groups. minSep 7 places 931 of 2,074; minSep 5 places 1,369; minSep 4 places 1,369 — identical, which is what proves depth rather than separation is binding. 'fill-all' places all 2,074 with none under a label and ring 2 using 18 rows. THE CAPTION states the TRUE total — the groups that have a ring — not the number of pins currently drawn. In the dense mode the same groups read as an arc of colour zoomed out and as separate pins zoomed in, so a caption counting what is visible would change as the reader moved: true at every instant and misleading overall. It joins the paragraph that already accounts for the centre, the no-relation groups and the unmatched ones, so those four numbers reconcile instead of competing. centered.shown added in all eleven locales; parity and keys-exist pass, and hardcoded-english did not rise (257, and that fall is studio's, not mine). |
||
|---|---|---|
| .. | ||
| api | ||
| charts/whiteboard | ||
| colors | ||
| components | ||
| composables | ||
| constants | ||
| dashboards | ||
| data | ||
| elements | ||
| i18n | ||
| layouts | ||
| lists | ||
| maps | ||
| packet | ||
| packets | ||
| scripts | ||
| stores | ||
| styles | ||
| utils | ||
| vendor/cldr | ||
| 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.