You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
To provide more clarity to the various communication components within the design system - they were defined & distinguished within the work-stream #16703. This provided clarity to define any new communication component within the DS. The need for a new component "Callout" (previously referred to as static notification) was validated and classified as an informational component within communication components.
What's a callout component
Callout is non-modal and used inline with content on the initial render of the page or modal. This should not be used for real-time notifications or notifications responding to user input. This is a passive component and is essentially just a styled div. (The terminology static notification to refer this component was hence avoided, since it was not meant to be used as a notification that provided feedback for a user input)
--
Explore Callouts as a new component
Explore usecases for "Callout"component within products, and define its parameters
Parallel study to understand - how the functionality for callouts are currently being implemented within IBM products.
Parallel study to explore how callouts are used in other products outside of IBM
Define the required variants for the component and their parameters
The text was updated successfully, but these errors were encountered:
benjamin-kurien
changed the title
Explore usecases for Callouts within products, and define its parameters
Explore usecases for "Callout"component within products, and define its parameters
Jul 4, 2024
benjamin-kurien
changed the title
Explore usecases for "Callout"component within products, and define its parameters
(Callout): Research & Definition
Jul 17, 2024
Research was done to identify how actionable inline notifications were being modified by various products teams within IBM. These findings were then explored as possible usecases for a potential new component - Callout.
The study concluded in differentiating this potential component "Callout" (Name to be finalised) with the other existing notifications components across their various properties
Callout was defined to highlight important information that could be provided contextually before users take an action. They cannot be dismissed unlike other notification components, are not triggered by a user/system action and would instead be long-lived always existing on the page. Explore all findings here
Recap
To provide more clarity to the various communication components within the design system - they were defined & distinguished within the work-stream #16703. This provided clarity to define any new communication component within the DS. The need for a new component "Callout" (previously referred to as static notification) was validated and classified as an informational component within communication components.
What's a callout component
Callout is non-modal and used inline with content on the initial render of the page or modal. This should not be used for real-time notifications or notifications responding to user input. This is a passive component and is essentially just a styled div. (The terminology static notification to refer this component was hence avoided, since it was not meant to be used as a notification that provided feedback for a user input)
--
Explore Callouts as a new component
Explore usecases for "Callout"component within products, and define its parameters
The text was updated successfully, but these errors were encountered: