Ecosyste.ms: Timeline

Browse the timeline of events for every public repo on GitHub. Data updated hourly from GH Archive.

vmware-clarity/clarity-guidance

kevinbuhmann created a review on a pull request on vmware-clarity/clarity-guidance

View on GitHub

kevinbuhmann created a review comment on a pull request on vmware-clarity/clarity-guidance
```suggestion - **Must not** use a dropdown menu to hide primary actions. Such actions **must not** be hidden behind a dropdown menu. ```

View on GitHub

kevinbuhmann created a review on a pull request on vmware-clarity/clarity-guidance

View on GitHub

kevinbuhmann created a review comment on a pull request on vmware-clarity/clarity-guidance
```suggestion - **Must not** have long content in each step. ```

View on GitHub

kevinbuhmann created a review on a pull request on vmware-clarity/clarity-guidance

View on GitHub

kevinbuhmann created a review comment on a pull request on vmware-clarity/clarity-guidance
```suggestion - **Must** use a stepper when you need the capability to navigate freely to other parts of an application during the workflow. To block access to other parts of the application while...

View on GitHub

kevinbuhmann created a review on a pull request on vmware-clarity/clarity-guidance

View on GitHub

kevinbuhmann created a review comment on a pull request on vmware-clarity/clarity-guidance
```suggestion - **Must** use a stepper when you have many steps with small data set in each step. For longer forms with a fewer number of steps, use a [timeline](https://clarity.design/documentati...

View on GitHub

kevinbuhmann created a review on a pull request on vmware-clarity/clarity-guidance

View on GitHub

kevinbuhmann created a review comment on a pull request on vmware-clarity/clarity-guidance
```suggestion - **May** use a stepper when you have complex and long work processes that may not fit in one viewport. ``` Other options exist such as the wizard.

View on GitHub

kevinbuhmann created a review on a pull request on vmware-clarity/clarity-guidance

View on GitHub

kevinbuhmann created a review comment on a pull request on vmware-clarity/clarity-guidance
```suggestion - **Must** use short and concise label for navigation items in order to prevent an ellipsis from being required. Lengthy labels are trimmed and followed by an ellipsis. ```

View on GitHub

kevinbuhmann created a review on a pull request on vmware-clarity/clarity-guidance

View on GitHub

kevinbuhmann created a review comment on a pull request on vmware-clarity/clarity-guidance
```suggestion ## Content Guidelines ``` nit: missing blank line

View on GitHub

kevinbuhmann created a review on a pull request on vmware-clarity/clarity-guidance

View on GitHub

kevinbuhmann created a review comment on a pull request on vmware-clarity/clarity-guidance
```suggestion ## Nav Hierarchy ``` nit: missing blank line

View on GitHub

kevinbuhmann created a review comment on a pull request on vmware-clarity/clarity-guidance
```suggestion ## Nav Icons ``` nit: missing blank line

View on GitHub

kevinbuhmann created a review on a pull request on vmware-clarity/clarity-guidance

View on GitHub

kevinbuhmann created a review on a pull request on vmware-clarity/clarity-guidance

View on GitHub

kevinbuhmann created a review comment on a pull request on vmware-clarity/clarity-guidance
```suggestion - **Must** place icons to the left of the top navigation labels. ``` I think this is a "must" because the component doesn't support icons on the right-hand side anyway.

View on GitHub

kevinbuhmann created a review on a pull request on vmware-clarity/clarity-guidance

View on GitHub

kevinbuhmann created a review comment on a pull request on vmware-clarity/clarity-guidance
```suggestion - **Must** apply icons to top-level navigation items. *Must not** apply icons to child links. ``` It this is better. If icons are not *required* for top-level items, change "must...

View on GitHub

kevinbuhmann created a review on a pull request on vmware-clarity/clarity-guidance

View on GitHub

kevinbuhmann created a review comment on a pull request on vmware-clarity/clarity-guidance
```suggestion - **Must** use dividers and groups to separate logical clusters of navigation items. ```

View on GitHub

kevinbuhmann created a review on a pull request on vmware-clarity/clarity-guidance

View on GitHub

kevinbuhmann created a review on a pull request on vmware-clarity/clarity-guidance

View on GitHub

kevinbuhmann created a review comment on a pull request on vmware-clarity/clarity-guidance
Please sync this with the input guidance. https://github.com/vmware-clarity/clarity-guidance/pull/34/files#r1808903933

View on GitHub

kevinbuhmann created a review comment on a pull request on vmware-clarity/clarity-guidance
```suggestion - **Should** provide a clear and concise visible label for context. - If there is no visible label, an `aria-label` (or other accessible name) **must** be provided and **should** be...

View on GitHub

kevinbuhmann created a review on a pull request on vmware-clarity/clarity-guidance

View on GitHub

kevinbuhmann created a review comment on a pull request on vmware-clarity/clarity-guidance
```suggestion - **Must not** use an input in case of multiple lines of text. Use a [textarea](https://clarity.design/documentation/textarea) for multiple lines of text input. ```

View on GitHub

Load more