History

Doxa Maps bfc99ff827 library/ keeps the reason and drops the speaker: no comment quotes or cites the Driver Every reference to the Driver in library/ is reworded: the engineering reason stays, the speaker and the quote go, and a decision still open reads "provisional, pending a product decision". Comments only: each changed file is identical after stripping comments (JavaScript, template and CSS, including CSS comments inside the style strings shadow-DOM components inject). Those style-string comments do ship, so several bundles change by exactly those comment bytes.		2026-09-29 05:26:25 +00:00
..
_registry.js	Complete app-profiles->plugin-designs sweep across comments/docs; build green; layouts kept at root (load-bearing)	2026-09-17 18:18:19 +00:00
adoption.js	Research tabs read at 15px; the status red is a step brighter	2026-09-17 02:38:38 -05:00
affinity-block.js	C1a: the affinity-block and doxa-region palettes move to library/colors/	2026-09-26 08:39:53 +00:00
doxa-region.js	C1a: the affinity-block and doxa-region palettes move to library/colors/	2026-09-26 08:39:53 +00:00
engagement.js	Research tabs read at 15px; the status red is a step brighter	2026-09-17 02:38:38 -05:00
language-family.js	Land the swarm's dashboard work: colour, rails, cascade, scroll	2026-09-22 18:57:39 +00:00
prayer-progress.js	Research tabs read at 15px; the status red is a step brighter	2026-09-17 02:38:38 -05:00
README.md	consolidate docs into documentation/ and deployment shells into deployment/	2026-09-21 23:23:23 +00:00
religion.js	The legends mirror now, and their labels never became their values	2026-09-26 22:06:58 +00:00
resource.js	C1b: the resource palette moves to library/colors/, and the local colour globs go with it	2026-09-26 08:51:39 +00:00
wagf-region.js	library/ keeps the reason and drops the speaker: no comment quotes or cites the Driver	2026-09-29 05:26:25 +00:00

README.md

library/colors/ — how pins get colored

Each file here is one color strategy — a way to color the map's pins (by language family, prayer progress, religion, …). Drop a <name>.js in and it's auto-discovered; no registration.

  library/colors/                        a map picks a mode
  ┌──────────────────────────┐           ┌───────────────────────┐
  │ language-family.js        │           │ getColorStrategy(      │
  │ prayer-progress.js        │──auto───► │   'language-family')    │──► colored pins
  │ religion.js   engagement.js│  glob     │                        │
  │ _registry.js (the scanner)│           └───────────────────────┘
  └──────────────────────────┘
        shared set                  a single map can add/override its own in
                                    plugin-designs/<map>/src/colors/ (that map only)

Shared here = reused by every map. Your map's own color → put it in your bundle's src/colors/ (it merges over the shared set, for your map only — never edit the library to recolor one map).
Filename = mode key (prayer-progress.js → prayerProgress). Files starting with _/. are skipped.

Writing or overriding a strategy? The full contract (required exports, legend wiring, checklist) is in ../../documentation/architecture/color-strategies.md.