History

Doxa Maps c53d356d3f The one event was the cascade's empty moment, not the selection rega, row 43 case 3 at `52eeb0db`: the coalescing landed — one event per click, exactly as intended — and in 3 of 4 runs that one event was EMPTY, {language:"", languageCode:"", languageCodes:[]}, so the grid stayed at 2,107. The name fix works whenever it fires; the event just carried nothing to name. THE CASCADE PASSES THROUGH A CLEARED STATE. mapStore.selectLanguage() sets selectedDialect = null BEFORE it sets the language, so a dialect click walks the store through "nothing selected" on its way to the answer. The settle timer fired inside that window and read exactly what was there. The composite then did the right thing with what it was told: an all-empty report IS how this element says "the reader cleared everything". MY FIRST FIX WAS A TIMEOUT, AND A TIMEOUT WAS THE WRONG KIND OF ANSWER. 60ms was enough in my seat and not under headless swiftshader. That is the third time I have tuned a duration on one machine and called it settled, so this one does not get lengthened — lengthening moves the failure rather than removing it. The guard is SEMANTIC instead. An all-empty read arriving straight after a filled one is the one genuinely ambiguous case — it is what a mid-cascade read looks like AND what a real clear looks like, and nothing in the payload separates them. So it is re-taken rather than believed: the transient fills in and is reported correctly, while a real clear stays empty through every re-take and is reported a few tens of ms later, which no reader can perceive. The re-takes are BOUNDED (3 x 60ms) so a clear can only ever be delayed, never swallowed, and the whole budget stays far below the composite's 1.2s push window so the two cannot collide. The budget resets on every fresh user action. Note what is NOT assumed: the retries re-read the store on their own timer rather than waiting for another watcher fire. In the failing runs the watcher fired only ONCE, so a fix that depended on a second fire would not have worked. check:language-code-link grows a section G for it, asserting both halves — the guard exists, and it is bounded. Without the first the transient ships; without the second a clear can never be reported at all. Both negative-tested. Source only. STUDIO: needs a rebuild of doxa-research-map.		2026-09-26 22:06:58 +00:00
..
all-people-groups	Three maps asked the window which engine drew them; now they ask the map	2026-09-26 17:28:46 +00:00
big-picture	Twenty-two keys the code asks for that no catalogue has ever had	2026-09-26 17:10:06 +00:00
cities-internet	Cities with Internet: the basemap's place names follow the reader's language	2026-09-26 18:26:38 +00:00
country-posters	Country posters: the map's loading and error lines speak the reader's language	2026-09-26 16:55:14 +00:00
dashboard-plus-grid	Decouple prose: no go-base / nuxtbase / nuxtinator / doxa-base names in plugin comments and docs	2026-09-26 17:28:45 +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	Decouple prose: no go-base / nuxtbase / nuxtinator / doxa-base names in plugin comments and docs	2026-09-26 17:28:45 +00:00
doxa-research-map	The one event was the cascade's empty moment, not the selection	2026-09-26 22:06:58 +00:00
doxa-simple-map	Six entries hand-rolled the RTL text plugin; the library already installs it	2026-09-26 13:35:57 +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-resources	C4 wave 3a, gospel-resources: four guards share one, English unchanged	2026-09-26 22:06:58 +00:00
key-cities	Key Cities (gated): the map, list, tables and posters speak the reader's language	2026-09-26 03:34:30 +00:00
my-upg-100-list	The selection packet names the territories in the order the reader picked them	2026-09-26 18:43:38 +00:00
people-groups-grid	"Arabic" is 23 ISO codes, not 22	2026-09-26 18:38:20 +00:00
plugin-studio	Plugin Studio rail laid out like plugin-designs/: one folder per bundle, its elements inside	2026-09-26 12:23:49 +00:00
pplr-data-maps	One guarded translator, and the fallback catalogue nobody needed	2026-09-26 22:06:57 +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	Register the embedder-key gate so it can actually run	2026-09-26 17:10:06 +00:00
research-dashboard	The legends mirror now, and their labels never became their values	2026-09-26 22:06:58 +00:00
research-map-plus-grid	"Arabic" is 23 ISO codes, not 22	2026-09-26 18:38:20 +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	One guarded translator, and the fallback catalogue nobody needed	2026-09-26 22:06:57 +00:00
wall-of-people-groups	One pinned-UMD loader for PPLR and the Wall: library/utils/loadPinnedUmd.js	2026-09-26 07:24:25 +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).