A few people are a little bit confused about what this library actually is, so quick thread with some explanation...
https://twitter.com/adamwathan/status/1309189613970481152
First of all, what it’s not:
❌ Not an alternative to Tailwind UI
❌ Not a predesigned UI kit
❌ Not styled at all
❌ Not in any way tied to Tailwind, there is no CSS or classes or anything of any kind in the library
❌ Not an alternative to Tailwind UI
❌ Not a predesigned UI kit
❌ Not styled at all
❌ Not in any way tied to Tailwind, there is no CSS or classes or anything of any kind in the library
Instead, it’s a set of low-level completely unstyled primitives that let you build *custom* versions of common components faster, *with your own design you bring yourself*.
This is what a menu button renders by default (that’s the default browser focus ring, not bundled CSS):
This is what a menu button renders by default (that’s the default browser focus ring, not bundled CSS):
The underlying motivation for building these libraries is so we can offer React, Vue, and other versions of what we offer in Tailwind UI, without making you copy and paste a ton of gnarly JS.
Instead you’ll still just copy the markup and styles, but the behavior will just work.
Instead you’ll still just copy the markup and styles, but the behavior will just work.
These are *headless* components, they have no styles, they render nothing, they have no visual opinion at all.
Tailwind UI on the other hand is design and CSS implementation. This is the JavaScript that will make designs like that magically come to life.
Tailwind UI on the other hand is design and CSS implementation. This is the JavaScript that will make designs like that magically come to life.
• • •
Missing some Tweet in this thread? You can try to
force a refresh
