Best Practices - SCSS Styleguide about scss-mixins HOT 5 CLOSED

• use stylelint
• Naming Conventions
  • don't reuse parent's class name in child's classes
  • keep order of declaring classes and it states (firstly declare state of current class then declare nested children ie. .active is higher than nested child class)
  • class should be described by entity, behaviour, state or look
• two (2) spaces indents, no tabs
• camelCase in react, rest in hypen-case
• use mixins for margins and paddings
• don't use hardcoded values in scss
• assign value to variable in variables.scss
• first use mixins, then override styles (if needed)
• never go more than 3 levels deep (add stylelint rule)

from scss-mixins.

• https://github.com/airbnb/javascript
• don't style elements, style classes
• don't use id if not needed
• how to use with react
• global styles
• styles from another packages

from scss-mixins.

• color naming
• creating JavaScript-specific classes to bind to, prefixed with .js-

from scss-mixins.

• - reboot.css or normalize.css
• - getting started - how to create first project and, how to configure it, how to style my first component
• - how to use typography

from scss-mixins.

@ArekRado

• - how to use typography

shouldn't this be in typography documents? or you have special purpose and want it to be described? (example pls)

also this

• - getting started - how to create first project and, how to configure it, how to style my first component

shouldn't be in Best Practices - SCSS Styleguide in my opinion

I think we should rename this issue for 'Best Practices - SCSS Styleguide' so it won't be so generic

from scss-mixins.