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** maintain consistency in icon usage within a tree view. If icons are added, they should be applied to all items to ensure a cohesive experience. Design teams *...
jbusta5 created a review comment on a pull request on vmware-clarity/clarity-guidance
```suggestion - Design teams **should not** use a tree view for only one level of nested information. Instead, they should use an [accordion](https://clarity.design/documentation/accordion) to pre...
jbusta5 created a review comment on a pull request on vmware-clarity/clarity-guidance
```suggestion - Design teams **should not** use excessive levels in a tree view, except when displaying user-generated information. Instead, they should consolidate layers whenever possible to enh...
jbusta5 created a review comment on a pull request on vmware-clarity/clarity-guidance
```suggestion - Design teams **must** use a tree view to display and manage large amounts of hierarchical information, as it helps users navigate complex data structures more efficiently. ```
jbusta5 created a review comment on a pull request on vmware-clarity/clarity-guidance
```suggestion The [tree view](https://clarity.design/documentation/tree-view) component displays a hierarchical list of items with a parent-child relationship, allowing users to toggle children in...
jbusta5 created a review comment on a pull request on vmware-clarity/clarity-guidance
```suggestion - Design teams **should** phrase the label to clearly indicate the dropdown action, helping users understand what to expect when interacting with the dropdown. ```
jbusta5 created a review comment on a pull request on vmware-clarity/clarity-guidance
```suggestion - Design teams **must** keep the descriptions of dropdown options as short as possible to enhance readability and ensure users can quickly understand their choices. ```
jbusta5 created a review comment on a pull request on vmware-clarity/clarity-guidance
```suggestion - Design teams **should** limit nested dropdown menus to three levels to prevent confusion and maintain clarity, ensuring users can easily navigate without feeling overwhelmed. ```
jbusta5 created a review comment on a pull request on vmware-clarity/clarity-guidance
```suggestion - Design teams **must not** use a dropdown menu as a form control for user input. Instead, they should use a [select](https://clarity.design/documentation/select) component, which is...
jbusta5 created a review comment on a pull request on vmware-clarity/clarity-guidance
```suggestion - Design teams **should** use nested dropdowns to organize longer lists into categories, allowing users to click to reveal deeper levels and enhancing navigation efficiency. ```
jbusta5 created a review comment on a pull request on vmware-clarity/clarity-guidance
```suggestion - Design teams **must not** use a dropdown menu to hide primary actions, as these actions should be readily accessible and not concealed behind a dropdown. ```
jbusta5 created a review comment on a pull request on vmware-clarity/clarity-guidance
```suggestion - Design teams **must not** use a dropdown menu to hide primary actions, as these actions should be readily accessible and not concealed behind a dropdown. ```
jbusta5 created a review comment on a pull request on vmware-clarity/clarity-guidance
```suggestion - Design teams **must** use a dropdown to facilitate immediate actions or navigate users outside of the current context, ensuring a seamless transition and clear user flow. ```
jbusta5 created a review comment on a pull request on vmware-clarity/clarity-guidance
```suggestion - The stepper panel header **should** contain a title and a description for the step, providing users with clear context and guidance on what is required at that stage of the process...
jbusta5 created a review comment on a pull request on vmware-clarity/clarity-guidance
```suggestion - Design teams **must not** include overly long content in each step, as this can overwhelm users and make it difficult to focus on the task at hand. Each step should present informa...