135: Lessons Learned Building Tailwind UI

Hey, everyone. Before we get into the show, I just want to share some pretty exciting news and that is that last week we finally launched early access to Tailwind UI, which is a collection of professionally designed, fully responsive HTML components built with Tailwind CSS put together by myself, the creator of Tailwind, Adam Wadden, and Steve Schoger, co author of Refactoring UI. If you love working with Tailwind but maybe don't consider yourself much of a designer or maybe you just wanna move really fast and don't wanna get hung up on tricky layout problems or weird CSS behavior, definitely check it out. I promise it's gonna save you hours and hours of time and it'll make building beautiful modern user interfaces a breeze. We're super proud of everything that we've published so far and excited to keep adding new components every single month until we run out of ideas. So So head over to tailwindui.com and check it out. Picking up is a great way to support both Tailwind CSS as well as this podcast. In this episode of Fullstack Radio, Sam Selakoff joins the show to talk to me about the lessons I learned building Tailwind UI. This is Fullstack Radio episode one thirty five. Yeah. So I guess maybe for anyone who has just hasn't really been following along with this project, Steve Shoger and I, my business partner who I worked on refractoring UI with for the last, I mean, I think our first prototype was March, so just about a year now. We've kind of been tossing around this idea of putting together some sort of commercial product on top of Tailwind CSS that, offers, like, premium either, like, themes or templates or a UI kit. It was kind of like we didn't really have it totally figured out at the beginning, but we just knew that there was there was something we could build somewhere that would, like, help people move faster with Tailwind who weren't as design inclined or maybe not as good with CSS as you kinda need to be to really achieve really good results with Tailwind or just to help people move faster in general where we work out some annoying edge cases and, stuff like that. We just thought, okay. There's there's something we can build that's like an HTML only product that gives people a bunch of, kind of starter templates for achieving common things, with Tailwind. And we think people will pay for it, and we think it's a good way to help, sort of sustain development, on the product. So Tailwind UI is, that essentially, and we can talk more about what it is, specifically. But, yeah, that's kind of, like, where the story starts at least. Yeah. And it was I mean, correct me if I'm wrong, but it was really born out of a lot of the feedback from refactoring UI. Right? I mean, I I kinda think this is funny because …