Red Hat Bugzilla – Bug 986736
Add UX guides to the developer guide to help with consistency
Last modified: 2017-01-11 22:39:23 EST
Currently the developer guide deals mostly with guidelines for laying out code, and how to submit patches. We should have some guidelines on how to deal with basic communication elements of the UX.
The following is a list I can think of off the top of my head, I'm sure there are others:
1) Idempotent functions, and how we report NOPs of these.
2) Text of add/remove buttons (i.e 'Add <entity>' vs 'Add').
3) Reporting failures/success in the WebUI and client.
We have such a guide now, which we can expand as needed when we find anything missing.