Skip to content

docs(inputs): update ux images#1819

Draft
panch1739 wants to merge 1 commit intomainfrom
docs/inputs
Draft

docs(inputs): update ux images#1819
panch1739 wants to merge 1 commit intomainfrom
docs/inputs

Conversation

@panch1739
Copy link
Copy Markdown
Member

@panch1739 panch1739 commented Apr 3, 2026

This PR updates the images of the inputs based on the latest alignment.
Related to #1732

Please make sure your PR follows the contribution guidelines
https://github.com/siemens/element/blob/main/CONTRIBUTING.md. -->


Documentation.
Examples.
Dashboards Demo.
Playwright report.

Coverage Reports:

Code Coverage

@panch1739 panch1739 added this to the 49.x milestone Apr 3, 2026
@panch1739 panch1739 requested a review from hbxes April 3, 2026 08:50
@panch1739 panch1739 added documentation Improvements or additions to documentation ux Marks all UX related topics (UX team is working on or UX input is required) labels Apr 3, 2026
Copy link
Copy Markdown
Contributor

@gemini-code-assist gemini-code-assist bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Code Review

This pull request introduces a new Rabbit Dashboard application and updates documentation for various input components to standardize terminology. Critical syntax errors were identified in the JavaScript file where unescaped single quotes in ASCII art strings will cause the script to fail. Additionally, several feedback points address violations of the UX writing guidelines, specifically regarding the removal of colons in labels and status messages to improve conciseness. A documentation update is also required to ensure consistent use of the term 'Helper text' instead of 'Feedback text'.

@@ -0,0 +1,54 @@
const variants = {
small: ['(\\_/)\n(\'.')\n(\" ) (\")', '(\\_/)\n(•_•)\n(> <)'],
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

critical

This line contains a syntax error. The unescaped single quote in ('.') terminates the string literal prematurely, which will cause the script to fail. You should escape the single quotes or use double quotes for the string.

  small: ['(\\_/)\n(\'.\')\n(\" ) (\")', '(\\_/)\n(•_•)\n(> <)'],

@@ -0,0 +1,54 @@
const variants = {
small: ['(\\_/)\n(\'.')\n(\" ) (\")', '(\\_/)\n(•_•)\n(> <)'],
classic: [' (\\_/)\n (=\'.'=)\n (")_(")'],
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

critical

This line contains a syntax error. The single quote in (='.'=) must be escaped to prevent the string from terminating early.

  classic: ['  (\\_/)\n  (=\'.\')\n  (")_(")'],

<h1>Rabbit Dashboard</h1>

<section class="controls">
<label for="variant">Variant:</label>
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

medium

According to the UX writing guidelines, colons should be avoided in labels.

Suggested change
<label for="variant">Variant:</label>
<label for="variant">Variant</label>
References
  1. Avoid colons whenever possible (e.g., "User name" not "User name:") (link)

function setVariant(name){
const frames = variants[name];
rabbitEl.textContent = Array.isArray(frames)? frames[0] : frames;
statusEl.textContent = `Status: showing ${name}`;
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

medium

To follow UX guidelines, avoid using colons and keep the status message concise. Showing is sufficient to convey the state.

  statusEl.textContent = 'Showing ' + name;
References
  1. Avoid colons whenever possible. (link)
  2. Use as few words as possible. (link)

async function animate(name){
const frames = variants[name];
if(!frames || frames.length<2) return;
animating = true; animateBtn.textContent = 'Stop'; statusEl.textContent = 'Status: animating';
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

medium

Simplify the status message and remove the colon to adhere to UX guidelines.

  animating = true; animateBtn.textContent = 'Stop'; statusEl.textContent = 'Animating';
References
  1. Avoid colons whenever possible. (link)

i++; await new Promise(r=>setTimeout(r,300));
}
animateBtn.textContent = 'Animate hop';
statusEl.textContent = `Status: idle (last ${name})`;
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

medium

Remove the colon and the redundant Status prefix to follow UX writing standards.

  statusEl.textContent = 'Idle (last ' + name + ')';
References
  1. Avoid colons whenever possible. (link)

![Pills input elements](images/pills-input-element.png)

> 1. Label (optional), 2. Pills, 3. Container, 4. Message (optional)
> 1. Label (optional), 2. Pills, 3. Container, 4. Feedback text (optional)
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

medium

Use the term Helper text instead of Feedback text for the optional message below the container to maintain consistency with other input documentation.

Suggested change
> 1. Label (optional), 2. Pills, 3. Container, 4. Feedback text (optional)
> 1. Label (optional), 2. Pills, 3. Container, 4. Helper text (optional)
References
  1. In documentation, prioritize conciseness over explaining the 'why' when the reason is considered obvious.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

documentation Improvements or additions to documentation ux Marks all UX related topics (UX team is working on or UX input is required)

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant