History

Doxa Maps c534781bac MapLibre region fills drew nothing: the worldview clause filtered out every feature rega measured it by eye at `b0cd3140` on the built tree: regions-mfe under ?provider=maplibre draws the basemap and 2,107 pins, the boundary geojson returns 200, and the fill layer holds 0 features. Mapbox draws 156. A filter that admits nothing looks exactly like data that never arrived. countryFilter() is two clauses ANDed. The ISO half was fine — the field bridge three lines above it already copies iso3 -> iso_3166_1_alpha_3 onto every geojson feature before setData, so one name is read everywhere. The WORLDVIEW half has no bridge and cannot have one: it exists because the Mapbox tileset repeats a country once per worldview and the highlight would otherwise draw two or three times over. The geojson has no such duplication and carries no worldview property at all, so both sides of the `any` were false on every feature and the `all` emptied the layer. It is Mapbox-only, not something to translate, so MapLibre now gets the ISO clause alone. I NEARLY FIXED THE WRONG HALF. Reading the RAW geojson I saw { iso3, shapeGroup, shapeName }, concluded the ISO key was wrong too, and branched it — adding a second name for a fact the bridge already normalises. The bridge was three lines above the filter I was editing. Reverted; the ISO clause is untouched. Proven headless, fail-first, by EVALUATING both filters against the real 162 features with MapLibre's own parser after applying the bridge: OLD filter admits 0 / 162 <- rega's bug, reproduced without a browser NEW filter admits 14 / 14 <- every requested country Mapbox path unchanged: still 14/14, and still drops a duplicate worldview copy The control asserts the OLD filter still admits 0, so the check reports when it has stopped demonstrating the bug it was written for. Needs eyes: rega to re-shoot row 13 on this sha.		2026-09-26 00:38:15 +00:00
..
all-people-groups
big-picture	Big Picture: read the language the host asked for	2026-09-25 15:15:55 +00:00
cities-internet	Raw maps shape Arabic, Persian and Hebrew place names: cities-internet and key-cities	2026-09-25 18:59:31 +00:00
country-posters	Composites forward `provider`, so a MapLibre partner gets MapLibre	2026-09-25 08:12:20 +00:00
dashboard-plus-grid	Let a host set the language of a whole page, not half of it	2026-09-25 14:26:02 +00:00
demo-map
doxa-maps-spa	Research Gallery: PPLR Data Maps and Wall of People Groups are named in all 11 languages	2026-09-25 23:41:17 +00:00
doxa-research-map	Merge main into bundler-2/work	2026-09-25 21:47:37 +00:00
doxa-simple-map
doxa-vision-card	Host locale: gate the profile-config contract, forward ?lang= into staging embeds, stop losing gate stderr	2026-09-25 12:18:26 +00:00
golden-path-check
gospel-resources	Gospel map: the country gap list says where to start	2026-09-25 22:49:05 +00:00
key-cities	Raw maps shape Arabic, Persian and Hebrew place names: cities-internet and key-cities	2026-09-25 18:59:31 +00:00
my-upg-100-list	The raw map shapes Arabic, Persian and Hebrew place names	2026-09-25 19:05:59 +00:00
people-groups-grid	Match the live page's wording where we differed only by case	2026-09-25 17:08:16 +00:00
plugin-studio	Plugin Studio: the header's menus stay on top of every plugin	2026-09-25 20:44:24 +00:00
pplr-data-maps	PPLR data maps: keep the loading globe up until the pins are drawn, not merely added	2026-09-26 00:14:16 +00:00
prayer-walk-planner	Export gate reads the tree name from the build config	2026-09-25 21:32:35 +00:00
regions-dashboard	MapLibre region fills drew nothing: the worldview clause filtered out every feature	2026-09-26 00:38:15 +00:00
research-dashboard	Leaf pages load only the engine their provider asks for: no Mapbox requests under MapLibre	2026-09-25 23:44:04 +00:00
research-map-plus-grid	Prove the grid-under-map link on both engines, not just the one we happened to run	2026-09-25 22:35:48 +00:00
stack-demo	Studio and stack-demo hand the host's language down to what they mount	2026-09-25 13:26:01 +00:00
template-bundle
upg-neighbor	Map labels ask for a font the engine's glyph server has: one shared helper	2026-09-25 13:48:10 +00:00
wall-of-people-groups	Wall of People Groups: say so when the live API cannot be reached, and stop a render error	2026-09-25 19:20:48 +00:00
.gitkeep
README.md

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).