Why you should not use CSS selectors like :not(). Even if you can.
Finally there’s a book on LESS CSS.
Calculating values was already possible with the advent of CSS preparsers, but now real-time calculations are within our grasp.
For those interested in code conventions for LESS CSS and how to perform checks.
One of the things that can make a website come to life is the use of opacity. Think of the translucent text boxes above a large image or a transparency change during a hover. If you’d only support IE9+, opacity will become easier to play with. Because then you’d have rgba and hsla to play with.
A more stable and more aesthetic alternative for !important
I was musing about what is crucial to make an internal project like Bootstrap from Twitter work.
plugins.jquery.com is down and appears not going to be up for a long time.
A quick tip on how to use MSIE filters in Less without throwing an exception.
Less CSS is cool. No doubt about it. But with all those cool advantages like functions, variables and mixins there must be some disadvantages as well, right? It took me some time to find a major but really obvious drawback: you cannot debug CSS the way you used to.
A few new and cool CSS3 styles become realistic options when building a website if you combine them with IE's filter.
Replace a CSS3 selector that's not supported in IE with a CSS2 selector that has support.
You probably didn't notice it, but the way you write CSS affects the rendering speed of the browser. Should you care about that? Most likely not, but it is possible to freeze your web page with inefficient selectors.
This article serves as a download page for the tool PixEm.