I bought tailwind UI more than a year ago. The lifetime/unlimited product or whatever it was.
It’s generally fine but feels incomplete. Many of the components don’t have any alpine or JS code documented even though the team has clearly built those aspects when building the previews and demos.
I’m not sure what the rationale was there but I hope they’ve fixed it here.
Cause that's not what it's for? It's like the opposite of headless components. It's all head and no component. That's what you're buying. I think that's pretty clear cause that is what Tailwind is. It's CSS, not a component library. That's what this thing is.
> If you'd rather write any necessary JS yourself or want to integrate with a framework other than React or Vue, we also provide every Tailwind UI component example as vanilla HTML that you can adapt yourself.
The js they use is mainly just showing how to hook headlessui up. Tailwind ui was never about buying fully fleshed ready to go react/etc components. They were building blocks you adapt. Guess a lot of people missed that and assume it’s copy paste. Catalyst will become that hopefully.
I bought Tailwind UI when it first came out, and have been thrilled. I view it as essentially I paid for a high quality template to build off of. You are still expected to know tailwind, or at least that's how I took it, I am not sure how its advertised now, but I am pretty sure its not advertised as a batteries included OOTB solution, but more as a starting point. From that perspective, I have been pleased.
Even though the discord said they refund with no issues I haven't asked for a refund but tailwind ui was not worth the money unless react is being used.
Such a massive disappointment there isn't any JS with the "vanilla" components.
I’ve been really happy with my tailwind ui purchase. I’m weaker on the design side so having a consistent and decent look and feel is great. Writing up a little bit of js to make them dance is no big deal, and I like that I don’t have to buy into another build process or toolchain for it.
Yes, agreed. I used them earlier and the examples on the page use alpine, but the "copy code" doesn't have it. It's actually easier to just inspect/view source and take what they did from the examples than try to write your own.
I’ve gotten into the habit of using “Inspect Source” in my browser when copying and pasting, because it tends to have almost fully-built Alpine transitions embedded.
I paid for DivMagic extension which lets me select elements on a page and it generates tailwind styled html code. It was quite useful for the first month but will probably cancel soon.
It’s generally fine but feels incomplete. Many of the components don’t have any alpine or JS code documented even though the team has clearly built those aspects when building the previews and demos.
I’m not sure what the rationale was there but I hope they’ve fixed it here.