Move coding style guidelines to somewhere more appropriate #517
Description
@manthey points out that the Tangelo docs include "Coding Style Guidelines" that don't describe the Python code style in the Tangelo codebase. This is because that section is meant for JavaScript code that might be included in Tangelo. The section doesn't belong here for a few reasons:
- There is no corresponding style guide for Python code, and the existing section doesn't make clear that it's for JavaScript code.
- Tangelo no longer makes a blurry distinction between core and "other" - "other" now clearly belonging in Tangelo plugins, making it somewhat less critical that they follow the Tangelo style guides. If a plugin were to be included in Tangelo's bundled plugin list, the style guide would apply strictly again.
There are a couple of ways to fix this. One is to make clear in the title of the existing section that it's meant for JavaScript code. Better would be to rip the whole section out and put it in CONTRIBUTING.md or somewhere else. If we do that, we might need to include a Python style guide as well. However, my intuition tells me that addition wouldn't need to be as long as the JavaScript rules, since Python style has less variation in the wild, due to the existence of "Pythonicness", etc.