“monitors changes in the file system. As soon as you save a file, it is preprocessed as needed, and the browser is refreshed.”
“Save your *.less file and, BOOOM, SimpLESS generates a 100% valid standard CSS document out of it. No further steps, it’s that simple.”
“lets you use only unprefixed CSS properties everywhere. It works behind the scenes, adding the current browser’s prefix to any CSS code, only when it’s needed.”
Awesome collection of responsive, multi-size Web layout resources, tools and articles.
“Compass and Sass without all the hassle… a cross-platform app that delivers the power of Sass and Compass to the hands of web designers.”
An app that autocompiles .less files into CSS. I like this idea much more than having JS do the work on the front-end, or for that matter, having the server-side scripting language like PHP or Python compile it.
A “folding” grid for responsive design. An interesting solution to accomodate the use of grids within responsive Web designs. Now to think up a new project to try it out…
A great breakdown on how to switch the order that the content and navigation is displayed based on the browser size, using CSS. A key component to truly responsive Web sites and apps.
Some are silly, but others spark some great ideas.
Paste your CSS into Prefixr and it will automatically add vendor prefixes for CSS3 properties. Even better, there’s an API available, so you can automate the change or hook into it from your favorite IDE.
Makes it easy to generate the CSS for the background-position, width and height of images within a sprite.
We’ve gone too long without a good lint tool for CSS. This one provides syntax checking and applies “a set of rules to the code that look for problematic patterns or signs of inefficiency. The rules are all pluggable, so you can easily write your own or omit ones you don’t want.”
I tend to avoid ’roundup’ posts as they’re usually just link-bait, but this one has managed to present several techniques that I want to dig in and experiment with.
“Beautiful Boilerplate for Responsive, Mobile-Friendly Development”
Why has it taken us so long to have a solution for this? It’s such a basic design requirement. Thanks to Roger Johansson for sharing his method.