roadmap

paths to alpha

The foundations, features, and polish on the way to Pindoba's first stable release.

in flight 03 planned 04 shipped 01
milestone in flight

ESM-only architecture

A modern ESM-only module system as the base everything else rests on.

key tasks
  • All packages ship as ESM with proper module exports
  • Tree-shaking tuned per package for smaller consumer bundles
  • Modern JavaScript standards throughout the build tooling
milestone planned

Independent style modules

Decouple styles from components so a style change in one slot never cascades into unrelated updates.

key tasks
  • Each component's styles live in their own sva() recipe package
  • Per-component versioning and independent tree-shaking
milestone planned

Cross-framework parity

The same component surface — Astro, React, Svelte — with no silent gaps between frameworks.

key tasks
  • Audit of existing components across Astro, React, and Svelte
  • Fill missing components in each framework
  • Automated checks for cross-framework compatibility
  • A public feature matrix so gaps are visible, not hidden
milestone in flight

Headless core and the connect pattern

Framework-agnostic logic exposed through connect*() functions that produce prop objects any framework can consume.

key tasks
  • Core packages with zero framework dependencies
  • Style recipes (sva()) in dedicated packages, consumed by core
  • PassThrough pattern for deep slot customization
  • Components for primitives; Blocks for compositions
milestone in flight

Universal setup and compatibility

Make the install step boring — it should just work, whichever stack the consumer brings.

key tasks
  • Integration verified with Vite and Rollup
  • SSR verified with Astro, SvelteKit, and Next.js
  • Setup guides per stack with the shortest working path
  • Automated compatibility checks in CI
milestone planned

Essential documentation

Reference deep enough that a new consumer can self-serve without reading the source.

key tasks
  • Getting-started guides for Astro, React, and Svelte
  • Component API docs with interactive examples
  • Theming, tokens, and customization
  • Connect pattern and PassThrough usage
milestone shipped

Design system philosophy

The principles the system answers to, written down — so future decisions can be checked against them.

key tasks
  • Accessibility as a floor, not a feature
  • Composition patterns and naming conventions
  • Color system and typography scale rationale
  • Responsive principles and breakpoint strategy
milestone planned

Alpha release preparation

Last mile before the first stable tag — the last time breaking changes are cheap.

key tasks
  • Testing across every supported environment
  • Performance benchmarking and tuning
after alpha

what comes next

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.