Skip to content

Changelog

A clean record of what shipped, what is in development, and what is next

Track component launches, Create updates, registry changes, accessibility work, and docs improvements in one place.

Release timeline

v0.2.2In development2026-06-22

Stack Builder beta preview and schema docs

Added Stack Builder to the docs IA and clarified that generated commands are preview artifacts until a cooud-stack generator package exists.

  • Stack Builder docs route with beta status and generator truth
  • Command palette entries for Stack Builder docs and the live builder
  • stack.json schema metadata for the current builder output
v0.2.0Released2026-06-22

Create studio and preset system

Added the Create route with live preview, preset save/export, shuffle controls, framework setup output, and runtime token overrides.

  • Nova, Aurora, Minimal, Brutalist, Editorial, and Terminal presets
  • Get Code dialog with install, provider, CSS vars, and JSON tabs
  • Chart, radius, font, and color overrides mapped to tokens
v0.2.1In development2026-06-22

Documentation sections and changelog

Expanded the docs IA with installation, CLI, registry, framework, forms, RTL, accessibility, and release notes surfaces.

  • Package-manager tabs for npm, pnpm, yarn, and bun
  • Framework cards with setup commands and accessibility checks
  • Clean changelog timeline for released and upcoming work
v0.1.0Released2026-06-21

Foundation component waves

Published the initial component catalog, token package, theme provider, registry generator, and showcase app.

  • Foundation, forms, overlays, navigation, data, display, and premium components
  • CLI registry generated from source components
  • Semantic token contract for runtime theming
v0.3.0PlannedNext

Framework adapters and examples

Add framework-specific examples, install smoke tests, and migration recipes for production Cooud apps.

  • Per-framework starter snapshots
  • Registry diff reports in docs
  • Accessibility snapshots for complex primitives

Release policy

Every visible change should include a short entry so teams know whether it is ready to use, still in development, or planned.

Component releases should mention docs, registry output, accessibility coverage, and migration notes when a change affects copied code or app-level setup.