Roadmap

Templates
Accordion

Roadmap

This page tracks what is actually done and what still needs implementation in 5h3ll-ui. It reflects the current source and docs state as of July 13, 2026.

How to read this page

  • Done means implemented and already represented in source/docs.
  • Recently closed means work that was open very recently and is now complete.
  • Planned means not yet implemented.

This is a planning page, not a release log. Release-visible changes belong in the changelog or CHANGELOG.md.

Done

These items were previously still listed as open in trackers, but they are already present in the project:

  • Drawer is implemented, documented, and shipped.
  • Item is already a dedicated component with .item and .item-group.
  • Component CSS and style-pack CSS are already split into dedicated source files.
  • Command already supports app-owned filtering with data-filter="manual" and command.refresh().
  • Combobox already supports app-owned filtering with data-filter="manual" and combobox.refresh().
  • The docs nav already includes Typeset, Components, and Blocks sections, plus a demo block page.

Recently closed

These items were the remaining partials and are now treated as complete:

  • Command now has a concrete remote-loading docs example using data-filter="manual" and command.refresh().
  • Combobox now has a concrete remote-loading docs example using data-filter="manual" and combobox.refresh().
  • Chart is no longer labeled beta in the docs navigation or component page.
  • Menubar, Separator, Sheet, and Toggle are now implemented and documented.
  • Carousel is now implemented and documented with native scroll snap plus lightweight JavaScript controls.
  • Blocks now include real dashboard, authentication, settings, marketing, analytics, cards, timeline, and organisation switcher pages with resizable preview frames and preview/code tabs.

Planned

Blocks

The docs now have a Blocks section with real dashboard, authentication, settings, marketing, analytics, cards, timeline, and organisation switcher pages plus the original demo page.

Next work for Blocks:

  • Add more reusable form and profile layouts.
  • Add more coherent 5h3ll-ui block pages from reusable product, admin, and content patterns.
  • Expand category coverage beyond the first product/admin/marketing/process-focused examples.

Block pages should stay true to 5h3ll-ui conventions:

  • semantic HTML first
  • minimal JavaScript
  • existing component primitives instead of React composition APIs
  • intentional shadcn concept mapping without copying React internals

Later

  • Calendar, likely via a browser-friendly integration such as Flatpickr
  • Wider Blocks expansion across dashboard, authentication, settings, cards, forms, and additional marketing categories

Suggested order

If the goal is to reduce ambiguity quickly, this is the best sequence:

  1. Add more reusable Blocks categories beyond the initial shipped examples.
  2. Expand the planning docs as new block and calendar work lands.

This order keeps docs, runtime capabilities, and public expectations aligned before expanding the surface area further.

Notes

  • This roadmap reflects source and docs status, not Git history.
  • Historical migration and sync work is tracked in WORKLOG.md.
  • Public release notes belong in CHANGELOG.md.