thermondo Development Style Guide

Why this Style Guide?

Since backend and frontend are going to work more and more together on coming projects, it makes sense to define some global coding/workflow rules. This repository provides all information a developer needs to get started.

What this Style Guide does not cover?

Information about a specific application should stay in its app’s repository. Only generic information is covered in the Style Guide.

Something missing?

If you see new content/changes for this Style Guide, we should discuss it and add it.

Table of contents

• Philosophy
• Code
  • Python
  • Django
  • i18n l10n
  • JavaScript
  • JavaScript/CSS 3rd party libraries
  • JSX
  • CoffeeScript
  • SCSS
  • LESS
  • NPM
  • Salesforce
  • Shell scripting
• Workflow
  • Deploy
  • Ticketing
  • Branching
  • Committing
  • Merging
  • Testing
  • Reviewing