Four releases in two years — each one a different answer to the question *what should a CSS framework be?*
| Date | Release | Answer | Legacy |
|---|---|---|---|
| 2024 | v1.0 | A frozen stylesheet: 1,038 hand-tuned classes, 19 palettes, 8K-ready screens | Taste — neon, glass, brutalism |
| 2026-09-12 | v2.0 | A generator: TypeScript CSSGenerator, 50 hues × 10 shades, npm packaging | Discipline — typed config |
| 2026 | v3.0 | A compiler: pnpm monorepo, JIT, CLI, 3,091 utilities | Speed — 18 ms builds |
| 2026 | v3.1 | A standard: Tailwind 3.4 parity, 11,417 utilities, LSP, CSS-first config | Trust — byte-identical oracles |
The through-line#
Nothing was discarded; everything was recompiled. v1’s palettes live as configs, v2’s generator API survives in v3, and the docs platform you are reading is the evolved form of v3.0’s generated-reference idea (release notes).
New. The next chapter is unwritten — beyond 3.1.