History

doxa-maps-88655c70 94b356d2b3 Tell the user when the data source is down, not that their filter matched nothing people-groups-grid caught a failed fetch, logged to the console and cleared its loading flag. The template's `v-else-if="!displayedUUPGs.length"` branch then rendered "No people groups match this filter." So when pray.doxa.life was unreachable, the element told the reader their FILTER was wrong. Measured by blocking that host in a browser: two console errors logged, and the only thing on screen was the ordinary empty state. A user adjusts filters that were never the problem; an operator glancing at the page sees normal operation. The console held the truth and nobody opens it — least of all on a partner site or inside the cap-4/cap-5 composites, which is exactly what this element is for. Now distinguishes the two. A `loadFailed` ref drives its own branch: "People-group data could not be loaded. This is a connection problem, not your filter." Also checks response.ok, which was a second silent path. fetch() only rejects on a NETWORK failure, so a 404, a 500 or an HTML error page all resolve — and response.json() on them either throws into the same silent catch or yields an object with no `posts`, which sets an empty grid and reports success. Both were indistinguishable from "nothing matched". Styling adds no colour: the palette is material-light only and --mut is what this component already uses, so the failure line is separated by weight and a hairline rather than an alarm state the design language does not have. Verified both directions. Host blocked: the new message renders, no cards. Host reachable: no message, the grid renders. And `bun run verify:gate1` still passes 13/13 against 2,107 live records, including its "nonsense query -> 0 (empty-state path)" case — so genuine zero-match still works and is now a different thing from a failed load. Found by reading EXPLORE-dxlife-people-groups-refactor.md (2026-09-18) in the staleness scan. Its PLAN is superseded — steps 1-5 describe editing DX-life's own UupgsList.vue, which the standing law forbids and which this flight solved by cloning instead. But its RISK register was still testable, and risk 3 named this exactly: "external data dep on pray.doxa.life/api/people-groups/list". Half of that was already mitigated — prayBaseUrl is injected three ways — and this was the unmitigated half. Risk 6 ("FIVE dropdowns not four, confirm with the Driver") is also settled: four are rendered. A doc can be stale as a plan and still carry a live finding.		2026-09-23 09:31: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	fix big-picture @element to a bare tag and stop embed-smoke reporting every error as a mount timeout	2026-09-20 07:07:48 +00:00
cities-internet	Describe every plugin: 15 of 26 profiles shipped with no description	2026-09-22 03:11:07 +00:00
country-posters	Give country-posters a real description so the SPA stops calling it "experimental bundle"	2026-09-22 02:45:07 +00:00
dashboard-plus-grid	Share the composite, not the child it nests	2026-09-23 08:16:18 +00:00
demo-map	consolidate docs into documentation/ and deployment shells into deployment/	2026-09-21 23:23:23 +00:00
doxa-maps-spa	Stop the capability-5 shells claiming a native element property	2026-09-22 15:03:52 +00:00
doxa-research-map	Land the swarm's dashboard work: colour, rails, cascade, scroll	2026-09-22 18:57:39 +00:00
doxa-simple-map	Describe every plugin: 15 of 26 profiles shipped with no description	2026-09-22 03:11:07 +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	Describe every plugin: 15 of 26 profiles shipped with no description	2026-09-22 03:11:07 +00:00
key-cities	Complete app-profiles->plugin-designs sweep across comments/docs; build green; layouts kept at root (load-bearing)	2026-09-17 18:18:19 +00:00
my-upg-100-list	Name the UPG-100 legend's tabs, instead of shipping the placeholder	2026-09-23 06:52:18 +00:00
people-groups-grid	Tell the user when the data source is down, not that their filter matched nothing	2026-09-23 09:31:10 +00:00
plugin-studio	Match the tab radius to the rest of the app, and open on the tab you were last on	2026-09-23 01:03:15 +00:00
research-dashboard	Read the pin colour and stroke from config instead of hardcoding them	2026-09-23 05:19:44 +00:00
research-map-plus-grid	Share the mobile composite too, and make the url absolute so the embed works	2026-09-23 08:32:50 +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).