Anja P

View Transitions

Community Picks is a section on daily.dev where our community members share the most interesting and valuable content they've discovered online. From insightful articles to handy tools, every post is a gem curated by our dedicated coomunity. To contribute to Community Picks, you need to have at least 250 reputation points, ensuring that only active and trusted members can share their finds.

Community Picks

daisyUI is a plugin for Tailwind CSS that adds component class names for common UI elements, reducing the need for writing utility class names. It also offers customizable color names and a theme generator. With daisyUI, developers can create beautiful websites faster and with less code.

daisyUI — Tailwind CSS Components ( version 4 update is here )

Get 1% better daily. Development resource sharing made easy. Post, comment, or upvote to show your contribution and support other developers! 🙌

⚠️ Please do not post any promotional resources.

Dev Squad

daisyUI : Magic of Tailwind CSS 💖

daisyUI : Magic of Tailwind CSS 💖

I don’t get the point of DaisyUI. If you’re going to switch from Tailwind classes to BEM classes, then why use Tailwind at all? Any half-decent dev environment has some sort of components system that keeps you DRY, so using a long string of TW class names in components is irrelevant to the workflow.
But if you’re fundamentally going to stick to BEM naming across the board and @apply everything from TW, you may as well just use your own set of variables rather than a gigantic CSS framework that needs a build process. Using BEM + TW feels like enjoying neither of their strengths.
I’m happy to be wrong, but I just don’t see why this would be great.

I always use this one when I want to quickly build an idea.

I got its best alternative: dev-components.vercel.app

We would need something like this in the React Native ecosystem
Using Nativewind