Build/create a linter for the styleguide

[msecret]

Find a way to create a programatic linter for the style guide. This means a linter that obeys all the rules of the style guide.

This would be run as part of a build process and could fail if the code doesn't pass.

An existing tool like this might work if we're able to configure it enough so it works for our style guide. My one requirement is that it's only dependency is nodejs as thats more inline with our current front end workflows.

http://csslint.net/
https://www.npmjs.com/package/sass-lint

[jeremiak]

Another potential option/place to start looking at this is with Twitter's Recess

[jeremiak]

Heard about postcss this weekend and thought this task would be a good test of the tool. I published some of my findings/work to a personal repo.

I think postcss would be a really great addition to our CSS toolchain (or nascent one, at least) because it is a pretty lightweight tool that basically gives you tree like access to your CSS. This enables small plugins that do small things like ensuring indentation or spacing.

PostCSS also has a pretty vibrant plugin ecosystem, with the most popular being autoprefixer so putting in our projects can potentially get us pretty far.

@msecret it would be cool to get some 👀 on this when you have a chance

[jeremiak]

Personal note that the "styleguide" linked in #15

[jeremiak]

@msecret and I are tracking progress on this in this 18f/css-linter milestone. Our goal for the first version is to have something launched (published on npm) by the next front end rally

[meiqimichelle]

Exciting!