Skip to content

What's new in v2.1

Design System v2.1.0, publication target dated 2026-11-13 (decision 397). This document and a local build do not establish that a GitHub tag or release has been published. The design-system version is independent of SpaceWorks 0.12.0 and the brand-book edition.

Release note (added 13 November 2026, v2.1.1): v2.1.0 was tagged and released on 13 November 2026 (PR #17, tag v2.1.0). v2.1.1 is the QA patch on top of it: demo cards keep their own theme for logo marks and focus rings, characters lost to an encoding round-trip in v2.1.0 are restored, the theme demo gets a keyboard radio model, and product rules §2.5 and §12.3 are added (SW-433, SW-436). See Releases and the README changelog.

Choose a platform: plain HTML/CSS and React/Tailwind starters, plus Android Compose and iOS SwiftUI source mappings. Native starters and generated exports are source-only here, not compiled or certified native components.

Token architecture, usage reference and contrast matrix accompany 425 paired tokens and 111 generated exports. Portable full-colour CSS sits beside the unchanged legacy RGB-triplet CSS. DTCG light/dark JSON, Tailwind preset, Android XML/Compose and Swift/asset catalogues retain their units, aliases and checksum manifest. Required-pair validation covers 204 pairs; diagnostic failures remain documented with restrictions and replacements.

Motion flow documents choreography, token timing, reversal, focus and reduced motion. The site publishes complete family READMEs, including box-open Files, Source of truth, Previews and SW-412. Coloured light box motion follows SW-412; black-and-white/reversed behaviour and later source notes remain visible in the box-open README.

Motion images start with static derivatives and explicit Play/Pause controls. Thumbnails are generated before site synchronization, leaving original files intact. Standalone demos and raw downloads have an explicit indexing policy; documentation remains the search entry point. Demo controls have minimum CSS target sizes, and easing previews use the duration their label states.

The site’s Downloads and Using the kit pages derive the target tag from VERSION. Adopt a published release tag or reviewed immutable commit, record the submodule SHA, and review migration guidance before changing it. The moving main download remains available as development material. This integration creates no tags, commits, releases or delivery policy.

Static build, links, source publication inventory, token guards and motion-flow checks accompany integration. Preview regeneration and browser compositing, scenario parity and geometry checks belong to the release orchestrator. Preview freshness alone does not prove behaviour or visual fidelity. The command node site/scripts/check-integration-browser.mjs runs the additional integrated browser checks when Playwright and a browser are available.