doxa-maps

History

Doxa Maps 457d16e708 A map's own ? can ask its host for help: HelpButton and useHostedHelp send doxa:help The Experimental maps' explainer lived in a "?" floating at the top centre of the app, which read as a game piece rather than part of the map. The map already has a "?" control. This lets that control answer from the HOST: a click dispatches doxa:help, bubbling and composed, so it crosses every shadow root between the button and the page, and the app answers with the map's text. library/composables/useHostedHelp.js is the one mechanism, for the HelpButton map control and for the maps whose "?" belongs in their own bar. It also decides WHERE the button shows: only under a host that answers (an ancestor, across shadow roots, carrying data-doxa-help), so the same bundle embedded on a partner page shows no dead "?". HelpButton keeps its open-help emit, so doxa-simple-map's own help popup is unchanged; hosted is opt-in.		2026-09-29 02:35:35 +00:00
..
FullscreenButton.vue	A lazy view that fails to load says so and offers Retry; map controls carry data-control	2026-09-28 11:42:54 +00:00
GeocoderComponent.vue	Every animating library component now honours prefers-reduced-motion itself	2026-09-29 01:38:07 +00:00
HamburgerButton.vue	Every animating library component now honours prefers-reduced-motion itself	2026-09-29 01:38:07 +00:00
HelpButton.vue	A map's own ? can ask its host for help: HelpButton and useHostedHelp send doxa:help	2026-09-29 02:35:35 +00:00
index.js	doxa-maps — portable bundler for embeddable JAMstack maps	2026-09-10 01:53:07 +00:00
LocationButton.vue	A lazy view that fails to load says so and offers Retry; map controls carry data-control	2026-09-28 11:42:54 +00:00
MapControlButton.vue	Every animating library component now honours prefers-reduced-motion itself	2026-09-29 01:38:07 +00:00
MapControlMenu.vue	Every animating library component now honours prefers-reduced-motion itself	2026-09-29 01:38:07 +00:00
MapToolbar.vue	The map controls and the pin hint printed; the attribution stays	2026-09-28 21:59:29 +00:00
README.md	consolidate docs into documentation/ and deployment shells into deployment/	2026-09-21 23:23:23 +00:00
ShareButton.vue	A lazy view that fails to load says so and offers Retry; map controls carry data-control	2026-09-28 11:42:54 +00:00
ThemeToggleButton.vue	A lazy view that fails to load says so and offers Retry; map controls carry data-control	2026-09-28 11:42:54 +00:00
ZoomInButton.vue	A lazy view that fails to load says so and offers Retry; map controls carry data-control	2026-09-28 11:42:54 +00:00
ZoomOutButton.vue	A lazy view that fails to load says so and offers Retry; map controls carry data-control	2026-09-28 11:42:54 +00:00

README.md

Each file is a single, focused button or input that mounts inside the map's control area. Replaces the older monolithic MapControlsComponent.vue.

  MapToolbar.vue  (container)
   ├─ ZoomInButton · ZoomOutButton · LocationButton
   ├─ FullscreenButton · HamburgerButton · ThemeToggleButton
   ├─ HelpButton · ShareButton
   └─ GeocoderComponent   (all built on MapControlButton.vue)

Every button takes a size prop (sm | md | lg) and follows the MapControlButton shape.
Click handlers go through inject('mapStore') or getMap() — never a captured Mapbox instance.
To add one: copy ZoomInButton.vue and register it in MapToolbar.vue.

Full conventions + catalog: ../../../documentation/architecture/components.md.

README.md

library/components/map-controls/ — toolbar buttons