roadmap
The foundations, features, and polish on the way to Pindoba's first stable release.
The first and most important focus: build the full component set across every framework, with parity and tests, so we can prove the ideas actually work before we refine them.
With the components working, raise the bar on how they look and feel — a deliberate visual and interaction polish across the system.
Make sure everything holds up in real applications — not just in isolation — so the ideas are validated against actual usage.
Decouple styles from components so a style change in one slot never cascades into unrelated updates.
Framework-agnostic logic exposed through connect*() functions that produce prop objects any framework can consume.
Make the install step boring — it should just work, whichever stack the consumer brings.
Reference deep enough that a new consumer can self-serve without reading the source.
The principles the system answers to, written down — so future decisions can be checked against them.
Last mile before the first stable tag — the last time breaking changes are cheap.
Once the foundation settles, the work opens up: broader framework support, contribution paths, and the wider design-system scope beyond core primitives. Track progress in the repo — this page follows the work, not the other way around.