5 ms·

Generally you’d have your button html and classes inside a component so you’re just tweaking that one component.

by makeee 8y ago

wishinghand 8y ago
Then it feels like we're just back to writing normal CSS classes.
- jorgesborges 8y ago
  The real value for me is just being able to sit down and start. The odious first impressions of tailwind are true. But try it out. I like it because I don't waste time flipping back and forth between my document and a style sheet. I don't waste time thinking of clever class names. I don't wait a second to compile css and refresh for every small change I make (even though developer tools have been helpful in this regard, you can only make so many changes at a time). I still break it down into components later but the actual design process is more fluid.
  - wishinghand 8y ago
    I use it in production at work. Wasn't my choice. I should have pushed harder for Bulma. Not only is the HTML just a hair length's away from `style` tags, but if I'm writing the same set of classes on more than 3 elements I compose a component. Then I also have to write our own classes for modals, cards, toasts, lists, media objects, drop down menus, side menus, breadcrumbs, buttons, forms, their labels, images and their captions, and get the right mix of responsive utility classes as well so they all play nice together. I'd rather just pick a framework that lets me customize the corner radii, padding, margins, and be done with it.
- rvense 8y ago
  Buttons are sort of a pathological example. Most components in a web app are container-like things, with collections of a couple of buttons and other things that need to have a cohesive look, internal and external positioning, etc. And how often do you end up with one large, crufty CSS class for each of those, or a handful that are closely tied to each other and the markup anyway? Frameworks like this allow you to easily move that gunk from the CSS to the HTML.
- jack9 8y ago
  The secret is that a solution where typical CSS classes are the exception and not the common case, is generally more useful.

Generally you’d have your button html and classes inside a component so you’re just tweaking that one component.

by makeee 8y ago

Generally you’d have your button html and classes inside a component so you’re just tweaking that one component.

wishinghand 8y ago

Then it feels like we're just back to writing normal CSS classes.

jorgesborges 8y ago
The real value for me is just being able to sit down and start. The odious first impressions of tailwind are true. But try it out. I like it because I don't waste time flipping back and forth between my document and a style sheet. I don't waste time thinking of clever class names. I don't wait a second to compile css and refresh for every small change I make (even though developer tools have been helpful in this regard, you can only make so many changes at a time). I still break it down into components later but the actual design process is more fluid.
- wishinghand 8y ago
  I use it in production at work. Wasn't my choice. I should have pushed harder for Bulma. Not only is the HTML just a hair length's away from `style` tags, but if I'm writing the same set of classes on more than 3 elements I compose a component. Then I also have to write our own classes for modals, cards, toasts, lists, media objects, drop down menus, side menus, breadcrumbs, buttons, forms, their labels, images and their captions, and get the right mix of responsive utility classes as well so they all play nice together. I'd rather just pick a framework that lets me customize the corner radii, padding, margins, and be done with it.
rvense 8y ago
Buttons are sort of a pathological example. Most components in a web app are container-like things, with collections of a couple of buttons and other things that need to have a cohesive look, internal and external positioning, etc. And how often do you end up with one large, crufty CSS class for each of those, or a handful that are closely tied to each other and the markup anyway? Frameworks like this allow you to easily move that gunk from the CSS to the HTML.
jack9 8y ago
The secret is that a solution where typical CSS classes are the exception and not the common case, is generally more useful.