History

doxa-maps-88655c70 2b08a4e8de i18n: 408 strings copied from DX-life, 8 locales, RTL, and the data follows too Localisation was the lowest dimension on the board at 12. The repo already had the vue-i18n layer — 11 locales, one JSON per area, eager glob, fallbackLocale en — so this adds an AREA, not a mechanism: library/i18n/locales/<lc>/ regions.json, 51 keys x 8 locales, every string COPIED from their own common.json rather than translated by me. The composer takes the namespace from the FILENAME, so the files are flat like legend.json (a "regions" wrapper would have produced regions.regions.*). ★ THE REASON IT DIDN'T WORK, AND WHY IT FAILED SILENTLY. With the Spanish catalogue provably in the bundle, every string still rendered English. The bundle installed i18n with app.use() but never app.provide('appI18n') — so ProfileLoader could not drive the locale (it does exactly that at ProfileLoader.vue:168-169, from profile-config.locale, its "established contract"), and createAppI18n resolves its locale ONCE from <html lang>, which every generated leaf page bakes as "en". One line, copied from doxa-simple-map/index.js:84-86. It degraded quietly because the t() shim falls back to its key, so a missing catalogue renders as English instead of throwing — convenient in production, and exactly what hid this. t() is a shim, not vue-i18n's t(), because their keys ARE English sentences and several contain dots ('Loading results...', 'Type to search...') which is vue-i18n's key separator. tm() returns the namespace object and we index it by the literal string, so the port reads 1:1 with their source: t('Prayer Coverage'). Plugin-local, per the placement rule — it is four lines shaped entirely by how these pages were written. THE DATA FOLLOWS THE LOCALE TOO, which the chrome alone would have hidden. The prayer API localises its labels from ?lang=, and our components read cfg.languageCode while the locale arrives as cfg.locale. Measured with ar: the whole UI translated and every country in the table stayed English. Now the fetch falls through locale/lang and refetches on change (Angola -> the Arabic list). RTL: ar sets dir on OUR OWN root via RTL_LOCALES, the house pattern (doxa-simple-map.vue:246/1346) — never document.documentElement, which belongs to whatever page embeds us. Verified in a screenshot, not just an attribute: the goal cards reverse order, the table right-aligns, the progress bars fill from the right. A CLONE FIX came free with it. Porting their uupgListTranslations.ts — the authoritative list of what this component's labels are called — corrected strings I had written from the markup instead: the rop1 filter is "People Group" and I had "Affinity Bloc"; the search placeholder is the full "Search names, country/continent, religions..."; prayer_coverage reads "Intercessors". Two assertions of mine were wrong again, both failing on correct behaviour: the back-link compared for equality when it carries their leading arrow, and the RTL check read document.documentElement.dir when an embedded element must not set it. Not done: it/ro/zh have no regions.json — DX-life translates 8 of our 11 — and resolve through fallbackLocale en, which library/i18n/README says is fine. Oswald (their Cyrillic heading face) is still unvendored. English unchanged throughout: region 68/68 vs live, country 28/28, chooser, map and dashboard suites all green, no gate newly red.		2026-09-24 03:00:38 +00:00
..
all-people-groups	light the remaining unconditional loading overlays and the copy-me starter	2026-09-21 16:40:53 +00:00
big-picture	Stop Big Picture showing the same total twice	2026-09-23 15:32:28 +00:00
cities-internet	Commit the two pinHint:false metas that were only on disk	2026-09-24 00:01:08 +00:00
country-posters	Search tier 2: a misspelled country resolves to THE country (best match, 2-edit cap)	2026-09-24 00:34:19 +00:00
dashboard-plus-grid	Religion/Language tree TOP TIERS now filter the grid (derived-axis interop)	2026-09-23 23:00:00 +00:00
demo-map	consolidate docs into documentation/ and deployment shells into deployment/	2026-09-21 23:23:23 +00:00
doxa-maps-spa	Regions mounts its cap-4 composite; UPG-100 drops its duplicate share and shrinks its dots	2026-09-23 19:37:55 +00:00
doxa-research-map	Merge main into bundler-2/work	2026-09-24 00:44:26 +00:00
doxa-simple-map	Search tier 2: a misspelled country resolves to THE country (best match, 2-edit cap)	2026-09-24 00:34:19 +00:00
doxa-vision-card	Brand-neutral shared VerticalTabsLayout with lazy nested-element hosting; fix cap-5 prayer tab leaf path; neutralize library identifiers; add Forgejo CI build-gate workflow	2026-09-19 17:24:30 +00:00
golden-path-check	golden-path-check: walk the develop-a-plugin-and-see-it-live path end to end	2026-09-22 03:55:18 +00:00
gospel-resources	Commit the two pinHint:false metas that were only on disk	2026-09-24 00:01:08 +00:00
key-cities	Resolve the shared asset base per bundle, so nested tabs stop 404ing	2026-09-23 12:14:52 +00:00
my-upg-100-list	Search tier 2: a misspelled country resolves to THE country (best match, 2-edit cap)	2026-09-24 00:34:19 +00:00
people-groups-grid	Religion/Language tree TOP TIERS now filter the grid (derived-axis interop)	2026-09-23 23:00:00 +00:00
plugin-studio	Plugin studio: show what a composite is made of, in one panel	2026-09-23 20:21:48 +00:00
prayer-walk-planner	Prayer-walk POSTERS: per-zone walking-scale street map on a poster sheet	2026-09-24 01:06:51 +00:00
regions-dashboard	i18n: 408 strings copied from DX-life, 8 locales, RTL, and the data follows too	2026-09-24 03:00:38 +00:00
research-dashboard	One prop swaps the engine for every map, not just three	2026-09-24 01:34:03 +00:00
research-map-plus-grid	Map engine is one prop: MapLibre drops the search bar, legend rises	2026-09-24 00:43:44 +00:00
stack-demo	Let a stacked composite find its siblings in either tree	2026-09-22 15:37:41 +00:00
template-bundle	consolidate docs into documentation/ and deployment shells into deployment/	2026-09-21 23:23:23 +00:00
.gitkeep	Rename app-profiles -> plugin-designs; build green under new naming (load-bearing paths updated, guards pass)	2026-09-17 18:18:18 +00:00
README.md	consolidate docs into documentation/ and deployment shells into deployment/	2026-09-21 23:23:23 +00:00

README.md

plugin-designs/ — where YOUR maps live

The shared template lives in ../library/ (aliased @map) — you never edit it per-map. You build your map by making a folder here, plugin-designs/<your-map>/, and composing the template's building blocks. Your folder is yours (colors, API, i18n); the template is shared (Apache-2.0, propagated to every map on the next build).

Shared vs. yours — the balance

  library/  (@map)  ── SHARED, reusable, parameterized ──►  legend · map · map-controls
        │                                                    (every map reuses these)
        │  imported by
        ▼
  plugin-designs/<your-map>/  ── YOURS ──►  the map's "main" class (the .vue profile = the Vue
        │                                  instance for that map)
        └── src/            ── YOURS ──►  this map's OWN non-reusable components, colors, API, utils

  One bundle can hold as many maps as you want — add another .vue profile and rebuild.

Reusable → library/. The legend, the map, the map-controls are shared, parameterized components every map reuses. Fix once, every map benefits. Never edit it to customize one map.
This map's own → plugin-designs/<your-map>/. It holds two things: the map's "main" class (each .vue profile is the Vue instance for that map) and that map's own non-reusable components (in src/). Nothing here leaks to another map.
Many maps per bundle. The bundler bundles one map or many — add another flat .vue and rebuild.

Production or experimental — every profile declares itself

Every app profile is one of two things, and experimental profiles are unlimited and encouraged — create as many as you need:

Experimental, not built: prefix the folder with _ — the build skips it; it just sits in code. Zero cost, zero risk.
Experimental, built: builds normally, but it belongs in the Experimental section of the power app's layout (nav section) — never embedded on partner surfaces.
Production: a real product — main sections of the power app + individually embeddable.

(The power app = the SPA layout that composes all profiles into one application.)

The pattern in one picture

plugin-designs/<your-map>/     ← one FOLDER = one BUNDLE, named after the folder
   ├── index.js               ← entry: registers the custom element, finds the profiles
   ├── overview.vue           ← one .vue = one PROFILE (flat in the folder — no profiles/ subfolder)
   └── detail.vue             ← another profile in the SAME bundle

     builds to ─────────────► public/doxa-maps/<your-map>/<your-map>.js   (one file)

Folder name = bundle name. Folders starting with _ or . are skipped (handy for WIP).
Each .vue = one profile (one map screen). One bundle can hold many.
Pick the profile at embed time with the profile field — every profile shares one bundle:

<script src="/doxa-maps/<your-map>/<your-map>.js"></script>
<doxa-map profile-config='{"profile":"overview","tk":"pk.eyJ..."}'></doxa-map>
<doxa-map profile-config='{"profile":"detail","tk":"pk.eyJ..."}'></doxa-map>

Add a map — three steps

# 1. create the folder + one profile
mkdir -p plugin-designs/<your-map>
#    index.js   ← copy doxa-simple-map/index.js, rename the tag
#    <name>.vue ← your screen, built from @map/* blocks (flat in the folder)

# 2. build
npm run build            # → public/doxa-maps/<your-map>/<your-map>.js
#    (just this one:  BUNDLE=<your-map> npm run build:bundle)

# 3. embed the script tag + element (dev staging at `npm run dev` shows a paste-ready snippet)

Your three things (everything else is shared)

Colors — how pins are colored. Pick one the template ships (getColorStrategy('language-family')), or drop your own in plugin-designs/<your-map>/src/colors/ (start from template-bundle/src/colors/example-mode.js). Never edit @map/colors/ to recolor your map.
API — your map reads its data from the profile-config on the page, so the same bundle points at different data with no rebuild. DataSourceManager accepts csv (bundled file), api (one JSON URL), or rest-api (a live REST endpoint, the default). Prefer the real API over inlined JSON.
i18n — the template ships 11 base locales in @map/i18n/locales/. Use useI18n() for strings and RTL_LOCALES for right-to-left; add or override strings from your own profile.

The one hosting variable

The only thing that changes between hosting modes is the <script src>: a relative path when your own site serves the file, or an absolute CDN URL when a partner site serves it. The bundle is identical either way. See ../documentation/CONTRIBUTING.md for the two CDN modes and partner-site embedding.

Profile patterns (mix freely)

Individual — one .vue per bundle (simplest).
Parameterized — one profile, behavior driven by profile-config props (e.g. tabs[]).
Nested — one profile that renders others (workbench-style, like doxa-research-map).