Skip to content
This repository was archived by the owner on Jul 7, 2025. It is now read-only.
Merged
Changes from 1 commit
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Prev Previous commit
Update content/components/banner.mdx
  • Loading branch information
lukasoppermann authored May 7, 2024
commit 0addac6d8c9fdc66a840b4f82f932e8ed50d08f9
4 changes: 2 additions & 2 deletions content/components/banner.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -173,8 +173,8 @@ Use upsell banners to inform the users about a feature that can be enabled by up
Banners with an `onDismiss` property automatically show a dismiss button. This should be used for banners that inform about something that the user can not solve. For example issues with the organization they are part of or informational banners. When it makes sense, the choice to dismiss the banner should be stored and the banner should not be shown again.

Use the following as a guideline:
- If you're on a page in which you can do other tasks, and the banner is not blocking / does not have to be addressed, then you should be able to have a close button.
- If accidental closure of the banner would leave the user confused or missing something critical, it should not have a close button.
* If you're on a page in which you can do other tasks, and the banner is not blocking / does not have to be addressed, then you should be able to have a close button.
* If accidental closure of the banner would leave the user confused or missing something critical, it should not have a close button.

<img
width="456"
Expand Down