docs: add TRG for UX/UI styleguide

[jjeroch]

Description

add TRG for UX/UI styleguide

Pre-review checks

• DEPENDENCIES are up-to-date. Dash license tool. Committers can open IP issues for restricted libs.
• Copyright and license header are present on all affected files

[FaGru3n]

Hi @jjeroch thanks for the work,

i personally would leave out the checkbox style within the TRG but would take it as a little tasklist for the Release guideline checks... or implement this within our PR template.

Then within the TRG it is clear what to consider is a must or be aware of the styleguide.

[RolaH1t]

Quality or Release Gateways are not confirmed for the future process; I therefore propose some wording updates to enable the check of the UI/UX criteria upon releasing a new GitHub version of any app with user interface

[tom-rm-meyer-ISST]

Thanks for providing! The TRG often refers to a styleguide for which I'm not sure which link actually must be handled as. For more explanations, please refer to the comments.

[tom-rm-meyer-ISST]

LGTM, reframing makes it more understandable!

[matbmoser]

So I have added my comments, I believe if we specify more on "what should be there" and "what should be not there" it would be more precise.

Like a "Do’s and don’ts" section

[FaGru3n]

Great work and team effort, thanks for the work LGTM

[evegufy]

So I have added my comments, I believe if we specify more on "what should be there" and "what should be not there" it would be more precise.

Like a "Do’s and don’ts" section

Thanks for the good feedback, just the idea was to transfer the previous state of the styleguide without any new requirements, I suggest to open an update pull request to the TRG once this has been merged.

[matbmoser]

LGTM, wonderful job!