86442aa4c0
repo's Arabic screenshot of the list was clean except for one string: the search box still read "Search people group, zone, or territory…" in every locale. It was a hardcoded literal, the last English on an otherwise localized screen. NO NEW TERMINOLOGY — composed from wording this product already ships and has already approved: search.kinds.peopleGroup for the group, tabs.upg100Zone for what this plugin calls a "zone" (its own legend names them "UPG-100 Lists" / "قوائم UPG-100" / "UPG-100 名单"), and search.kinds.region for the territory. That is precisely why this one could be translated while the UUPGs column header could not: there, no source established any candidate acronym, and a wrong term looks authoritative to a reader who cannot check it. Here the words were already on the page. ⚠ A computed, and declared beside LEGEND_TITLE rather than at the literal's old position, because t() is not initialised until later in setup — a const at the original line would have captured the fallback and never re-evaluated when the locale changed. |
||
|---|---|---|
| .. | ||
| 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.