I'm just in the process from migrating from UIKit to tailwind. So take this with a grain of salt:
Before you get into tailwind-ui, I would start out with the basics of tailwind, which can already take you quite far. I would even say, that using simply tailwind will make your design unique in a way that tailwind-ui won't. That way, while you are in the process of designing your website, you always have the option, to extract your own components and don't fall back to templates which restrict your design.
One video, which was eye opening for me, was watching Adam Wathan rebuild Netlifly from scratch [1]. My takeaway: You don't need fancy ui-components to build something great.
Before you get into tailwind-ui, I would start out with the basics of tailwind, which can already take you quite far. I would even say, that using simply tailwind will make your design unique in a way that tailwind-ui won't. That way, while you are in the process of designing your website, you always have the option, to extract your own components and don't fall back to templates which restrict your design.
One video, which was eye opening for me, was watching Adam Wathan rebuild Netlifly from scratch [1]. My takeaway: You don't need fancy ui-components to build something great.
[1] https://youtu.be/_JhTaENzfZQ?t=382