Document coding guidelines

[bloudermilk]

• How/when to use Tailwind, .css files, inline style
• How/when to use comments

[loiclefloch]

• Browser compatibility
• Specify with Tailwind in which order we should add the class names. See:
  Some links we could look at:
  https://gist.github.com/sandren/0f22e116f01611beab2b1195ab731b63
  Order class names in markup. What's your secret? tailwindlabs/discuss#124
  https://www.youtube.com/watch?v=J_7_mnFSLDg&feature=youtu.be. This video looks interesting I will surely look at it and make a resume of it for myself that I can share

[bloudermilk]

@loiclefloch that's an excellent video! I think we should link to it from these docs. If you have time to summarize the main points that would be helpful as well :)

[loiclefloch]

• maybe we could define if we want to prefer margin-top or margin-bottom to place our elements.

[bloudermilk]

• Understanding issue priority (P0, P1, P2, ...)
• Don't pass pageContext into components

[loiclefloch]

• create and use generic components
• for margin, some people offer to not use css at all but components: https://mxstbr.com/thoughts/margin
• run and write unit tests with jest