History

doxa-maps-88655c70 2a0976f834 Some checks are pending build-gate / build (push) Waiting to run Details The no-selection state is now a map you pick from The Driver's brief, with explicit creative freedom: "some type of map that would show the regions and countries and let you select one that you want to select, which will then show you the page results". It was two dropdowns and a table — a form, not a map. Now the map IS the chooser. Pins are coloured by WAGF region so the seven read AS regions the moment it loads, with a seven-pill key rendered in REGION_ORDER beside it. The key is a control as well as a key: hovering one lifts that region's pins and recedes the rest, clicking one opens that region's dashboard, and clicking any individual pin opens ITS COUNTRY's page. The two dropdowns stay as the keyboard and screen-reader path, and the key items are real <button>s with aria-labels so check:a11y-button-names has a name to find. Colours come from library/colors/wagf-region.js — never a table in the component, because check:one-palette exists precisely to stop that. Rendered in REGION_ORDER because that palette's CVD separation was validated on ADJACENT pairs in that order. HIT TARGET IS PINS, NOT COUNTRY POLYGONS. Polygons would be the obvious choice and would be dead here: the Mapbox country-boundaries tileset 403s on this box (measured, 1 request, 1x403, URL-restricted token), so polygon hit-testing would be both broken and untestable. Pins are our own GeoJSON and always render. ★ TWO THINGS THE SCREENSHOT CAUGHT THAT NO ASSERTION DID — both on the one screen whose entire job is to invite a choice: · a world-wide fitBounds pulled the globe into a skewed crescent of pins over mostly empty white. Twelve assertions were green through that. Replaced with a fixed world view; bounds are now refused outright when the subject is everything. · Mapbox v3 defaults to the GLOBE projection below about zoom 6, so the world view rendered as a small sphere floating in a 1200x780 frame. setProjection ('mercator') for the CHOOSER ONLY — the cloned pages are deliberately left alone, because DX-life sets no projection either and their region page shows the same globe at the same zoom. Matching them is the point. And one the mobile screenshot caught: a fixed zoom that fills 1200px shows barely a third of the world at 390px, with Asia off the right edge. The zoom now follows the CONTAINER WIDTH — log2(width/512), the width at which Mercator's world fits — clamped to [0,2], re-derived on resize via ResizeObserver. A phone still crops (Mapbox will not go below zoom 0) but ~24% rather than ~67%, and it pans. Verified: 12 chooser assertions, including that the CLONED pages are untouched — their prayer colouring and their four-row prayer key both return on a selected region. Region page still 68/68 vs live, country 28/28, app 10/10, no gate newly red.		2026-09-24 02:43:42 +00:00
..
all-people-groups	light the remaining unconditional loading overlays and the copy-me starter	2026-09-21 16:40:53 +00:00
big-picture	Stop Big Picture showing the same total twice	2026-09-23 15:32:28 +00:00
cities-internet	Commit the two pinHint:false metas that were only on disk	2026-09-24 00:01:08 +00:00
country-posters	Search tier 2: a misspelled country resolves to THE country (best match, 2-edit cap)	2026-09-24 00:34:19 +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	Regions mounts its cap-4 composite; UPG-100 drops its duplicate share and shrinks its dots	2026-09-23 19:37:55 +00:00
doxa-research-map	Merge main into bundler-2/work	2026-09-24 00:44:26 +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	Commit the two pinHint:false metas that were only on disk	2026-09-24 00:01:08 +00:00
key-cities	Resolve the shared asset base per bundle, so nested tabs stop 404ing	2026-09-23 12:14:52 +00:00
my-upg-100-list	Search tier 2: a misspelled country resolves to THE country (best match, 2-edit cap)	2026-09-24 00:34:19 +00:00
people-groups-grid	Religion/Language tree TOP TIERS now filter the grid (derived-axis interop)	2026-09-23 23:00:00 +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	The no-selection state is now a map you pick from	2026-09-24 02:43:42 +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
.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).