== Usability Testing ==
Whilst we have had a fair amount of testing and bug reports filed, we are also looking for good user experience testing and recommended improvements to make it easier for untrained users to operate Sahana effectively in challenging situations.

We are currently going through a lot of Rapid Application Development as new requests for capabilities go in, and this sometimes means that the user experience is less than optimal. As such, we'd like some good testing of the user experience, and would welcome any suggestions and improvements.

=== Usability Testing Rules of Engagement ===
 * The testing should take place on our Demo server which is located at http://demo.eden.sahanafoundation.org/ - your first task will be to register and apply for an account ;)
 * You will need a Trac account to log tickets for UI/UX bugs and enhancements - please jump into #sahana-eden on irc.freenode.net and ask for an account to be created for you.
 * Please do not enter test data on any production servers for obvious reasons.
 * Please file bugs/technical issues as tickets as per the [wiki:BugReportingGuidelines Bug Reporting Guidelines].
 * If you wish to capture some general advice and guidance, please add it to this wiki page in the Usability Guidelines below.
 * We are not currently testing the installation process, our main UX interest currently is around the deployed interface.

== Usability Guidelines ==
''Please note all usability recommendations and guidelines here.'' 

 * http://www.uxmag.com/design/the-psychologists-view-of-ux-design
 * [http://www.sensible.com/secondedition/index.html Don't Make Me Think]
 * http://www.smashingmagazine.com/2009/03/24/designing-drop-down-menus-examples-and-best-practices/
 * [http://projects.opengeo.org/geoext/wiki/interaction-guide GeoExt style guidelines]
 * Check popular websites, such as Google, Facebook

== Usability Questions ==
There are a number of usability decisions that the developers of Sahana Eden find challenging to make - we're too deep in the code to be objective about it. If you're a user or a a UX wizz, it would be great to have your input!

 * (hrm/human_resource/create) Should we hide the person sub-form if we're selecting from the registry?
 * Should search pages use a single (google-esque) text box to search all fields, or separate boxes for different fields?

----
DeveloperGuidelines[[BR]]

Projects/Advanced/Usability