What I Consider when Writing CSS
Date: Thu Apr 04 2019 Tags: CSS, Opinion, Maintainability
At a high level, all of these considerations break down into two fronts. The Users download and the Developer ergonomics.
For the users download we want to deliver only the CSS necessary for what they are viewing. And for it to be built on clean HTML.
For the Developers ergonomics we want to break CSS down into manageable chunks, create separation on features and allow reusability. And maybe most importantly, we want our CSS solution to scale and allow for growth with the project.
Write only what you need and writing it once
CSS is flexible, and allows you to do so much. But there is danger in the large amount of flexibility afforded by CSS.
When I write CSS I don't want to repeat myself more than I have to. But there is a balancing act between writing specific CSS for a core feature and general CSS for generic features.
The classic example is button styles. Buttons need to be consistent and a Developer should be able to update all buttons in one location. When a button is styled on a per-feature bases this can lead to CSS getting repeated in each feature.
This repetition can also lead to inconsistent button designs as well as problems updating it in the future.
Don't let tools bloat your final CSS
Tools create an abstraction away from your final CSS. Which has greatly helped the developer ergonomics around CSS. Especially when you live in a world of browser prefix's. However this abstraction hides the CSS you're creating.
Sass for example is a popular CSS preprocessor with features like mixin's, variables and loops. But there are times when the distance from CSS can lead to large amounts of repeated CSS with very minimal developer ergonomic gain.
To demonstrate some of the CSS bloat I have seen I put together two examples on SassMister (SassMister being a playground for SASS that compiles it in the browser).
The first example shows mixins causing repeated CSS vs placeholders expanding only the CSS selector. https://www.sassmeister.com/gist/160390ca9b723bbf08f1d000fa2fa2a7
The second shows the each directive adding svg flag backgrounds. Which I have seen cause over 1000 lines of repeated CSS in live Production code. https://www.sassmeister.com/gist/160390ca9b723bbf08f1d000fa2fa2a7
FYI: If the CSS doesn't load, just put a space into the SASS terminal.
Try not to let CSS Dictate your HTML
First off, a cavate, unfortunately this can't always be avoided. Technologies like Grid and Flex have reduced the need for extra HTML scaffolding dramatically, but its not always avoidable.
This doesn't mean you should let CSS dictate the HTML you write. Treat HTML as a first class citizen, it is a language in its own right. Assistive technologies and search engine crawlers rely on it to understand your site. Two very important parts of any website. Treat it with respect and you will reap the rewards.
Be aware of your Media Queries
In my experience, media queries get more attention spent on the Developer ergonomic front, then in the User download front. The primary reason I say this is that media queries can be dynamically added to the page using the link media attribute.
This means that all of your CSS that you're using to make your site look nice on desktop and tablet, doesn't need to be downloaded by phone Users. So a clean media query strategy is a must for any project.
You also only need 1 media selector for each size you're targeting. Which hasn't been the common strategy I have come across.
The most common strategy I come across is media queries being added into the same file as the features styles. Leading to repeated media queries across multiple features. Essentially needlessly repeated CSS.
Think About the Future (But not too much)
Things change, and this needs to be part of the approach when implementing CSS. If a button design updates brand wide, it should update site wide in one easy place. And If a current feature has to fit into a new page it should be easily extended to achieve the new requirements.
All of this can be done by brute forced of course. But creating a clear way of working with CSS that stays predictable and maintainable is the primary success factor for any CSS system.
Scale in CSS is all about the future features not getting in the way of the past features, and a strategy that doesn't lead to a poor User download or a frustrating Developer experience.
CSS is fun, complex, and has a lot to consider. These are the abstract ideas that I like to think about when writing CSS. Different CSS mythologies can help guide you in avoiding these issues. And some tools can just make them not a problem for the User. Just try to be aware because CSS won't yell at you, its that good friend that just helps you out without mentioning it. Even if its harming the friendship.
If you have any thoughts do reach out to me on twitter @LiamMyles92