TailNG roadmap & focus areas
Building a scalable Angular component system that works with plain CSS, Tailwind, and custom design systems.
TailNG is evolving as an Angular-first UI system with its own CDK, headless primitives, and ready-to-use components. The focus is practical: accessible behavior, flexible styling, token-based theming, and components shaped by real application needs.
Guiding priorities
- Angular-first: standalone components, signals, typed APIs, and modern Angular patterns.
- Flexible styling: support plain CSS, Tailwind utilities, and custom design-system classes.
- Token discipline: keep templates mode-safe, theme-friendly, and brand-ready.
- Own CDK + primitives: shared behavior for focus, keyboard navigation, overlays, forms, and selection.
- No styling lock-in: applications should own the final visual system.
Focus areas
- Reusable focus, keyboard, overlay, and selection utilities.
- Consistent active-item and option-list behavior.
- Shared contracts for accessibility-aware components.
- Headless building blocks for lists, inputs, overlays, and forms.
- Behavior-first APIs without forcing one visual style.
- Foundation for custom application-specific components.
- More semantic tokens and clearer theme guidance.
- Better support for dark mode, light mode, and brand themes.
- Examples for both plain CSS and Tailwind-based usage.
- Form-field, input, select, autocomplete, date, and number controls.
- Validation UX patterns, hints, errors, labels, and accessibility states.
- Composition-friendly APIs for real business forms.
- Table patterns for CRUD screens and business applications.
- Sorting, pagination, filtering, actions, and empty/loading states.
- Simple spreadsheet-like UI without a heavy grid dependency.
- More runnable examples and copy-paste patterns.
- Component guides for when to use and how to compose.
- Side-by-side examples for plain CSS and Tailwind.
Bedrock + Owned direction
TailNG is moving toward a clear split between the stable foundation and the application-ready component layer. This helps teams choose the level of abstraction they need.
Bedrock
Own CDK utilities, headless primitives, accessibility-aware behavior, and minimal assumptions.
Owned
Ready-to-use TailNG components with theme tokens, slots, and practical defaults for product teams.
What we are validating in real apps
TailNG is being shaped through real application usage, including business screens with forms, tables, filters, invoices, reports, settings, and workflows. The roadmap is driven by practical gaps found while building actual Angular applications.
- Can components be customized locally without deep CSS overrides?
- Can the same component work with plain CSS and Tailwind examples?
- Can forms stay consistent across create, edit, delete, and filter screens?
- Can tables remain simple for CRUD pages while still supporting real business needs?
- Can shared primitives reduce repeated keyboard, focus, and accessibility logic?
Get involved
If you are using TailNG in a real Angular app, feedback on styling, theming, forms, data components, accessibility behavior, and developer experience is most valuable.