History

Doxa Maps 127a2e0930 The funnel states the list it was actually drawn from A LIVE WRONG NUMBER, not a future risk. The universal `list` prop is already on main (`e3d25ff6`) and this profile already honours it — applyPeopleGroupList() filters the rows at all four fetch sites, packetRecords included — and the membership files are on disk. So under ?list=frontier-500k the packet's rows were the 71 network groups that are Project 700, while the funnel took its denominator from the last step of vision-funnel.json and printed "of the 2,107". Off by a factor of 30, with nothing on the page looking broken. Measured from data/people-groups/lists/*.json (counts.doxa, what a Tier A map shows): frontier-500k 71 · frontier 1,745 · unengaged 1,929 · unreached 2,082 · the default 2,107. THREE NUMBERS WERE WRONG, NOT ONE, because all three descended from one total: the share's denominator; the footnote's "N are in no list" (total minus assigned); and "1 of 27 lists", which is a property of the UPG-100 ZONE CATALOGUE, not of the active list — the zones partition the default list and nothing else. A non-default list now gets its own step, labelled with the list's own label, so the narrowing does not jump from one list's total to another list's packet. AND EACH CLAUSE IS SUPPRESSED SEPARATELY, because they are provable separately. A first pass dropped the whole share line whenever listCount was absent, throwing away a true statement ("5.4% of the 1,745") to avoid an unprovable one. The footnote splits the same way: provenance holds for every list, coverage does not. ⚠ The footnote is NOT split by parsing the translated sentence — hi ends in "।" and zh in "。", and reading translated prose for structure is the trap check-packet-render's own comment warns about. It is a second key. ⚠ And `funnel.unassigned ?? 0` would have printed "0 of the 1,745 are not yet in any list" — a confident falsehood whose zero reads as a completeness claim. ── AND THREE FINDINGS FROM rega'S RENDER, none of which I could see ────────── "0 people" PRINTED ON THE READER'S ROW OF EVERY PACKET. Number(null) is 0 (only Number(undefined) is NaN), so `Number.isFinite(Number(x))` admitted the deliberate `population: null` marker as the number zero. I asked "is this a finite number?" when the question was "did anyone give me a population?" — the same presence-vs-value confusion as inferring "did it work" from a field that answers "did it isolate". Zero is suppressed too: a people group with no people is missing data wearing a number's clothes. THE SHARE LINE READ AS PART OF THE FOOTNOTE. Measured: 218px below the reader's row, 42px above the footnote, because the last row kept the full inter-row gap. Proximity is the only thing grouping them, so an even gap grouped the share with the wrong element. The last row's margin is now 14px: share 14px under its row, 288px clear of the footnote. THE GATE ASSERTED PAGE 2 AND PRINTED NOTHING ABOUT IT. rega: "a reader cannot see WHAT it asserted." A silent pass is the mirror of a printed-but-unasserted number — the check is real and the evidence invisible. It now reports rows, bars and the share line, and gained two assertions: every row must have a BAR (the reader's step had none, so the funnel never visibly narrowed to "yours"), and no row may print a zero population. Verified: all five list cases render their own true numbers — doxa keeps the full claim, unreached/frontier/unengaged get their own step and a percentage with no false "1 of K", frontier-500k reads "100% of the 71" with the duplicate row suppressed (a step that repeats its neighbour is not a step). The four fixtures are byte-for-byte unchanged on the default path, so the list-awareness is purely additive. check:packet-strings-parity PASS with the three new keys. Both new gate assertions mutation-tested in en and ar: removing a bar is DETECTED, injecting a zero population is DETECTED. 5 rows = 5 bars, 0 zero-population rows, "0 people" absent. Six-row layout recomputed: fits with 318px headroom, 206px if every label wraps. BUNDLE=my-upg-100-list vite build clean. NOT re-rendered in a browser: rega measured the previous state and these are responses to it, so the new geometry wants one more look.		2026-09-26 08:13:34 +00:00
..
all-people-groups	All People Groups loads fast on a light map; the Vision Card becomes a true funnel from data	2026-09-25 07:18:30 +00:00
big-picture	Integrate main into bundler-2/work	2026-09-26 06:43:22 +00:00
cities-internet	India by state: all 36 states, Mizoram and Nagaland included	2026-09-26 08:13:34 +00:00
country-posters	Show-on-map, second pass: stop trusting the bookkeeping, and make deselect mean something	2026-09-26 05:26:48 +00:00
dashboard-plus-grid	The people-group list is a universal prop: the same maps can show any project's list	2026-09-26 05:16:02 +00:00
demo-map	Move internal files out of the repo; fix five dead links; a fuller delegation diagram	2026-09-25 05:14:10 +00:00
doxa-maps-spa	Research Gallery: PPLR Data Maps and Wall of People Groups are named in all 11 languages	2026-09-25 23:41:17 +00:00
doxa-research-map	Integrate main into bundler-2/work	2026-09-26 06:43:22 +00:00
doxa-simple-map	The people-group list is a universal prop: the same maps can show any project's list	2026-09-26 05:16:02 +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	Gospel map: provinces for India and China, fetched only when someone looks	2026-09-26 06:53:22 +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 funnel states the list it was actually drawn from	2026-09-26 08:13:34 +00:00
people-groups-grid	The people-group list is a universal prop: the same maps can show any project's list	2026-09-26 05:16:02 +00:00
plugin-studio	Plugin Studio: collapse the header to give the plugin the whole page, and bring it back in one click	2026-09-26 04:39:00 +00:00
pplr-data-maps	One pinned-UMD loader for PPLR and the Wall: library/utils/loadPinnedUmd.js	2026-09-26 07:24:25 +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	The filters-toggle padding used an undefined token, so it voided and made the gap worse	2026-09-26 07:12:07 +00:00
research-dashboard	Integrate main into bundler-2/work	2026-09-26 06:43:22 +00:00
research-map-plus-grid	The people-group list is a universal prop: the same maps can show any project's list	2026-09-26 05:16:02 +00:00
stack-demo	Studio and stack-demo hand the host's language down to what they mount	2026-09-25 13:26:01 +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	The people-group list is a universal prop: the same maps can show any project's list	2026-09-26 05:16:02 +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).