vajkri / css Goto Github PK

README.md, line 445

I totally agree with this! But I think it's important to highlight that people should avoid nesting, as it qualifies their selectors, and eventually ruins the idea of OOCSS/BEM - to control the cascade. Some nesting is unavoidable / unpractical, so I'd suggest that:

• Avoid all nesting, unless:
  • You're using pseudo-classes, like `:hover``
  • You're targeting pseudo-elements, like :before
  • You're using a Modifier

Example:

// Bad
.block {
    .block__element {}
    .block__element:hover {}
}

 // Good
.block {}
.block__element {}
.block__another-element {
    &:hover {}
}
.block--modifier {
    .block__element {}
}

README.md, line 38

Tabs should be used for indentation, spacing for alignment only. See Lea Verou's excellent article on the subject for more information.

In general, I very much feel that code shouldn't take views or editors into account - that's why we have editors. So that every developer can format her code to fit her needs, using view settings, not indentation or line breaks. So I'd also prefer not limiting lines to a specific number, as most editors do this fine by themselves.

README.md, line 139

I'm a huge fan of meaningful whitespace, and I still order my properties in groups, so they're easier to find and logically placed. 1508 advocates just listing properties alphabetically, but I personally don't like that. I prefer ar more logical grouping better, e.g.:

1. Box model - display mode, width, height, padding, margin etc.
2. Position - Positioning and offsets
3. Typography
4. Background styles
5. Miscellaneous
6. Transitions

There should a be TL:DR; that summarizes the most important things