From a1dccaa8ffe1e2d55f2269339a8a14d4b0c2fefa Mon Sep 17 00:00:00 2001 From: Ingo Schommer Date: Thu, 5 May 2016 20:44:38 +1200 Subject: [PATCH] Add linting note in coding conventions --- docs/en/00_Getting_Started/07_CSS_Coding_Conventions.md | 7 +++++++ 1 file changed, 7 insertions(+) diff --git a/docs/en/00_Getting_Started/07_CSS_Coding_Conventions.md b/docs/en/00_Getting_Started/07_CSS_Coding_Conventions.md index 5014cb8ff..2324b87c1 100644 --- a/docs/en/00_Getting_Started/07_CSS_Coding_Conventions.md +++ b/docs/en/00_Getting_Started/07_CSS_Coding_Conventions.md @@ -25,6 +25,13 @@ and the [BEM](http://getbem.com/) methodology (block-element-modifier). File naming and style include ordering is inspired by [ITCSS](https://www.xfive.co/blog/itcss-scalable-maintainable-css-architecture/). +## Linting + +We use [SCSSLint](https://github.com/brigade/scss-lint) to ensure all new SCSS +written complies with the rules below. Please consider installing it +in your development environment (you'll need Ruby). There's also +quite a few [SCSSLint IDE integrations](https://github.com/brigade/scss-lint#editor-integration) +which highlight any linting errors right in your code. ## File and Folder Naming