Sass Clearfix Mixin

There are a few ways to implement the clearfix hack but the following Sass Mixin has been in my toolbox for the last year thanks to this article on Nicolas Gallaghers blog. Usage:

URL as a Sass Variable

Do you ever find yourself trying to remember the URL path of you images directory? Well with Sass you can quickly add the path to the desired location and just use the variable throughout your code. Sass to the rescue. All you need to do is declare the variable and then use the interpolation syntax … Read more

Converts pixels to EMs with Sass

If you like using pixel values but understand that having your fonts set in EMs works better, especially when tackling responsive web design then this little Sass function will become super handy. This function automatically converts pixels to EMs with Sass so that you don’t have to manually calculate them. The function takes two arguments, … Read more

SassyLists moving to 2.x

Hugo Giraudel shares his journey of building SassyLists. SassyLists is a toolbox providing almost 40 functions to help working with Sass lists. The Sass default list API is very light therefore you might need some extra functions, especially if you are building a Sass framework or a robust grid system.

Handy Sass Mixins

Mixins are one of the most powerful features of Sass. Mixins allow for efficient and clean code repetitions as well as an easy way to adjust your code with ease. If you are using Sass in your development workflow, no doubt you are using some of the mixins that I have covered below but some might also be new and helpful.

Why You Scared of Sass?

During a discussion a few weeks ago with an amazing front-end developer I was blown away that they hadn’t even given CSS preprocessing a go. I was bamboozled.

Learning something new, be it Sass, Less, YUI, Grunt, etc can always be a little daunting but making the time to ‘try’ is an important part of developing for the web.

If you get overwhelmed with all these new fandangle ‘things’ people are talking about, be mindful that you don’t necessarily have to adopt them. Having a basic understanding and awareness of what they do is all you really need to know. If the ‘thing’ really fits into your development workflow, then it’s a win. Dedicating more time to really learn and adopt it should be a no brainer. If it doesn’t, then at least you have the peace of mind that you’re not doing things in a inefficient manner.