EmilyUI

Roadmap

Current product direction for docs quality, framework reliability, and team workflows.

Now

Arbitrary values and extend system

  • Arbitrary value syntax — w-[123px], text-[#ff0000] — generated on-demand without config changes.
  • Expand extend system beyond utilities to support custom component patterns and token overrides.
  • Tighten config validation messaging with actionable fix suggestions.

Next

Editor and tooling depth

  • EmilyUI VS Code extension — EmilyJS directive support: autocomplete, hover docs, and option guidance for emily-state, emily-click, and the full directive set.
  • More actionable doctor diagnostics with specific fix suggestions, not just warnings.
  • emily-css doctor framework fixture examples — React, Vue, Astro, Next, Nuxt, Drupal, WordPress.

Later

Ecosystem and documentation

  • emilyui.com documentation site — full reference, search, and interactive examples.
  • Premium component tier — extended component sets with dark mode variants and layout patterns for teams that need more, faster.
  • Migration helpers for large teams and multi-repo setups.

Planning principles

  • Reliable generation and predictable output beats feature volume.
  • Docs should match shipped behaviour, not planned behaviour.
  • Prefer explicit migration guidance over risky auto-rewrites.
  • Performance and accessibility stay default concerns in every release.

How to use this roadmap

Treat roadmap items as active priorities, not date promises. For implementation details and shipped changes, use the changelog as the canonical source.

Next step

Check the Changelog for what is already delivered.