-
Notifications
You must be signed in to change notification settings - Fork 143
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
Coachmark: UX review #6592
Comments
Coachmark: UX ReviewAreas the Coachmark components could be made more flexible:Additional use case identified in What’s new notification work:
![]() Theming: ![]() Sizing: ![]() Figma Kit Review:See Figma Onboarding Update: Coachmark # 61 Storybook Review:Rework how Coachmark components are coded: Hardcoded Icons: ![]() Stepped Tooltip coachmark : The current Stepped tooltip coachmark is not designed to change locations in the UI when a user moves between steps. This is an essential interaction for onboarding and product walkthroughs. Designers should have the option of using static tooltip coachmarks, and tooltip coachmarks that shifts around the UI. ![]() Documentation Review:
Re-triggering Coachmark:
Product gallery:Product gallery does not include the coachmark component. It might be one to consider adding Carbon Design System:The toggletip documentation on Core has a related section. Similar to the coachmark, the toggletip also has interactive elements, and visually looks very similar. What sets them apart is the trigger and intent. Is it worth mentioning the Coachmark here and linking out to further guidance on the Carbon for IBM products documentation? ![]() |
The goal of this step is to get familiar with the component/pattern as it exists today. You'll be reviewing the component across the docs, coded versions, and Figma kit. For this first step, keep in mind the goal of discovering if there are ways to make this component more flexible and composable. You don't need to answer these know, but think about:
Tasks
The text was updated successfully, but these errors were encountered: