Last night, WordPress DC (which, if you live in/near Washington, D.C. and love WordPress, you really must join) held a round of lightning talks covering a range of WordPress and WordPress-related topics.
I gave a quick five-minute talk on some stupid Sass tricks you can do, including changing the entire color scheme on a page just using one hex color and a whole bunch of Sass color functions. Then I demoed how you can create odd grid systems by again, modifying only a handful of variables.
Seriously, Sass, where have you been all my life?
Or, more truthfully, why did I not appreciate you before now?
In this world where web developers might like to say “we only support the latest browsers,” the truth of the matter is we’re constantly making tweaks and fixes to support browsers that, well, haven’t quite kept up with the times. And a great tool in this thankless task is Modernizr.js, a library of browser feature tests that can tell you “yes, this browser can support CSS3 gradients” or “sorry, but no support for RGBa here.” Modernizr does this by putting the browser the visitor is using through its paces, and then including the capabilities and deficiencies as CSS classes added to the
<html> tag. Continue reading
So, I’ve already posted a bit about how CSS preprocessors (namely, Sass) can save you gobs of time when coding a responsive site. In the week since I posted that, I’ve discovered even more tips and tricks that make preprocessors an almost necessary part of your responsive development portfolio, and I’ll share those with you in the near future.
In the meantime, I wanted to respond to Allison Wagner’s post entitled “Preprocess THIS!”, and address some of the concerns she had regarding Sass and how we at RP3 Agency have begun to address the same issues. Continue reading
When you’re building a responsive website, there’s a formula you learn pretty quickly, and apply pretty often:
target / context * 100 = percentage