Normalize & document icon usage, and move design documents into storybook #2597
+1,095
−164
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR is the result of investigating our usage of icons and colors across the app. This investigation is document in the first table “In Use (as of 2025-05-06)” on the Status Indicators page in Storybook, included as a screenshot below.
I've then consolidated these uses with the previous version of the Status Icons document that @Shrinks99 wrote into a new Intended Implementation table, as seen below.
Finally, I updated icons across the app in places that were using different icons for the same meanings. Certain places (e.g. the superadmin org list) deviate from these norms, but I think this is okay — that implementation in particular is quite information-dense, so using a wider variety of icons and colors there works.
Finally finally, I moved both design docs from the public docs page into Storybook, as these more internally-facing design docs aren't particularly useful to end users.
Changes
remark-gfm
to enable tables in MDXColorSwatch
blockScreenshots
[working on it]