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 **should** use parentheses for any additional metadata required within the same label to keep the information organized and easy to read. ```
jbusta5 created a review comment on a pull request on vmware-clarity/clarity-guidance
```suggestion - Design teams **must not** use multiple lines of text within a single label to keep the interface clear and easy to scan. ```
jbusta5 created a review comment on a pull request on vmware-clarity/clarity-guidance
```suggestion - Design teams **must not** use all capital letters in labels. Using all caps can confuse users, making them think the label is a button or actionable element. This also impacts read...
jbusta5 created a review comment on a pull request on vmware-clarity/clarity-guidance
```suggestion - Design teams **must** keep labels short and concise to ensure they are easy to read and quickly understood. ```
jbusta5 created a review comment on a pull request on vmware-clarity/clarity-guidance
```suggestion A [label](https://clarity.design/documentation/label) component provides a concise description or identifier for interface elements, like form fields or statuses, helping users quic...
jbusta5 created a review comment on a pull request on vmware-clarity/clarity-guidance
```suggestion - Design teams **must not** use a textarea as a substitute for a proper label element. Labels are essential for accessibility and ensure users clearly understand the purpose of the f...
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, ensuring users understand what input is expected and reducing the chance of errors. ```
jbusta5 created a review comment on a pull request on vmware-clarity/clarity-guidance
```suggestion - Design teams **must** use a textarea when the expected user input spans multiple lines. If only a single line is needed, use an [input](https://clarity.design/documentation/input) ...
jbusta5 created a review comment on a pull request on vmware-clarity/clarity-guidance
```suggestion - Design teams should favor nouns over verbs in tab labels, for example, "Settings," "Permissions," and "Performance," to create clearer, more scannable navigation. ```
jbusta5 created a review comment on a pull request on vmware-clarity/clarity-guidance
```suggestion - Design teams **must** show a clear relationship between the tabs to help users understand how the content is connected and navigate intuitively. ```
jbusta5 created a review comment on a pull request on vmware-clarity/clarity-guidance
```suggestion - Design teams **must not** use icons in tab labels. Icons can reduce clarity and increase cognitive load, making it harder for users to understand the content at a glance. ```
jbusta5 created a review comment on a pull request on vmware-clarity/clarity-guidance
```suggestion - Design teams **must** use title case capitalization for tab labels to maintain consistency and improve readability. ```
jbusta5 created a review comment on a pull request on vmware-clarity/clarity-guidance
```suggestion - Design teams **must not** use generic labels like "General" or "Advanced," as they provide little clarity and can confuse users about the content within the tabs. ```
jbusta5 created a review comment on a pull request on vmware-clarity/clarity-guidance
```suggestion - Design teams **may** consider dividing long content into subsections within a tab to improve readability and help users quickly find relevant information. ```
jbusta5 created a review comment on a pull request on vmware-clarity/clarity-guidance
```suggestion - Design teams **should** keep similar content within the same view to prevent unnecessary back-and-forth navigation, allowing users to compare data more easily and stay focused. ```