Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

DaisyUI – Tailwind CSS Components

daisyui.com

Post reply on HN
Print view View original

111–120 of 174 posts

Re: DaisyUI – Tailwind CSS Components

#111

Post by faeyanpiraat »

411111111111111 wrote: post #97
armchairhacker wrote: post #83

We've gone full circle - CSS components to inline CSS-in-HTML back to CSS components. But I actually think I will use this. A big problem with CSS is that you end up making overrides no matter how composable you make the classes. And some simple things (e.g. responsiveness) are unintuitive and / or annoying to do in CSS. Hence Tailwind's "CSS-in-HTML" mini classes. But that doesn't fill the core purpose of CSS, bigge…

It's not really full circle considering that tailwind-ui has always been how the people that created tailwind made their money. Tailwind never wanted to remove component libraries, they just wanted a straightforward and easy way to make these components.

Op meant it in a bigger-picture-way.

Oldschool custom stuff -> BS -> Tailwind -> Tailwind with BS UX

Re: DaisyUI – Tailwind CSS Components

#112

Post by FractalHQ »

automatic6131 wrote: post #80
karlerss wrote: post #54

Earlier quoted context omitted.

If it's just one class per property, you could just type out the CSS. Using emmet in IDE is probably faster than finding the tailwind classes with autocomplete.

>If it's just one class per property, you could just type out the CSS. You can, but then it rarely happens that you want the CSS to be fixed in that way for all time: the brilliance of tailwind is that you get resposniveness just by adding a few more classes. You cannot do that with inline CSS.

This is the one pro-tailwind argument I can agree with. Sometimes I’ll use their shorthand md: & sm: in @apply in place of media queries. The advantage is that they remain local to their relevant selectors.

Makes me think- all I would really want is to be able to have multiple values in css. Maybe something like .

.card { width: 5rem md: 10rem; }

Snap… am I on to something?

Re: DaisyUI – Tailwind CSS Components

#113

Post by FractalHQ »

I am so glad that I took the time to get fast with CSS. I can build unique UIs in real time, and with Svelte Components, everything is automatically scoped to the component. I would waste so much time and gave a lot of analysis paralysis if I had to choose from all these cool looking libraries and frameworks, learn their api’s, and then learn how to override them more and more over time.

Re: DaisyUI – Tailwind CSS Components

#114

Post by tailspin2019 »

lawn wrote: post #105
bennyp101 wrote: post #43

Earlier quoted context omitted.

Refactoring UI [1] is a good place (from the guys behind Tailwind) - admittedly I've drunk the Tailwind koolaid, but there are some useful tips on there from a designer POV [1] https://www.refactoringui.com/

I dislike Tailwind's choice of inlined styles in html, but I agree that the advice in the book is very good.

Unrelated tangent: I'm always frustrated when I see a recommendation for a book only to go and look it up and find that it's actually an "ebook" (in this case PDF).

Not to make a value judgement on ebooks, but I just really like physical books sometimes - if it was on Amazon I likely would have bought it.

Again, not a value judgement on the content - I'm sure it's great (I'm a paid and happy user of TailwindUI)

Re: DaisyUI – Tailwind CSS Components

#115

Post by tailspin2019 »

eric4smith wrote: post #59

Very welcome. Sometimes the amount of classes needed in Tailwind is enormous. I paid for the TailwindUI pack too. But as nice as Tailwind is, the guys who built TailwindUI don't really get or understand a lot of real-world design patterns. A lot of stuff in there is needlessly complicated. Our team end up trimming down things to 50% of the markup that they use, while retaining full responsiveness. Overuse of flex for…

> the guys who built TailwindUI don't really get or understand a lot of real-world design patterns

It's all relative. It's clear they understand more than I do, and I'm not a terrible UI designer, so paying for TailwindUI has been a no-brainer in terms of the value delivered to my projects so far.

Re: DaisyUI – Tailwind CSS Components

#116

Post by dceddia »

udbhavs wrote: post #38
whoisjuan wrote: post #5

I’m not saying this is ugly but the visual execution of some of these components is poor. No good usage of padding in some examples, poor ratios between the typography and the containers, inconsistent use of different line widths and border radius, weird and incosistent design choices in spacing and proportions… I mean. This looks alright and it will certainly make any UI look pretty decent, but the execution is not…

This sort of stuff was difficult to figure out when I was learning HTML/CSS, do you know of any guides which list similar rules and how to make "proper" use of properties like borders, padding, typography etc?

This stuff all falls under the umbrella of “design”. One thing that helped me a ton was the articles at https://learnui.design - especially the 2-part “Rules for Designing Gorgeous UI”. The course itself is also excellent.

Re: DaisyUI – Tailwind CSS Components

#117

Post by tailspin2019 »

whoisjuan wrote: post #5

I’m not saying this is ugly but the visual execution of some of these components is poor. No good usage of padding in some examples, poor ratios between the typography and the containers, inconsistent use of different line widths and border radius, weird and incosistent design choices in spacing and proportions… I mean. This looks alright and it will certainly make any UI look pretty decent, but the execution is not…

I agree that there is room for improvement - though I think it's not a bad V1 at all.

A lot of the products I see turning up on Show HN would look infinitely better if they used this library. (The ones where UI design is clearly not the solo-developer's strength).

Re: DaisyUI – Tailwind CSS Components

#118

Post by sgt »

Recently bought Tailwind UI. Haven't really used it much except for a concept UI, and didn't work completely out of the box (you kind of have to know something about Tailwind the open source project first).

Aside from that, it looks like a really convenient way to put together a web UI when you don't really want to focus on the UI part of your app too much.

Not too expensive either, I think it was $175 or so.

Re: DaisyUI – Tailwind CSS Components

#120

Post by saadeghi »

debarshri wrote: post #90

I am new to UI/UX. Is it comparable to bootstrap? How is it actually different from the CSS and UI component libraries?

You could say it's a component library like Bootstrap but it's customizable in core because it's based on Tailwind CSS. For example if you want to customize a Bootstrap button, you need to write additional CSS files. With daisyUI you can simply add a class name.
Post reply on HN