The rows under "No resource found" carried a name, a language and a population and nothing else, so the question a mobiliser opens a country to answer — what do I do about these? — cost one click per group. 369 of the 370 groups with nothing have a way in, and it was reachable only by opening each pin in turn. Mali's two now read "way in: French"; Benin's one reads "way in: SUN (signed)". Text rather than a link, and it could not be otherwise: these rows are button drill-ins and HTML forbids an anchor inside a button — the parser hoists it out and it stops being a link, which is why the rows that DO have resources are plain containers instead. The row still opens the group sheet, and the sheet carries the bridge's real links. It names the bridge and claims nothing further. "Bambara" here does not say Bambara reaches this group; that stays the local question the sheet spells out. It turns a list of dead ends into a list with a first move against each one. |
||
|---|---|---|
| .. | ||
| dx-maps | ||
| README.md | ||
public/ — the built output
This folder is GENERATED by bun run build; do not edit it by hand. It holds exactly one thing:
dx-maps/— the output folder: 23 plugin bundles and 35 pages, self-contained. Copy this one folder to any web host (or open it from disk) and it works.dx-maps/index.html— the front page: the Plugin Studio, every plugin in one place.dx-maps/<plugin>/<plugin>.js— a plugin's bundle (a custom element; load it with a<script>tag).dx-maps/<plugin>/<page>/index.html— a ready-made page for one plugin view (embed it in an<iframe>).dx-maps/manifest.json— every plugin, page and embed snippet, machine-readable.dx-maps/assets/— the data, fonts and images the plugins fetch at runtime.
The folder's name comes from name in vite.doxa-maps-build-config.json. Sources live in
plugin-designs/, library/ and data/; rm -rf public/ && bun run build recreates all of this.