Changelog

What shipped and what it changed for the systems you author. Milda is in closed alpha, so this is a record of capability rather than a semver history - the packages you generate carry their own versions, derived from their contracts.

#November 2026

#The layout model is one size

What the spec promised, the file reads, the document holds and every target draws: per-axis weight, ratio and min/max clamps, and position pinned and bleed on logical edges. A position overlay used to be dropped on the way into the document; it is not any more. Surface 0.8.

#The docs teach the language

A fourteen-lesson tour builds one system a file at a time, every file opening in the Playground and the last one generating a library the docs' own tests typecheck. An archetype catalogue with a page per blueprint is read off the prelude, every status claim renders from one table a test holds to the product, and a glossary fixes one word for each thing.

#October 2026

#The system says how it is used

A props block can say required, required when and one-of / any-of / exclusive, typed by the React target; a top-level rule says how many, inside what, from which tokens and through which component, and ships in AGENTS.md, DESIGN.md and design-system.json. The surface moved to 0.7.

#The icon library travels in the file

A top-level icons block carries the sets a bare glyph name resolves against and every curated glyph with its vendored SVG, so an imported system draws its icons. Surface 0.6.

#The Playground

play.milda.dev reads a file as you type, with the language server's diagnostics and completion, a tree of what the file describes, and a share link that is the file itself. A font family and a text style, a computed value and a unitless ratio (surface 0.5) all survive the file.

#August 2026

#The Foundations editor, per token type

Every token type now has an editor built around what that type actually is: a radius is shown on a box you choose, spacing in a role (row gap, stack gap, inset), a duration as frames you can replay, an elevation as a light direction. Sixteen types, each answering the question that type raises rather than showing a number field.

• Multi-select and bulk operations across tokens.
• Table and flow views beside the tree.
• Exceptions and the layer chain are visible where you edit.

#Storybook for the editor's own components

Internal, but it is why the editor's controls now behave consistently.

#July 2026

#The .milda file carries the whole system

Export and re-import round-trips a complete document - foundations, components, examples, docs and the written contract - and the round trip is a tested fixed point over a real corpus. The surface version moved to 0.4.

#Typed lengths and first-class values

A length says what it means rather than carrying a CSS unit: 12px is density-independent, scaled(0.75) follows the user's text size, and pill is the intent "fully rounded" rather than a large number. Colours are space-aware functions -hex(), oklch(), p3() - instead of quoted strings, and a computed colour prints as the relationship it is.

#Release lines and snapshots

A release stores the document it was built from, content-addressed and immutable, so the past stays reproducible.

#The CLI and the MCP server

milda pulls a published system from the command line, and the MCP server exposes it to AI coding agents. See The CLI and Milda & AI.

#Editor support

A language server, a VS Code extension and a JetBrains plugin, all reusing the same parser the compiler uses - so completion and diagnostics cannot drift from the language.

#June 2026

#Figma as a design target

Foundations export as Figma Variables and DTCG tokens, and components as component sets. The plugin is a persistent bridge rather than a one-way dump - Milda stays the source of truth.

#Icon provenance

An icon records where it came from - an uploaded asset or a named set - and the generator emits it accordingly, with no CDN fallback anywhere in the output.

#Documentation as part of the system

A design system carries its own docs, published per tenant at *.milda.page.

#Before that

The editor, the IR, the React generator, the registry and the release pipeline - the wedge that makes the rest possible. Thinking in Milda is the shortest route to what those are.