You dev? If so, ever popped open a fresh PSD and thought to yourself, “Oh man, I can’t WAIT to get this party started”? I have, and I do, with each new project. As a front-end developer, that specific, exciting moment is my fresh start.
A while ago I wrote a little post discussing my dive into CSS preprocessing, and, at the time, I wasn’t totally convinced that this hot newness was the best approach for my workflow. I shared my internal struggle with bloated output and questioned if this preprocessor business really did save me that much time. When I wrote the article, I had only worked with LESS, one of several popular CSS preprocessors, as it was a project requirement. Many of you fine folks suggested (both on Cognition and off) that I try Sass. Well, I did. Fast-forward 10 months and HOLY TOLEDO THIS FRONT-END DEV IS SERIOUSLY SASSY AND LOVING IT.
I love writing CSS. I really do. I love spinning straw into gold, rescuing HTML elements from browser default styles, curving corners, softening colors, and cushioning containers. I love abstracting complex design systems into powerful classes and efficient declarations while minding the cascade and the rules of inheritance and specificity. I see a site’s visual design as one giant puzzle, patiently waiting to be analyzed, broken down into component parts, and built back up again. I easily spend 70% of my time at Happy Cog developing the presentation layer, so I’ve had my eye on the hot newness that is the Sass / LESS / CSS preprocessor movement for a little while now.
At Happy Cog, process is not sacred. We respect process, but we are constantly looking to improve the way our projects run; especially with regard to transitioning between project phases. Last week, Yesenia Perez-Cruz described how she crafts sweet systems and digital cupcakes. This week, I’m going to show you how we turn those cupcakes into a well-built tower of yummy cupcakery.