Use a blue background, instead of green, for notes

[jstirnaman]

1. Use a blue background style for notes, replacing the current green background.
   Blue is somewhat the de-facto standard for informational tips, whereas green is a visual indicator of success.

2. Add icons to tips/notes, cautions, and warnings.

Examples of both in Google Developer Style Guide

[sanderson]

Currently, the blue background is used for things specifically related to InfluxDB Cloud. I think with the additions of icons to these blocks, we can use blue for both notes and cloud-specific blocks. They would just have different icons.

Another question – Right now, we only have notes and warnings, no intermediate level notice. Do we need and intermediate level or are notes and warnings sufficient?

If we do introduce an intermediate level, do we need to rename our notice blocks to align with common alert levels?

• note
• warn
• crit

This also would require an audit of all the existing note and warn blocks.

[jstirnaman]

Renaming... wouldn't it be

• note
• caution
• warn

Or are you suggesting to add "crit" (red) to what we have already?

That said, I'm not sure how much value there is in distinguishing caution vs warn/crit.

[kelseiv]

@jstirnaman @sanderson, maybe a different shade of blue to distinguish Cloud and notes? Like the idea of following Google dev for both color and similar-ish icons.

Good point on alert levels to marinate and discuss...and with the different meanings in context, we'll want to clarify/distinguish the differences.

re audit of existing warnings/notes, we noticed a lot of incorrect usages in the 1.x docs, so there's that to wrestle with too.

[kelseiv]

@jstirnaman @sanderson, looping back on this one.

Lets go with note, caution, and warn given their industry standard usage, and add relevant icons.

In our contributing guidelines, we can highlight their purpose and clarify they're not to be confused with InfluxDB alerts. I think in context this shouldn't be too confusing. We can start implementing these moving forward, and then add a lower priority issue to track/audit older ones as time permits.