Style guide/formatting policy

[s-makin]

As per discussion started in this PR - we ought to have a style guide for contributors. Let's use this issue to align on what we want the policies to be, and create the style guide based on that. Starting it off with DV's suggestions from that PR:

• max line lengths (doesn't have to be 79 characters; we don't live in the 80s)
• empty new line at end of file
• no trailing whitespace at end of line
• two (or more) consecutive empty lines should be avoided (exceptions are okay, if they improve readability)

[dviererbe]

1. What should the usage conventions/restrictions of cards, tabs, dropdowns be?

2. Does anyone have a good Idea how we can utilize badges and inline icons? I don't want to use them just because we can, but I have the feeling that there is an opportunity to make our documentation more intuitive.

[dviererbe]

Thought: Maybe we could use the icons for links to indicate if they are external links or cross references.

[s-makin]

I was just wondering if maybe we should have a roundtable discussion during the sprint to decide what we do and don't want in the policy? Get the whole thing written up and published in one session - wdyt?

[dviererbe]

I am closing this issue for now as the current strategy is to upstream all styling related changes into the canonical starter-pack/style-guide to have a unified style across all Canonical documentation.