Goal

Made by Vibe Coders for Vibe Coders to prepare the way of the Lord and make His paths straight.

Isaiah 40:3 “...Prepare the way for the LORD in the wilderness; make a straight highway for our God in the desert."

Bottom line up front

• Why: To Bless the Nations

• Great Commission: dx-maps exists to give disciples, churches and leaders what they need to bless the nations. We believe the deeper answer to the Great Commission is indigenous disciples, churches and leaders multiplying among their own peoples and blessing them, so that the Commission is fulfilled through love. The maps serve that in three ways: praying for the unreached peoples of the world, mobilising believers to bless their own neighbours and cities, and caring for the needy with private maps that stay with the people who serve them.

• How it was made: no human wrote this code. It is about 100% AI-coded, and about 90% of the maps began as a vision spoken aloud (voice-to-text, such as Rudder) and handed to an AI agent that built it with dx-maps. If you can picture a map and say it in plain English, an agent can build it.

• Who it's for: vibe coders, people who build by describing what they want to an AI agent. One repo, one shared library and a live Plugin Studio let your agents build many maps side by side (what you get).

• Our favorite: the experimental Gospel × Internet dashboard: the most experimental, and likely the most impactful for the Great Commission, because everything comes together there. It is inspired by the Perspectives course and book, and by Curtis Sergeant's 100-list and relational-stewardship training (bounded and centered sets).

• What each map is for:

  • Big Picture: the library's own interface, the one agents use to build maps.
  • UPG-100: the most strategic. It divides the task into prayer packets.
  • Gospel maps: the resources that exist in each language.
  • UPG Neighbor: the reached neighbors near each unreached group.
  • Gospel × Internet: all of it, together. Built for linguists, catalysts, translators (human and AI) and prayer warriors.

Built with love, with the prayer that these maps bless the nations.

A blessing for you. These maps and posters are given to bless the people who bless the nations. We love you, and we are thankful for your work. We bless you in Jesus' name.

Every poster is in Posterverse (plugin-designs/posterverse/): the UPG 100 List, Country Posters, Poster Design and Wall of People Groups. They are all in the Plugin Studio (bun run dev) too.

dx-maps — one build, maps that embed everywhere

Write a map once in plugin-designs/<your-map>/, run one build, and drop it on any site — iframe, script embed, mobile app — or open every map at once as one app. Five plugin capabilities, three outputs, one shared library, one build.

Using an AI agent? Give it skills/plugin-designer. It learns this framework's terms and patterns, which lowers the barrier to entry.

What the library gives every map

🗺️ Two map engines	Every map draws with Mapbox or MapLibre (free, no key) — switch with "provider" in its settings or ?provider=mapbox in the address. By default it uses MapLibre; Mapbox is an explicit choice ("provider": "mapbox" and a token).
🔑 A key or a key service	Give Mapbox a public token, or the address of a token service that hands one out — set once in the Plugin Studio header.
🌍 11 languages	?lang= or "locale", with Arabic right to left — Languages.
🧩 Web components	Each map is its own HTML tag, like <all-people-groups>, that works on any page — no framework needed.
🔗 Maps that talk to each other	Maps share props and events, so one app can nest them and a click in one can move another.
🪶 Small bundles	Each map's file carries only the parts of the shared library it uses (tree-shaken).
⚙️ One build step	bun run build makes every map at once.
📦 Three outputs	A web folder (iframe, script embed), a mobile app, a desktop app — the 3 outputs.

What dx-maps set out to do	Proof
One build → one folder you can drop on any host	bun run check:drop
Every map embeddable from a copy-paste snippet	the 3 outputs · bun run check:embed-targets
Every map interoperable through props and events	bun run verify:interop
One app nests every map — and each stays embeddable on its own	capability 5 · bun run check:composite-reg
5 capabilities, every one shippable in every output	bun run verify:5-caps
Shared library, private plugins — reuse without breaking each other	bun run check:library-index
One owner per plugin, a second reader for every change, one landing at a time	agent swarm

For vibe coders: build, open the Studio, embed a map

1. Open the Plugin Studio (every map, live, updating as you or your agent edit):

bun install --frozen-lockfile
bun run dev                     # open the address it prints: that page is the Plugin Studio

2. Build. The built maps are already in the repo. After a change, rebuild just that map, or all of them:

BUNDLE=<map> bun x vite build && bun run tree && bun run fix:sri   # one map, then its pages and hashes
BUILD_ALLOW=1 bun run build                                         # every map (~4 min); the output is public/dx-maps/

After a one-map build, bun run tree rewrites the map's pages and the manifest (a changed .meta.json reaches them only this way), and fix:sri refreshes their integrity hashes. Skip them and the map's own page and any pasted snippet keep the old settings and refuse the new file. When the DX Life site's repo sits next to this one (../doxa-life), the full build also copies the maps into its public/. That is the one path set in vite.doxa-maps-build-config.json (dropin.dest); nothing else on your computer is searched. No site there: the step says so and skips. DOXA_DROPIN=off turns it off, and bun run dropin copies on demand.

3. Embed a map. Every map has its own embed script: its embed.script in public/dx-maps/manifest.json (an embed.iframe too). Paste it whole. It preloads the map engine, points the map at its data (window.MAP_APP_API_URL), loads the map's script with its integrity hash, and places the map's tag. The two lines at its core:

<script src="/dx-maps/doxa-simple-map/doxa-simple-map.js" integrity="sha384-…" crossorigin="anonymous"></script>
<doxa-map profile-config='{"profile":"doxa-simple-map","assetsBase":"/dx-maps/assets"}'></doxa-map>

On DX Life, the maps are served from its own public/dx-maps/, so a page loads /dx-maps/<map>/<map>.js and places the map's tag. Copy each snippet from the manifest: its integrity hash changes with every build. More: the three routes and how a page shows a map.

For agents: what this repo is for

This repo builds mobilization maps: maps that help disciples, churches and leaders reach their city and the people groups of the world. When you work here, the goal is one of these:

Goal	The production maps that serve it
Reach a city	Regions (regions-dashboard) and the country map (country-map): the people groups of each country. The production maps work by country and region; city-level planning (Prayer Walk Planner) is still experimental
Mobilize for people groups	Big Picture (dashboard-plus-grid); Simple Research (research-map-plus-grid)
Plan outreach	Gospel Resources (gospel-resources): what exists in each language; Cities with Internet (cities-internet): whether a group can be reached online
Pray: packets and prayer resources	UPG 100 List (my-upg-100-list), Regions and Simple Research: posters and prayer packets; Prayer Progress (doxa-simple-map)

• Start with the skill: skills/plugin-designer teaches the patterns, the shared library and the checks.
• One plugin per folder in plugin-designs/; shared code goes in library/ only if it stays reusable for every other plugin.
• Land on development, one change at a time through the lock, with bun run gates:pre passing. main is production and moves only on a publish.
• These 8 maps are in production: the 7 in the gallery, plus the country map for DX Life's country pages. The other maps are experimental: leave them as they are unless your task is one of them.

Click any ▸ to read more. Everything below is folded so you can scroll the pictures first.

---

The 7 production maps

Seven maps DX uses today — each one a plugin you can embed on its own, and all seven together in the Research Gallery, which DX Life publishes as Deep Research. An eighth production map, the country map (country-map), draws DX Life's country pages; it isn't in the gallery.

Big Picture the whole research dashboard: filters, map, charts, people groups	Simple Research the research map with the people-groups grid, made for phones	Regions every region and its countries, then a dashboard per region	Prayer Progress where prayer is happening, and where it is still needed
UPG-100 List prayer lists of 100 people groups, with posters to print	Cities with Internet internet access where unreached people groups live	Gospel Resources which people groups have scripture, film or audio — and which have nothing	Research Gallery all seven in one app — capability 5

On a phone

Simple Research	Regions	Prayer Progress	UPG-100 List
Cities with Internet	Gospel Resources	Research Gallery	Big Picture a desktop dashboard by design — on a phone, Simple Research is the dashboard, and the Research Gallery opens on it.

Every capability ships every way

Capability	Example	iframe	Mobile app	JavaScript embed	WordPress / Disciple Tools	Desktop
5 — app shell	Research Gallery	✅	✅	✅	🧪	✅
4 — composite	UPG-100 List	✅	✅	✅	🧪	✅
3 — multi-view	research map	✅	✅	✅	🧪	✅
2 — presets	Prayer Progress	✅	✅	✅	🧪	✅
1 — single element	all people groups	✅	✅	✅	🧪	✅

_{✅ works today · 🧪 proven, not yet in production. Every plugin builds into the same folder, and that folder is what all five methods ship — so a capability never limits where a plugin can go.}

The Experimental shelf

New plugins the Research Gallery picks up by itself — each builds and embeds like any other, and graduates to a named tab when it's ready.

Wall of People Groups all 2,107 Doxa people groups as photo cards on one zoomable prayer wall, with a pray dialog

Prayer Walk Planner plan a prayer walk through a zone, open it full screen from any embed, and print a walking map that stays sharp when zoomed

_{Also on the shelf: UPG neighbor, all people groups, country posters, the vision card, and the PPLR data maps.}

How one build becomes three outputs — the "map cruncher"

 map · map · map · map · map · map · map        many maps, each once its own codebase
   \    \    |    |    |    /    /
    +----- plugin-designs/ ------+              one folder per plugin — the free zone
                 |
           library/ (@map)                      shared, reusable pieces — the high bar
                 |
            ONE build step
                 |
          public/dx-maps/                     OUTPUT 1: one drop-anywhere web folder
          /       |        \                   how a page shows a map:
      iframe   JS embed   WordPress            (WordPress just for fun)

    the same folder, wrapped:
    mobile app (OUTPUT 2) · desktop app (OUTPUT 3)

---

Who it's for

Vibe coders — who dx-maps was built for

If you build with AI agents, this repo is made for you:

• One repo, many plugins. Each plugin is one folder in plugin-designs/ with its own src/, and they all share one library, so your agents can build many plugins side by side.
• See every design live. bun run dev opens the Plugin Studio: every plugin in one place, updating the moment you save.
• Speak instead of typing. Rudder, an offline voice-to-text tool, sits as a corner widget in the Studio: look at a plugin, say what you see, and hand the text to your agent. Nothing leaves your computer (Linux today).
• One plugin, several outputs. The same plugin ships as a web embed or a mobile app, and a plugin can target the desktop: Rudder is the desktop example, a corner widget in the Studio and its own desktop app (bun run desktop:build rudder-voice, see HOWTO-build-the-desktop-app).
• Build together. Run it in the cloud gives a whole team one shared dev server.

The people doing the work

Each map answers a real task for someone doing the mission. Open it in the Research Gallery, or embed just the one you need.

You are…	Open	It answers
a translator (or an AI translation pipeline)	Gospel Resources (map, list, data tables)	which people groups have no Scripture, film or audio in their language, and which bridge language already reaches them
media to movements	Cities with Internet · Gospel × Internet	where unreached people groups live with internet access, country by country and down to province where data exists
a catalyst or mobilizer	Big Picture · Prayer Walk Planner · UPG 100 List · Gospel × Internet	find gospel resources for the people you are reaching real time, build prayer walking maps for real outreach, as you prayer walk each key zone in your cities of choice, find indigenous disciples, groups, and leaders mobilize them each to have prayer packets, cards and posters to blanket all the people groups in prayer as a prayer mobilizer catalyst
praying	Prayer Progress · UPG-100 List	where prayer is covered and where it is still needed; print a Prayer List, Poster Map or Card Deck for a list of 100
a teacher or presenter	the Research Gallery	every map in one app, multiple languages support

For AI agents

• Every map, and how to embed it: public/dx-maps/manifest.json lists each plugin with its embed.iframe and embed.script snippet (with its integrity hash).
• The data behind the maps: public/dx-maps/assets/tables/*.json (gospel access, internet access, bridge languages, resource links…), assets/people-groups/*.json (points and slim records) and assets/people-groups/lists/ (the membership of each list).
• Live people-group data (public, no key): https://pray.doxa.life/api/people-groups/list and …/detail/{slug}, the same endpoints the published maps call.
• Switches on any map page: ?lang= (11 languages), ?provider=maplibre|mapbox, ?list= (a project list such as 700), ?tk= (a Mapbox token). Embeds take the same keys in profile-config. Contract: documentation/reference-universal-props.md.

---

The 5 plugin capabilities

A capability is how much a plugin nests, from one element (1) to an app of apps (5). Every screenshot is a real plugin from this repo's build.

Capability 5 — app shell: the Research Gallery

One plugin that holds every map as a tab — and each tab is still a plugin you can embed on its own.

More about capability 5 — the app shell

An app shell is the outer frame of a whole app: a rail of tabs down the side, a header, and navigation. Each tab loads a real plugin from a lower capability, only when you open it, so the app stays fast. Nothing is copied into the shell: when a plugin improves, the shell shows the improvement on the next build.

• Where it lives: plugin-designs/doxa-maps-spa/ — one element, <doxa-maps-spa>.
• Changing the tabs: the order and grouping are one list, NAV_MODEL in doxa-maps-spa.vue.
• New plugins show up by themselves: any plugin that isn't placed in a section lands on the folded Experimental shelf, read from the built manifest.json — no code to edit.
• A second app shell ships too: the Plugin Studio (below), which holds every plugin for developers.

What the Research Gallery is made of — seven production maps, an Experimental shelf, all five capabilities in one plugin

Research Gallery                          <doxa-maps-spa>          capability 5
├─ Dashboards
│  ├─ Big Picture                         dashboard-plus-grid      capability 4
│  │   ├─ research dashboard              research-dashboard       capability 3
│  │   └─ people-groups grid              people-groups-grid       capability 2
│  ├─ Simple Research                     research-map-plus-grid   capability 4
│  │   ├─ research map                    doxa-research-map        capability 3
│  │   └─ people-groups grid              people-groups-grid       capability 2
│  └─ Regions                             regions-mfe              capability 4
│      ├─ regions list                    regions-list             capability 1
│      └─ region dashboards               region-dashboards        capability 1
├─ Prayer Mobilization
│  ├─ UPG-100 List                        upg-100-mfe              capability 4
│  │   ├─ list                            upg-100-list             capability 1
│  │   └─ poster wall                     poster-wall              capability 1
│  └─ Prayer Progress                     doxa-simple-map          capability 2
├─ Gospel Research
│  ├─ Cities with Internet                connectivity-map         capability 1
│  └─ Gospel Resources                    resources-map            capability 1
└─ Experimental (a folded shelf, filled automatically from manifest.json)
   ├─ prayer walk planner                 prayer-walk-planner      capability 1
   ├─ UPG neighbor                        upg-neighbor             capability 3
   ├─ all people groups                   all-people-groups        capability 1
   ├─ country posters                     country-posters          capability 4
   ├─ vision card                         doxa-vision-card         capability 2
   ├─ PPLR data maps                      pplr-data-maps           capability 3
   └─ Wall of People Groups               wall-of-people-groups    capability 3

Capability 4 — composite: plugins wired together

Several plugins glued into one, talking to each other — and each piece still embeddable alone.

List (capability 1, embeddable alone)	Poster wall (capability 1, embeddable alone)

More about capability 4 — composites

A composite takes plugins that already exist and places them together — side by side, stacked, or as views you switch between — and ships the set as one new element. The pieces talk through props (settings passed in) and events (messages sent out): click a region in one piece and another piece updates. Nothing is copied, so each piece can still be embedded on its own.

• Example: plugin-designs/my-upg-100-list/ — the UPG-100 list and its poster wall, joined into upg-100-mfe. Big Picture, Simple Research and Regions are composites too.
• How to declare one: a <name>.meta.json beside it with "type": "nested-elements-mfe" and a "composes" list of the plugins inside.
• The layouts that do the placing: VerticalTabsLayout and StackLayout in library/layouts/.

Capability 3 — multi-view: many screens, one element

One plugin with several screens inside — tabs you switch between.

More about capability 3 — multi-view

All the screens live in one plugin, so they share code and data and switch instantly. The trade-off: you embed the whole thing — you can't embed just one of its tabs. When you need that, split the tabs into separate plugins and join them with a composite (capability 4).

• Example: plugin-designs/doxa-research-map/ — Prayer, Engagement, People Groups, Regions, Languages and Religions in one map.
• How to declare one: a <name>.meta.json with "type": "monolithic".

Capability 2 — presets: one plugin, many maps

The same map code, several ready-made versions — each with its own page and embed code.

Prayer	Engagement	Adoption

More about capability 2 — presets

You write one map, then list its versions in a small table: a name and the settings for each. The build turns every row into its own standalone page and embed snippet — same code, different map. Adding a version means adding a row, not writing code.

• Example: plugin-designs/doxa-simple-map/ — Prayer, Engagement and Adoption from one map.
• How to make one: add <name>.instances.json beside the plugin: { "instances": [{ "id": "prayer", "title": "Prayer", "props": { … } }] }.

Capability 1 — single element

One folder, one map, one tag you can paste into any page.

More about capability 1 — single element

The simplest plugin, and where every map starts: a folder with three files — the map's .vue, an index.js that registers its tag, and an index.html for previewing it (under bun run dev, a plugin's own page is /__leaf/<plugin>/<profile>). The build turns it into one custom HTML tag, like <all-people-groups>, that works on any web page.

• Example: plugin-designs/all-people-groups/ — every people group on one map.
• How to make one: copy plugin-designs/template-bundle/ to plugin-designs/<your-map>/ and rename it. The studio finds it automatically.
• Which plugin is the example of each capability is generated, not remembered: documentation/reference-capability-exemplars.md.

---

What the build makes — 3 outputs

One build step makes one folder. That folder is the product — every other choice is where you put it and how a page shows it.

#	Output	What it is	Status
1	The web folder public/dx-maps/	every map, each embeddable on its own, all working together — 1367 files, 163 MiB (about 170 MB)	✅ production
2	Mobile app	the same folder, wrapped as an Android app by Capacitor	✅ built
3	Desktop app	the same folder, wrapped as a desktop app by Tauri	✅ works today

Output 1 — the web folder

Two questions: where does the folder go (hosting), and how does a page show a map (embedding).

Where the folder goes: three routes

The easiest path: drop-in. The folder goes into your own site's public/, and your site's own server serves every map: one server, no PocketBase, nothing else to run. Set dropin.dest in vite.doxa-maps-build-config.json to your site's public/ (the default is ../doxa-life/public), then:

EMBED_BASE_URL=https://your-site bun run tree   # seconds: writes your address into the copy-paste snippets
bun run dropin                                  # copies dx-maps/ into your site's public/; the rest of the site is left alone

The built maps are already in the repo, so no build is needed. If you changed a plugin, rebuild just that one first: BUNDLE=<name> bun x vite build. Without EMBED_BASE_URL, the pages still work, but the snippets in manifest.json stay relative (./…) and other sites can't paste them. bun run tree rewrites the manifests in this repo's public/; git restore public puts them back after the copy.

This route is proven on DX Life: real pages rendering maps, one server, every production map passing its embed checks, copy-paste snippets included. Its drop-in branch copies the folder into public/dx-maps. Its /research page shows the research map by itself, with a link to /deep-research, a page not in the menu that holds the whole gallery as Deep Research.

Embeds are pinned. A host pastes a map's embed.script from manifest.json; its integrity hash makes the browser refuse the bundle if it changed by even one byte, so copy the snippet again after each release (bundle integrity).

Subdomain: the dx-maps container with PocketBase. When maps need a backend of their own (accounts, saved data, an API for mobile apps), run the dx-maps container on its own subdomain, such as maps.your-site. It serves the same folder with PocketBase beside it, and its schema ships as migration files in the repo. The Dockerfile and compose.yaml sit at the repo root; recipe and settings: deployment/cloud/.

Plugin Studio: the public Studio, with PocketBase. The highest route: the same container with ACCESS=public, on your research subdomain.

• The Plugin Studio follows development and is open to everyone, so what agents land shows up live.
• Its /cdn, built from main, serves your site's production maps.
• Publishing and PocketBase's dashboard ask for a password you set when you deploy; OIDC stays available.

Settings: the public Studio.

Route	What runs	Backend	Capability
Drop-in	your site's own server serves the folder	none	the simplest, for most sites
Subdomain	the dx-maps container on its own subdomain, behind a sign-in	PocketBase	accounts, saved data, an API
Plugin Studio	the container's public Plugin Studio on your research subdomain; your site embeds maps from its /cdn	PocketBase (a password now, OIDC-ready)	the highest: plugins built live in public, plus everything above

More about the folder

• The folder works from any address. Every link inside it is relative, so it can sit at https://your-site/dx-maps/ or at the root of a subdomain and nothing breaks (bun run check:drop proves it).
• iframes need nothing special. A map's page loads inside the frame from wherever the folder is.
• JS embeds on another site need one header. The embed loads scripts and manifest.json across sites with a security hash, so the host must allow it: Access-Control-Allow-Origin: *. The container sends it; a drop-in needs it only if other sites embed from yours.

How a page shows a map

iframe — the prayer map on any site ✅ production

Paste one line of HTML and the map appears — on any website, no coding.

More about the iframe

An iframe is a window in your page that shows another page — here, the map's own page. It's the easiest way to share a map: it works on any site that accepts HTML, and the map keeps its own look. Every plugin's exact snippet is embed.iframe in public/dx-maps/manifest.json:

<iframe src="https://YOUR_HOST/dx-maps/doxa-simple-map/doxa-simple-map/prayer/index.html?utm_source=YOUR_SOURCE"
        width="100%" height="600" style="border:none;border-radius:12px;" allowfullscreen></iframe>

JavaScript embed — Deep Research for DX Life ✅ works today

Two lines of code put a whole app inside your own page — here, the Research Gallery, which DX Life publishes as Deep Research on a page of its own (/deep-research).

An earlier build, when the gallery sat on DX Life's research page with its tabs in the old order. It now has a page of its own.

More about the JavaScript embed

Instead of a window onto another page, the map becomes part of your page, so your page can talk to it. On dx-life, one embed of the gallery is the whole /deep-research page, and the research page keeps the research map by itself. The exact snippet is embed.script in manifest.json; copy its integrity hash from there, because it changes with every build:

<script>window.MAP_APP_API_URL="https://pray.doxa.life";</script>
<script src="https://YOUR_HOST/dx-maps/doxa-maps-spa/doxa-maps-spa.js"
        integrity="sha384-…" crossorigin="anonymous"></script>
<doxa-maps-spa profile-config='{"profile":"doxa-maps-spa","tk":"YOUR_MAPBOX_TOKEN","utmSource":"YOUR_SOURCE","assetsBase":"https://YOUR_HOST/dx-maps/assets"}'></doxa-maps-spa>

WordPress / Disciple Tools — 🧪 proven, just for fun

We got a JAMstack map running inside WordPress and Disciple Tools.

More about WordPress / Disciple Tools

It works, but it isn't yet a production feature of the map bundler. Two ways to try it:

• Easiest: paste the iframe or JavaScript snippet into a WordPress Custom HTML block.
• As a plugin: install deployment/wordpress/doxa-maps-embed/ in wp-content/plugins/. It adds a [doxa_map] shortcode and a block for the block editor.

bun run check:wp-embed confirms the plugin writes the right HTML, without needing WordPress installed.

Output 2 — the mobile app ✅ built

The same maps, wrapped as a phone app. No new code — the maps are JAMstack: they fetch their data from a remote API, which is exactly what a mobile app needs.

More about the mobile app

Capacitor wraps the built folder into an Android app. Shown here: the UPG-100 prayer lists and posters at phone size, each poster with its own print options.

bun run check:mobile   # checks the app is wired up correctly — needs no Android tools
bun run phone          # builds the app and installs it on a phone or emulator

bun run phone needs the Android SDK, JDK 17 and adb. Only Android is set up; iOS is not yet.

Output 3 — the desktop app ✅ works today

We got the JAMstack map app running as a desktop app.

Rudder, the voice-to-text plugin, runs as its own desktop app too, built with bun run desktop:build rudder-voice (HOWTO-build-the-desktop-app).

More about the desktop app

Tauri wraps the same built folder into a desktop program: it produced a Linux app and a .deb installer. It isn't in the dx bundler for production yet — and the Research Gallery could become a strong desktop app.

bun run check:tauri    # checks the desktop setup — needs no Rust tools
bun run tauri:build    # builds the app — needs Rust, the Tauri CLI and webview libraries

_{WordPress and Tauri marks from Simple Icons (CC0); the trademarks belong to their owners.}

---

Security controls

Bundle integrity. Every bundle ships with a SHA-384 hash in public/dx-maps/manifest.json (bundles[].integrity), and every copy-paste script snippet (profiles[].embed.script) already uses it:

<script src="https://YOUR_HOST/dx-maps/doxa-simple-map/doxa-simple-map.js"
        integrity="sha384-…" crossorigin="anonymous"></script>

If the file on the host is changed by anyone, even by one byte, the browser refuses to run it. crossorigin="anonymous" is required for the check to work across sites, so the host must send Access-Control-Allow-Origin: *. Copy the snippet again after each release, because the hash changes with the bundle. bun run check:sri keeps the manifest and the built pages in step.

The backend in the cloud container (v1, experimental)

• Locked by default. A new PocketBase collection starts with admin-only rules; you open it deliberately, collection by collection.
• Dashboards hidden. The production instance exposes only its /api/; its admin dashboard is blocked at the proxy. The development dashboard is open only to the admin group.
• No server-side code. PocketBase's JavaScript hooks are switched off in both instances.
• Not built yet: per-plugin locks between plugin authors (who may edit which plugin's backend) and isolated edge functions. Until they exist, everyone with dev access is trusted with every plugin's backend.

---

Languages

Every map speaks 11 languages — add ?lang=<code> to a map's page address, or, when a map is embedded in your own page, set "locale" in its profile-config. Arabic reads right to left.

_{UPG-100 List with ?lang=ar: the interface is in Arabic; people-group and place names come from the data.}

Code	Language		Code	Language
en	English		hi	हिन्दी — Hindi
ar	العربية — Arabic (right to left)		it	Italiano — Italian
de	Deutsch — German		pt	Português — Portuguese
es	Español — Spanish		ro	Română — Romanian
fr	Français — French		ru	Русский — Russian
zh	中文 — Chinese

More about languages

• Pick a language with the address: …/prayer/index.html?lang=fr shows the map in French. It works on every map's own page and on the Research Gallery. ?locale= works too.

• Set it from your own page: when you embed the Research Gallery or a single map with the JavaScript embed, put the language in its profile-config ("lang" works too). Set it again later and the map switches language live.

  <doxa-maps-spa profile-config='{"locale":"ar"}'></doxa-maps-spa>
  

• Without either, a map follows the page's own language (<html lang>, which WordPress sets), and otherwise shows English.

• Right to left: in Arabic the map's layout mirrors — the Research Gallery's tab rail moves to the right. Set through profile-config, only the map's own box mirrors; the rest of your page is left alone. A ?lang=ar address mirrors the whole page, which is what a map's own page wants.

• Where the words live: library/i18n/locales/<code>/, one folder per language. Adding a language: documentation/architecture/i18n.md.

---

Build it with an agent swarm

Many AI agents can build many plugins at once without breaking each other's work. Every plugin has one agent that owns it, and changes are added to development, the shared working version, one at a time. main is the production version: it moves only when you publish a release.

Bring your own harness. dx-maps works with whatever AI coding agent or agent harness you already use. The repo gives you the branch strategy below, the checks (bun run gates:pre) and the Plugin Studio; it does not ship a harness. Roles such as a coordinator that puts the landings in order, or a gate-keeper that reads each change before it lands, are jobs your harness gives to its agents.

_{Open the diagram full size: on a phone its small text needs it.}

Set up the branch strategy

1. main is production. It moves only when you publish a release (step 7).
2. development is the shared working branch. Create it once, from main:

   git fetch origin && git switch -c development origin/main && git push -u origin development
   

3. One branch and worktree per plugin agent, from origin/development, then install once in each:

   git worktree add -b regions/work ../dx-maps-regions origin/development
   git worktree add -b upg100/work  ../dx-maps-upg100  origin/development
   cd ../dx-maps-regions && bun install --frozen-lockfile
   

4. One preview server per agent, each on its own port:

   bun x vite --port 5301 --strictPort    # the next agent uses 5302, and so on
   

5. Land one at a time, through a lock. Catch up with development, run the checks, and push only if nothing fails (gates:pre exits non-zero when a check fails, so the push never runs then):

   flock /tmp/dx-maps-development.lock sh -c '
     git fetch origin && git rebase origin/development &&
     bun run gates:pre && git push origin HEAD:development'
   

   flock guards one machine. Agents on several machines need a shared lock, such as one your harness provides.
6. One agent owns the full build; the others build only their own plugin:

   BUILD_ALLOW=1 bun run build                                          # the build owner: every plugin
   BUNDLE=<name> bun x vite build && bun run tree && bun run fix:sri    # everyone else: one plugin
   

7. Release: fast-forward main to a development commit that passed the checks, tag it, and deploy from the tag:

   git fetch origin && git switch main && git merge --ff-only origin/main
   git merge --ff-only <development-commit>   # a commit that passed the checks
   bun run gates:pre                          # the checks must pass on exactly this commit
   git tag -a v1.0.0 -m "Release v1.0.0" && git push origin main v1.0.0
   

   The tag's public/dx-maps/ folder is the built site: deploy that (how to deploy).

How to contribute, and the bar for shared code: documentation/CONTRIBUTING.md. Taking contributions from a contributor's own forge into your GitHub repository: documentation/contribute/TUTORIAL.md. Diagram source: delegation-model.svg.

What problem does this solve? (in plain words)

All the maps here share one project, one library and one build step. That's what makes them work together, and it's also the danger: if one agent's change breaks the shared library, every map breaks at once. And when several agents work in the same project at the same time, they step on each other — two agents edit the same file, one change quietly erases another, or half-finished work lands in the version everyone else is using.

So the project works like a busy kitchen:

1. Each agent works in its own branch and copy of the project — its own counter, so nobody bumps anybody. One owner per plugin, and one per shared file.
2. Only one change lands at a time. Whoever holds the landing lock first catches up with everyone else's latest work, fixes any clash itself and runs every check; the change goes into development only if nothing fails. development always works.
3. Someone keeps order. A coordinator can put the landings in order, and a gate-keeper can read each change by its content before it lands. Your harness gives these jobs to its agents.
4. main moves only when you publish a release, after the checks pass on that exact version. A preview can follow development; the published site follows main.

That's how many plugins get built at the same time, in one project, without the maps breaking.

The words, if you're new to git

Word	In plain terms
repo	the project folder, with its full history
development	the shared working version: every agent's change is added here, one at a time
main	the production version: it moves only when development is published
worktree	a private copy of the project for one agent to work in
merge conflict	two changes touched the same lines; someone has to decide how to combine them
rebase	catching your work up with everyone else's latest before adding it
landing lock	only one change lands on development at a time; its holder catches up and runs every check first
tag	a fixed name for one release commit, such as v1.0.0, so you can always deploy exactly it

---

The Plugin Studio — ★ where you work

Every plugin in one place, sorted by capability. Pick any plugin to run it live, fold open the plugins inside it, and copy its embed code. Tell your agent which plugins to group, and it builds a higher-capability plugin from them — that's how the Research Gallery was built.

Get it running

You need git, Bun and Node ≥ 18. The maps draw with the keyless MapLibre engine by default; for Mapbox, add a free Mapbox public token (it starts with pk.) and choose "provider": "mapbox" (see No Mapbox token? below). For Rudder's voice engine, also Go 1.22+, then run bash backend/rudder-engine/setup-runtime.sh once; without Go, everything except voice works.

git clone --depth 1 <your-repo-url>   # latest code only: seconds, not hundreds of MB of history
cd doxa-maps
bun install --frozen-lockfile
cp .env.example .env.local      # optional: paste your pk. token after VITE_MAPBOX_TOKEN= (.env works too; .env.local wins)
bun run dev                     # → open the URL Vite prints: that page is the Plugin Studio

No build needed first — the built maps are already in the repo. bun run dev also starts a local PocketBase on port 8090 for the plugins that use a backend; it is downloaded on the first run (if 8090 is taken, set DX_PB_PORT to any free port in .env.local and restart bun run dev). To start a plugin, copy plugin-designs/template-bundle/ to plugin-designs/<your-map>/; the studio finds it automatically. Then rename it as its own README.md says. Each plugin also has its own page while bun run dev runs, at /__leaf/<plugin>/<profile> (for example /__leaf/all-people-groups/all-people-groups), and the Studio's list of plugins is /__plugin-gallery/manifest.json.

To put the maps on your own site, take the easiest path: drop-in.

Make changes to the studio itself

The studio is a plugin like any other: plugin-designs/plugin-studio/plugin-studio.vue.

1. Run bun run dev and open the URL Vite prints (http://127.0.0.1:5173/ unless that port is taken) — that page is the studio.

2. Edit plugin-studio.vue (or ask your agent to). The page updates as you save.

3. When it looks right, build just the studio and refresh its security hashes:

   BUNDLE=plugin-studio bun x vite build
   bun run fix:sri
   

4. Check it opens every plugin, with bun run dev running: bun run smoke:studio -- --url <the URL Vite printed>. It drives a headless browser (Playwright's Chromium).

No Mapbox token? And other map settings

• No token: nothing to do. Every map draws with MapLibre by default, which needs no key. Mapbox is an explicit choice: "provider": "mapbox" on a plugin (or ?provider=mapbox on a map's page), plus a token.
• Built pages take a token from ?tk=pk.… in the address, from a token you paste once into the page, or from a token endpoint.
• Every command and prerequisite, per deployment method: documentation/README-SECTION-3-cli-commands.md.

Command	What it does
bun run dev	The Plugin Studio, updating as you save, at the URL Vite prints
BUNDLE=<name> bun x vite build	Build one plugin only
BUILD_ALLOW=1 bun run build	Build everything into public/dx-maps/ (~4 min; refuses without the flag, to protect a shared project)
bun run serve	Serve the built output folder — the Plugin Studio is http://localhost:4173/dx-maps/index.html (PORT=<n> bun run serve if 4173 is taken)
bun run gates:pre · bun run gates:post	The checks that keep main working
bun run shots	Retake these screenshots (ONLY=<name> for one)

Run it in the cloud

One shared dev server for the whole team, no laptop setup. A container clones the repo, follows development, and hot-reloads every change an agent lands, so everyone sees the Plugin Studio update in their browser within seconds, with no rebuild. Add OIDC settings and it puts a "Sign in with your provider" page in front of everything, open only to the groups you allow. Recipe and settings: deployment/cloud/. Working from your own laptop alongside the team (zero config, everything local by default): documentation/HOWTO-join-the-table.md. The three ways dx-maps ships (a drop-in into your own site, the container on its own subdomain, or the public Plugin Studio): the three routes and documentation/DEPLOY.md.

Cloud development environment

Your laptop can follow what agents land somewhere else. By default bun run dev is fully local: no settings, nothing fetched, and only your own edits hot-reload. To also see what agents push to a shared branch (an agent on a server, or the whole team), add two lines to .env.local (gitignored):

DX_SYNC_REMOTE=origin          # a remote name or a repo URL; a private repo uses your usual git credentials
DX_SYNC_BRANCH=development     # the default: your team's shared branch (the public repo has only main)

Every few seconds the dev server fetches that branch, fast-forwards your checkout and hot-reloads what changed. It never merges over your work: it pulls only when you are on that branch with no edits and no local commits, and otherwise waits and says "development is N commits ahead".

If your own agents also edit this checkout, the sync stops following, and the landings you haven't pulled pile up. Push small and often: a day of local commits against a day of landings is a merge conflict waiting to happen. Details: documentation/CLOUD-DEVELOPMENT-ENVIRONMENT.md.

---

Repository layout

doxa-maps/
├── plugin-designs/            YOUR maps — one folder per plugin (the free zone)
│   ├── doxa-maps-spa/         the Research Gallery (capability 5)
│   ├── plugin-studio/         the Plugin Studio (capability 5)
│   ├── my-upg-100-list/       UPG-100 List (capability 4)
│   ├── doxa-simple-map/       Prayer Progress and its presets (capability 2)
│   ├── all-people-groups/     a single map (capability 1)
│   └── template-bundle/       copy this to start a new plugin
│       ├── template-map-a.vue     the map itself
│       ├── index.js               registers its HTML tag
│       ├── index.html             a preview page
│       └── src/                   private pieces only this plugin uses
├── library/                   the SHARED toolkit, imported as @map (the high bar)
│   ├── layouts/               VerticalTabsLayout, StackLayout — how composites compose
│   ├── components/            legends, map controls, search, posters, detail panels
│   ├── composables/           map instance, data, layers, shared helpers
│   ├── colors/ styles/        colour strategies and the house style
│   ├── i18n/locales/          the 11 languages
│   └── data/ api/             lookup tables and data sources
├── public/dx-maps/          the BUILD OUTPUT — the drop-anywhere folder + manifest.json
├── deployment/                mobile (Capacitor) · WordPress · desktop (Tauri)
├── internal/                  the build and its checks
└── documentation/             tutorial · how-to · reference · architecture

Where your code goes — a plugin, or the shared library?

• Write your app in plugin-designs/<your-map>/. On the build step it becomes its own plugin in the output folder — its own embeddable app. Nothing you do there can break anyone else's map.
• Only put something in library/ if it is genuinely reusable and parameterized — built so other maps can use it with their own settings. The library is shared by every map, so every edit there can break every map: it is a high bar. Keep anything specific to one map inside that map's own folder.
• The full contribution guide: documentation/CONTRIBUTING.md · every reusable piece you can import: documentation/reference-library-index.md.

Maps should be open source, run everywhere, and multiply. One build makes each map a self-contained file for your site, your partners' sites and a phone. The Plugin Studio is where you compose them into something bigger.

---

Acknowledgements

dx-maps stands on the work of open-source communities: Vue, Vite, MapLibre GL JS, Pinia, Vue I18n, Capacitor, Tauri, oauth2-proxy, NeMo-Speech.cpp with NVIDIA's open Nemotron speech model, and the map data of OpenStreetMap contributors served by OpenFreeMap. Thank you.