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
..
api	consolidate docs into documentation/ and deployment shells into deployment/	2026-09-21 23:23:23 +00:00
colors	consolidate docs into documentation/ and deployment shells into deployment/	2026-09-21 23:23:23 +00:00
components	consolidate docs into documentation/ and deployment shells into deployment/	2026-09-21 23:23:23 +00:00
composables	consolidate docs into documentation/ and deployment shells into deployment/	2026-09-21 23:23:23 +00:00
utils	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

src/ — this map's sandbox

Everything this map needs that isn't already in the shared library/ gets built here. Nothing in this folder leaks to another map — build freely.

src/
├── api/          which API/CSV/endpoint this map reads
├── colors/       this map's colors: values (colors.json) + strategy .js files
├── components/   this map's own .vue pieces (not reusable)
├── composables/  this map's own logic hooks (useThing.js)
└── utils/        this map's own pure helpers

Two import styles, two meanings:

import { useMapInstance } from '@map/composables/useMapInstance.js'  // reuse the shared library
import colors             from './src/colors/colors.json'            // your own sandbox (relative)

There is no @map/-style alias for your sandbox — your code is always relative. That boundary keeps it private. Reusable + parameterized → library/ (an expert move); specific to this map → stays here. Local by default.

Each subfolder has its own README. See also: ../../README.md (authoring guide) · ../../../documentation/reference.md (the @map/… menu).