History

doxa-maps-88655c70 20c1c0d325 Some checks are pending build-gate / build (push) Waiting to run Details Delete the 100-list wall's dead hidden-map export, and stop it lying to a gate renderFor() had ZERO call sites and was the only caller of makeHiddenMap() and loadPoster(); EXPORT_SPEC was never read. The whole chain dated from when this wall rendered a poster by spinning up an off-screen map and compositing tiles. Export and print now take the shipped .webp, or rasterise posters/<id>.html in the browser. 52 lines out, 17 of explanation in: 925 -> 888. ★ IT WAS NOT MERELY UNUSED — IT WAS CORRUPTING A GATE. isMapLeaf() in generate-tree.mjs is a REGEX over FILE TEXT, so the engine handle inside the unreachable function flagged this profile isMap=true. That flag made verify-map-paint.mjs EXCLUDE the profile, with a written justification — "constructs a real gl.Map ON DEMAND during poster export, off-screen at left:-9999px" — where every clause was true of the SOURCE and false of the RUNNING PRODUCT. A profile was excluded from a paint gate on the strength of code that never ran, and the exclusion read as a measured product fact. Deleting the chain flips the manifest to isMap=false, which is correct: the poster wall is a wall of cards, not a map. The gate's comment now says it is absent because it IS NOT A MAP, rather than because it is a map the gate cannot see. ⚠ The explanation had to be written carefully. Naming the engine handle whole in a comment RE-TRIPS the same regex and reinstates the bug, so it is spelled in two pieces on purpose with a note saying why — the same class as asserting Mark 5:1-20 via the English word "Gadarenes": describing a thing in the terms the detector scans for makes the description itself the defect. ALSO FIXED, found while verifying: check:poster-print-fallback probed '../assets/posters/<id>.html', one level up. A leaf lives at <tree>/<bundle>/<profile>/index.html and resolves assetsBase to '../../assets', two levels up — so on a tree that DID carry the sources the probe 404'd and the gate SKIPped with "posterSources:true was not set" when it had been. A precondition check that is wrong about the precondition silently turns the whole gate off. VERIFIED AT THE RENDERED LAYER after the deletion, not before: the print path still rasterises with every .webp aborted ("generating the poster", clean terminal state), and the card deck still prints 116 cards at 2.5in x 3.5in with 116 QR codes and 0 page errors.		2026-09-24 09:12:17 +00:00
..
all-people-groups	all-people-groups can be shared: its own button, verified by a round-trip	2026-09-24 07:25:19 +00:00
big-picture	Stop Big Picture showing the same total twice	2026-09-23 15:32:28 +00:00
cities-internet	connectivity-map honours the provider switch	2026-09-24 03:14:35 +00:00
country-posters	refactor(poster): the 100-list wall stops carrying its own copies	2026-09-24 05:10:44 +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	Experimental shelf: Kingdom-impact order + curated exclusions	2026-09-24 05:02:21 +00:00
doxa-research-map	The map keeps the wheel; the edge strips carry the page	2026-09-24 03:47:28 +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	resources-map honours the provider switch	2026-09-24 03:20:44 +00:00
key-cities	Close the visa-data leak at its factory + harden the gate	2026-09-24 03:03:53 +00:00
my-upg-100-list	Delete the 100-list wall's dead hidden-map export, and stop it lying to a gate	2026-09-24 09:12:17 +00:00
people-groups-grid	Exact sits in the search row, where DX-life puts it	2026-09-24 03:52:44 +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	prayer-walk-planner can be shared — the last published map with no sharing path	2026-09-24 08:23:30 +00:00
regions-dashboard	Regions: delete four dead imports, after checking the slug port is consumed	2026-09-24 09:08:57 +00:00
research-dashboard	One prop swaps the engine for every map, not just three	2026-09-24 01:34:03 +00:00
research-map-plus-grid	Map engine is one prop: MapLibre drops the search bar, legend rises	2026-09-24 00:43:44 +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
upg-neighbor	Experimental shelf: Kingdom-impact order + curated exclusions	2026-09-24 05:02:21 +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).