History

Doxa Maps 592880ac75 Teach the gate the two classes gospel classified by hand gospel found 12 real defects — including a search box's aria-label, which is screen-reader text — inside 88 findings they had already described as mostly deliberate. None were visible from the count. They classified every remaining finding by hand and named the two shapes the gate miscounts. A string compared with === against table data is a value, not a label. `scope === 'Full Bible'` tests a cell of the shipped resource table; the reader never sees that literal, and the row it selects renders through a key. Translating it makes the comparison miss and the feature stop, while the count falls and it looks like progress — the same inversion as a lookup-table key, which is why gospel classed them together. A separator followed by a brand is not a sentence. `{{ t('…') }} · GRN` splits into a keyed half and the text node "· GRN", and only the second reaches this scan. The names are LISTED, not patterned. "Punctuation then a capitalised word" would swallow "· Not found in any pool", a real caveat, and that is the class gospel's 12 defects were hiding in. A name earns its place by being a publisher or standard that is the same word in every language. Each quiet case is paired in the self-test with the nearest thing that must stay loud: a caveat after the same separator, prose that merely begins with a brand, a real English sentence used as a table key, and an .includes() argument. Poisoning the name list into a punctuation rule fails. Poisoning the operator check did NOT fail, which is why there is now a concatenation case: `greeting + 'Welcome to the prayer map'` is a BinaryExpression too, so accepting any operator would silence a sentence assembled for the reader. Only an equality test means "compared against data". Also the last finding in this owner's plugins. All seven main tabs resolve through tabs.<id> in all eleven locales, so their English labels could never render — a second copy of each name that could only drift. The sub-tab tables lost theirs the same way. Fleet 152 -> 143. This owner's plugins: 1 -> 0.		2026-09-29 08:11:49 +00:00
..
all-people-groups	All People Groups: no DOXA group is drawn twice; the base is re-sent slim without them	2026-09-29 02:53:16 +00:00
big-picture	Keep the reason, drop the speaker	2026-09-29 03:46:37 +00:00
cities-internet	The embedded map drew 340px below its card, and said nothing for the 30s it took	2026-09-28 23:43:44 +00:00
country-map	No country codes means no pins, not every pin on earth	2026-09-29 07:07:48 +00:00
country-posters	Share the legend-map bridge between the two 811-line twins	2026-09-29 07:31:17 +00:00
dashboard-plus-grid	One phone flag per map, and the leaf page follows it as well as the Gallery	2026-09-29 07:31:16 +00:00
demo-map	Five plugins were silently monolingual, because the bootstrap was copied sixteen times	2026-09-28 17:40:34 +00:00
doxa-maps-spa	One phone flag per map, and the leaf page follows it as well as the Gallery	2026-09-29 07:31:16 +00:00
doxa-research-map	Teach the gate the two classes gospel classified by hand	2026-09-29 08:11:49 +00:00
doxa-simple-map	Prayer Progress: the basemap colours' comment states the measurement instead of citing a folder outside the repo	2026-09-29 03:38:57 +00:00
doxa-vision-card	Every Experimental map carries its own hosted ?, where its controls already are	2026-09-29 02:35:35 +00:00
golden-path-check	golden-path-check finds its manifest from its own script, so it answers when embedded	2026-09-28 23:23:58 +00:00
gospel-internet	One phone flag per map, and the leaf page follows it as well as the Gallery	2026-09-29 07:31:16 +00:00
gospel-resources	Arabic readers get the language code, the link gap and the population column on the wrong side	2026-09-28 23:43:44 +00:00
key-cities	Eleven plugin entries import the element helper they call	2026-09-28 17:40:35 +00:00
my-upg-100-list	The generated sheets fetch their capitals and cities at print time, instead of every page bundling them	2026-09-29 06:23:20 +00:00
people-groups-grid	The grid's "controls off" preset did nothing, and nothing said so	2026-09-28 22:25:30 +00:00
plugin-studio	Plugin Studio keeps the reason and drops the speaker: its 15 references to the Driver reworded, comments only	2026-09-29 05:26:26 +00:00
pplr-data-maps	PPLR Data Maps: on a phone the ten views are one select, and the prayer map's coach-mark stays off this research tool	2026-09-29 05:17:38 +00:00
prayer-walk-planner	Prayer Walk Planner: on a phone the zone list opens from a ☰ Zones button instead of being hidden	2026-09-29 02:58:03 +00:00
regions-dashboard	Country posters print their list, deck and packet, with the map drawn at the click	2026-09-29 08:07:36 +00:00
research-dashboard	Retire the last one-cycle re-export in the dashboard composables	2026-09-29 07:31:16 +00:00
research-map-plus-grid	check:no-free-identifiers counts __DX_LOCALE_SRI__ as build-bound: the locale plugin prepends it, and its one read is typeof-guarded	2026-09-29 07:31:17 +00:00
rudder-voice	Dictation fell behind because our own build took every core	2026-09-29 05:26:25 +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: each screen carries its meta.json, so a copy of the starter is listed in the Plugin Studio	2026-09-29 02:01:33 +00:00
upg-neighbor	UPG Neighbor: on a phone the list can be lowered to a bar and raised again	2026-09-29 07:22:57 +00:00
wall-of-people-groups	Wall of People Groups: the store no longer downloads every photo in the background, and the dead source picker and old card are gone	2026-09-29 07:22:57 +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).