History

doxa-maps-88655c70 06c6455fdc Regions: the selected page is now an exact clone; the chooser is the one addition The rule: a SELECTED region or country must look identical to the DX-life page you land on when you click it, and the ONLY thing we add is the state their site has no route for. Three things followed from that. 1. THE BAR CHART IS GONE. It was ours, not theirs. RegionDetail.vue is four stat cards, the map, three goal cards and the country table — nothing else. The goal cards and the country table now belong to a SELECTED region only; they were showing on the no-selection view as totals, which made the chooser look like a region page wearing the wrong numbers. 2. THE COUNTRY LIST IS THEIR UupgsList, ported. CountryDetail.vue:63-69 nests <UupgsList :lock-country-code hide-see-all-link />, so cloning that page means cloning that component — a DataTable of ours was a stand-in, not a clone. src/UupgsList.vue carries their markup and their class names so the CSS is theirs rather than a lookalike: .filters / .filters__toggle / .filters__panel / .filters__active / .filter-chip, the .search-box with its 1.5em text-indent, the .grid[data-width-lg] 400px track, and the .uupg__card grid-template-areas with its 576px reflow. Their endpoint and field list too, and .uupg__content stays display:none as theirs is. Scoped to what the page can actually reach: CountryDetail passes none of useSelectCard / useHighlightedUUPGs / randomizeList / dontShowListOnLoad, so the select-card variant, the /highlighted endpoint and the see-all link are branches no consumer runs. 3. THE CHOOSER is the one deliberate difference, and it is now the only one. Opening tab 2 first is a state DX-life cannot reach (/regions is the list, /regions/<slug> always has a subject, [slug].vue 404s otherwise), so it gets a generic map of everything plus three ways in: a region dropdown, a country dropdown (both the shared FilterDropdown), and the all-regions table whose rows were already clickable. Choosing a subject replaces it with the clone. Also removed a visible difference nothing had flagged: the shared PinHint's "Tap a coloured dot" coach-mark was floating over the cloned map, and their page has no such overlay. pinHint:false now, and the fix had to go in the COMPOSITE — a child profile's meta only configures its own leaf page, while a nested pane is handed the config regions-mfe.vue builds, and PinHint reads it off the injected profileConfig. Same cap-4 inheritance gap assetsBase hit, so pinHint joined INHERITED_PAGE_KEYS as well. Verified against the LIVE page, not the stylesheet: doxa.life/regions/cameroon at 1440x1000, filter panel open on both sides, 28 of 28 computed properties IDENTICAL, 0 differ. That diff found the one real error — their .button sets no font-size so it inherits 19.5312px, and I had hardcoded 15.625px. Two rows it could NOT measure are reported as unmeasured rather than counted either way: .filter-chip is absent on both sides with no filter selected. Every suite still green: the map draws 934 pins / 51 outline for a region and 61 / 5 for a country, the country page renders 8 UupgsList cards with their filter toggle and search box, no page has a coach-mark, and all six viewports still match their container formula.		2026-09-24 00:59:10 +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	Search tier 2: a misspelled country resolves to THE country (best match, 2-edit cap)	2026-09-24 00:34:19 +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	Add prayer-walk-planner: experimental polygon prayer-walking map	2026-09-23 16:22:56 +00:00
regions-dashboard	Regions: the selected page is now an exact clone; the chooser is the one addition	2026-09-24 00:59:10 +00:00
research-dashboard	Search tier 2: a misspelled country resolves to THE country (best match, 2-edit cap)	2026-09-24 00:34:19 +00:00
research-map-plus-grid	Show the cap-4 composite in the studio's Simple Research slot	2026-09-23 23:26:40 +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).