BEM - Building 'em modular
summary
Claims that BEM (Block Element Modifier) solves CSS cascade, reuse, and naming at scale and shows a decade of deployment inside Yandex across 50+ services with a dedicated 30‑person front‑end core and an internal Lego library of reusable blocks. Tools include a block‑wise file structure, build bundles, declarative BM tree templating, and open source packages B-core and B-components. The system runs in production, supports JS and server/browser rendering, and is actively maintained.
AI-written summary · about
chapters (29)
- 0:00Intro
- 0:53Vladimir
- 2:52Where pain comes from
- 4:50CSS has no scoping
- 5:06Specificity conflicts
- 5:22How to overwrite
- 5:49Non-deterministic matches
- 5:59Removing unused code
- 6:29BEM Methodology
- 6:45elements
- 7:12cat_state_wet
- 7:24Naming convention
- 7:47Some of BEM principles
- 8:45Why no selectors on tags?
- 9:40Hard to override
- 10:45Library time!
- 11:45File system
- 12:01BEM tree
- 14:16Declarative CSS
- 17:10BEM templates
- 18:23Web components
- 18:54BEM blocks
- 21:34Problems we faced
- 25:28BEM grew into
- 27:26Core team and the community
- 30:31Activities
- 31:41With methodology
- 31:55With the platform
- 32:39With what you have
related talks
40mBEM: complete guide for your component frontend development
42mbem components — like Bootstrap, only better
44mThe Future is in Pieces
43mHow to build your reusable UI component library like a pro
32mWhat's New in bem-core@v4
49mComponent-Based Modular Development
41mWeb Components: Maintaining and Reusing your Frontend
32mBuilding UI at Enterprise Scale with Web Components