What is the BEM naming convention in CSS?

This chapter brings you what is the BEM naming convention in CSS? , has certain reference value, friends in need can refer to it, I hope it will be helpful to you.

1 What is the BEM naming convention

Bem is the abbreviation for block, element, and modifier. It is a front-end CSS naming methodology proposed by the Yandex team.

- Dash: Used only as a hyphen to represent a connection mark between multiple words of a block or a sub-element.
__Double underline: Double underline is used to connect blocks and sub-elements of the block
_ Single underscore: A single underscore is used to describe a state of a block or a sub-element of a block

BEM is a simple and very useful naming convention. Make your front-end code easier to read and understand, easier to collaborate with, easier to control, more robust and unambiguous, and more rigorous.

1. BEM naming pattern

The BEM naming convention pattern is:

.block {}
.block__element {}
.block--modifier {}

Each block (block) name should have a namespace (prefix)
Block represents a higher level abstraction or component.
block__element represents the descendants of .block and is used to form a complete .block as a whole.
block--modifier represents different states or different versions of .block

Use two hyphens and underscores instead of one so that your own blocks can be delimited with a single hyphen . Such as:

.sub-block__element {}
.sub-block--modifier {}

2. The benefits of BEM nomenclature

The key to BEM is that you can get more descriptions and a clearer structure, and you can know the meaning of a certain mark from its name. Therefore, by looking at the class attribute in the HTML code, you can know the relationship between elements.

Conventional nomenclature example:

<div class="article">
    <div class="body">
        <button class="button-primary"></button>
        <button class="button-success"></button>
    </div>
</div>

This way of writing can understand the meaning of each element from the DOM structure and class naming, but it cannot clarify its true hierarchical relationship. When defining CSS, you must also rely on hierarchical selectors to limit the constraint scope to avoid cross-component style pollution.

Examples using the BEM naming method:

<div class="article">
    <div class="article__body">
        <div class="tag"></div>
        <button class="article__button--primary"></button>
        <button class="article__button--success"></button>
    </div>
</div>

Through the BEM naming method, the module hierarchical relationship is simple and clear, and there is no need to make too many hierarchical choices when writing css.

2. How to use BEM nomenclature

1. When should you use BEM format

The trick to using BEM is , you need to know when and what should be written in BEM format. Not every place should use BEM naming. The BEM format should be used when explicit module relationships are required. For example, if there is just a single public style, there is no point in using the BEM format:

.hide {    display: none !important;}

2. Using the BEM format in the CSS preprocessor

One disadvantage of BEM is the naming method It is long, ugly and poorly written. Compared with the convenience brought by the BEM format, we should look at it objectively. Moreover, CSS is generally written using preprocessor languages ​​such as LESS/SASS, and it is much simpler to write using its language features.

Take LESS as an example:

.article {
    max-width: 1200px;
    &__body {
        padding: 20px;
    }
    &__button {
        padding: 5px 8px;
        &--primary {background: blue;}
        &--success {background: green;}
    }
}

3 Using BEM format in components of popular frameworks
In the currently popular front-end frameworks such as Vue.js / React / `Angular, there are compilation implementations of CSS component-level scope. The basic principle is to use the CSS attribute selector feature to generate different attribute selectors for different components. .
When you choose this local scope approach, the BEM format may seem less important in smaller components. However, for public and global module style definitions, it is still recommended to use the BEM format.
In addition, for public components released to the outside world, generally for the sake of style customization, this local scope method is not used to define component styles. This is where using the BEM format will also come in handy.

4 Avoid the .block__el1__el2 format
In deeply nested DOM
structure, overly long style name definitions should be avoided.
The final level should not exceed level 4, otherwise it will increase the difficulty of reading comprehension

3. Summary

One of the most difficult parts of BEM It is clear where the scope starts and ends, and when to use it or not to use it. As you accumulate experience with continuous use, you will slowly know how to use it, and these problems will no longer be a problem. There is no good or bad technology, only the right one is best.

Recommended writing and style

//常规写法：
.xxx{}
.xxx__item{}
.xxx__item_current{}

// 嵌套写法
.xxx__item_current .mod-xxx__link{}

推荐：
.xxx{}
.xxx__item{}
.xxx__item_hightlight{}
.xxx__product-name{}
.xxx__link{}
.xxx__ming-zi-ke-yi-hen-chang{}

// 嵌套写法
.xxx__item_current{
    .xxx__link{}
}

//对应的HTML结构如下：

<ul class="xxx">

	<li class="xxx__item">第一项

		<div class="xxx__product-name">我是名称</div>

		<span class="xxx__ming-zi-ke-yi-hen-chang">看类名</span>

		<a href="#" class="xxx__link">我是link</a>

	</li>

	<li class="xxx__item xxx__item_current">第二项 且 当前选择项

		<div class="xxx__product-name">我是名称</div>

		<a href="#" class="xxx__item-link">我是link</a>

	</li>

	<li class="xxx__item xxx__item_hightlight">第三项 且 特殊高亮

		<div class="xxx__product-name">我是名称</div>

		<a href="#" class="xxx__item-link">我是link</a>

	</li>
</ul>

##

The above is the detailed content of What is the BEM naming convention in CSS?. For more information, please follow other related articles on the PHP Chinese website!