Working with large teams of multiple developers requires consistency. Having a clear styleguide for CSS and general preprocessing rules will make this easier for developers to maintain. Having a standard will mean that from start of a project developers will know what the CSS should look like and will have to spend less time worrying about formatting.
You don't have to. This is only one option that hopefully some people will get on board with. It should mean that individuals and companies don't have to spend time creating their own standards or style guides.
If you want to make suggestions feel free to leave it as an issue or make a pull request. If you would like to be a contributor feel free to email me and state why you would like to be a part of the project.
The two choices available were ordering by group or alphabetically. It was decided that alphabetically would be harder to scan as similar properties would be futher away. Grouping by type signifies a level of inheritance and importance. There is still a level of ambiguiity but through awareness of these groups this should be limited.
Just me, Adam Hughes at the moment. The Frontend team at Rippleffect have contributed also.
I've noticed over the past couple of years the growth of internal styleguides. Google, Git and many others publish their coding styleguides for everyone to see and they're all a bit different. They do share quite a lot of similarities though, most of which I agreed with. Mark Otto's CodeGuide has also influenced this document heavily. Also many other languages (PHP has PSR for example) have styleguides so I thought why not CSS. With the growth of Preprocessors as well has come with a variety of ways to write CSS. Having a standard can help with consistency across all of these different subsets of CSS. Lastly I wanted to put something in place for myself and my team and thought that if it was shared more people may get on board.