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

Tailwind UI

tailwindui.com

Post reply on HN
Print view View original

301–310 of 367 posts

Re: Tailwind UI

#301

Post by ahallock »

bensochar wrote: post #234
ahallock wrote: post #214

Earlier quoted context omitted.

Why not use view templates to capture these?

For alerts a sharable template is doable. So maybe a bad example, LOL. But for buttons & heros not so much. I've worked with apps that have a "button" template. I find it overkill. For one project we have some components rendered both server-side & with Vue. Other cases I've had are sharing styles across multiple apps and pulling in markup from a 3rd party, like Stripe or a WYSIWYG. But you're right. Ideally this wou…

I agree; for smaller components like labels and buttons, having some compound rules would help. They tend to be well-defined. I believe you can create composite styles in Tailwind.

Re: Tailwind UI

#302

Post by marc_io »

rsp1984 wrote: post #287

Please excuse the newbie questions but would I be able to use this in a WYSIWYG framework like Webflow or Weebly or Wordpress? How about compatibility with React? Or is this the land of "bare metal" HTML+JS+CSS?

You can use it with WordPress for sure, as you have total control of the markup.

But you can't use it directly with Webflow. I don't know about Weebly.

Re: Tailwind UI

#303

Post by makeee »

erikig wrote: post #293
makeee wrote: post #255

Earlier quoted context omitted.

I should have mentioned that I created it.. so I'm a bit biased. You can see some opinions in our Show HN awhile back though: https://news.ycombinator.com/item?id=20688044

I remember seeing this earlier, looking forward to the passportjs authentication integration.

Looking forward to getting that in! Which DB do you generally use?

Re: Tailwind UI

#304

Post by sandGorgon »

rawfan wrote: post #294
sandGorgon wrote: post #152

Earlier quoted context omitted.

Not to be an ass, but so is Ant design or Semantic UI. I honestly think this is priced too high.

Compared to what? If you look at any agency license (use on as many sites as you want) for themeforest WordPress themes, they are about the same price, if not higher. I guarantee you, they‘ll make a million bucks on launch day!

That's a great point actually. It would be nice to have a single use license. Not all of us are building many sites in our day jobs.

Re: Tailwind UI

#305

Post by neya »

I can totally see the value of Tailwind UI, and as an experienced user of UIKIT (https://www.getuikit.com), I don't see much difference, to be honest. Can someone please help me understand what is so good about Tailwind UI that UIKIT doesn't already?

UIKIT is super light weight and modular. I've developed extremely high converting landing pages with almost no JS at all using only components I needed. Can the same be done with Tailwind? And if yes, then what exactly is the appeal? Simply the difference in number of components?

I love the look and feel of Tailwind, but it just looks like another UI framework to me and I don't understand all the raving reviews here. If it's something obvious I'm missing, very happy to learn it and pick it up.

Thank you.

Re: Tailwind UI

#306

Post by leviathan »

pests wrote: post #269
mike1o1 wrote: post #248

Earlier quoted context omitted.

Typically the "text-sm text-gray-700" would be a one-off styling while I'm developing a page or a component, not necessarily something that will be repeated a hundred times. If it turns out that later down the line I realize that "every card should have that size and color for the card title", then I'll pull it out to a separate class or part of a partial or something like that. The idea being at that point then I ha…

My question is why you cant just name the card and then use selectors to style the title or any other internal styling? This removes the need to name at all. It can just be .card > h2 or whatever and there you would do your font-weight and color.

That is answered by the author here https://adamwathan.me/css-utility-classes-and-separation-of-...

Re: Tailwind UI

#308

Post by davidbanham »

I'm very excited by this!

I currently use https://materializecss.com/ over several products. It's been great, but I'm stuck on the 0.100.x line because the upgrade path was too difficult. It's also hasn't been updated since the first 1.0 release some time ago. Not complaining since I got what I paid for (it was free) but it's left me pretty anxious to find a replacement.

Salesforce's Lightning components are good but challenging to understand how to work with outside the walled garden. Zurb's Foundation UI is interesting but seems to want me to use whole page templates rather than components.

This looks like exactly what I've been dreaming of. I've put my money where my mouth is as I can't wait to have more components built out to a stage where I can start using it for real.

Re: Tailwind UI

#309

Post by stefanfisk »

jaf656s wrote: post #168
arcatek wrote: post #130

Earlier quoted context omitted.

Disclaimer: I haven't used Tailwind. Maybe I'm missing something. > For example, if I'm working on a card and I want some text below the main text to have a smaller, gray font size. What do I name that class? "card-sub-text", "card-sub-title"? No - don't even worry about it - "text-sm text-gray-700" and move on. What's the difference with "color: gray; font-weight: 700"? In this case I really don't have to care about…

I have been using tailwind on a new project and I only see 3 real benefits over using inline css styles: 1) Sizes are standardized in a predetermined set of discrete size classes. So you start to think about sizes, padding, margins, etc in terms of steps instead of values. You can change the steps in one place and they apply globally. It's a little easier to standardize a rough style guide compared to starting from s…

I big benefit is that Tailwind supports media queries, while inline styles can't help you at all there.

Re: Tailwind UI

#310

Post by stefanfisk »

ec109685 wrote: post #156
city41 wrote: post #124

Earlier quoted context omitted.

It’s common, even expected, to extract that card into a component of some kind (React, web components, mustache template, etc) so you still only have to update the css once.

Your components often get bloated since you have to account for subtle business logic differences between views.

Isn't that what the container/component split is for? Presentation logic in a container, markup and styling in a component. If you need to reuse the same visual component in logically different contexts you create a new container that mangles the props as appropriate.
Post reply on HN