"Purple should never be used outside of officially endorsed Heroku products or without explicit permission."<p>I wonder how others feel about this, I really enjoy breaking apart existing websites and having a guide like this is certainly something I can use for inspiration in any of my projects - but I also wonder about the above clause and any implications it may have on copycat behaviour.
Alex Lande did something similar for WalMart <a href="http://walmartlabs.github.io/web-style-guide/" rel="nofollow">http://walmartlabs.github.io/web-style-guide/</a> ... on the tail of that, he built Radium. We had many conversations in between about the shortcomings of CSS after working on such large projects. <a href="http://projects.formidablelabs.com/radium/" rel="nofollow">http://projects.formidablelabs.com/radium/</a>
GitHub has a similar "living" style guide that is open source: <a href="http://primercss.io/" rel="nofollow">http://primercss.io/</a>
Firebase has a similar style guide:<p><a href="https://www.firebase.com/docs/styleguide.html" rel="nofollow">https://www.firebase.com/docs/styleguide.html</a>
> Purple should never be used outside of officially endorsed Heroku products or without explicit permission.<p>then why opensource it at first place? Bootstrap became popular even though it used some Twitter design styles. How is it a bad thing?<p>When you write this in the lib description,you're making sure nobody's going to use that.
How do people feel about the BEM naming scheme for CSS rules? It looks like overkill when used with a preprocessor but I haven't actually taken time to try it yet. I also find myself absolutely turned off by the idea of a class that mixes underscores and dashes.