NoticeGlobal is a component designed for conveying messages about events related to the entire website's operations.
To be considered a notice, it must meet four specific criteria. If it fails to meet at least one of these criteria, it cannot be classified as a notice. Let's explore the distinctions between NoticeGlobal and Notice as well as NoticeBubble.
|Refers to the entire website||❌||✅ ❌||✅|
|Global: Refers to pages, blocks, or large components rather than specific elements||✅||✅ ❌||✅|
|Important: Missing the notice may result in missed opportunities or loss of data||✅||❌||✅|
|Temporary: Appears and disappears under certain conditions, not a default block element||✅||✅||✅|
Use the global notice to communicate the following:
- Special viewing modes of a page, product, or site (for example, pertaining to admin or other rights on the page).
- Notifications about outdated browser versions.
- Messages related to the entire site's operations, such as downgrades, technical work, and other similar events.
Component consists of the following:
This theme is suitable for neutral messages about the entire website.The Notice background color uses
Use this theme when collecting feedback for the entire website. The Notice background color uses
Opt for this theme for success messages related to the entire website. The Notice background color uses
This theme is ideal for displaying important but not critical errors or warnings pertaining to the entire website. The Notice background color uses
Use this theme to convey serious error or problem messages concerning the entire website. The Notice background color uses
Placement in the interface
- Always position this notice above the main website header.
- Stretch the notice to cover the full width of the screen.
When the global notice appears, it shifts the entire page down.
As the notice is a temporary message, it should have a preset "lifespan." The "lifespan" can be determined by the following rules:
- Number of days (for example, during an experiment).
- Number of user sessions.
- Events (for example, completion of works, bug fixes, moving features out of beta).
- User actions as triggers (for example, installing something, viewing specific content, fixing an error).
When user hides the notice, the entire page moves up to the height of the closed component.
NoticeGlobal can be hide by:
- Clicking on the
- Clicking on the link that triggers the re-opening condition (for example, "Ask me later," "Never show again," etc.).
- If there is no
Closeicon or hide link, the user can't manually hide such notice. It will be hidden according to the conditions set by the service (after a certain time, a certain number of sessions, after clicking on the trigger, etc.).
By clicking on the closing icon or closing link, the notice shall smoothly close with a
fade-out effect lasting
250ms. The page content moves up to the notice's position within
These are special notices that have their own unique rules and styles, distinct from default themes.
Notice with illustration
In exceptional cases, you have the option to include a thematic illustration with the message. For example, if technical work is scheduled during holidays, etc.
However, it is crucial to consider that an excessive use of visual elements in notices can add unnecessary visual noise to the page. Therefore, exercise restraint when adding illustrations to this type of message.
Two notices per page
Avoid displaying more than one global message at a time. Below is an example of what you SHOULD NOT do:
In situations where a user on the site has two or more global messages to display, prioritize them accordingly.
- Give higher priority to messages that require a response from the user or contain controls to close or exit a special mode.
- Messages without controls inside should have lower priority. Display them after a user has interacted with a higher priority message.
Usage in UX/UI
- You can use global notices to notify about the following: website mode (for example, admin), system status (error, failure, end of works).
- Keep the messages concise, so they don't obscure other widgets or report functionality. Try to convey the message's meaning to users in just one line.