History

Doxa Maps 308e1e82ab The joining page opens with the promise the setup actually keeps repo's zero-config .env.example is on main (`8c529c031`), verified before writing about it: every DX_* and VITE_* line is present and empty, empty meaning the local default. That is the follow-up patch I held back rather than documenting a file whose contents had not landed. "Every line in it is optional" is a better opening than the list I had, because it IS the zero-config promise in five words — a reader who copies the file and fills in nothing has a working setup, which is exactly what the Driver asked the default to be. Also states what happens if the Mapbox token is left empty: the Mapbox-backed maps do not draw, and the keyless MapLibre provider is the alternative. My previous wording implied the token was required to get anywhere, which is not true and is discouraging at exactly the wrong moment.		2026-09-28 01:46:52 +00:00
..
architecture	Decouple prose: no go-base / nuxtbase / nuxtinator / doxa-base names in plugin comments and docs	2026-09-26 17:28:45 +00:00
assets	consolidate docs into documentation/ and deployment shells into deployment/	2026-09-21 23:23:23 +00:00
contributing	README: lead with the objectives, showcase the Research Gallery, teach the agent swarm	2026-09-24 18:34:02 +00:00
needs-eyes	The partner-embed check becomes something a person can open	2026-09-26 00:47:12 +00:00
readme-images	README shots: retake the 3 stale shots on `b37138d7`	2026-09-27 09:58:51 +00:00
screenshots	consolidate docs into documentation/ and deployment shells into deployment/	2026-09-21 23:23:23 +00:00
CLOUD-DEVELOPMENT-ENVIRONMENT.md	The advanced page: working when your agent lives on a server	2026-09-28 01:12:43 +00:00
CONTRIBUTING.md	README: three outputs, not five methods; a Languages section; screenshot gates see every shot again	2026-09-25 19:40:03 +00:00
develop-a-plugin-and-see-it-live.md	README: three outputs, not five methods; a Languages section; screenshot gates see every shot again	2026-09-25 19:40:03 +00:00
explanation.md	consolidate docs into documentation/ and deployment shells into deployment/	2026-09-21 23:23:23 +00:00
how-to.md	Decouple prose: no go-base / nuxtbase / nuxtinator / doxa-base names in plugin comments and docs	2026-09-26 17:28:45 +00:00
HOWTO-join-the-table.md	The joining page opens with the promise the setup actually keeps	2026-09-28 01:46:52 +00:00
PRESET-PLUGIN-STANDARD.md	Capability is derived from what a plugin composes, and the preset-plugin standard is written down	2026-09-27 23:14:15 +00:00
README-embed-example.md	consolidate docs into documentation/ and deployment shells into deployment/	2026-09-21 23:23:23 +00:00
README-embed-gospel-resources.md	The map learned to name peoples, not just their languages	2026-09-27 02:40:12 +00:00
README-SECTION-3-cli-commands.md	Docs: an iframe updates itself; a script embed's integrity hash pins the bytes, so re-copy it after each release	2026-09-26 02:07:14 +00:00
README.md	The embed contract, written down for partners	2026-09-26 17:24:55 +00:00
reference-capability-exemplars.md	Rename the output folder to dx-maps	2026-09-25 19:26:14 +00:00
reference-library-index.md	A filtered table becomes a link anyone can open, and the link now carries the typed search	2026-09-27 18:25:01 +00:00
reference-universal-props.md	List names speak the reader's language: listLabel and listDefinition	2026-09-26 08:39:52 +00:00
reference.md	README: three outputs, not five methods; a Languages section; screenshot gates see every shot again	2026-09-25 19:40:03 +00:00
tutorial.md	Docs: every build line a reader copies now carries BUILD_ALLOW=1	2026-09-25 03:07:52 +00:00
vendored-font-noto-serif-devanagari.md	Move the vendored font's README out of the served folder	2026-09-24 04:15:26 +00:00
why.md	consolidate docs into documentation/ and deployment shells into deployment/	2026-09-21 23:23:23 +00:00

README.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-config contract.
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.