History

Doxa Maps f68cb24e78 2,001 groups had readable Scripture and were told they did not go-int cross-checked 20 roster languages with "no New Testament found in the pools" against open-data signals. Thirteen of the twenty had readable text all along — on a record the tier could not see — and chasing that found one rule written four times and wrong in two of them. THE BUG. tierOfCode tested `!!c.s`, one field, while this build's own hasReadableScripture tested four sources. Tier 2 means "Scripture AND film", so a language whose text is on the Faith Comes By Hearing record (au.m names the media it holds), on Scripture Earth, or in a Door43 translation was scored 1 — "some resource found" — with its own text and the JESUS Film both in hand. Measured: 602 codes and 2,001 of 12,379 groups move 1 -> 2. Tier 0 does not move at all, 1,592 before and after, so nothing about who has NOTHING changes: the gap lists, the 369 zero-access groups and the bridge-reach table are untouched. THE SAME BUG DOWNSTREAM, and this is the one a catalyst would have felt: resourceRows typed an FCBH record "audio, text, video" as Audio Scripture only, so the access table's byType.Scripture never saw it. 288 people groups were published as "watch or hear, cannot read" while their own readable Scripture sat behind that link. Access now reads 1,129 "read and watch" (was 869), 518 "cannot read" (was 806), 85 "read" (was 57), 369 nothing found and 6 stories only — unchanged where it should be, and 2,107 in total either way. Typing the row by its text would have dropped "can hear", so the access builder now counts a Scripture row whose scope names audio as hearable too. ONE OWNER NOW. hasReadableScripture is exported from gospel-resource-rows.js and imported by the pin builder and by check-gospel-coverage-consistent, whose arm F had its own narrow copy and therefore reported 2,001 disagreements against the corrected tier — a gate defending the bug it exists to catch. A rule with four copies has no owner; this one has. `sx` ships alongside: the readable text with its source named, for the 887 codes whose text is not at c.s, so a surface can LINK what the tier now counts instead of claiming Scripture and showing a film. Wiring it into the sheet and the field card is the next commit; this one is data and rules only, and public/ is deliberately NOT rebuilt because rega is rendering this worktree.		2026-09-27 18:53:52 +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	Plugin Studio and the gallery split production from experimental, from each bundle's own stage	2026-09-27 06:04:08 +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	Gallery: count the gospel-internet board as a heavy tab	2026-09-27 06:04:09 +00:00
doxa-research-map	Two setup-time defects: a TDZ that blanked the map, and a cleanup that never ran	2026-09-27 04:00:31 +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 selection strip no longer runs under the combinations	2026-09-27 08:47:20 +00:00
gospel-resources	2,001 groups had readable Scripture and were told they did not	2026-09-27 18:53:52 +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	Unblock studio's landing 13: drop the dead fallback, make the zoning gate measure on a clean tree	2026-09-27 06:57:00 +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	The Rudder corner button carries its name in the reader's language, not the raw key	2026-09-27 09:47:44 +00:00
pplr-data-maps	PPLR Religion: the legend names each religion in the reader's language	2026-09-27 08:20:41 +00:00
prayer-walk-planner	Prayer Walk Planner: the resolved instance id is exposed under its own name	2026-09-27 04:38:17 +00:00
regions-dashboard	Regions list asks for two fields, not eight	2026-09-27 06:20:57 +00:00
research-dashboard	RTL drag: the direction probe reads the handle, and two handle margins become logical	2026-09-27 06:42:54 +00:00
research-map-plus-grid	check:no-free-identifiers reads .js modules, which is how the NEUTRAL P1 got past it	2026-09-27 06:42:55 +00:00
rudder-voice	Corner widgets: a plugin can declare a fixed corner of the Plugin Studio, and Rudder takes bottom-right	2026-09-27 09:07:17 +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: flying to a neighbor keeps it above the phone sheet	2026-09-27 09:18:14 +00:00
wall-of-people-groups	Wall of People Groups opens where the photos are, with rows as far apart as columns	2026-09-27 05:30:05 +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).