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
The following is cross-posted from the RP3 Magnetisms blog, and is presented here in its original form.
As you read this, I have no idea where you are.
You could be on the train, on your way home, reading this on your smartphone. You could be sitting on your couch, reading this on a tablet like the iPad or Kindle Fire. Or you could be sitting at your desk at work, reading this on your computer, but the numbers show that this is becoming a less likely scenario every day.
And in the end, it shouldn’t matter. People today are confronted with a staggering amount of Internet-based media, from online news sources to blogs to streaming video and audio, and increasingly they’re ditching the traditional computer to consume it. 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