Determine status variant names

[bradfrost]

Goal: establish solid, sensible code guidelines for the Open UI design system patterns. (working draft here). Cast your vote and join the discussion. This poll will be kept open for a finite time (specific timing to be determined) and then the team will make calls. Before voting, please review the agreed-upon design principles the library's code conventions will adhere to.

---

Goal: Establish consistent naming for status-based component variants

Considerations:

• Must be universally understood across cultures and languages
• Should avoid negative connotations where possible
• Needs to cover common status types
• Should be consistent with existing design system conventions
• Must be clear and unambiguous

[bradfrost]

Example:

<div class="oui-alert oui-alert--error">
 <!--component innards-->
</div>

vs

<div class="oui-alert oui-alert--destructive">
<!--component innards-->
</div>

[bradfrost]

More holistic options:

• Error states: error, danger, critical, destructive, blocked, negative
• Success states: success, valid, positive, complete
• Warning states: caution, warning
• Info states: info, neutral, default

[bradfrost]

In our experience, we've found good success with:

• error
• success
• warning
• info

But we've worked with plenty of clients that have existing conventions in place, and usually bend towards those existing conventions when they exist.