History

Nath fc4d6228f8 feat: sync arabic translation		2026-09-25 11:34:14 +01:00
..
app-profiles	hide adoption UI and add country links to pray cards	2026-06-24 16:13:34 +01:00
docs	Set up home, prayer, adopt and research maps	2026-05-21 03:45:15 -05:00
src	feat: sync arabic translation	2026-09-25 11:34:14 +01:00
.env.example	Set up home, prayer, adopt and research maps	2026-05-21 03:45:15 -05:00
.gitignore	Maps: Fly, share, bug fixes (#8 )	2026-05-28 10:13:51 -05:00
index.html	Set up home, prayer, adopt and research maps	2026-05-21 03:45:15 -05:00
package.json	Set up home, prayer, adopt and research maps	2026-05-21 03:45:15 -05:00
README.md	Maps: Fly, share, bug fixes (#8 )	2026-05-28 10:13:51 -05:00
vite.config.js	Set up home, prayer, adopt and research maps	2026-05-21 03:45:15 -05:00

README.md

1040-maps

A Vite-powered monorepo + map forge for building embeddable Mapbox MFE bundles. Named after the 10/40 window — the geographic frame most of these maps serve.

What it is

One repo. One library (packages/map-core). N bundles (one per app-profiles/<bundle>/ folder). npm run build emits one IIFE per bundle into app/.

Why it exists

Replaces the clone-the-template-then-edit pattern. Every map app that previously was its own MFE repo (cloning template/src/ and drifting) gets refactored into 1040-maps once, then re-output as its own bundle. Edits to SemanticTreeLegend, colorStrategies, etc., happen once in packages/map-core/ and propagate to every bundle on next build.

Layout

1040-maps/
├── packages/map-core/        ← shared library: components, composables, config, utils
├── app-profiles/<bundle>/    ← bundle source folders (committed)
│   ├── index.js              ← bundle entry — imports profiles + registers web component
│   └── profiles/             ← 1..N .vue files
├── app/                      ← build outputs (gitignored)
└── vite.config.js            ← multi-entry: discovers app-profiles/<bundle>/ folders

Convention: folder = bundle

A subfolder of app-profiles/ IS a bundle. Folder name = bundle name. npm run build discovers them at build time, no manual entry list needed.

Three profile patterns supported

Individual — single .vue profile per bundle (simplest)
Parameterized — one profile, behavior driven by profile-config.tabs[] props at runtime
Nested — one profile internally rendering others via tabs (workbench-style)

A single bundle can mix all three. Recursive composition allowed.

Quick start

npm install
npm run build      # builds every bundle in app-profiles/ → app/<name>.iife.js
npm run dev        # Vite dev server for live development

Adding a new bundle

mkdir -p app-profiles/my-new-map/profiles
# create app-profiles/my-new-map/index.js (entry)
# create app-profiles/my-new-map/profiles/*.vue
npm run build
# → app/my-new-map.iife.js appears

Migration plan

See the refactor ideation for the first refactor (doxa-simple-map-mfe → 1040-maps).