History

doxa-maps-88655c70 d5fff78ccd Some checks are pending build-gate / build (push) Waiting to run Details upg-100: ask the registry for the stylesheet URL, and let the gate hear mapbox A map inside a SHADOW ROOT has to inject its own copy of mapbox-gl.css, because a document stylesheet does not cross a shadow boundary. This profile did that by writing the URL out a second time, and the second copy drifted: it pinned v3.3.0 while every production loader -- generate-tree's baked <script>, useMapInstance, generate-gallery -- had moved to v3.24.0. So the map ran new JS against old CSS. MEASURED on the leaf: mapboxgl.version 3.24.0, the only mapbox stylesheet reaching the shadow root v3.3.0, and mapbox-gl emitting its own "missing CSS declarations" warning. The file's own header already says the engine loader is imported rather than re-declared "because a second copy of one fact drifts". The stylesheet URL was that second copy. It now comes from the same registry via engineStylesheetUrl(). ★ THE GATE COULD NOT SEE ANY OF IT, which is the more useful half of this commit. verify-map-paint asserts a live GL context, zero console ERRORS, and that mapbox emitted attribution -- all true of a map whose stylesheet never applied, since the basemap paints fine while the chrome around it does not. Mapbox itself says so, but as a WARNING, and the listener filtered to type()==='error'. It now listens for _detectMissingCSS's verdict and fails on it. MUTATION-TESTED BOTH WAYS on the same leaf: restore v3.3.0 -> FAIL, exit 1; restore the registry lookup -> PASS, exit 0. Two things I had wrong on the way, recorded so the next reader does not repeat them. I first asserted position:absolute on .mapboxgl-canvas-container -- but v3.24.0 declares only cursor and touch-action there, so static is its CORRECT value and that assertion would have failed every healthy map. I also read "0 .mapboxgl-marker elements" as missing pins; mapbox draws pins as GL geometry in the canvas, so zero is expected. A screenshot showed the polygons, the region colours and hundreds of pins all rendering. Both were properties I assumed rather than verified, and the canary's background-color is the one mapbox actually defines -- it is the test _detectMissingCSS uses. The canary alone would still have been a false green here: that rule is identical in v3.3.0 and v3.24.0, so it is salmon under both. It catches an ABSENT stylesheet; the warning catches a MISMATCHED one. The gate asserts both.		2026-09-24 22:27:52 +00:00
..
all-people-groups	All people groups: count the DOXA groups again	2026-09-24 18:52:33 +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	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	consolidate docs into documentation/ and deployment shells into deployment/	2026-09-21 23:23:23 +00:00
doxa-maps-spa	Research Gallery: a host that asks for maplibre gets maplibre in every tab	2026-09-24 19:57:23 +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	Stop the country sheet calling 729 reached groups unreached	2026-09-24 22:10:03 +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	upg-100: ask the registry for the stylesheet URL, and let the gate hear mapbox	2026-09-24 22:27:52 +00:00
people-groups-grid	One worldmap.svg, at the path that carries its provenance	2026-09-24 09:37:45 +00:00
plugin-studio	Plugin studio: an Explorer tree for the rail, imitating VS Code	2026-09-24 21:40:48 +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	Two posters per row on the regions wall, with a control to change it	2026-09-24 22:04:28 +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	Composites: pass the provider prop down, so keyless embeds are keyless	2026-09-24 19:05:19 +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	consolidate docs into documentation/ and deployment shells into deployment/	2026-09-21 23:23:23 +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).