History

Doxa Maps 379509c5c2 The factory stopped being a one-liner, so a whole bundle stopped being looked at check:i18n-keys-exist reported PASS over two planted poison keys in gospel-internet, three rounds running, and over 12 real keys its new panels name that exist in no locale. Reproduced before changing anything: with both poisons on disk the gate found 1 missing key; it now finds 15 on that same tree — the 2 poisons plus the 12. TWO CAUSES, EITHER ALONE ENOUGH TO HIDE EVERYTHING. factoriesIn() demanded the exact shape `export function useX() { return useOptionalT('ns') }`. useGiT is no longer that. It became a WRAPPER -- `const t = useOptionalT()` and a returned arrow adding an English-fallback argument -- which is ordinary refactoring and moved the bundle outside this gate: useGiT was not a factory, so `const T = useGiT()` was not an alias, so every T('…') was not a call site. Discovery now also accepts an exported function whose body BUILDS a translator, reading a namespace only when the call states one literally. And when a namespace could not be read, `if (ns === null) continue` dropped the binding in silence. That is the line that turned "I cannot see this" into "there is nothing to see", and it is why the bundle passed by having nothing looked at. Note what it is NOT: useOptionalT('') gives ns === '', an author DECLARING no namespace, which was already handled and counted. Empty is a decision; null was this gate's own ignorance. Such a binding is now registered for the FULL-KEY pass anyway -- a fully dotted key is checkable whatever the namespace is, which is what catches both poisons -- while the BARE calls it genuinely cannot qualify are counted, listed by binding, and FAIL. The gate states which translators it could not resolve instead of scoring them clean. Both poisons are pinned as permanent fixtures HERE rather than left in gospel's tree, so the proof does not depend on another agent keeping deliberately-broken code on main. The fixture asserts the four things that were independently broken: a wrapper factory is discovered, no namespace is guessed for one that states none, its binding still reaches the full-key pass, and a bare key behind it is recorded rather than skipped. Negative-tested: restoring the silent `continue`, or narrowing discovery back to one-liners, each fails the self-test; restored, it passes. NOT wired into gates:pre and left on demand, as it already was. It reports 13 real missing keys on today's main -- 12 of gospel's panel keys plus a pre-existing legend.noList -- and those are their owners' to add, not this gate's to hide.		2026-09-28 16:49:01 +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	min-height clamps height, so the pane could not hold the plugin it was pinning	2026-09-28 15:01:19 +00:00
cities-internet	Cities with Internet: the AI-notice dismiss button meets the 24px target minimum	2026-09-28 12:41:10 +00:00
country-posters	Country Posters: Export poster is a toolbar button every reader sees, not a drawer item behind a hidden opener	2026-09-28 15:18:17 +00:00
dashboard-plus-grid	A composite embedded bare dropped tokenUrl, and passed because a ProfileLoader sat above it	2026-09-28 15:52:47 +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	min-height clamps height, so the pane could not hold the plugin it was pinning	2026-09-28 15:01:19 +00:00
doxa-research-map	The packet was praying over the numbers the page loaded with, not the live ones	2026-09-28 13:56:22 +00:00
doxa-simple-map	Prayer Progress: note the accessibility work due before the help modal or a second tab is switched on	2026-09-28 12:41:10 +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	Read the zone tables from the asset pool, and name zones from their slugs	2026-09-28 16:30:40 +00:00
gospel-resources	Use the keys that landed for three strings the map still said in English	2026-09-28 12:57:56 +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: imb_gsec arrives nested, so the packet lost half of every description	2026-09-28 16:09:12 +00:00
people-groups-grid	The composed grid's locale depends on a spelling neither file mentions	2026-09-28 10:26:43 +00:00
plugin-studio	library: one embedScript for the app shells, replacing four private copies	2026-09-28 07:07:33 +00:00
pplr-data-maps	Pplr Data Maps: tab and legend labels follow a language change instead of keeping the one they started with	2026-09-28 13:01:16 +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	Stop the dimmed pins reading as white rings, and lift the chooser map	2026-09-28 16:24:36 +00:00
research-dashboard	Big Picture: the share button fits its 38px header instead of overflowing it	2026-09-28 15:27:03 +00:00
research-map-plus-grid	The factory stopped being a one-liner, so a whole bundle stopped being looked at	2026-09-28 16:49:01 +00:00
rudder-voice	Rudder is thin-client by default; the robot voice is an experimental opt-in (High performance mode)	2026-09-28 15:35:51 +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: each row carries its DX slug, and every DX group ships, so a DX page joins by the key it holds	2026-09-28 16:28:04 +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).