What is BEM?

BEM stands for Block, Element, Modifier. It's a naming convention that helps divide the user interface into independent blocks, making frontend code more maintainable and scalable. The methodology uses a specific pattern for CSS class names that makes the relationship between HTML and CSS clear and consistent.

Core Components

1. Block

A standalone component that is meaningful on its own. Think of it as an independent piece of your interface.

/* Examples of Blocks */
.header { }     /* Header block */
.menu { }       /* Navigation menu block */
.button { }     /* Button block */
.form { }       /* Form block */

2. Element

A part of a block that has no standalone meaning. Elements are semantically tied to their block and are denoted by two underscores (__).

/* Examples of Elements */
.header__logo { }      /* Logo inside header */
.menu__item { }        /* Menu item */
.button__icon { }      /* Icon inside button */
.form__input { }       /* Input inside form */

3. Modifier

A flag on blocks or elements that changes appearance or behavior. Modifiers are denoted by two hyphens (--).

/* Examples of Modifiers */
.button--large { }           /* Size modifier */
.button--primary { }         /* Style modifier */
.menu__item--active { }      /* State modifier */
.form__input--disabled { }   /* State modifier */

Practical Example

Here's a complete example showing how BEM components work together:

<form class="form form--theme-dark">
    <div class="form__group">
        <label class="form__label">Username</label>
        <input class="form__input form__input--required" type="text">
        <span class="form__error">This field is required</span>
    </div>
    <button class="form__button form__button--primary">
        <span class="form__button-text">Submit</span>
    </button>
</form>

/* Block */
.form {
    padding: 2rem;
    border-radius: 8px;
}
 
/* Block Modifier */
.form--theme-dark {
    background: #333;
    color: white;
}
 
/* Elements */
.form__group {
    margin-bottom: 1rem;
}
 
.form__label {
    display: block;
    margin-bottom: 0.5rem;
}
 
.form__input {
    width: 100%;
    padding: 0.5rem;
    border: 1px solid #ddd;
}
 
.form__button {
    padding: 0.75rem 1.5rem;
    border: none;
    border-radius: 4px;
}
 
/* Element Modifiers */
.form__input--required {
    border-color: #ff4444;
}
 
.form__button--primary {
    background: #007bff;
    color: white;
}

Why Choose BEM?

BEM provides several key advantages for CSS architecture:

Clarity and Maintainability
- Self-documenting class names
- Clear relationship between HTML and CSS
- Easy to understand component structure
Reusability and Modularity
- Components can be copied between projects
- Independent blocks prevent style leaks
- Modifiers enable flexible variations
Scalability
- Consistent naming across large projects
- Easy to extend and modify
- Supports team collaboration
Reduced Specificity Issues
- Flat CSS hierarchy
- Predictable specificity
- Easier to override styles when needed

Best Practices

1. Keep Names Simple and Clear

/* ✅ Good */
.search__input { }
.card__title { }
 
/* ❌ Avoid */
.site-search-box__input-field { }
.card__primary-heading-text { }

2. Avoid Element Chains

/* ✅ Good */
.card__title { }
.card__meta { }
 
/* ❌ Avoid */
.card__header__title { }
.card__footer__meta__date { }

3. Use Modifiers Wisely

/* ✅ Good */
.button--large { }
.button--primary { }
 
/* ❌ Avoid */
.button--large-primary-disabled { }

4. Keep Components Independent

/* ✅ Good */
.header__nav { }
.nav__item { }
 
/* ❌ Avoid */
.header .nav .nav-item { }

Common Patterns

1. Layout Components

.layout { }
.layout__sidebar { }
.layout__main { }
.layout--reversed { }

2. Interactive Components

.dropdown { }
.dropdown__trigger { }
.dropdown__menu { }
.dropdown--open { }

3. Form Components

.form-field { }
.form-field__label { }
.form-field__input { }
.form-field--error { }

Integration with Modern CSS

Using Custom Properties

.button {
  --button-bg: #007bff;
  --button-color: white;
  background: var(--button-bg);
  color: var(--button-color);
}
 
.button--secondary {
  --button-bg: #6c757d;
}

With CSS Grid

.grid {
  display: grid;
  gap: 1rem;
}
 
.grid--cols-2 {
  grid-template-columns: repeat(2, 1fr);
}
 
.grid__item { }
.grid__item--span-2 {
  grid-column: span 2;
}

Common Pitfalls to Avoid

Over-nesting Elements
- Keep the structure flat
- Avoid deep element chains
- Create new blocks for complex components
Inconsistent Naming
- Stick to a single naming convention
- Use clear, descriptive names
- Document any exceptions
Overusing Modifiers
- Keep modifications simple
- Use semantic names
- Avoid boolean-style modifiers when unnecessary

Conclusion

BEM methodology provides a robust foundation for writing maintainable CSS. Key takeaways:

Use blocks for independent components
Elements represent component parts
Modifiers change appearance or behavior
Keep naming consistent and meaningful
Avoid excessive nesting
Think in components

Following these principles will help you create more maintainable and scalable CSS code that's easier to work with in team environments.

Mastering BEM Methodology: Writing Clean and Maintainable CSS

References

BEM Official Documentation

Understanding the CSS BEM convention