-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Naming conventions #1
Comments
Yes ok, even if
Perfect
Perfect
Perfect
I use this convention and I find it very useful. So yes for me.
In fact this point of view is interesting. I'm not used to code like that. Since I added my media querie directly with the root class to change. But I find it rather good, and useful |
|
Are you ok with for .org-B {}
.org-B-menuLink {} /* hamburger */
.org-B-menu {} /* list of links */
.org-B-menu-link {} /* links in the menu*/ |
Update
|
I want to write down our conventions base on suit ones https://github.com/suitcss/suit/blob/master/doc/naming-conventions.md
Here is what I'm thinking about
My concern is for mq for components. We are not likely to be able to use element queries soon, so we should mq has component modifier. eg:
What do you think about that @bloodyowl @magsout ?
The text was updated successfully, but these errors were encountered: