The SPARSE series line rounds its total to tens -- 173 reads as ~170, 28 as ~30 -- because a series that large is read as a size, not counted. Below ten the rounding breaks: China is the only 3x4 country sheet, so its tier has one member, and Math.round(1 / 10) * 10 = 0 printed "1 of ~0 maps". Under ten the line now states the exact count, "map 1 of 1" -- the same text the dense layout already prints for China, so the move to SPARSE is not a regression for it on the print. PROVED: China rendered SPARSE reads "— map 1 of 1" with 0 occurrences of "~0"; and Sudan rendered after this change is BYTE-IDENTICAL to Sudan rendered before it, so no series of ten or more changes -- the 173 country sheets and the UPG-100 zones are unaffected. Not decided here: China's thumbnail says 174 of 174 and its print 1 of 1. That is per-tier against whole-series numbering, the pre-existing R-CHN-SERIES-TIER, left for a product decision after the demo. poster-render.js is sha384-pinned; re-pinned so check:poster-render-pinned accepts it. |
||
|---|---|---|
| .. | ||
| api | ||
| charts | ||
| 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.