How Somnia DS is run

Light enough for a small team to actually follow. A design system that goes stale in public is worse than none.

Versioning

Somnia DS uses semantic versioning: major.minor.patch.

Major (2.0.0)Something that worked stops working: a token renamed or removed, a component's markup changed.
Minor (1.1.0)Something new that doesn't break anything: a token, a component, a brand, a page of guidance.
Patch (1.0.1)A fix: a value adjusted for contrast, a bug, a correction to the docs.

Every release is listed in the changelog. The version on the docs' home page is the changelog's newest entry, and the build stops if that isn't the version of the package, so the two can't drift apart. Removed tokens are deprecated for one minor version first, with a note saying what replaces them.

Ownership

Design, tokens and componentsDavid Balfour, who leads design at Media Dreams
Release schedulingJulia Balfour, who leads delivery
ContributionsAnyone on a Media Dreams project, including network specialists. See Contributing.

Review rhythm

  • Every build: token references, light and dark parity, contrast pairs and page structure are checked automatically.
  • Every release: axe in both themes, print preview in Chrome and Safari, changelog entry.
  • Every quarter: a review of unused tokens, component gaps, the roadmap and these docs.