Repository navigation
feat(ui): uxdocs - add Interaction Guidelines page (#1916) - #2063
Conversation
Fixes #2056. The context provider only set `appearance`, leaving `tabStyle` as `undefined` for any consumer reading it from `TabBarContext`/`TabNavigationContext`. Both fields now carry the resolved appearance value. Signed-off-by: Franz Heidl <franz.heidl@sap.com>
Signed-off-by: Franz Heidl <franz.heidl@sap.com>
Signed-off-by: Franz Heidl <franz.heidl@sap.com>
|
|
There was a problem hiding this comment.
Copilot review overview
🟡 Changes recommended
Two guidelines need accessibility corrections for screen-reader and keyboard users.
Review effort: Balanced
Findings: 1
Open (1)
What changed in this PR
Adds an Interaction Guidelines page to Juno’s UX documentation and integrates it into existing navigation.
Changes:
- Documents interaction, feedback, consistency, disabled-state, and accessibility guidance.
- Links the page from both UX indexes.
| File | Description |
|---|---|
docs/ux/interaction-guidelines.md |
Adds the new guidelines page. |
docs/ux/application-design-guidelines.md |
Links the new page. |
docs/ux/0_contents.md |
Adds the page to the contents index. |
💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.
…ed states Signed-off-by: Franz Heidl <franz.heidl@sap.com>

Summary
Adds a new Interaction Guidelines page to the UX docs (docs/ux/interaction-guidelines.md) and links it from the contents index and Application Design Guidelines.
Related Issues
Closes #1916.
Checklist
PR Manifesto
Review the PR Manifesto for best practises.