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 dividers and groups to separate logical clusters of navigation items, enhancing clarity and helping users quickly locate related links. ```
jbusta5 created a review comment on a pull request on vmware-clarity/clarity-guidance
```suggestion The [vertical nav](https://clarity.design/documentation/vertical-nav) component offers vertically-aligned navigation links. It accommodates as many links as needed, allowing users to...
jbusta5 created a review comment on a pull request on vmware-clarity/clarity-guidance
```suggestion - Design teams **must not** use placeholders in place of helper text, as this can lead to confusion about the expected input. Helper text **should** provide additional guidance and c...
jbusta5 created a review comment on a pull request on vmware-clarity/clarity-guidance
```suggestion - Design teams **must not** use placeholders as a substitute for a proper label element, as this creates accessibility challenges for users. Placeholders can be invisible when typing...
jbusta5 created a review comment on a pull request on vmware-clarity/clarity-guidance
```suggestion - Design teams **must** provide an `aria-label` (or other accessible name) if there is no visible label, ensuring the input is accessible to all users. This accessible name **should*...
jbusta5 created a review comment on a pull request on vmware-clarity/clarity-guidance
```suggestion - Design teams **should** provide a clear and concise visible label for context, helping users understand what information is expected in the input field. ```
jbusta5 created a review comment on a pull request on vmware-clarity/clarity-guidance
```suggestion -Design teams **must not** use an input for capturing multiple lines of text. Instead, use a [textarea](https://clarity.design/documentation/textarea) for this purpose. ```
jbusta5 created a review comment on a pull request on vmware-clarity/clarity-guidance
```suggestion The input component allows users to enter a single sentence or less of text, providing a straightforward way to capture concise information. ```
jbusta5 created a review comment on a pull request on vmware-clarity/clarity-guidance
```suggestion - Design teams **should** use a step description to provide additional information and guidance to users, helping them understand what is required at each stage of the process. ```
jbusta5 created a review comment on a pull request on vmware-clarity/clarity-guidance
```suggestion - Design teams **must not** use tooltips to display error messages, as this can hinder accessibility for users who rely on screen readers or keyboard navigation. Instead, error messa...
jbusta5 created a review comment on a pull request on vmware-clarity/clarity-guidance
```suggestion - Design teams **should** display the error message under the error icon in the error state to provide users with clear information about the issue. ```
jbusta5 created a review comment on a pull request on vmware-clarity/clarity-guidance
```suggestion - Design teams **must** disable buttons when loading or adjust buttons to reflect the contextual loading state, ensuring users understand that actions cannot be taken during this tim...
jbusta5 created a review comment on a pull request on vmware-clarity/clarity-guidance
```suggestion - Design teams **must** use a spinner when loading or performing an action (e.g., in the processing state) to provide users with visual feedback and indicate that their request is be...
jbusta5 created a review comment on a pull request on vmware-clarity/clarity-guidance
```suggestion - Design teams **must** ensure each step in a timeline has one of five visual states: complete, current step, not started, processing, or error, to clearly indicate progress and stat...
jbusta5 created a review comment on a pull request on vmware-clarity/clarity-guidance
```suggestion - Design teams **must** use a vertical layout when a workflow has more than five steps to ensure clarity and prevent overwhelming users with too much information at once. ```