Following the generator's pin (studio's follow-up): the Natural Earth table the sheets fetch at print time (boundaries/ne-places.json) is data, not code, but pinned the same way — its sha384 sits beside the generator's in poster-render.integrity.js (bun run pin:poster-render writes both), and posterSheets hashes the fetched text before parsing it. A table that is not the pinned one is not used: the sheet draws no city dots and says so in the console, rather than plotting places it cannot vouch for. check:poster-render-pinned, two-sided for the table as for the generator: the pin matches the source and the served copy; a FORGED table (every name replaced) yields exactly the sheet drawn with no places; the genuine table IS used (its sheet differs) — the probe's pins now span Chad, because a single pin framed too small an area for any place to fall inside it and the check could see nothing. check:poster-browser-equiv still byte-identical; gates:pre green. |
||
|---|---|---|
| .. | ||
| 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.