Enforced casing and fix inconsistent homepage example #310
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
|
@floatdrop could you give consensus on this PR? We are uncertain about what's standard bc of conflicting documentation (words don't match the example) |
JamesManningR
changed the title
|
Yeah, changes looks right. You can double-check with https://en.bem.info/methodology/naming-convention/ |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Made a decision about how names should look.
Block and elements have no casing guidance so the convention becomes more subjective.
Fixes #302
I feel like I should mention that I read through #94 but there wasn't a strong consensus either way
Apologies for the double PR, I misspelled the branch name