Publishing JS Guidelines in the TechDocs

[Cronus1007]

Discussion 🗣

Lack of Javascript Coding Guidelines

• reduces efficiency of communication and pull requests
• sets new contributors up to fail
• increases cognitive work of working across multiple repositories

Solution Description

Document Javascript coding guidelines.

• Communicate with stakeholders
• Draft guidelines
• Publish guidelines

Context

For example:

• nodev14
• eslint
• stylelint

[jolanglinais]

Trying to understand what the issue is and what you'd like done. Is this something that would be resolved by having an ESLint configuration in place in our codebases?

[Cronus1007]

For reference you can have a look at the Creative Commons Python Guidelines https://opensource.creativecommons.org/contributing-code/python-guidelines/

[jolanglinais]

I think this can be folded into #308