README: lead with the story — one sign-up site is the bottleneck, the map embeds on every partner team's site, Training-for-Trainers roles, the share-button campaign, private CRM for the team list

README.md

@@ -1,4 +1,52 @@
-# doxa-maps — a JAMstack map bundler for vibe coders
+# doxa-maps — prayer maps that embed everywhere
+
+> **Bottom line up front.** A global prayer movement stalls when there is only **one** website where people
+> can see the task and sign up — today that plateau sits at roughly 600–1,000 people groups covered. The fix is
+> not a better single website. It is a map that lives on **thousands** of partner-team websites at once, shows
+> the prayer task clearly, changes as people sign up, and carries a **Share** button so every team that receives
+> it can pass it on. This bundler builds that map — and every other map you need — as one embeddable file each.
+
+## Why embed, not link
+
+One sign-up site is a bottleneck. A map embedded on a partner team's *own* site multiplies three surfaces at
+once: the **prayer surface** (more people see the task), the **information surface** and the **understanding
+surface**. And a team that has the map on its own site treats it as its own — ownership becomes stewardship.
+Sign-up can still happen in one place; the *map* does not have to.
+
+## What this trains you to be (Training for Trainers)
+
+We borrow the language of **Training for Trainers (T4T)** — Ying Kai's method, told in *T4T: A Discipleship
+Re-Revolution* (Steve Smith with Ying Kai, 2011; trainer resources at [t4tonline.org](https://t4tonline.org)):
+the goal is never one trained person, but trainers who train trainers. This README trains you to be three things:
+
+1. a **map maker** — you (with your AI agent) build maps on the shared library in this repo;
+2. a **map multiplier** — every map you build embeds anywhere and carries a Share button;
+3. a **prayer mobilizer** — you get the map onto the websites of every team you know that is trying to multiply
+   disciples among the unreached, and you train each of them to pass it on with the same button.
+
+## Run the campaign (learn by doing)
+
+1. **Build your partner-team list — privately.** Every team you know that has a website: the site, the contact,
+   who to call. This list is an **attack surface** — never a public spreadsheet. Keep it in a private, multiplayer
+   CRM such as [Disciple.Tools](https://disciple.tools) (open source: contacts, groups, phone numbers, websites —
+   shared with your mobilizers and no one else).
+2. **Open a map and press Share.** *Share Link* gives the map's own page; *Add to Your Website* gives the embed
+   code. Try it in the playground: `bun run dev`.
+3. **Paste it on the partner team's site.** Verified places a pasted embed works: WordPress (Custom HTML block),
+   Squarespace (Code block — iframes need a Business or Commerce plan), Wix (Add → Embed → HTML iframe),
+   Google Sites (Insert → Embed → By URL), Notion (`/embed` + the Share Link), and internal boards with an iframe
+   add-on (e.g. Trello's *Card Frames* Power-Up). Rule of thumb: anywhere that accepts an HTML snippet or a URL
+   embed, over https.
+4. **Train that team to press Share on their copy** — and to keep their own private team list. That is the whole
+   multiplication mechanism: the map travels team to team without coming back through you.
+5. **Watch the progress change on every copy.** All embeds read the same live data, so a sign-up anywhere shows
+   up everywhere.
+
+Full walkthrough: [docs/tutorial.md](./docs/tutorial.md). Everything below is for the people who build the maps.
+
+---
+
+## What the bundler is — a JAMstack map bundler for vibe coders
 
 > **Built by a vibe coder, for vibe coders** — and for map multipliers and prayer mobilizers who
 > want every people, in every place, prayed for by name.
@@ -108,7 +156,7 @@ New to this? Read this table first. You do **not** need to memorize it — just
 
 - **One build → many embeddable maps.** `bun run build` turns every map into a self‑contained web component
   *and* generates a standalone HTML page for each one.
-- **Embed anywhere.** Drop a map on your own site, a partner church's site, or WordPress — via an **iframe**
+- **Embed anywhere.** Drop a map on your own site, a partner team's site, or WordPress — via an **iframe**
   (safe and isolated) *or* via **shadow DOM** (the map's JavaScript runs directly in the page, for deep
   integration and advanced features).
 - **Compose maps into a single‑page app.** Put several maps into one layout — a whole multi‑map site — and it
@@ -259,7 +307,7 @@ Your map data has to come from somewhere. Common sources:
 
 You found some really cool maps on the internet, didn't you? On discipleship sites, maybe — maps that
 inspired you, that made you want to build your own. But the code wasn't available. Or if it was, it wasn't
-written to run on WordPress, or on your own site, or across your partner churches' websites. It wasn't
+written to run on WordPress, or on your own site, or across your partner teams' websites. It wasn't
 simple. It wasn't modular. It didn't work the way you needed it to.
 
 That was me too. That's why I built this framework. I love maps — I'm going to build maps until the day I

docs/why.md

@@ -2,7 +2,7 @@
 
 ## The problem
 
-You built a good map. Now ten partner organizations want it on *their* websites — one runs
+You built a good map. Now ten partner teams want it on *their* websites — one runs
 WordPress, one runs Nuxt, one is a plain landing page, one is a link-dashboard like Start.me.
 The usual answers are all bad: