History

Doxa Maps be3ee1cdde Kit 4d-1: the shared search is declared once, which landing 4a meant to do and did not finish Landing 4a extracted buildSearchAccessors / makeSearchMatcher / filterRowsBySearch into library/composables/useDashboardSearch.js. It left them DEFINED in useDashboardShell.js as well — 4.3KB of code-identical copies, including the Fuse.js matcher. I compared all three function bodies with comments and whitespace stripped: identical, byte for byte. Nothing had diverged, so nothing failed, and that is exactly why it survived: the facet rail ran the library copy while the shell's KPIs and three panels ran the shell's. The comment that used to sit above those definitions said the point of ONE declaration is that "the searchable text can never drift from what the panels show" — and there were two. This tree has already paid for that shape once, at Jaccard 0.82, with useNeighborT and usePplrT. The shell now imports them like every other consumer, and DashboardChartsRail, DashboardDataTable and DashboardMapPanel read '@map/composables/useDashboardSearch.js' instead of reaching through the shell. No re-export shim: all four consumers are repointed in this commit, so there is nothing for a shim to serve, and an unretired shim is how three older ones sat in the tree unnoticed until this afternoon. check:filter-multivalue grows arm E, deliberately beside arm B. Arm B exists because a copied FILTER predicate lets one panel disagree with the others about what is on screen; a copied SEARCH is the same hazard with a different name. Arm E asserts the library module declares all three, that the shell declares none of them, and that no file anywhere imports them from the shell. Its importer sweep walks plugin-designs and library rather than a hardcoded list, because a hardcoded list of "files that might import this" is the assumption that let 4a's copies survive. Groundwork for 4d-4: this removes 4.3KB from the file that has to be split into a generic kernel and a research composition root, and it removes three exports from the surface that split has to preserve. Source only. research-dashboard and dashboard-plus-grid need a rebuild.		2026-09-27 06:04:09 +00:00
..
all-people-groups	A bare-host embed under ?lang=ar now renders Arabic here too	2026-09-27 02:17:35 +00:00
big-picture	Big Picture: the live count speaks, and the locale reaches the children	2026-09-26 22:06:58 +00:00
cities-internet	Plugin Studio and the gallery split production from experimental, from each bundle's own stage	2026-09-27 06:04:08 +00:00
country-posters	Country posters: a religion search names the family in the reader's language	2026-09-27 01:10:49 +00:00
dashboard-plus-grid	Plugin Studio and the gallery split production from experimental, from each bundle's own stage	2026-09-27 06:04:08 +00:00
demo-map	C2: one library helper for per-engine projection, across 12 call sites in 9 plugins	2026-09-26 08:39:53 +00:00
doxa-maps-spa	Plugin Studio and the gallery split production from experimental, from each bundle's own stage	2026-09-27 06:04:08 +00:00
doxa-research-map	Two setup-time defects: a TDZ that blanked the map, and a cleanup that never ran	2026-09-27 04:00:31 +00:00
doxa-simple-map	Plugin Studio and the gallery split production from experimental, from each bundle's own stage	2026-09-27 06:04:08 +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-internet	Gospel x Internet credits Glottolog on the board	2026-09-27 02:26:09 +00:00
gospel-resources	Plugin Studio and the gallery split production from experimental, from each bundle's own stage	2026-09-27 06:04:08 +00:00
key-cities	Key cities: the map honours provider=maplibre instead of always building Mapbox GL	2026-09-27 04:38:17 +00:00
my-upg-100-list	Plugin Studio and the gallery split production from experimental, from each bundle's own stage	2026-09-27 06:04:08 +00:00
people-groups-grid	One place decides how a count is punctuated, and it still says en-US	2026-09-27 06:04:08 +00:00
plugin-studio	Plugin Studio and the gallery split production from experimental, from each bundle's own stage	2026-09-27 06:04:08 +00:00
pplr-data-maps	PPLR maps: a map that cannot be built says so instead of throwing	2026-09-27 04:38:17 +00:00
prayer-walk-planner	Prayer Walk Planner: the resolved instance id is exposed under its own name	2026-09-27 04:38:17 +00:00
regions-dashboard	Plugin Studio and the gallery split production from experimental, from each bundle's own stage	2026-09-27 06:04:08 +00:00
research-dashboard	Kit 4d-1: the shared search is declared once, which landing 4a meant to do and did not finish	2026-09-27 06:04:09 +00:00
research-map-plus-grid	Kit 4d-1: the shared search is declared once, which landing 4a meant to do and did not finish	2026-09-27 06:04:09 +00:00
stack-demo	Decouple prose: no go-base / nuxtbase / nuxtinator / doxa-base names in plugin comments and docs	2026-09-26 17:28:45 +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	UPG Neighbor cockpit: the view switch, sort buttons, tooltip and legend follow the reader's language	2026-09-27 03:26:35 +00:00
wall-of-people-groups	Wall of People Groups opens where the photos are, with rows as far apart as columns	2026-09-27 05:30:05 +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).