History

doxa-maps-88655c70 30e6e5699b Prayer Walk Planner: full screen from any embed, and a print proven sharp by resolution The Driver asked for full-screen, and for "a print that stays sharp when zoomed". Full screen. The planner mounts the shared FullscreenButton (the library's Fullscreen-API control, with its CSS pseudo-fullscreen fallback for iOS Safari) as a map overlay. It full-screens the whole planner, toolbar and map, not just the canvas. Measured from a 520px embed in the Research Gallery on a foreign page: the planner took 1280x800 and the map grew 459 → 739px. The label is translated (Arabic "تبديل ملء الشاشة"), because the planner now keeps the shared vue-i18n instance on its own locale. Before, Share and Full screen took the PAGE language even when the gallery sent another. Print resolution, measured, not asserted. The printed map lays out at 7.53 x 8.4 in on the letter sheet (printable width = 8.5in minus the two 12mm margins; emulateMedia alone does not apply @page margins, which misread it once as 8.48in). Its image is 2400x2688 px, so 319 x 320 DPI. A 1:1 crop of the zoomed print was read: small street names (Sancaktar Yokuşu Sokağı, Baki Dede Sokağı), individual building outlines and footpaths are crisp, because the map is rendered from vector tiles at pixelRatio 2, not upscaled from the screen. One PDF page. check:prayer-walk-planner gains both: full screen from a 520px embed must take the viewport, and the printed map must measure >= 300 DPI. 10/10 PASS.		2026-09-25 10:51:21 +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	Stop Big Picture showing the same total twice	2026-09-23 15:32:28 +00:00
cities-internet	Cities with Internet and the phone legend speak the page's language	2026-09-25 06:05:46 +00:00
country-posters	Composites forward `provider`, so a MapLibre partner gets MapLibre	2026-09-25 08:12:20 +00:00
dashboard-plus-grid	Simple Research + Big Picture: the host's style stops at the box, and the last English goes	2026-09-25 08:19:56 +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: boot on a partner page under the CORS the live server actually sends	2026-09-25 08:55:52 +00:00
doxa-research-map	Link religion and language between the map and the grid, by the one table they already share	2026-09-25 10:20:27 +00:00
doxa-simple-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-vision-card	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
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	A gate that asks whether anything is there — and it caught a dead bundle	2026-09-25 09:52:25 +00:00
key-cities	Move the private field-access dataset out of the repo	2026-09-24 18:34:01 +00:00
my-upg-100-list	Batch selection builds a packet, instead of recolouring regions	2026-09-25 09:56:14 +00:00
people-groups-grid	Link religion and language between the map and the grid, by the one table they already share	2026-09-25 10:20:27 +00:00
plugin-studio	Plugin studio: host attributes stay on the host; map-load measurement probe	2026-09-25 08:34:52 +00:00
pplr-data-maps	PPLR data maps: every view loads under MapLibre, and the legend has accessible names	2026-09-25 09:57:17 +00:00
prayer-walk-planner	Prayer Walk Planner: full screen from any embed, and a print proven sharp by resolution	2026-09-25 10:51:21 +00:00
regions-dashboard	Port the switcher's last rule, so six goal cards would stack as theirs do	2026-09-25 09:14:25 +00:00
research-dashboard	The last English in the shared header, panel and facet rail — and a 24px touch target	2026-09-25 09:15:30 +00:00
research-map-plus-grid	Link religion and language between the map and the grid, by the one table they already share	2026-09-25 10:20:27 +00:00
stack-demo	Simple Research + Big Picture: the host's style stops at the box, and the last English goes	2026-09-25 08:19:56 +00:00
template-bundle	Move internal files out of the repo; fix five dead links; a fuller delegation diagram	2026-09-25 05:14:10 +00:00
upg-neighbor	UPG Neighbor: build the five neighbor maps from source, not from a frozen IIFE in an iframe	2026-09-24 18:47:14 +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).