History

doxa-maps-88655c70 6958d0a187 Expose the fitted bounds, so a probe can ask the engine what it would choose Two lines that assign the box we pass to fitBounds onto window, beside the map instance that has been exposed there for the same reason since this element was built. It lets a probe call cameraForBounds on the SAME box and compare the answer with where the map actually sits — which is what separates "the fit is wrong" from "something overrode the fit". It earned itself immediately. Looking at our Africa map beside theirs, the framing differs: theirs cuts the Sahel off the top and shows city labels, ours shows the whole continent with margin. The engine's own answer for our box at our frame is zoom 2.777 and the map sits at 2.777, so fitBounds is correct; the dynamic world-fill minZoom — the best suspect, whose own comment records it pinning this dashboard at ~1.45 once — measures 1.229, well below the actual zoom, so it is not overriding anything either. Both cleared by measurement rather than by argument, which leaves their bounding box, and their map is a bundled ESM import with no global to read it from. Recorded as an open, measured difference. Everything about how the map is drawn matches — projection, style, highlight, pin colours, legend, controls, attribution, and Botswana and Lesotho unhighlighted on both sides because neither is among the 41 countries the Africa rollup returns. What it is pointed at does not.		2026-09-24 21:56:43 +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	Make the translation-priority list a table you can export	2026-09-24 21:14:21 +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: no mapbox stylesheet under maplibre, and assert the preview exists	2026-09-24 20:28:45 +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: call the cap-5 shell "Research Gallery"	2026-09-24 20:49:42 +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	Expose the fitted bounds, so a probe can ask the engine what it would choose	2026-09-24 21:56:43 +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).