The legend was stacked below the chart in a centred column. On its own it is taller than the pane — a 360px card with a nine-cell grid and four footer lines — so the figure was pushed out of view entirely and the panel overflowed its host: the legend covered the row beneath it and the caption drew over the page tabs. The chart was not visible at all at 1440x900. It is now a row: figure left, legend right, which is also the side placement the legend was asked for. Every flex child takes min-height and min-width 0, because a flex item's default minimum is its content size — without that an item never shrinks below its natural height and the container overflows however little room it has. That default is what turned a tall card into an unbounded one. Under 900px it returns to a column and scrolls rather than clipping. Both charts now clear the centre tab strip, which is absolutely positioned near the top and was covering the top of the bounded set's dots and all of the centered set's caption. The bounded set also takes overflow:hidden, so a tall caption can never do to it what the legend did to its neighbour. Nothing about the counts changes. The page reads 2,082 placed where a slug-only join predicts 2,074: the difference is the name-and-country fallback recovering eight of the sixteen groups the neighbour table carries no slug for, and both readings still sum to the full 2,107. |
||
|---|---|---|
| .. | ||
| 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: 24 plugin bundles and 36 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.