Bug 986736 - Add UX guides to the developer guide to help with consistency
Summary: Add UX guides to the developer guide to help with consistency
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Beaker
Classification: Retired
Component: Doc
Version: develop
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: beaker-dev-list
QA Contact: tools-bugs
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-07-22 01:12 UTC by Raymond Mancy
Modified: 2018-02-06 00:41 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-01-12 03:39:23 UTC
Embargoed:


Attachments (Terms of Use)

Description Raymond Mancy 2013-07-22 01:12:58 UTC
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-12 03:39:23 UTC
We have such a guide now, which we can expand as needed when we find anything missing.

https://beaker-project.org/dev/guide/ui-guidelines.html


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