About UX -> development workflow and canonical UX specification
Point 1
Some of the workflow is described here: https://about.gitlab.com/jobs/ux-designer/ and https://gitlab.com/gitlab-org/gitlab-ce/blob/master/PROCESS.md#workflow-labels
We should probably think about make it clearer and centralize it in a single place.
Also, this is not always clear by simply reading comments in an issue when a proposed UX is:
- approved (btw, who can approve a UX proposal?): normally the
UX
->Frontend
label switch represents this approval - up-to-date: if the UX proposal is 2 months old, it might be outdated
Point 2
This leads to a second question: Is there a canonical place where we can find the current state of the UX that developers should/can implement. The best answer would be:
- mockups file with precise specification about sizes, colors, padding, margin, line height etc., for each page
- a live sandbox where all the individual elements (buttons, dropdowns, search fields etc.) are actually implemented as HTML/CSS/JS, something like http://getbootstrap.com/css/
I found https://gitlab.com/gitlab-org/gitlab-design but the README could get some love so that developers could actually open the design source files (.atype
files?) to see the detailed specification of the UX (colors, sizes, margin, padding, line-height etc.). Working from a screenshot posted in an issue is not the most efficient way to implement a design IMHO. :)
What do you think?