My Journey to build daisyUI: Why Tailwind CSS was not enough?
1–10 of 18 posts
Re: My Journey to build daisyUI: Why Tailwind CSS was not enough?
#2This looks like a very good project. I am setting up for a new project and I was planning on using ShadcnUI for it, but after reading this blog post I'm interested in trying Daisy. I like the way it's structured for customizability. Does anyone have any thoughts on using this vs Shadcn?
Re: My Journey to build daisyUI: Why Tailwind CSS was not enough?
#3This looks like a very good project. I am setting up for a new project and I was planning on using ShadcnUI for it, but after reading this blog post I'm interested in trying Daisy. I like the way it's structured for customizability. Does anyone have any thoughts on using this vs Shadcn?
I don't personally have any thoughts on ShadcnUI (I've really never heard of it), but I did use DaisyUI when it first launched (v1 or so?). I personally like the way Daisy is thought out, and structured. I also recently started a new project, and I'm integrating DaisyUI again after reading this blog post as well!
Re: My Journey to build daisyUI: Why Tailwind CSS was not enough?
#4[deleted]
Re: My Journey to build daisyUI: Why Tailwind CSS was not enough?
#5This looks like a very good project. I am setting up for a new project and I was planning on using ShadcnUI for it, but after reading this blog post I'm interested in trying Daisy. I like the way it's structured for customizability. Does anyone have any thoughts on using this vs Shadcn?
Using Daisy UI, great project. Some minor annoyances because it does not have JS. E.g. some popups don’t close when you click on the button they are tied to because they are open based on button focus…
Re: My Journey to build daisyUI: Why Tailwind CSS was not enough?
#6Been using DaisyUI for a year. Highly recommend - it’s opinionated just to the right level
Re: My Journey to build daisyUI: Why Tailwind CSS was not enough?
#7If I remember right, the design philosophy around why Tailwind encourages you to write all the different classes out individually each time is that it wants you to reuse components rather than CSS classes because as the codebase scales and gets more complex you now know that any changes are only going to affect that component and not that component + whatever dev decided to use that custom class you made somewhere else. The other issue it solves is loads of devs making custom classes that are almost identical and cluttering up the codebase. If you're working on personal projects and know you're only ever going to need to change those three things about buttons then this is probably a great thing to use but be aware that if you're creating a commercial project and may have lots of people working on it, this is probably not the way to to go. I will see if I can find the exact part of the tailscale docs where they go into this and update this comment with the link later.
Edit: The core concepts section is worth a read in it's entirety but I believe this is the relative part:
https://tailwindcss.com/docs/reusing-styles#avoiding-prematu...
Re: My Journey to build daisyUI: Why Tailwind CSS was not enough?
#8A wonderful UX on my mobile device. I personally am fond of Microsoft’s Fluent UI, but I can’t get their websites to work in Safari—either it doesn’t render anything (Blazor) or it manages to render but it’s just not mobile ready (React). That’s a show stopper concern for any UI library. Nevertheless I made a couple of mock-ups for which I solved those rendering issues, which later went in production. But I must say, that Daisy UI site is amazing and just a true eye candy. I think I’ll try it for my blog, it’s been long overdue to refresh the UI.
Re: My Journey to build daisyUI: Why Tailwind CSS was not enough?
#9If I remember right, the design philosophy around why Tailwind encourages you to write all the different classes out individually each time is that it wants you to reuse components rather than CSS classes because as the codebase scales and gets more complex you now know that any changes are only going to affect that component and not that component + whatever dev decided to use that custom class you made somewhere el…
If you want to deep dive more into this css methodology, you should check out this interview with ThierryK.
https://css-tricks.com/thierry-koblentz-atomic-css/
Re: My Journey to build daisyUI: Why Tailwind CSS was not enough?
#10Hello, thank you for this. I recently got PR(s) to add astro/tailwind/daisyui to yakshalang.github.io from 2 devs. I'm blown away from how good the website looks now. :) Happily deleted my homegrown and badly written CSS.