Rob Cherny

https://github.com/isobar-idev/code-standards/blob/master.next/content/en/general.md

I think that we'll need to update this since we may have changed our tab settings.

This is _very_ cool. As indicated we have a new branch. Our hope is to be publishing that work in progress here in the near future. Please keep an eye...

Note that master.next has been pushed to master. It's long and will be going through more edits, but if anyone wanted to translate...

We have a recent list of content [here](https://github.com/isobar-idev/code-standards/wiki/Useful-Links-and-Resources) that is potentially worth examining ...

- Test Driven Development - Build Systems (e.g. Grunt, etc.) - Build systems and preprocessors are a tricky one. Should not be heavy content but brief overviews, IMHO

I think for most automation tools we're probably going to shy away from doing too much of a deep dive other than some pointers to resources. Their availability and discussing...

The current draft of the standards includes a reference to editor configurations. The intent was something along those lines for sure. https://github.com/isobar-idev/code-standards/blob/master.next/content/en/general.md > It's worth establishing conventions at the project...

We could probably do more here. Only real reference currently is: https://github.com/isobar-idev/code-standards/blob/master/src/content/en/general.md#code-consistency

Our current TOC is generated by JavaScript when the page is loaded. However, we could probably generate the TOC from the Markdown during the build with something like: https://github.com/jonschlinkert/markdown-toc