History

Doxa Maps f8f81b9bcb One writer for the region polygons, and its idle state compiles the shader at layer-add Both halves are rega's measurements on main `373b7979b`, now that the WAGF selection holds and it is worth optimising rather than optimising a bug. NINE WRITES PER CLICK -> THREE. A single "Asia (Region)" click produced nine regions-* paint writes: fill-opacity, line-color and line-width, three times each inside ~110 ms. Two paths painted the same highlight from DIFFERENT sources — onSemanticTreeSelect from node.isoCodes, applyDimFilter from mapLayers.regionIsoMap — each triggering the other through mapStore. Two sources for one visual is not just wasted work: it is how they drift, and it already cost a debugging cycle, because when the highlight was being cleared we first had to establish WHICH writer had done it. All four paths (click, watcher, clear, and the layer-add below) now go through paintRegionScope, which writes a property only when the value actually differs — asked of the MAP rather than a remembered key, so a layer torn down and re-added cannot leave a skip holding a paint that is no longer there. 5.5 s AND 11.1 s OF SHADER COMPILE, MOVED OFF THE GESTURE. rega measured the row click compiling a new variant — 5.5 s MapLibre, 11.1 s Mapbox on SwiftShader — because that click was the first moment these three properties stopped being constants. Identical to the pins defect and fixed the same way: the idle value is now ['case', ['has', 'iso_3166_1_alpha_3'], x, x], both branches the same so not one pixel changes, and it is installed the moment addRegionsLayer returns. The variant therefore compiles on the tab visit that is already loading a 6.4 MB GeoJSON, not in the middle of a gesture. That placement is the whole point, and it is what I got wrong on the pins the first time: an idle expression that is never installed pre-warms nothing. Here it is painted at layer-add, where the layers first exist. LEFT ALONE DELIBERATELY: highlightCountryByIso (0.30/0.02) and applyDimFilter's dim path (0.20) are different states of the same layers, not duplicates of this one, so collapsing them into this writer would have merged three features into one function to save nothing. Verified: gates:pre 12/12, check:composite-interop PASS. Needs eyes: rega — expect 3 regions-* writes per click instead of 9, and no compile on the row click; the compile should appear on the TAB visit instead.		2026-09-28 05:46:36 +00:00
..
all-people-groups	A bare-host embed under ?lang=ar now renders Arabic here too	2026-09-27 02:17:35 +00:00
big-picture	Big Picture: the live count speaks, and the locale reaches the children	2026-09-26 22:06:58 +00:00
cities-internet	Cities with Internet: people-group dots are dark slate, not red	2026-09-28 04:38:32 +00:00
country-posters	Country posters: Show on map, go to the map, come back: the same card shows the country again	2026-09-27 07:28:32 +00:00
dashboard-plus-grid	Plugin Studio and the gallery split production from experimental, from each bundle's own stage	2026-09-27 06:04:08 +00:00
demo-map	C2: one library helper for per-engine projection, across 12 call sites in 9 plugins	2026-09-26 08:39:53 +00:00
doxa-maps-spa	Rudder stays out of the Research Gallery and makes no network call on a static host	2026-09-28 03:12:46 +00:00
doxa-research-map	One writer for the region polygons, and its idle state compiles the shader at layer-add	2026-09-28 05:46:36 +00:00
doxa-simple-map	Plugin Studio and the gallery split production from experimental, from each bundle's own stage	2026-09-27 06:04:08 +00:00
doxa-vision-card	Doxa Vision Card: take the page language from profile-config lang as well as locale	2026-09-26 01:10:51 +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-internet	Gospel x Internet: the Studio rail names it 'Gospel × Internet'	2026-09-28 04:31:15 +00:00
gospel-resources	Neutral wording in a table strangers read	2026-09-28 00:45:42 +00:00
key-cities	Key cities: the map honours provider=maplibre instead of always building Mapbox GL	2026-09-27 04:38:17 +00:00
my-upg-100-list	UPG-100: test handles are also keyed by instance	2026-09-28 05:27:38 +00:00
people-groups-grid	One place decides how a count is punctuated, and it still says en-US	2026-09-27 06:04:08 +00:00
plugin-studio	Dev server: a pull no longer reloads the page in a burst, and Rudder's recording pill keeps a fixed width	2026-09-28 05:30:58 +00:00
pplr-data-maps	PPLR maps: the legend tabs are named in the reader's language	2026-09-28 04:06:20 +00:00
prayer-walk-planner	Prayer Walk Planner: the phone toolbar fits, with the list actions behind More	2026-09-28 00:36:26 +00:00
regions-dashboard	The manifest descriptions were mine	2026-09-28 00:37:25 +00:00
research-dashboard	The country's code comes from the row, not from its name	2026-09-28 02:38:50 +00:00
research-map-plus-grid	Shared links keep partner param names, and a CSV export matches multi-value filters	2026-09-27 18:40:47 +00:00
rudder-voice	Rudder stays out of the Research Gallery and makes no network call on a static host	2026-09-28 03:12:46 +00:00
stack-demo	Decouple prose: no go-base / nuxtbase / nuxtinator / doxa-base names in plugin comments and docs	2026-09-26 17:28:45 +00:00
template-bundle	template-bundle: the starter's first screen is now a real map	2026-09-26 04:38:12 +00:00
upg-neighbor	UPG Neighbor: the start view shows the unreached dots	2026-09-27 23:52:08 +00:00
wall-of-people-groups	Wall of People Groups: no debug logging in the shipped bundle	2026-09-28 02:53:46 +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	plugin-designs/README: the tree is dx-maps, and a bundle's tag is its folder name	2026-09-26 01:19:53 +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/dx-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="/dx-maps/<your-map>/<your-map>.js"></script>
<your-map profile-config='{"profile":"overview","tk":"pk.eyJ..."}'></your-map>
<your-map profile-config='{"profile":"detail","tk":"pk.eyJ..."}'></your-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/dx-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).