Ecosyste.ms: Timeline
Browse the timeline of events for every public repo on GitHub. Data updated hourly from GH Archive.
jbusta5 created a review comment on a pull request on vmware-clarity/clarity-guidance
```suggestion - Design teams **must** use a horizontal layout when all steps can be displayed without wrapping to maintain a clear and organized visual flow. ```
jbusta5 created a review comment on a pull request on vmware-clarity/clarity-guidance
```suggestion Timelines have two types of layouts: horizontal and vertical. ```
jbusta5 created a review comment on a pull request on vmware-clarity/clarity-guidance
```suggestion - Design teams **may** use a timeline when breaking down complex and lengthy workflows into multiple clear steps (more than two steps) to help users follow the process more easily. ```
jbusta5 created a review comment on a pull request on vmware-clarity/clarity-guidance
```suggestion - Design teams **must** use a timeline when longer forms require more space and have fewer steps. For workflows with many steps that contain small amounts of data in each step, use a...
jbusta5 created a review comment on a pull request on vmware-clarity/clarity-guidance
```suggestion - Design teams **must** use a timeline when showcasing a list of events that are relevant to the user in chronological order to increase user awareness of the sequence of events. ```
kevinbuhmann created a review comment on a pull request on vmware-clarity/clarity-guidance
We should keep the `[timeline](https://clarity.design/documentation/timeline)` link.
jbusta5 created a review comment on a pull request on vmware-clarity/clarity-guidance
```suggestion The timeline component is a visual indicator that displays progress through a workflow. It can also guide users through specific processes or predefined steps, helping them understan...
jbusta5 created a review comment on a pull request on vmware-clarity/clarity-guidance
```suggestion - Design teams **must** ensure the content is concise and provides a clear explanation of the task or information that the user should focus on to avoid confusion and improve usabili...
jbusta5 created a review comment on a pull request on vmware-clarity/clarity-guidance
```suggestion - Design teams **must** ensure the content title is similar to its step title to maintain consistency and help users easily follow along with the workflow. ```
jbusta5 created a review comment on a pull request on vmware-clarity/clarity-guidance
```suggestion - Design teams **must** ensure the wizard title describes the overall workflow to provide users with clear context about the steps they are about to take. ```
jbusta5 created a review comment on a pull request on vmware-clarity/clarity-guidance
```suggestion - Design teams **may** use a wizard to guide users through a defined step-by-step process, helping to ensure clarity and improve user understanding. ```
jbusta5 created a review comment on a pull request on vmware-clarity/clarity-guidance
```suggestion - Design teams **should** use a wizard when the content is self-sufficient and does not require access to other parts of the app, as wizards can block access to necessary areas for c...
jbusta5 created a review comment on a pull request on vmware-clarity/clarity-guidance
```suggestion - Design teams **must not** use a wizard when users need to leave mid-workflow and resume later, as this can disrupt their progress and lead to confusion. Instead, consider using a d...
jbusta5 created a review comment on a pull request on vmware-clarity/clarity-guidance
```suggestion - Design teams **must not** use a wizard in conjunction with an additional modal, as this can lead to lost context and block accessibility for keyboard users. It’s important to maint...
jbusta5 created a review comment on a pull request on vmware-clarity/clarity-guidance
```suggestion - Design teams **must not** include long or complex content in each step of the wizard, as this can overwhelm users and hinder their progress. Each step should be clear and concise. ...