Skip to content

Adding information about UX involvement into non-visual features

Nadia Udalova requested to merge nudalova-master-patch-22123 into master

Why is this change being made?

This change is being caused by discussions in the How to indicate a need for different UX deliverables from Product Designers? issue.

The intention is to raise the awareness that UX involvement is not only relevant to features that are visual or are user interface (UI) related. Features like APIs, yml files, code editors, etc can highly benefit from attention of UX department too.

Author Checklist

  • Provided a concise title for the MR
  • Added a description to this MR explaining the reasons for the proposed change, per [say-why-not-just-what][transparency]
  • Assign this change to the correct DRI
    • If the DRI for the page/s being updated isn’t immediately clear, then assign it to your manager.
    • If your manager does not have merge rights, please ask someone to merge it AFTER it has been approved by your manager in [#mr-buddies][mr-buddies-slack].
    • If the changes relate to any part of the project other than updates to content and/or data files please make sure to ping @gl-static-site-editor in a comment for a review and merge. For example changes to .gitlab-ci.yml, JavaScript/CSS/Ruby code or the layout files.
Edited by Nadia Udalova

Merge request reports