Skip to content

Roadmap

Delivery is phased so each stage is usable on its own. The toolkit keeps shipping independently; the kit never blocks core releases.

  • Foundation components: useButton, useInput, useCard, useBadge, useAlert (+ *Class SSR helpers) in the private @katanakit/ui workspace.
  • Stylesheet build: @katanakit/ui/styles.css (self-contained vendored framework + dark tokens + .* classes).
  • Docs skeleton: UI Kit section with component pages and live demos.
  • Theming: dark tokens compiled in and driven by the data-theme contract (ThemeService owns the attribute).
  • Token contract: a namespaced, documented override surface on top of the vendored palette.
  • Headless primitives: disclosure, focus trap, popover positioning, roving tabindex.
  • Full a11y checklist pass (keyboard map per component).

Exit criteria: a themed button and modal work in vanilla, Vue/Nuxt and Astro with keyboard support and no SSR errors.

  • App shell (sidebar, topbar, breadcrumbs, command palette).
  • Auth shell, settings shell and marketing shell.
  • The 50 common layout examples.

Exit criteria: every layout renders in light/dark and passes the a11y checklist.

  • Four auth pages and profile settings.
  • Eight dashboard layouts with chart blocks and data tables.
  • Support/FAQ page.

Exit criteria: dashboards run against mock Safe Result contracts with loading, empty and error states.

  • E-commerce pages (10).
  • File manager and Agentic Storage UI.
  • Chat app on AssistantService.
  • Gen-AI app (home, images, content creator, library).

Exit criteria: each app works end to end with the toolkit services and no custom data layer.

  • 15+ ready-to-use UI blocks.
  • 100+ interaction examples with plugin integrations.
  • ApexCharts adapter plus the SVG fallback.

Exit criteria: every example is documented, keyboard-operable and covered by the metadata registry.

  • Publish @katanakit/ui with per-component entry points.
  • Tailwind and daisyUI presets.
  • Six curated themes.
  • Generate llms.txt, llms-full.txt and registry.json in CI.

Exit criteria: a fresh project installs the package, picks a theme and scaffolds a block using only the LLM files.