404b2c866e
gospel-resource-rows.js builds each resource row's display text, and its fallbacks were English literals: a record with no name of its own showed "Scripture in this language", "Audio Scripture", "Listen in a browser" to an Arabic or Chinese reader — precisely the rows whose source data was least complete. check:hardcoded-english does not read .js files, which is why the bundle's sweep never saw them. Thirteen keys in eleven locales, and the translator is PASSED IN rather than imported: the module is a pure function with no component context, and it stays optional, so a caller without one degrades to the English written at the call site instead of throwing. Three publisher names stay verbatim — JESUS Film, Scripture Earth, Zume — but where a name sits inside an ordinary phrase the phrase is keyed and the name is INTERPOLATED, so "Zume discipleship training" translates around a brand a translator never retypes. SE_KIND's values are displayed and take keys; its keys are the upstream feed's codes and must not be touched. Verified by running the module both ways: without a translator every row reads as it does today; with an Arabic one the labels and scopes are Arabic while "Scripture Earth" and "Zume" are unchanged. ROUTED TO STUDIO, not self-landed: the eleven locale files make this a library change. The route test says 11, and the last time I judged a landing by which plugin the work was for rather than which directories it touched, the scan ran against most of the fleet and timed out twice. |
||
|---|---|---|
| .. | ||
| 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.