History

doxa-maps-88655c70 9dc4dda8cf Some checks are pending build-gate / build (push) Waiting to run Details consolidate docs into documentation/ and deployment shells into deployment/ Driver 2026-09-21: 'a folder called deployment which will store the capacitor folder, wordpress folder and tauri folder', and 'a folder called documentation to store the contributing folder so docs are in one place'. docs/ + contributing/ + CONTRIBUTING.md -> documentation/ (three doc homes into one). capacitor/ + wordpress/ + src-tauri/ -> deployment/. The public/ -> dist/ rename the Driver asked about is NOT here: after seeing the measured blast radius (855 tracked files, 54 source refs, and public/ is the served web-root four consumers point at) the Driver withdrew it - 'keep the public folder the same'. Path references were rewritten mechanically (258 across 87 files), but three classes needed hand fixes because a prefix regex cannot see them: - join(ROOT,'docs',...) in 10 internal scripts - a quoted SEGMENT, not a prefix - tauri frontendDist '../public' -> '../../public', since src-tauri is now one level deeper; check:tauri caught this exactly as the card predicted - the WordPress contract test's dirname(__DIR__,2) -> 3, same reason Also reverted one over-reach: the rewrite renamed a FINDING-CATEGORY label 'docs' in public-hygiene-check.mjs, which is a rule name in its own header, not a path. Verified: full build ALL GUARDS PASS, SRI consistent; check:tauri, check:mobile (cap sync + webDir OK), check:wp-embed, quoted-scripts, capability-citations, capability-exemplars, library-index, public-hygiene, parse and drop all pass.		2026-09-21 23:23:23 +00:00
..
locales	Phones: the search bar sits in its own header band; the share menu is titled Share and shows its content without scrolling	2026-09-16 23:02:09 -05:00
index.js	consolidate docs into documentation/ and deployment shells into deployment/	2026-09-21 23:23:23 +00:00
README.md	consolidate docs into documentation/ and deployment shells into deployment/	2026-09-21 23:23:23 +00:00

README.md

library/i18n/ — the map's translations

One of the three customization seams (colors/, api/, i18n/). This one owns every user-facing string. Translations are one folder per locale, one JSON file per area, inlined at build time into a Vue I18n instance (one per <doxa-map>, so embeds don't bleed state).

  i18n/
  ┌───────────────────────────────┐
  │ index.js   ← engine, don't edit │
  │ locales/                        │
  │   en/  buttons.json legend.json …│  ← en is the source of truth + fallback
  │   es/ ar/ zh/ …  (same keys)     │  ← 11 shipped locales, drop in your own
  └───────────────────────────────┘
     filename → namespace:  buttons.json → $t('buttons.prayForThem')

11 shipped locales; ar renders right-to-left (RTL_LOCALES).
Add a language by copying locales/en/ to locales/<code>/ — never by editing index.js (except adding the code to SUPPORTED_LOCALES).
Missing keys fall back to English silently.

Adding or overriding a locale? The full contract (locale matrix, checklist, integration) is in ../../documentation/architecture/i18n.md.