# How to Bemify with Sass?

## What is BEM?

BEM is an intuitive way to write scalable CSS. Applying BEM methodology from the very start provides us an easy-to-follow, modular structure which also renders really fast.

BEM methodology was invented at Yandex to develop sites which should be launched fast and supported for a long time. It helps to create extendable and reusable interface components.

## Refactoring existing CSS to apply BEM with Sass (Bemifying)

Following BEM principles from the first line of CSS is highly recommended, however it might happen that we already have some written and/or we are using some frameworks (wich we would like to get rid of) and we would like to improve on maintainability. In that case Bemifying is the way to go.

The issue with refactoring our CSS code is that it is strongly related to our markup and logics. Refactoring something in multiple places and jumping back and forth between different files can be a pain in the butt (specially when testing & debugging), therefore a flat, step-by-step technique is required where we don’t have to shift our attention from the CSS code.

With this technique we can refactor our CSS and apply BEM without touching any HTML or JavaScript. This comes very handy for testing, and when the CSS refactoring is done and tested, we can begin refactoring our HTML and JS.

In the following example let’s assume we have a login screen, with a login box and a signup box.

.login {
/* ... */
h1 { /* ... */ }
h1.warning { /* ... */ }
.email-field { /* ... */ }
&.condensed { /* ... */ }
&.condensed .email-field { /* ... */ }
}

.signup {
.signup h1 { /* ... */ }
.signup h2 { /* ... */ }
}


## Steps:

1. Create a BEM structured, individual file
2. Create an alias to remove nesting eg.: .login > h1 { /* ... */ }
3. Create BEM compatible element eg.: .login__headline { /* ... */ }  with the properties
4. Extend alias with BEM elem eg.: .login > h1 { @extend .login__headline; }

### 1. Create a BEM structured, individual file

I recommend to have 1 UI component / file. Therefore I would split the code above into 2 different files, as they are 2 different components: something like c-login-box.scss and c-signup-box.scss (Why prefix it with c-?) Each of these files containing UI components should follow an easy to understand and standardized format. Start up with the following:

/* Block */
/* you will insert code here */

/* Modifiers */
/* you will insert code here */

/* Elements */
/* you will insert code here */

/* Original - block */
/* ... */
h1 { /* ... */ }
h1.warning { /* ... */ }
.email-field { /* ... */ }
&.condensed { /* ... */ }
&.condensed .email-field { /* ... */ }
}

/* Original - modifiers */
/* you will insert code here */

/* Original - elements */
/* you will insert code here */


### 2. Create alias for nested elements

Our .login element is our block element, so it is in its place (–> no need for creating an alias). But h1 element is nested, so it should be a Bem element. Our code becomes:

/* Block */
/* Modifiers */
/* Elements */

/* Original - block */
...
h1.warning { ... }
.email-field { ... }
&.condensed { ... }
&.condensed .email-field { ... }
}

/* Original - modifiers */

/* Original - elements */
.login > h1 { /* ... */ }



### 3. Create BEM compatible element

Move the properties to a BEM compatible element.

/* Block */
.c-login { /* ... */ }

/* Modifiers */

/* Elements */

/* Original - block */
h1.warning { /* ... */ }
.email-field { /* ... */ }
&.condensed { /* ... */ }
&.condensed .email-field { /* ... */ }
}

/* Original - modifiers */

/* Original - elements */


At this point we have no relation between our old (.login and .login > h1) and new (.c-login, c-login__headline) elements, so we need to connect the dots.

### 4. Extend alias / original element with BEM element

This happens with the @extend Sass command..

/* Block */
.c-login { /* ... */ }

/* Modifiers */
/* Elements */

/* Original - block */

h1.warning { /* ... */ }
.email-field { /* ... */ }
&.condensed { /* ... */ }
&.condensed .email-field { /* ... */ }
}

/* Original - modifiers */

/* Original - elements */



## The final result

After going through all the elements and modifiers, our code should look like this:

/* Block */
.c-login { /* ... */ }

/* Modifiers */
.c-login--condensed { /* ... */ }

/* Elements */
.c-login__email-field { /* ... */ }
.c-login__email-field--condensed { /* ... */ }

/* Original - block */

/* Original - modifiers */

/* Original - elements */


At this point we have succesfully restructured our CSS and applied BEM without touching any HTML or JS. We can start testing, and if we are happy with the result we can continue on refactoring our next component, or jump to the markup or logics.

Please note: the .email-field element used to be dependent on its parent and changed values whether .login had a modifier class or not. We have changed this structure in a way that .email-field is now not depending on any other elements but itself. This is one of the principles of BEM, and therefore refactoring the HTML actually means restructuring it, not just renaming the classes.

After succesfully refactoring our HTML and JS files, we can remove the original parts.

## Bemifying template

/* Block */
.block { /* ... */ }

/* Modifiers */
.block--modifier01 { /* ... */ }
.block--modifier02 { /* ... */ }

/* Elements */
.block__element01 { /* ... */ }
.block__element02 { /* ... */ }
.block__element02--modifier01 { /* ... */ }

/* Original - block */