History

Doxa Maps 1fd562c28e Read the page's own direction at mount, not at our first write The clear-only-ours fix recorded the host's dir lazily, inside the rtl branch, the first time it wrote. That is correct only while nothing else has written a direction first. If anything set dir="rtl" on the host before that moment, the element recorded rtl as "the page's own declaration" and then faithfully restored it on every switch away from Arabic -- so the direction never cleared, which is the defect this whole change exists to remove. Measured on the Big Picture leaf: ar left rtl, and zh put rtl straight back, while its three siblings with the same code passed. The difference was not the code; it was that something writes rtl on that host before the element does. Reading the attribute on the FIRST call instead, before any write of ours, is the only moment it is certainly the page's and not ours. A page that genuinely declares dir still owns that decision and still gets it back. Five cases driven against the real function in all four files: no dir at boot, a page declaring ltr, a page declaring rtl, an element mounting while already Arabic, and -- the case that reproduces the failure -- a FOREIGN writer setting rtl after mount and before ours. Restoring the lazy capture to one file fails that fifth case alone and leaves the other four passing.		2026-09-29 20:31:04 +00:00
..
all-people-groups	Repair what the union resolution duplicated	2026-09-29 16:01:45 +00:00
big-picture	Read the page's own direction at mount, not at our first write	2026-09-29 20:31:04 +00:00
cities-internet	Repair what the union resolution duplicated	2026-09-29 16:01:45 +00:00
country-map	country-map: key the refetch by value, let only the newest response win, show the wait	2026-09-29 19:11:37 +00:00
country-posters	Every shadow stylesheet gets its own label, and a gate keeps it that way	2026-09-29 17:42:44 +00:00
dashboard-plus-grid	Read the page's own direction at mount, not at our first write	2026-09-29 20:31:04 +00:00
demo-map	Five plugins were silently monolingual, because the bootstrap was copied sixteen times	2026-09-28 17:40:34 +00:00
doxa-maps-spa	The gallery's published section order: Prayer Progress before the UPG-100 List	2026-09-29 20:00:36 +00:00
doxa-research-map	Four more gates:post reds, hidden until a failed gate printed why	2026-09-29 18:40:27 +00:00
doxa-simple-map	Prayer Progress: a multi-tab bar is a tablist, and says which tab is selected	2026-09-29 18:56:53 +00:00
doxa-vision-card	exp's maps keep the reason and drop the speaker: no comment quotes or cites the Driver	2026-09-29 08:56:44 +00:00
golden-path-check	golden-path-check finds its manifest from its own script, so it answers when embedded	2026-09-28 23:23:58 +00:00
gospel-internet	Repair what the union resolution duplicated	2026-09-29 16:01:45 +00:00
gospel-resources	Mark resources-map production, because a production page already ships it	2026-09-29 18:42:06 +00:00
key-cities	Repair what the union resolution duplicated	2026-09-29 16:01:45 +00:00
my-upg-100-list	Repair what the union resolution duplicated	2026-09-29 16:01:45 +00:00
people-groups-grid	Read the page's own direction at mount, not at our first write	2026-09-29 20:31:04 +00:00
plugin-studio	Keep the reason, drop the speaker, in two comments the merge restored	2026-09-29 14:54:15 +00:00
pplr-data-maps	Repair what the union resolution duplicated	2026-09-29 16:01:45 +00:00
prayer-walk-planner	exp's maps keep the reason and drop the speaker: no comment quotes or cites the Driver	2026-09-29 08:56:44 +00:00
regions-dashboard	Track every pane's getter, prune detached ones, and say when one throws	2026-09-29 17:32:33 +00:00
research-dashboard	Research dashboard: filter lists read as lists in the reader's language	2026-09-29 14:08:04 +00:00
research-map-plus-grid	Read the page's own direction at mount, not at our first write	2026-09-29 20:31:04 +00:00
rudder-voice	Merge development into the gospel handoff branch	2026-09-29 15:19:40 +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	The Wall's and the template's proofs become guards: four two-sided headless checks, in the plugins' own scripts/	2026-09-29 13:14:46 +00:00
upg-neighbor	Repair what the union resolution duplicated	2026-09-29 16:01:45 +00:00
wall-of-people-groups	The Wall's and the template's proofs become guards: four two-sided headless checks, in the plugins' own scripts/	2026-09-29 13:14:46 +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).