c46a9a04bd
Some checks are pending
build-gate / build (push) Waiting to run
- Opens with what dx-maps is for: seven objectives, each paired with the gate or section that proves it is met. - New Research Gallery section: the cap-5 app shell and the tree of cap-4..1 plugins it nests, each still independently embeddable. - Plugin Studio: clone main (the old branch was 198 commits behind), a command table, and a fresh studio screenshot (the old one showed a retired nav and tofu icons). - Agent swarm: renamed to industry terms (trunk-based development, merge queue, maintainer), a laptop recipe (worktrees, strict ports, one builder, flock as the queue), and a redrawn diagram whose inner ring is an actual queue with one gate. SVG source committed next to the PNG. - MapLibre is now described as it is: a one-prop, token-free engine. - Removed internal credential/push instructions (AGENT-BRIEF.md covers agents). - documentation/: fixed 19 dead links left by the docs/ move, removed internal references, and listed the working docs in the index. - readme-shots: ONLY=<name> retakes a single image. |
||
|---|---|---|
| .. | ||
| COLORS.md | ||
| README.md | ||
| staging-reference-design.html | ||
Contributing to doxa-maps
Welcome. You want to help build maps — edit colors, add a map, tune a legend — without
learning the whole architecture first. This folder is the contributor entry point; the
full guides live in the documentation/ set and are linked below, so nothing here goes stale by
being duplicated.
The one rule that keeps everything clean
Parameterized + genuinely reused by more than one map → the shared library (
library/, alias@map). Not reused → it lives in your app-profile folder (plugin-designs/<your-map>/).
"Local by default, promote deliberately." When in doubt, keep your change local to your
own map; something graduates into the shared library only once a second map genuinely
needs it. Full reasoning — the promotion / orphan-audit rule — is in
../documentation/explanation.md.
Start here
| You want to… | Read |
|---|---|
| Understand the whole picture (one library, many bundles, no rebuild) | ../README.md · ../documentation/explanation.md |
| Learn step-by-step with no jargon (non-coders welcome) | ../documentation/tutorial.md |
| Do a task (add a map, embed, change colors, pick a CDN) | ../documentation/how-to.md |
| Look something up (file map, config fields, library index) | ../documentation/reference.md |
| Understand build-vs-dev + partner-site embedding | ../documentation/CONTRIBUTING.md |
| Edit or add colors (the two places a color can live) | COLORS.md |
Colors live here
COLORS.md is the beginner deep-dive on the two places a color strategy
can live — the shared library/colors/ set vs your bundle's private
plugin-designs/<bundle>/src/colors/ — and how the filename decides override-vs-add. The
strategy contract (the required export default shape) is in
../library/colors/README.md.