Hey! I'm using basically a Bootstrap-like syntax for my own "framework" at work. We've been running it for almost 4 years so I'd love to respond to everything y

Hey! I'm using basically a Bootstrap-like syntax for my own "framework" at work. We've been running it for almost 4 years so I'd love to respond to everything your saying: 1. it does actually happen but more often than not, individual buttons need some changes. 2. absolutely but that's why we use SCSS to help "cascade" those changes. Unfortunately, those large changes, again, require individual tweaks in some tricky areas. 3. adding classes is always the safer approach. One thing that has helped us is to make sure classes hold little (but valuable!) responsibility. 4. this is an awesome question. So, for us, those little adjustments specified in the post (small margins and so on) were tweaked at component-CSS level while large-changes were kept to our SCSS framework 5. It's basically CSS-in-HTML So my own experience has taught me a general approach of my own: 1. create a framework for your site in SCSS. This includes basic styles for buttons, input boxes, colors, typography, tables etc. but stay away from more complicated styles (like trying to create CSS for a "profile card") 2. keep "component" CSS inside a component. Profile card CSS goes in profile.component.scss 3. overrides/hacks belong to where those overrides/hacks need to happen.