674d56559a
repo END-REPO-PBDOC: the Driver's decision went live and REVERSED their earlier instruction to me. When I first wrote this section repo said to leave DX_PB_URL out entirely, because it sat behind the team sign-in and failed from a laptop. It is now the TEAM DEFAULT, and the local database is the fallback. So the section is rewritten rather than appended to: a joiner is now told to set DX_PB_URL=https://<your team's dev server>/pb, that they sign in with the same team account and there is no separate password, and that leaving it unset still gives them a private local one — which is a fine way to start. Placeholder host in the public text, not ours. ⚠ THE OPENING LINE WAS QUIETLY WRONG AFTER THE CHANGE and I nearly left it. "There are three databases and you only ever touch one" was true when the local one was the only option a joiner had; now they touch the shared one OR a local one depending on one env line. The claim that actually matters — and is still exactly true — is that they never touch the third. Now reads "You work against one of the first two — never the third." A sentence can survive an edit around it and stop being true without looking any different. Added the detail repo gave that a reader needs and would not guess: new collections start LOCKED until a migration opens them, deliberately, so nothing is public by accident. That reinforces the schema-as-commits point the section already makes rather than sitting beside it. Names unchanged and re-verified: DX_PB_URL points at the PocketBase root (.../pb), DX_PB_PORT for the port-in-use case. No internal hostnames anywhere in the file. |
||
|---|---|---|
| .. | ||
| architecture | ||
| assets | ||
| contributing | ||
| needs-eyes | ||
| readme-images | ||
| screenshots | ||
| CONTRIBUTING.md | ||
| develop-a-plugin-and-see-it-live.md | ||
| explanation.md | ||
| how-to.md | ||
| HOWTO-join-the-table.md | ||
| PRESET-PLUGIN-STANDARD.md | ||
| README-embed-example.md | ||
| README-embed-gospel-resources.md | ||
| README-SECTION-3-cli-commands.md | ||
| README.md | ||
| reference-capability-exemplars.md | ||
| reference-library-index.md | ||
| reference-universal-props.md | ||
| reference.md | ||
| tutorial.md | ||
| vendored-font-noto-serif-devanagari.md | ||
| why.md | ||
documentation/ — pick your path
"what is this?" "teach me" "how do I …?" "look it up" "all the detail"
│ │ │ │ │
why.md ──────────► tutorial.md ────► how-to.md ────► reference.md ───► architecture/
(2 min, 1 diagram) (first map) (task recipes) (tables) (contracts)
- why.md — the problem and the "map islands" idea. Start here.
- tutorial.md — build your first map, no jargon.
- how-to.md — recipes: embed, iframe, SPA, colors, CDN, mobile, tokens.
- reference.md — config fields, build scripts, the
profile-configcontract. - explanation.md — the model in 15 lines.
- architecture/ — the deep end: full contracts, the per-file catalog.
- README-embed-example.md — the drop-in README used when this bundler is embedded inside a host repo.
- README-embed-gospel-resources.md — the gospel map's URL contract for partner embeds: bring your own ISO 639-3 list, one country, one group, or the zero-access view.
Working on the repo:
- develop-a-plugin-and-see-it-live.md — ★ the golden path: zero to a plugin live, in 6 steps.
- README-SECTION-3-cli-commands.md — every command, per deployment method, with prerequisites.
- reference-capability-exemplars.md — which bundle is at which capability tier (generated).
- reference-library-index.md — the reusable
library/pieces you can import (generated). - CONTRIBUTING.md and contributing/ — how to contribute, and the bar for
library/.
Nothing on the simple path is longer than a few minutes; everything complex lives in
architecture/, linked from where you'd need it.