3 ms·

Now change the padding on card-body. All of a sudden tailwind makes more sense.

by armatav 4y ago

ceejayoz 4y ago
Isn’t that a single SCSS variable in Bootstrap?
- samtho 4y ago
  SCSS cannot be of use to the 98% of all bootstrap sites that just use the CDN to deliver a compiled stylesheet. The point here is can just change it in the HTML.
  - sussmannbaka 4y ago
    Tailwind cannot be of use to those same sites either, because the compiler needs to process your HTML to cut the generated CSS down to size. You have merely traded one tool for another. If you actually want to change things without preprocessing, your option remains good old HTML and CSS.
    - rendall 4y ago
      Amazing, the lengths that devs go to not to learn CSS fundamentals.
      - kaba0 4y ago
        It’s almost like CSS just fails at its job (though to cut it some slack, it was never designed for “apps”)
awb 4y ago
Now maintain an app with 3 front end devs. With Tailwind there’s no consistency across developers. It’s all highly configurable, but no convention.
- alvarlagerlof 4y ago
  That's when you make components
  - awb 4y ago
    Dev 1 might make a card component with grey text as #999 and Dev 2 might make a footer component with grey text as #888. Components are locally consistent but not globally consistent. Or, let’s say you want to change all your grey text to #777, then you have to go back through all your individual components and hope you didn’t miss anything.
    - kaba0 4y ago
      You ain’t hardcoding colors inline, you refer to them via “variables” basically, so this situation doesn’t exist: https://tailwindcss.com/docs/customizing-colors https://tailwindcss.com/docs/customizing-colors
    - armatav 4y ago
      No buddy, text-gray-600 is globally consistent. So are your own custom defined colors like text-armatav-500. Use the thing before you dismiss it.
- armatav 4y ago
  Have maintained one with 10 FE devs - Tailwind is a godsend. You should have a design with a catalogue of components to build off of so you don’t have 30 card components. It’s a your-team issue, not a Tailwind issue.
acdha 4y ago
That’s a single variable or rule if you want to change it site-wide. If you want an unsemantic one-off, you can do it just like Tailwind by setting a utility class like “p2”.

Now change the padding on card-body. All of a sudden tailwind makes more sense.

ceejayoz 4y ago

Isn’t that a single SCSS variable in Bootstrap?

samtho 4y ago
SCSS cannot be of use to the 98% of all bootstrap sites that just use the CDN to deliver a compiled stylesheet. The point here is can just change it in the HTML.
- sussmannbaka 4y ago
  Tailwind cannot be of use to those same sites either, because the compiler needs to process your HTML to cut the generated CSS down to size. You have merely traded one tool for another. If you actually want to change things without preprocessing, your option remains good old HTML and CSS.
  - rendall 4y ago
    Amazing, the lengths that devs go to not to learn CSS fundamentals.
    - kaba0 4y ago
      It’s almost like CSS just fails at its job (though to cut it some slack, it was never designed for “apps”)

awb 4y ago

Now maintain an app with 3 front end devs. With Tailwind there’s no consistency across developers. It’s all highly configurable, but no convention.

alvarlagerlof 4y ago
That's when you make components
- awb 4y ago
  Dev 1 might make a card component with grey text as #999 and Dev 2 might make a footer component with grey text as #888. Components are locally consistent but not globally consistent. Or, let’s say you want to change all your grey text to #777, then you have to go back through all your individual components and hope you didn’t miss anything.
  - kaba0 4y ago
    You ain’t hardcoding colors inline, you refer to them via “variables” basically, so this situation doesn’t exist: https://tailwindcss.com/docs/customizing-colors https://tailwindcss.com/docs/customizing-colors
  - armatav 4y ago
    No buddy, text-gray-600 is globally consistent. So are your own custom defined colors like text-armatav-500. Use the thing before you dismiss it.
armatav 4y ago
Have maintained one with 10 FE devs - Tailwind is a godsend. You should have a design with a catalogue of components to build off of so you don’t have 30 card components. It’s a your-team issue, not a Tailwind issue.

acdha 4y ago

That’s a single variable or rule if you want to change it site-wide. If you want an unsemantic one-off, you can do it just like Tailwind by setting a utility class like “p2”.