React utility component primitives & UI framework for use with Tailwind CSS
NB: As the 0.#.# version number suggests this is still very much work in progress, so semantic versioning will not be followed until a v1 release is solidified. Expect breaking changes to occur on minor version jumps.
Tailwind React UI provides ready built components that make use of Tailwind CSS utility framework.
If you're unfamiliar with the concepts behind Tailwind you can get an overview at https://tailwindcss.com/docs/what-is-tailwind:
Creating a framework for building custom UIs means you can't provide abstractions at the usual level of buttons, forms, cards, navbars, etc. Instead, Tailwind provides highly composable, low-level utility classes that make it easy to build complex user interfaces.
Tailwind React UI leverages these utility classes to provide base level components that are common across various projects, whilst still offering the ability to customise the output to match your project's style.
Tailwind React UI's components have no inline/encapsulated styles (barring some use for CSS transitions), so there's no specificity issues, no new CSS in JS tool chain to apply. The library simply uses classes made available by Tailwind CSS that your whole app will make use of with hooks available to specify which classes are applied.
Introduces a props API for Tailwind's uitlity classes that allows for extensive customisation & quick prototyping
withTailindhigher order component or by using the component primitives to have that handled down wind
Has a configurable theme to apply a design system approach for the base styling of components
Uses React context in order to allow for customising which color / space / etc classes get applied by default
Can still leverage the utility props in all components to override the default styling in whatever way you wish with sensible defaults applied in relevent components, e.g.will also apply interactive styling to the resulting element
Tailwind React UI's suite of components are highly composable allowing for a large degree of flexibility.
Components are largely functional, but where applicable offer wrappers to control UI state for opening/closing/etc.
Components have accessibility best practices built in; inputs will read out related help/error text, toggleable components correctly call out their open state, etc
PurgeCSS is a key tool when using TailwindCSS to strip out any of the unused utilities and to avoid any complications with this the library provides a whitelist of classes your theme will generate from components as well as a custom extractor that parses the utility class props API used by the components.
Hello World Foo Bar
Hello World Foo Bar