Bug 986736 - Add UX guides to the developer guide to help with consistency
Add UX guides to the developer guide to help with consistency
Product: Beaker
Classification: Community
Component: Doc (Show other bugs)
Unspecified Unspecified
unspecified Severity unspecified (vote)
: ---
: ---
Assigned To: beaker-dev-list
: Documentation
Depends On:
  Show dependency treegraph
Reported: 2013-07-21 21:12 EDT by Raymond Mancy
Modified: 2018-02-05 19:41 EST (History)
5 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2017-01-11 22:39:23 EST
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Raymond Mancy 2013-07-21 21:12:58 EDT
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.
Comment 3 Dan Callaghan 2017-01-11 22:39:23 EST
We have such a guide now, which we can expand as needed when we find anything missing.


Note You need to log in before you can comment on or make changes to this bug.