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
- org-{mq}-{utility} (we have did that for (grid) utils)
- org-B (classic)
- org-B-e(-e) (classic)
- org-B--m (classic)
- org-B--{mq} ? (it's a modifier ? here is an important point I want to "solve")
- org-B.is-{state} (should we get this? it's sort of a modifier)
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:
.org-B--minS .org-B-e {
display: inline;
}
.org-B--minL .org-B-e {
display: block;
font-size: 2rem;
}
What do you think about that @bloodyowl @magsout ?
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 ?