Malevich

v1.0 architecture

Roadmap (v0.2.0 → v2.0)

Malevich Roadmap (post-quiz update)

Last updated: 2026-05-18 Status: Architectural decisions finalized via 8-section quiz. Implementation scoping below.

This roadmap replaces the previous roadmap.md. It reflects the architectural model defined in 01-master-diff-merge.md and the 42 principles in 02-principles.md.


Version philosophy


v0.2.0 — Architectural refactor

Goal: Bring v0.1.0 code into v1.0 architectural model without adding components. This is the migration step.

Scope:

Component reorganization

Token system migration

Modifier renaming

Lint rules

Documentation

Migration tooling

Estimated work: ~40-60 hours total. Can be batched into 3-4 parallel tracks.

Definition of done:


v1.0 — Full architectural model

Goal: Ship all 53 v1.0 components with documentation, tests, and AGENTS.md.

Foundations (8 components, +6 net from v0.2.0)

Elements / Interactive (6 components, +3 net)

Elements / Form (12 components, +11 net)

Elements / Display (6 components, +4 net)

Blocks (7 components, +5 net)

Sections / Layout (4 components, +4 net)

Sections / Ready (4 components, +4 net)

Overlays (6 components, +4 net)

Separate packages

Token system extensions

Modifier system implementation

Documentation site

Quality bar

Estimated work: ~300-400 hours. Months, not weeks. Realistically v1.0 ships Q3 2026.


v1.1 — Stabilization & expansion

Goal: Address community feedback, add components held back from v1.0.

Additional components

Token system upgrades

Carousel enhancements

Layout additions

Tooling

SSR support

Estimated work: ~100-150 hours.


v2.0 — Multi-brand, shaders, advanced sections

Goal: Enterprise features, advanced visual capabilities, pattern promotion.

@malevich/shaders

Multi-brand support

Advanced ready sections

Inline composites

Masonry runtime

Ask AI button

Component versioning

Estimated work: ~200-300 hours. Could span multiple quarters depending on community traction.


Cross-cutting work

Documentation maintenance

Tooling maintenance

Community


Out of roadmap (out of scope for foreseeable future)


Decision points along the way

These are architectural questions deferred for later decisions. They will likely be discussed before v1.1 or v2.0 ship.

  1. Native CSS masonry adoption — pending browser support. If stable by v1.1, native; if not, defer to v2.0 with JS fallback.
  2. Custom Select component — if community demands rich dropdowns, custom Select replaces native styled in v1.1. Otherwise stays native.
  3. Shader bundle splitting — if @malevich/shaders becomes large, split into core + extensions packages.
  4. i18n token category — RTL support, locale-specific font-family overrides may warrant a dedicated semantic group.
  5. Animation framework integration — Framer Motion / Motion One vs CSS-only. Currently CSS-only by principle, may revisit if complex animations become common request.