Skip to content

Docs/ai chat history#1636

Draft
panch1739 wants to merge 4 commits intomainfrom
docs/ai-chat-history
Draft

Docs/ai chat history#1636
panch1739 wants to merge 4 commits intomainfrom
docs/ai-chat-history

Conversation

@panch1739
Copy link
Member

@panch1739 panch1739 commented Mar 13, 2026

This PR adds documentation to construct the AI chat history.

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

Dependency with: #1641

Documentation.
Examples.
Dashboards Demo.
Playwright report.

Coverage Reports:

Code Coverage

@panch1739 panch1739 added this to the 49.x milestone Mar 13, 2026
@panch1739 panch1739 requested a review from hbxes March 13, 2026 10:05
@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 Mar 13, 2026
Copy link
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 documentation for the AI chat history pattern. The new documentation is well-structured and informative. I have provided a couple of suggestions to better align the content with the repository's UX writing guidelines, specifically concerning sentence length and image accessibility.

Comment on lines +50 to +51
If space remains insufficient due to a high number of metadata elements, consider prioritizing
the most relevant attributes and progressively removing secondary ones to preserve clarity.
Copy link
Contributor

Choose a reason for hiding this comment

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

medium

This sentence is 30 words long, which exceeds the 25-word limit recommended by the repository's UX writing guidelines for better readability. Please consider shortening it.

Suggested change
If space remains insufficient due to a high number of metadata elements, consider prioritizing
the most relevant attributes and progressively removing secondary ones to preserve clarity.
If space is insufficient, prioritize the most relevant attributes and progressively remove secondary ones to preserve clarity.
References
  1. The repository's UX Writing Guidelines recommend keeping sentences under 25 words for readability. (link)

@hbxes
Copy link
Member

hbxes commented Mar 13, 2026

What happens if you click on the icon below??
Bildschirmfoto 2026-03-13 um 12 17 29

@hbxes
Copy link
Member

hbxes commented Mar 13, 2026

otherwise, it's good to go...

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.

2 participants