Using SCSS and frameworks makes it distressingly easy to hit these limits.
A good semantic model cuts across a single layer of abstraction. If two things have the same structure and info hierarchy, they should share a CSS class.
Organize and clean up your CSS with the Single Responsibility Principle and the Law of Demeter.
My goal was to find something that would be quick to install and easy to use, which ruled out tools like Hammer and CodeKit.
SCSS has numerous beneficial features, include one that I really came to love during my last project. The @extend feature really took the cake.
Our app's CSS is being compiled by the Rails Asset Pipeline, and the colors are fetched over an API call—this poses an interesting challenge.
AngularJS lets you build responsive forms in HTML that let users know what they've changed and whether the information they've entered is valid.
We’ve found CSS classes used to connect JS to the DOM are best kept separate from css classes intended for visual style and layout.
Internet Explorer has terrible support for pseudo selectors. With Selectivizr, we can make that support a little nicer and do some fun stuff with CSS!
How and why to use css sprites, ems, and percentages — demonstrated with a fully-scaleable CSS/HTML card deck using minimal, semantic markup.
Font Awesome gives us the ability to use vector icons in web apps with ease. Using Font Custom, we can create our own icon sets like Font Awesome!