4 ms·

I actually prefer coding CSS from scratch. Color schemes and making things look nice IS hard, for my previous and current projects I had to get feedback from fr

I actually prefer coding CSS from scratch. Color schemes and making things look nice IS hard, for my previous and current projects I had to get feedback from friends, family, end users, graphic designers, etc. UX is hard, it's a different field than programming, but there is a method, research, and science behind it. Here's a good resource for UX: https://goodui.org https://goodui.org And here is one for color theory: https://uxplanet.org/color-theory-brief-guide-for-designers-76e11c57eaa https://uxplanet.org/color-theory-brief-guide-for-designers-...

devmunchies 8y ago
I also really enjoy building CSS UIs from scratch, but editing existing stylesheets is a pain point. Band-aid after band-aid. I think keeping UI components tiny and coupling the stylesheets with the component is the best way I've seen (not necessarily styled components, just styles in the same folder as the component.) As the component is removed, its easy to nuke the stylesheet with surgically removing related styles and not breaking something else.
- monkpit 8y ago
  Why not styled components? It’s what immediately jumped to my mind while reading your comment, until you said otherwise :)
  - arvinsim 8y ago
    Styled components, CSS-in-JS and CSS modules largely solve the same problem. I think it's just a matter of preference.
- hycaria 8y ago
  >I also really enjoy building CSS UIs from scratch, but editing existing stylesheets is a pain point. Band-aid after band-aid. I feel the same. I fiddled with css on personal projects just fine, but in my job, diving into years of accumulated, imbricated classes is a nightmare and even though I try, 80% of the time I end up passing the problem to the design team.
thirdsun 8y ago
Same here. I recommend to avoid bloated kitchen sink frameworks like Bootstrap and Foundation unless you don't plan to do any customizations at all and only include the parts you actually use. Otherwise you'll realize that you're actually fighting the framework by trying to override it.

devmunchies 8y ago

I also really enjoy building CSS UIs from scratch, but editing existing stylesheets is a pain point. Band-aid after band-aid. I think keeping UI components tiny and coupling the stylesheets with the component is the best way I've seen (not necessarily styled components, just styles in the same folder as the component.) As the component is removed, its easy to nuke the stylesheet with surgically removing related styles and not breaking something else.

monkpit 8y ago
Why not styled components? It’s what immediately jumped to my mind while reading your comment, until you said otherwise :)
- arvinsim 8y ago
  Styled components, CSS-in-JS and CSS modules largely solve the same problem. I think it's just a matter of preference.
hycaria 8y ago
>I also really enjoy building CSS UIs from scratch, but editing existing stylesheets is a pain point. Band-aid after band-aid. I feel the same. I fiddled with css on personal projects just fine, but in my job, diving into years of accumulated, imbricated classes is a nightmare and even though I try, 80% of the time I end up passing the problem to the design team.

thirdsun 8y ago

Same here. I recommend to avoid bloated kitchen sink frameworks like Bootstrap and Foundation unless you don't plan to do any customizations at all and only include the parts you actually use. Otherwise you'll realize that you're actually fighting the framework by trying to override it.