History

doxa-maps-88655c70 ca13f04bd2 Regions: delete a dead prop, after auditing what the probes can actually prove The source change is small: countryName was declared on UupgsList and passed by region-dashboards but never read — residue of the invented count line removed earlier. Rule 3 prefers deleting a workaround to keeping one, so both the prop and its call site are gone. Audits for the two shapes that revealed real gaps earlier — a prop declared and never used, and state read but never written — now come back clean across all four components, and every reachable prop their CountryDetail passes is implemented. The substantial finding is about the probes themselves, and it lands in _qa-cycle rather than here. Scanning all 42 for "no ok() calls AND never exits non-zero" returned 23, including both numbers reported every tick: region-vs-live's 79/79 and country-vs-live's 32/32 printed "N IDENTICAL · M differ" and returned success either way, so the headline parity was read from text rather than enforced. _probe-standalone-app.mjs had already drifted for exactly that reason: it printed its table, counted gaps, and exited 0 regardless. Read properly it was 9 of 10, not the 10/10 reported for several ticks. The gap was "one h1 on the page: h1 count 2", and measuring resolved it rather than silencing it — the composite is a scroll column, both panes are genuinely on the page (both h1s compute hiddenBy null at 1200x75), so they are two cloned pages in one document. "One h1 per document" collides with clone parity, since region-vs-live and list-vs-live both diff an h1 selector; the clone requirement wins and the property now states "one h1 per pane (scroll column)" with that measurement attached. All three now exit non-zero on a real failure, each proven by a negative test. Two of those tests were wrong first: one swapped a selector on BOTH sides so they stayed identical, and one read $? after a pipe, which reports tail's exit rather than node's. Also made the chooser's pin assertion wait for the condition instead of a stopwatch. It had read queryRenderedFeatures at a fixed 4200ms and measured 0 once while consecutive runs gave 1991 and 2107 — a flaky check, which is worse than a missing one because it teaches you to ignore a red. Three runs now return 2107 every time. Regression: 18 suites green, 9 gates green.		2026-09-24 07:22:38 +00:00
..
all-people-groups	All 12,379 pins were missing on MapLibre, and now a gate says so	2026-09-24 06:24:40 +00:00
big-picture	Stop Big Picture showing the same total twice	2026-09-23 15:32:28 +00:00
cities-internet	connectivity-map honours the provider switch	2026-09-24 03:14:35 +00:00
country-posters	refactor(poster): the 100-list wall stops carrying its own copies	2026-09-24 05:10:44 +00:00
dashboard-plus-grid	Religion/Language tree TOP TIERS now filter the grid (derived-axis interop)	2026-09-23 23:00:00 +00:00
demo-map	consolidate docs into documentation/ and deployment shells into deployment/	2026-09-21 23:23:23 +00:00
doxa-maps-spa	Experimental shelf: Kingdom-impact order + curated exclusions	2026-09-24 05:02:21 +00:00
doxa-research-map	The map keeps the wheel; the edge strips carry the page	2026-09-24 03:47:28 +00:00
doxa-simple-map	Search tier 2: a misspelled country resolves to THE country (best match, 2-edit cap)	2026-09-24 00:34:19 +00:00
doxa-vision-card	Brand-neutral shared VerticalTabsLayout with lazy nested-element hosting; fix cap-5 prayer tab leaf path; neutralize library identifiers; add Forgejo CI build-gate workflow	2026-09-19 17:24: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	resources-map honours the provider switch	2026-09-24 03:20:44 +00:00
key-cities	Close the visa-data leak at its factory + harden the gate	2026-09-24 03:03:53 +00:00
my-upg-100-list	refactor(packet): the legend's packet export uses the shared action	2026-09-24 05:22:29 +00:00
people-groups-grid	Exact sits in the search row, where DX-life puts it	2026-09-24 03:52:44 +00:00
plugin-studio	Plugin studio: show what a composite is made of, in one panel	2026-09-23 20:21:48 +00:00
prayer-walk-planner	Prayer-walk POSTERS: per-zone walking-scale street map on a poster sheet	2026-09-24 01:06:51 +00:00
regions-dashboard	Regions: delete a dead prop, after auditing what the probes can actually prove	2026-09-24 07:22:38 +00:00
research-dashboard	One prop swaps the engine for every map, not just three	2026-09-24 01:34:03 +00:00
research-map-plus-grid	Map engine is one prop: MapLibre drops the search bar, legend rises	2026-09-24 00:43:44 +00:00
stack-demo	Let a stacked composite find its siblings in either tree	2026-09-22 15:37:41 +00:00
template-bundle	consolidate docs into documentation/ and deployment shells into deployment/	2026-09-21 23:23:23 +00:00
upg-neighbor	Experimental shelf: Kingdom-impact order + curated exclusions	2026-09-24 05:02:21 +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).