Ecosyste.ms: Timeline
Browse the timeline of events for every public repo on GitHub. Data updated hourly from GH Archive.
kevinbuhmann created a review comment on a pull request on vmware-clarity/clarity-guidance
```suggestion - **Must** use range input component when it is acceptable to have an imprecise input control and the exact value is not important. ```
kevinbuhmann created a review comment on a pull request on vmware-clarity/clarity-guidance
```suggestion - *Should* use appropriate [range input states](https://clarity.design/documentation/range#states). ```
kevinbuhmann created a review comment on a pull request on vmware-clarity/clarity-guidance
```suggestion - **Should** use [radio buttons](https://clarity.design/documentation/radio) or a [select](https://clarity.design/documentation/select) when only a few distinct choices are available...
kevinbuhmann created a review comment on a pull request on vmware-clarity/clarity-guidance
```suggestion - **Must not** stack side panels since it would make it hard to dismiss them and confuses the user. ```
kevinbuhmann created a review comment on a pull request on vmware-clarity/clarity-guidance
```suggestion - **Must** keep it simple. Side panels can include components like links, cards, images, or text. Avoid putting complex components in a side panel, like tables or accordions. ```
kevinbuhmann created a review comment on a pull request on vmware-clarity/clarity-guidance
```suggestion - **Must** use a side panel when you have more content or complex interactions than a modal. It is recommended to be used for any tertiary actions or sub-processes. You can use a [mo...
kevinbuhmann created a review comment on a pull request on vmware-clarity/clarity-guidance
```suggestion - **Should** use [vertical tabs](https://clarity.design/documentation/tabs/code#vertical-tabs) for vertical alignment. ``` Same here. Not a proper noun.
kevinbuhmann created a review comment on a pull request on vmware-clarity/clarity-guidance
```suggestion - **Must not** use tabs to break user interactions into a series of steps. Serial workflows are best presented in a [stepper](https://clarity.design/documentation/stepper) or [wizard...
kevinbuhmann created a review comment on a pull request on vmware-clarity/clarity-guidance
```suggestion - **Must** avoid using more than seven tabs and limit labels to one or two words to ensure that all tabs appear in the container. You may use [tab overflow](https://clarity.design/do...
kevinbuhmann created a review comment on a pull request on vmware-clarity/clarity-guidance
```suggestion - **Should not** use too many colors within the same context. Displaying too many colors may distract the user from the core of your application and the information it presents. - *...
kevinbuhmann created a review comment on a pull request on vmware-clarity/clarity-guidance
If there is a count related to the label, is using a badge within the label *required* or *optional*. It it is required, this should be reworded to a must. ```suggestion - If there is a count o...
kevinbuhmann created a review comment on a pull request on vmware-clarity/clarity-guidance
```suggestion - **May** use a close icon at the right-most side of a label to dismiss it. ``` I think this one is better worded as a "may" because dismissing labels is optional. Not all labels...
kevinbuhmann created a review comment on a pull request on vmware-clarity/clarity-guidance
```suggestion - **Must not** use multiple lines of text within a single label. ```
kevinbuhmann created a review comment on a pull request on vmware-clarity/clarity-guidance
```suggestion - **Must not** use all capital letters in labels. Using all capital letters might make the user think the label is a button and conflates the use case for labels with actions and but...
kevinbuhmann created a review comment on a pull request on vmware-clarity/clarity-guidance
```suggestion - **Must** use title case for capitalization. ```