3 ms·
I'm going to have to agree. Out of all the technologies my team had to juggle while I was on a web team, CSS and its various components (CSS precompilers, sass/
by ckosidows 8y ago
I'm going to have to agree. Out of all the technologies my team had to juggle while I was on a web team, CSS and its various components (CSS precompilers, sass/scss/less, frameworks, etc) were the hardest to keep neat.
You don't _have_ to write CSS well to get it to work. People wouldn't follow naming conventions, wouldn't group common components near others... some people didn't understand CSS precedence and it could lead to incredible confusion, spaghetti code and extra work. Often people re-implemented functionality that was present elsewhere. And problems were exacerbated with sass.
From my perspective, tools that prevent people from writing additional CSS code will have a niche to fill for the foreseeable future.
- weka 8y agoThis is where I have seen stylelint personally come into play and shine. https://github.com/stylelint/stylelint https://github.com/stylelint/stylelint It lints and validates the styles written and does it ruthlessly.
- airstrike 8y agoAs useful as this tool may be, it doesn't seem to prevent redundant or repetitive styles from being created, which is a bigger issue than ensuring correct syntax (since your editor is likely to do that already).