Skip to content

Commit

Permalink
chore: more feedback
Browse files Browse the repository at this point in the history
  • Loading branch information
nkrantz committed Oct 18, 2024
1 parent 0643cb2 commit c738812
Showing 1 changed file with 3 additions and 6 deletions.
9 changes: 3 additions & 6 deletions packages/paste-website/src/pages/patterns/status/index.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -186,12 +186,7 @@ Check out the [icon usage guidelines](/components/icon/usage-guidelines) for mor

### Process status

Process statuses indicate an object’s progress through a certain set of stages. There are generally 3 or more stages in a given process,
which may be considered “good”, “bad”, or “neutral”. Process statuses are composed of a status Icon and Text.

**Process icons should be paired with text whenever possible.** When using process icons, try to limit the number of icons
used to 3 or 4 of the most important statuses. For statuses that are not as critical to a user’s workflow, consider
[plain text statuses](#plain-text-status).
Process statuses indicate an object’s progress through a set of stages. **Process statuses should always be paired with text.**

<LivePreview
scope={{
Expand All @@ -216,7 +211,9 @@ To determine how to show a process status:
- If additional information is needed about the status, use Icon, Text, and [Anchor](/components/anchor) (optional).
- If it’s in a Table and no additional information is needed, use a [borderless Status Badge](/components/status-badge#borderless-badges).
- Otherwise, use the default [Status Badge](/components/status-badge).

Placement of the status in a Table should depend on the importance of the status to the given user flow and should be tested with users.

For statuses that are not as critical to a user’s workflow, use [plain text statuses](#plain-text-status).

<LivePreview
Expand Down

0 comments on commit c738812

Please sign in to comment.