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
Evaluating the information architecture of our Design system (Components, Patterns, etc) so that there's clarity on how notifications and its sub components should be classified in our system
The content you are editing has changed. Please copy your edits and refresh the page.
benjamin-kurien
changed the title
Evaluating the information architecture of our Design system (Components, Patterns, etc) so that there's clarity on how notifications and its sub components should be classified in our system
Evaluating the IA of our Design system to help calssify communication components within it
Jun 6, 2024
Initiated work on evaluating our design system to understand how notifications should be classified across its various sections.
The following were defined:
Guidelines & Assets: Guidelines help create new components and layouts, so that they are aligned to the carbon design language. (They may also include a library of graphical elements that can be used as design assets)
Components: Components are visually styled modular blocks that fulfil a function. (Components can have multiple visual variants that fulfils the same function)
Patterns: Patterns are UX recommendations that use a combination of components, layouts and guidelines to solve common user and business needs.
Layouts: Layouts are common templates by which components can be used in design. They are provided only for an ease to start, and can be changed according to our guidelines to meet specific product needs.
Notification falls under the definition of patterns as it provides a set of guidelines and UX recommendations that help communicate information from the business to the users about their actions. This pattern is achieved through a combination of components like Inline and toast messages, Modal, etc ... which will be further classified in the upcoming stream of work
Evaluating the information architecture of our Design system (Components, Patterns, etc) so that there's clarity on how notifications and its sub components should be classified in our system
Tasks
The text was updated successfully, but these errors were encountered: