voorhoede/riotjs-style-guide

Contribute without merge conflicts on master

phortuin opened this issue · 1 comments

Not sure how to go about this; maybe add all new content at the bottom of a file, then after merging into master, move content into place in a separate (non-content-changing) commit?

I think this issue will resolve itself once the guide stabilises. I've created a separate PR (#26) to re-order some rules.