History

doxa-maps-88655c70 471bd05cea Stop showing English where the catalogue already holds the translation A reader on an Arabic page saw a handful of English words among the Arabic: the table's "People Groups" title, its count line, the Engagement column, the Gospel Access chart title, and the side drawer's close button. Every one of them had a correct Arabic entry sitting in the catalogue; nothing looked it up. THE CHECK CAME FIRST, AND IT REPLACES A SWEEP THAT PASSED A BROKEN TREE. The old method sorted every rendered string into third-party / data / chrome and counted only chrome. That split is a guess, and it guessed wrong exactly where the defect lived: single words like "Region", "Prayer" and "Country" are as plausible as values as they are as labels, so they scored as data and the sweep reported zero on a page that was visibly leaking. check:composite-locale-leaks asks a question with an answer instead: the English catalogue holds this exact string as a value, AND this locale holds a DIFFERENT value for that key, AND the page still renders the English one. No judgement about what kind of word it is — if the translation exists and the reader is not getting it, that is the defect. The two surfaces a lookup cannot judge (vendor map chrome, and table/facet cells carrying API values) are muted by NAME with a stated reason, never by word, so muting one can never hide the next real leak that happens to reuse it. The gate failed on this tree naming 9 strings before any of them were fixed. Also threaded here: both composites now accept `lang` / `locale` in profile-config and pass it to the children they mount, alongside `tk` and `provider`. A partner writing {"lang":"ar"} reached nothing before — the knob was documented and read by nobody. The prayer facet's label in DashboardResearchFilters is now a catalogue getter too. Measured before touching it: dashboard.config.js does define prayer_level and FACETS spreads the config last, so that literal never rendered for this config — it is a default for a config that omits the facet, and it stays, with the merge order written down so the next reader need not re-derive it. Four strings remain English with no catalogue entry at all — "Top countries", "Select all {n}", the table dock's title, and the singular "group". They need wording in ten languages that cannot be composed from existing entries, so they are a DECIDE card for the Driver rather than translations invented here.		2026-09-25 12:16:59 +00:00
..
all-people-groups	All People Groups loads fast on a light map; the Vision Card becomes a true funnel from data	2026-09-25 07:18:30 +00:00
big-picture	Stop Big Picture showing the same total twice	2026-09-23 15:32:28 +00:00
cities-internet	Cities with Internet and the phone legend speak the page's language	2026-09-25 06:05:46 +00:00
country-posters	Composites forward `provider`, so a MapLibre partner gets MapLibre	2026-09-25 08:12:20 +00:00
dashboard-plus-grid	Stop showing English where the catalogue already holds the translation	2026-09-25 12:16:59 +00:00
demo-map	Move internal files out of the repo; fix five dead links; a fuller delegation diagram	2026-09-25 05:14:10 +00:00
doxa-maps-spa	Research Gallery: boot on a partner page under the CORS the live server actually sends	2026-09-25 08:55:52 +00:00
doxa-research-map	Link religion and language between the map and the grid, by the one table they already share	2026-09-25 10:20:27 +00:00
doxa-simple-map	Move internal files out of the repo; fix five dead links; a fuller delegation diagram	2026-09-25 05:14:10 +00:00
doxa-vision-card	All People Groups loads fast on a light map; the Vision Card becomes a true funnel from data	2026-09-25 07:18: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	A gate that asks whether anything is there — and it caught a dead bundle	2026-09-25 09:52:25 +00:00
key-cities	Move the private field-access dataset out of the repo	2026-09-24 18:34:01 +00:00
my-upg-100-list	Batch selection builds a packet, instead of recolouring regions	2026-09-25 09:56:14 +00:00
people-groups-grid	Link religion and language between the map and the grid, by the one table they already share	2026-09-25 10:20:27 +00:00
plugin-studio	Plugin studio: host attributes stay on the host; map-load measurement probe	2026-09-25 08:34:52 +00:00
pplr-data-maps	PPLR data maps: every view loads under MapLibre, and the legend has accessible names	2026-09-25 09:57:17 +00:00
prayer-walk-planner	Map place names in the reader's language, on both engines	2026-09-25 09:46:21 +00:00
regions-dashboard	Port the switcher's last rule, so six goal cards would stack as theirs do	2026-09-25 09:14:25 +00:00
research-dashboard	Stop showing English where the catalogue already holds the translation	2026-09-25 12:16:59 +00:00
research-map-plus-grid	Stop showing English where the catalogue already holds the translation	2026-09-25 12:16:59 +00:00
stack-demo	Simple Research + Big Picture: the host's style stops at the box, and the last English goes	2026-09-25 08:19:56 +00:00
template-bundle	Move internal files out of the repo; fix five dead links; a fuller delegation diagram	2026-09-25 05:14:10 +00:00
upg-neighbor	UPG Neighbor: build the five neighbor maps from source, not from a frozen IIFE in an iframe	2026-09-24 18:47:14 +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).