A Checkpoint Of My Current Approach To CSS


The way I implement CSS has changed and morphed drastically over the years, with the incorporation of different technologies and methodologies. However I feel somewhat confident in my current methods and thought I would share this for archival purpose.

(What this really means is I’m aware that these methods are open/destined to change further over time. This post serves as a checkpoint of my current approach to CSS)

My current approach to CSS

I write my CSS using SCSS, and implement the ITCSS (Inverted Triangle CSS) architecture using the BEM (Block Element Modifier) naming convention.


The simple (and obvious) reason for using SCSS is that it provides a DRY (Don’t Repeat Yourself) and feature rich way of creating CSS.


ITCSS pushes for styles to be grouped by CSS specificity, instead of arbitrary contexts. This drastically reduces style collisions/leaks and calls an end to specificity wars. However, the benefit of the architecture that I like the most is that styles are very manageable and easily extended into the future.

Why BEM?

Utilising BEM naming means that styles can be built up in a structured and modular fashion. The outputted benefit of this is a library of reusable blocks that can be used intelligently across a wide range of UI compositions.


This implementation has allowed me to follow a pattern that delivers a manageable and reusable library of styles of which I am confident can be highly effective in any project. I’ll follow up with further detail about my implementation of these technologies and methodologies in future posts.

Further reading


Manage large CSS projects with ITCSS by Harry Roberts | Creative Bloq

Bem | Yandex

Back to top Back to Home