Repository navigation
feat(ui): uxdocs - add rendering empty and unknown values guidelines - #2071
Conversation
|
There was a problem hiding this comment.
🟡 Changes recommended
The guidance needs accessible placeholder handling and consistent wording for name versus identifier columns.
2 open findings
What changed in this PR
Adds UX guidance for consistently displaying missing or unknown values.
Changes:
- Defines
- -as the standard visual placeholder. - Documents ID fallback rules for missing names.
- Cross-references the guidance from DataGrid documentation.
| File | Description |
|---|---|
docs/ux/ux-writing-content-design.md |
Adds placeholder and identifier fallback guidance. |
docs/ux/datagrid.md |
Applies the guidance to DataGrid cells. |
🧠 Review effort: Balanced
Give feedback about Copilot approvals in this survey to enter a drawing for a $150 gift card.
Signed-off-by: Franz Heidl <franz.heidl@sap.com>
|

Summary
Adds UX writing guidance for rendering missing or unknown values consistently across the UI.
Two rules are documented:
- -(two hyphens separated by a space) as a visual placeholder for any empty or unknown value. En and em dashes are explicitly discouraged — they look similar but carry different semantic meaning and can be silently introduced by editors with smart typography enabled.- -when no name is set. Exception: verbatim metadata display (e.g. a definition list showing raw item properties) should use- -to accurately reflect that no name value exists.Changes
docs/ux/ux-writing-content-design.md— new "Rendering Empty or Unknown Values" sectiondocs/ux/datagrid.md— added a bullet to "DataGrid Content and Writing" cross-referencing the new guidanceRelated Issues
Closes #2067
Checklist
PR Manifesto
Review the PR Manifesto for best practises.