bb589d584e
Some checks are pending
build-gate / build (push) Waiting to run
Their heading face has no Cyrillic glyphs. That is why base/_globals.scss:35-44 switches every h1/h2/h3 to --font-family-cyrillic under [lang="ru-RU"], with letter-spacing -0.02em — without it a Russian heading leaves the family entirely and lands on whatever condensed system face the browser picks. We ship a `ru` locale and had neither the rule nor the font, so that is exactly what every Russian heading in this clone was doing. Four subsets vendored, Google's own unicode-range values carried verbatim so the browser fetches only what a heading needs: cyrillic 6700B and cyrillic-ext 7688B are the point, latin 12248B and latin-ext 11624B come too because a Russian heading routinely contains Latin characters — a country name, a figure, an ampersand — and a Cyrillic-only face drops those back to the fallback mid-word, which looks worse than not switching. Each file verified to begin with the wOF2 magic after download, because a fetch that returns an HTML error page also "succeeds" and a font that is really a 404 fails at render time with no network error left to find. Two things the rule needed beyond the font. [lang] cannot cross a shadow boundary, so the attribute has to be INSIDE the root for a selector in the root's own stylesheet to see it — our roots now carry :lang for the same reason they already carried :dir, and it is correct HTML besides. And the selector accepts both `ru` and `ru-RU`: their site tags the document ru-RU while our i18n locale is `ru`, and a host page embedding this element may set either, so a selector matching only one would work on their site and fail on ours. Only the headings, as theirs. Their .region-stat__value is a <p>, so their ru-RU rule does not touch it and it keeps the heading family even in Russian — switching everything would be wrong in a way no Russian reader would report and no English reader could see. _probe-cyrillic-headings.mjs checks the mechanism and the result separately, so a rule that is present but inert cannot pass: the attribute is on the root, the Oswald subset returned 200, the face is usable once document.fonts.ready resolves, the h1 and h2 switched, the stat value did not, and English is untouched in both family and letter-spacing. It awaits fonts.ready before asking about a font — not doing so is what made a sibling probe report a cross-origin font failure that did not exist. |
||
|---|---|---|
| .. | ||
| api | ||
| colors | ||
| components | ||
| composables | ||
| constants | ||
| data | ||
| i18n | ||
| layouts | ||
| maps | ||
| packet | ||
| scripts | ||
| stores | ||
| styles | ||
| utils | ||
| index.js | ||
| ProfileLoader.vue | ||
| README.md | ||
library/ (@map) — the shared map template
The other half of the architecture (see ../plugin-designs/README.md):
every map in plugin-designs/<your-map>/ composes the reusable, parameterized pieces that live here.
Fix something here and every map benefits on the next build; break something here and every map
breaks — read components/WARNING.md before touching shared pieces.
| Folder | What lives there |
|---|---|
ProfileLoader.vue |
The root of every bundle: parses profile-config, loads the profile, provides the stores + config |
components/ |
Shared UI — map, legends, controls, popup (PeopleGroupDetail), tables, charts, hints (README) |
composables/ |
Shared logic — map engine (useMapInstance), provider switch, shadow-DOM styles, theming |
stores/ |
Per-instance Pinia stores (ui / map / data) — provided by ProfileLoader, injected by children |
api/ |
Data-source registry (sources.json) + fetch layer — the JAMstack runtime wiring |
colors/ |
Color sets maps opt into via profile-config.colorSet |
i18n/ |
The shared string catalogs (all maps speak the same languages) |
data/ |
Small shared datasets baked at build time (big served data lives in ../data/) |
constants/ |
Shared constants |
scripts/ |
Maintainer pipelines (posters, research) — not part of any bundle |
The rule of thumb (same as WARNING.md): custom code in your app-profile, reusable code here — and things only move from the first to the second once they've earned it.