Refactoring with Sass
I’ve been spending a lot of time working on my front end skills. One of the technologies I’ve been learning is Sass. Sass is a CSS preprocessor, meaning you write your Sass code that is then compiled to CSS to be read by the browser. Using a CSS preprocessor like Sass is pretty useful because you can incorporate tools that are not available in CSS. In this post I will show three ways I refactored my styling in my app Stitcher with Sass. Before I show any code, it is important to note, quickly, that Sass has two supported syntaxes: Sass and Scss. I will be using Scss.
Sass has a few tools that are frequently used: variables, mixins, nesting, and extend. In Stitcher, I made the best use of variables, nesting, and extend. Variables in Sass are marked with “$” and can be set globally or locally. I set the following variables:
I employed these variables in a variety of places like this:
Nesting selectors with Sass is very useful, but, as the documentation and many articles point out, it should be used with caution. If you overuse nesting, it’s very easy to override other CSS properities but can be tricky to debug. In Stitcher, I used nesting to collect button effects using the “&” as you can see below.
Lastly, I’d like to share my use of Sass’s extend tool. This is a useful tool that allows you to define a group of CSS declarations together and use them throughout your stylesheet. You name the collection with an “%” and then write “@extend %[name]” wherever you’d like the collection to be used. I noticed that throughout Stitcher I was calling both “display: flex” and “flex-direction: column” frequently and decided to make that an extend and applied the same logic to aligning items and justifying content in the center.
These are just a couple ways I have refactored my Stitcher stylesheet with Sass. I’m really looking forward to using Sass in a project from the very beginning. Many of my previous projects were written quickly within a short deadline and my CSS is functional, but a bit of a mess. While learning Sass, I came across two ways that people commonly organize their stylesheets. They seem to either have all their Sass in one directory separate from their components or they have a component-specific stylesheet included within the component’s folder. I’m going to approach my next project in one of these two ways in order to maintain more organized and easy-to-read styling.
Resources:
Sass Documentation