BEM Comparison
- Dominant language
- CSS
- Stars
- 840
- Forks
- 29
- PR merge metrics
- No merged PRs in 30d
Description
I think a comparison with BEM would be really great in the FAQ. A why of csstyle.
The biggest change I've noticed is the modifier, and I think there's some potential for issues where components overlap. See: https://en.bem.info/faq/#why-include-the-block-name-in-names-of-modifier-and-element particularly the part about ambiguity of what a modifier belongs to[1]. and potential for modifier overlap. I was interested in your considerations & solutions around this sort of problem?
[1] For clarity, I mean this line:
> This kind of HTML markup leaves it unclear as to whether the modifier relates to the menu item (menu__item.active) or the button (button.active). Specifying the block name (button_active) indicates the BEM entity to which the modifier will be applied.
Contributor guide
Research direction
Start by reviewing the project's FAQ and the linked BEM FAQ section on modifier ambiguity. Determine what comparison and explanation of csstyle's rationale are needed, then consider the work complete when the FAQ addresses modifier ownership, overlap concerns, and the relevant BEM trade-offs.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- css
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100