History

doxa-maps-88655c70 33bd7ca387 Some checks are pending Deploy to GitHub Pages / build (push) Waiting to run Details Deploy to GitHub Pages / deploy (push) Blocked by required conditions Details All People Groups loads fast on a light map; the Vision Card becomes a true funnel from data ALL PEOPLE GROUPS. The Driver: "not even loading, takes a very long time", and its DOXA pins were dark on a dark map. - It downloaded the 7.5 MB people-groups-slim.json (22 columns) to draw ten fields. It now fetches people-groups-points.json: the same rows in column order, repeated strings in dictionaries, coordinates at 3 decimals. 0.74 MB, generated deterministically by library/scripts/people-groups/build-points.mjs and staged into the tree by generate-tree. It falls back to the old file on an older tree. - Pins no longer wait for the live prayer API. Every pin draws by GSEC from the file, and the DOXA overlay recolours when the API answers. The DOXA count reads "…" until then, not 0. - Named style 'paper' (Mapbox light-v11 / MapLibre positron) instead of 'ink'. The four categories keep their meaning; yellow and green are a step darker, and pins get a thin dark ring, so they read on near-white. - Its words are in all 11 locales (allPeopleGroups.json), with a guarded useI18n and values passed to vue-i18n so {n} is not blanked. Measured on a served built tree, 3 fresh runs each, median time to first rendered pins: 8.3 s before, 5.2 s after, on localhost. This box renders GL in software, so most of the remaining time is map start-up; the 10x smaller download matters more on a real connection. DOXA VISION CARD. The Driver: "the data doesn't make sense … super false information". The card rotated four typed-in figures with no source. It is now a proportional funnel, every number computed from data by library/scripts/people-groups/build-vision-funnel.mjs: 12,379 people groups (IMB rows: one group in one country) 7,341 unreached (IMB LostnessPriority 0-2, < 2% evangelical) 4,754 frontier (LostnessPriority 0, < 0.1% evangelical) 2,107 DOXA groups (the DOXA prayer list, snapshot saved in data/; 1,745 of them frontier) The first three nest; DOXA groups do not all sit inside frontier, so the card says how many do. The rules are on the card ("How these are counted") and in HOW-THE-NUMBERS-ARE-COUNTED.md, which also explains why the total is not the 16-17 thousand of Joshua Project's count. Material light, all 11 locales, right-to-left in Arabic, sources and dates shown. The old fake stats are removed from the instances file, the frontier page, the manifest, the staging page and the gallery. CHECKS. - check:vision-card-numbers recomputes the funnel independently (own CSV reader, the published rules) and compares with vision-funnel.json and, with --url, the rendered bars. Negative-tested: a corrupted count exits 1. On the built tree: bars 12,379 / 7,341 / 4,754 / 2,107 and "1,745 of them are frontier", all matching. - check:map-embed-cells measures PRODUCTION-MATRIX cells B and C for the seven gallery maps on a foreign origin; C proves the host's token is used by handing the host a distinct token and checking every Mapbox request. 14 of 14 pass.		2026-09-25 07:18:30 +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	Stop Big Picture showing the same total twice	2026-09-23 15:32:28 +00:00
cities-internet	Cities with Internet and the phone legend speak the page's language	2026-09-25 06:05:46 +00:00
country-posters	country-posters: a phone can export too — and the gate was shutting the panel	2026-09-24 18:21:35 +00:00
dashboard-plus-grid	Composites: pass the provider prop down, so keyless embeds are keyless	2026-09-24 19:05:19 +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: name the Experimental maps, in every locale	2026-09-25 05:48:21 +00:00
doxa-research-map	Merge main into bundler-2/work	2026-09-25 06:12:10 +00:00
doxa-simple-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-vision-card	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
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	Wire the corrected GRN sweep, and translate the three lines that make the map usable	2026-09-25 07:06:33 +00:00
key-cities	Move the private field-access dataset out of the repo	2026-09-24 18:34:01 +00:00
my-upg-100-list	Print a UPG-100 list straight from the map legend	2026-09-25 07:10:23 +00:00
people-groups-grid	Simple Research: one filter state, so the two halves move together	2026-09-25 06:10:43 +00:00
plugin-studio	Plugin studio: mount the element the bundle defines, not the one a profile's JSDoc names	2026-09-25 05:34:16 +00:00
prayer-walk-planner	prayer-walk-planner can be shared — the last published map with no sharing path	2026-09-24 08:23:30 +00:00
regions-dashboard	Forward urlSync to the nested panes: the guard was unreachable without it	2026-09-25 06:31:36 +00:00
research-dashboard	Translate the chrome that was English in all eleven locales	2026-09-25 06:10:27 +00:00
research-map-plus-grid	Simple Research: one filter state, so the two halves move together	2026-09-25 06:10:43 +00:00
stack-demo	Studio and stack-demo: forward the host's engine and token too	2026-09-24 19:39:59 +00:00
template-bundle	Move internal files out of the repo; fix five dead links; a fuller delegation diagram	2026-09-25 05:14:10 +00:00
upg-neighbor	UPG Neighbor: build the five neighbor maps from source, not from a frozen IIFE in an iframe	2026-09-24 18:47:14 +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	consolidate docs into documentation/ and deployment shells into deployment/	2026-09-21 23:23:23 +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/doxa-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="/doxa-maps/<your-map>/<your-map>.js"></script>
<doxa-map profile-config='{"profile":"overview","tk":"pk.eyJ..."}'></doxa-map>
<doxa-map profile-config='{"profile":"detail","tk":"pk.eyJ..."}'></doxa-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/doxa-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).