gospel-internet was running the same point-in-polygon over the same two geometry files and refusing to write unless its per-province counts matched this table's — which is good discipline and should not be necessary. The assignment ships now: one row per placed group, 1,005 of them, with the language code, population and tier. The two files are reconciled BEFORE either is written — per-province counts and the assigned total must agree or the build refuses — because they are published separately (the map fetches only the aggregate, lazily, and has no use for a thousand rows) and separate files can drift. The failing direction of that guard is not proven, only the passing one: 46 provinces agree, 1,005 = 1,005. |
||
|---|---|---|
| .. | ||
| 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.