History

Doxa Maps 303b712469 Draw the pins first: they need 68 KB, not 3.6 MB rega's BASELINE TRACE OVERTURNED MY OWN PROFILE, and this commit is built on their measurement rather than my arithmetic. Baseline at main `ccc2b1bb`, tokenless MapLibre, software GL: every key byte arrives by 1.2-2.9 s, and the first territory draws 5.6-6.4 s LATER. Only ~2.6 s of that gap is main-thread long tasks. The rest is MapLibre's WORKERS parsing and tiling ~3.6 MB of boundary GeoJSON. I HAD PROFILED FILE SIZES AND REQUEST ORDER — the artifact — and concluded the download was the cost. On localhost those 3.6 MB arrive in ~230 ms. Reordering requests was never going to reach 3 s, because PARSING is the bottleneck, and my own two-pass-zones plan would have been just as blocked: resolving even the 15 record-free zones still needs world-adm0 parsed. dx-shepherd dropped it in favour of pins-first (ENDTOKEN-DXS-UPG-PINSFIRST). Right call. THE PINS NEED NONE OF THE GEOMETRY, verified in the code rather than assumed: they are built from `records` (lat/lng) plus slugToZone, and the evaluate() in the pin build maps slugs to zone keys without touching a boundary file. 68 KB, arriving at ~2.9 s cold. SO THE BOOT ORDER IS NOW: records (68 KB) -> build pins -> PAINT PINS -> await the boundaries (3.6 MB parse) -> tapestry -> search index -> full repaint. Three things make that safe rather than clever: · all three boundary downloads are still started BEFORE any await, so nothing is serialised — they fetch and parse while the pins are being drawn; · paintAll now paints WHAT IS READY instead of refusing until everything is. Its old guard `if (!map \|\| !tapestry) return` was what forced the pins to wait on the parse. Every step below it is idempotent and guards its own source AND layers, so calling it twice adds each thing exactly once — which is only true because of ea90e9b2; · `tapestry` STAYS WHOLE-OR-NULL. Nothing paints a partial tapestry; the pins simply stop depending on one. boundsFor(), the search index and the status telemetry keep their invariant, so a reader can never search or fly-to against a half-built index. That was the correctness constraint dx-shepherd and I agreed before rega's trace, and it survives the change of plan. The early paint is FIRE-AND-FORGET: it uses the same style-readiness rule as the boot gate, and if the style is slow the pins simply appear later while the boot gate repaints everything regardless. It must not delay the boundary await. ⚠ NOT MEASURED BY ME. Every claim about timing here is rega's; I have only verified that the code order now matches the plan and that the build is clean. Sending them branch@sha for the same cold trace, and the honest comparison is baseline-cold vs this-cold in THEIR environment — software GL inflates rendering, so the absolute numbers are not the point. ALSO CONFIRMED BY THEIR TRACE, about the previous commit: the list API sends `public, max-age=14400`, so dropping cache:'no-store' is a real win and not a guess — the warm reload was still refetching 68 KB over the network, which fits a client-side no-store exactly. BUNDLE=my-upg-100-list vite build clean; check:packet-strings-parity PASS.		2026-09-26 08:40:53 +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	The people-group list is a universal prop: the same maps can show any project's list	2026-09-26 05:16:02 +00:00
cities-internet	The people-group list is a universal prop: the same maps can show any project's list	2026-09-26 05:16:02 +00:00
country-posters	Show-on-map, second pass: stop trusting the bookkeeping, and make deselect mean something	2026-09-26 05:26:48 +00:00
dashboard-plus-grid	The people-group list is a universal prop: the same maps can show any project's list	2026-09-26 05:16:02 +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 people-group list is a universal prop: the same maps can show any project's list	2026-09-26 05:16:02 +00:00
doxa-simple-map	The people-group list is a universal prop: the same maps can show any project's list	2026-09-26 05:16:02 +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	The people-group list is a universal prop: the same maps can show any project's list	2026-09-26 05:16:02 +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	Draw the pins first: they need 68 KB, not 3.6 MB	2026-09-26 08:40:53 +00:00
people-groups-grid	The people-group list is a universal prop: the same maps can show any project's list	2026-09-26 05:16:02 +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	Every runtime CDN script and stylesheet is an exact version with an integrity hash	2026-09-26 05:50:24 +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	Merge branch 'main' of https://git.nuxtbase.app/doxa-life/doxa-maps into bundler-1/work	2026-09-26 05:42:29 +00:00
research-dashboard	check:dashboard-geocoder-provider: a leaf with no search bar fails instead of passing hollow	2026-09-26 05:50:24 +00:00
research-map-plus-grid	The people-group list is a universal prop: the same maps can show any project's list	2026-09-26 05:16:02 +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	The people-group list is a universal prop: the same maps can show any project's list	2026-09-26 05:16:02 +00:00
wall-of-people-groups	The people-group list is a universal prop: the same maps can show any project's list	2026-09-26 05:16:02 +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).