One of the core selling points of writing styles using Sass (or SCSS) is being able to use variables. This isn’t as novel a concept now that we have CSS variables native to CSS, but it’s still a big part of Sass. They work as you’d expect for the most part with one exception, the !default keyword. It’s not a feature most people take advantage of that often or maybe even know about, but let’s take a look at how this works so you can leverage it should the need arise.
Pretty interesting read pointing to a trend that Chrome is becoming the new IE6. I've seen the 'best in Chrome' messages more than I'd like recently. This is a bummer of a trend. Hopefully this doesn't continue.
It took a bunch of people I follow on Twitter to decide to take a Twitter break for me to really start to think about how I use Twitter.
As much work as I do in HTML I often forget all the different elements we have at our disposal. I think the ones that are most often forgotten and also most useful are the inline elements.
Sass version 3.3.0 brought with it a handy new feature called SassScript Maps. These things are pretty powerful and can be used in quite a few interesting scenarios, but today we're going to take a look at how they can make our work with color variables even easier.
I've been spending a fair amount of time working with microdata recently and I've found this Google Structured Data Testing Tool an incredibly useful to have a tool to help me test whether or not my markup has been correctly written.
This post from html5 Doctor is more than four years old, yet it's still one of the best resources on microdata that I’ve found.
Reading through a spec is not always super useful for actually understanding how to use it, but it isn’t a bad thing to have on hand.
Here’s a brief introduction to the concept of microdata from Google. It’s a nice resource with a handful of examples attached. SEO is definitely something that microdata improves so info coming straight from the horse’s mouth is something we should pay attention to.