-
Notifications
You must be signed in to change notification settings - Fork 38
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
NotificationMarker
docs page
#1999
Conversation
|
||
### Status | ||
|
||
`NotificationMarker`s can have `primary` (default), `positive`, `warning`, `negative`, or `white` statuses. The `white` status is used on colored backgrounds, such as when using it in the [high visibility](button#high-visibility) or the [call-to-action](button#call-to-action) buttons. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
(Unrelated) This is making me realize that we should handle the primary
vs white
statuses by default when used in Button. The user shouldn't need to think about the difference.
Co-authored-by: Mayank <[email protected]>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
Changes
This PR adds a page to the docs site for the
NotificationMarker
component.It also makes a few nitpick changes in other docs files to try to have a consistent format across all docs pages.
Testing
N/A
Docs
N/A