9dc4dda8cf
Some checks are pending
build-gate / build (push) Waiting to run
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.
2.6 KiB
2.6 KiB
doxa-maps — slide deck outline (BLUF; hand-off pitch)
One slide = one gold nugget. Bottom line up front, then facets. Real product names named. Keep the itch words: JAMstack · SPA · embed on thousands of partner sites.
- Title — "doxa-maps — a JAMstack bundler for composable, embeddable-first maps." Sub: build once, embed on thousands of partner sites, or ship as an app. Authored agent-first.
- The bottom line (the whole pitch on one slide) — One build step outputs every map as a self-contained web component with its own HTML page → embed anywhere, compose into a single-page app, or wrap as iOS/Android. [pipeline diagram from README]
- The problem — 10 partner sites, 3 bad options (rebuild per site / iframe farm / framework lock-in). Change once → redo ten times.
- The answer: map islands — one file, drops in like an image, host needs no framework or build step. [hero diagram]
- One build, three products — embeds · SPA (the power app) · mobile. Same bundles.
- Proof it's portable (the WordPress story) — the whole site changed frameworks; the map moved with a few-line wrapper, zero refactor. Migration-proof by design.
- JAMstack = future-proof — front end moves anywhere; swap the back end (or map engine Mapbox↔MapLibre) with no rebuild. Live: partners get new maps on reload.
- Fast & lean — one inlined file (Vue+CSS), tree-shaken, one request; faster than Vue-CDN.
- The one rule (the entire learning curve) — non-reusable code stays in your app-profile; only proven components graduate to the shared library. Follow it → maps never break each other.
- Built for agents — connect your agent → dev server → staging of every map → feedback → one build. "Built by agentic engineers, for agentic engineers." (aka vibe coders.)
- The mission fit — prayer maps embedded on partner sites; MapLibre = token-free, no single point of failure across thousands of embeds; posters + prayer packets print from one codebase.
- Where it thrives (the pairing, not a dependency) — decoupled by design; pair with an internal developer platform (MCP onboarding, multi-tenant, CI/CD) and the multiplication compounds. Standalone today; exponential paired.
- The stack (name the real products) — Vite · Bun · Vue web components · MapLibre/Mapbox · Capacitor · Forgejo (source-control-as-CDN). No lock-in — un-closable primitives.
- Try it / take it — the repo, the docs (why → tutorial → how-to → reference → architecture), the live plugin gallery. Deep-dive: point your agent at documentation/architecture/.