Skip to content

Design system v0.9.4

Choose a tag to compare

@dauglyon dauglyon released this 02 Sep 18:45
· 10 commits to main since this release
f6c119a

One change since ds-v0.9.3 (#43): links keep KBase's blue when a skin moves the primary, and MIGRATING.md §2 no longer names a fleet-wide skin variable. No React component API changes; the Button and Collapsible sheets change colour only. Portals pinning ds-v0.9.3 upgrade to drop their own link overrides and any KBASE_SKIN fallback.

--c-link, held apart from --c-primary. Every rule drawn as link text took --ct-primary, so a skin that moved the primary moved link colour with it — purple links under a purple portal, which read as visited. tokens.css states --c-link: #007dc3 beside the semantic colours and derives --ct-link the way --ct-primary is derived, so it meets the same contrast on both schemes. The five link-text rules — .link, .prose a, .solara-markdown a, the link Button and the Collapsible trigger — take it; theme.tokens() returns c-link and ct-link. The code-block trigger stays ink and the breadcrumb hover stays the un-underlined accent; both keep the brand. A portal that carried a link-colour block in its skin sheet removes it on upgrade.

MIGRATING.md §2: the skin lookup is one variable, the portal's own. The guide told a portal to read KBASE_SKIN after its own <APP>_SKIN. Nothing in KIND, king or a pod sets one, and a portal reading it claims a shared selection layer that was never built. The example reads only PORTAL_SKIN; a portal that carries the fallback drops it.

Tests: 47 against the installed wheel (pip install '.[dev]', pytest tests), two new — --ct-link holds when the primary moves, and each of the five link rules names --ct-link and not --ct-primary, read from the built sheets.