History

Doxa Maps 97d0ef264a Clamp the goal card's big number as theirs does; the nowrap worry was backwards utilities/_typography.scss gives .font-size-4xl a clamp: font-size: clamp(var(--font-size-2xl), 6vw, var(--font-size-4xl)) and ours was a flat var(--font-size-4xl). Identical at 1024 and above, where both sit on the ceiling, but below that ours never shrank. Their resolved values against ours: 390px theirs 38.15 ours 59.60 ours 21.46 too large 768px theirs 46.08 ours 59.60 ours 13.52 too large 1024px+ theirs 59.60 ours 59.60 identical ★ I REPORTED THIS AS UNCHANGEABLE ONE COMMIT AGO, AND THAT WAS BACKWARDS. I said it interacted with the documented nowrap decision — a figure must never split across lines in a 372px card, which is why the flat value was chosen. But the clamp makes the figure SMALLER exactly where the wrap was observed: in a 372px container 6cqw is 22.3px, below the 2xl floor, so it resolves to 38.15px against the 59.60px that was breaking. The clamp helps the very problem the flat value was picked to avoid. I had assumed a conflict instead of computing it, and one line of arithmetic settled it. The nowrap stays as a belt. cqw rather than vw, consistent with every other clamp in this element (the container-vs-viewport substitution the Driver is still ruling on). At 768 that lands 42.4 against their 46.08 — 3.68 off instead of 13.52. _chk-clamp-floors-at-phone-and-tablet.mjs picks the new clamp up on its own: 14 clamps now, and 12/12 token-bounded ones still pin to their floor at 390, so the "exact parity at phone width, provable without a container measurement" result now covers the big number too.		2026-09-26 05:35:51 +00:00
..
all-people-groups	All People Groups loads fast on a light map; the Vision Card becomes a true funnel from data	2026-09-25 07:18:30 +00:00
big-picture	Translate the eight strings that had no catalogue entry, keeping their English exactly	2026-09-26 03:34:42 +00:00
cities-internet	Cities list + tables: keep numbers in their previous format while numerals are held	2026-09-26 02:38:06 +00:00
country-posters	"Show on map" switched the view and the map never acted: retain the request	2026-09-26 04:21:49 +00:00
dashboard-plus-grid	Big Picture and Simple Research mount again: import the three locale names they use	2026-09-26 03:02:46 +00:00
demo-map	Move internal files out of the repo; fix five dead links; a fuller delegation diagram	2026-09-25 05:14:10 +00:00
doxa-maps-spa	Research Gallery: PPLR Data Maps and Wall of People Groups are named in all 11 languages	2026-09-25 23:41:17 +00:00
doxa-research-map	The map follows the list: filter the grid and the camera goes there	2026-09-25 23:28:53 +00:00
doxa-simple-map	Prayer Progress: no hardcoded English left in the map's own chrome	2026-09-26 03:34:16 +00:00
doxa-vision-card	Doxa Vision Card: take the page language from profile-config lang as well as locale	2026-09-26 01:10:51 +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	Gospel map: give the zero-access view an address, and say the way in on every row	2026-09-26 03:56:24 +00:00
key-cities	Key Cities (gated): the map, list, tables and posters speak the reader's language	2026-09-26 03:34:30 +00:00
my-upg-100-list	The prayer packet shows how its list was narrowed out of all the earth	2026-09-26 04:38:59 +00:00
people-groups-grid	Match the live page's wording where we differed only by case	2026-09-25 17:08:16 +00:00
plugin-studio	Plugin Studio: collapse the header to give the plugin the whole page, and bring it back in one click	2026-09-26 04:39:00 +00:00
pplr-data-maps	PPLR data maps: loading d3 no longer writes into the host page's own d3	2026-09-26 04:54:42 +00:00
prayer-walk-planner	Export gate reads the tree name from the build config	2026-09-25 21:32:35 +00:00
regions-dashboard	Clamp the goal card's big number as theirs does; the nowrap worry was backwards	2026-09-26 05:35:51 +00:00
research-dashboard	Translate the eight strings that had no catalogue entry, keeping their English exactly	2026-09-26 03:34:42 +00:00
research-map-plus-grid	A gate for the mistake I shipped: a name used but never bound	2026-09-26 04:21:49 +00:00
stack-demo	Studio and stack-demo hand the host's language down to what they mount	2026-09-25 13:26:01 +00:00
template-bundle	template-bundle: the starter's first screen is now a real map	2026-09-26 04:38:12 +00:00
upg-neighbor	My UPG Neighbors: the Language Clusters lens draws its map again	2026-09-26 04:57:47 +00:00
wall-of-people-groups	Wall of People Groups: nothing leaks onto the host page (no Font Awesome, no window.d3)	2026-09-26 03:34:31 +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	plugin-designs/README: the tree is dx-maps, and a bundle's tag is its folder name	2026-09-26 01:19:53 +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/dx-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="/dx-maps/<your-map>/<your-map>.js"></script>
<your-map profile-config='{"profile":"overview","tk":"pk.eyJ..."}'></your-map>
<your-map profile-config='{"profile":"detail","tk":"pk.eyJ..."}'></your-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/dx-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).