| 5 | | |
| 6 | | === Redesign the Layout === |
| 7 | | The design of Sahana Eden could be enhanced greatly with everything from a better colour scheme (for example, the grey menu blends into the browser which is confusing) to making more efficient use of space. If you're more of a web designer than programmer, your input is greatly needed. If you could come up with static designs for the following pages, or programmers can do their thing and make Sahana Eden beautiful. If you can design and program, even better! |
| 8 | | * Home Page - http://demo.eden.sahanafoundation.org/eden/ |
| 9 | | * [http://eden.sahanafoundation.org/attachment/wiki/ProjectInformation/Sahana%20Eden%20-%20Home.jpg] |
| 10 | | * Dashboard - http://demo.eden.sahanafoundation.org/eden/org/index |
| 11 | | * [http://eden.sahanafoundation.org/attachment/wiki/ProjectInformation/Sahana%20Eden%20-%20Dashboard.jpg] |
| 12 | | * List View - http://demo.eden.sahanafoundation.org/eden/project/activity |
| 13 | | * [http://eden.sahanafoundation.org/attachment/wiki/ProjectInformation/Sahana%20Eden%20-%20List.jpg] |
| 14 | | * List Add View - http://demo.eden.sahanafoundation.org/eden/org/organisation (requires login) |
| 15 | | * [http://eden.sahanafoundation.org/attachment/wiki/ProjectInformation/Sahana%20Eden%20-%20List%20Add.jpg] |
| 16 | | * Component View - http://demo.eden.sahanafoundation.org/eden/org/organisation/8/store |
| 17 | | * [http://eden.sahanafoundation.org/attachment/wiki/ProjectInformation/Sahana%20Eden%20-%20Components.jpg] |
| 18 | | Please share the image files and the original design files (preferably an open standard) |
| 19 | | |
| 20 | | === Design a Sahana Eden Theme === |
| 21 | | Using the [DeveloperGuidelines/Themes Theme Functionality]. If it's good it may even be used to update the current Sahana Eden theme! |
| 22 | | |
| 23 | | |
| 24 | | === Conduct a Usability Test === |
| 25 | | 1. Find a person to do be your test subject for the Usability Test. Anyone will do! |
| 26 | | 1. On either the [http://demo.eden.sahanafoundation.org/ The Sahana Eden Demo Site] or a local instance of Sahana Eden get your test subject to go through one of these workflows |
| 27 | | 1. Add a Volunteer |
| 28 | | 1. Add an Office |
| 29 | | 1. Send an Item from a Warehouse |
| 30 | | 1. Add an Asset and assign it to a Volunteer |
| 31 | | 1. View Staff on the Map |
| 32 | | 1. Write up a report on the Usability Test and send it to the Sahana Eden MailingList. |
| 33 | | 1. What the test subject found easy |
| 34 | | 1. What the test subject found hard |
| 35 | | 1. What the test subject liked |
| 36 | | 1. What the test subject dis-liked |
| 37 | | 1. What would you improve in Sahana Eden (even better if you can make these improvements!) |
| 38 | | |
| 39 | | For more instructions of how to conduct a usability test from the book "Don't Make Me Think" go to: http://www.sensible.com/downloads-dmmt.html |
| 40 | | |
| 41 | | === Design a (better) GUI for the CAP broker === |
| 42 | | Proposed by: [http://lirneasia.net/profiles/nuwan-waidyanatha | Nuwan][[BR]] |
| 43 | | |
| 44 | | This is for Common Alerting Protocol (CAP) with capabilities for multi-language alerting and multi-media delivery. Use Agasti CAP Broker as a starting point. (This needs clarification. Eden does not have a CAP broker that I know of. And the current Agasti CAP support is in Krakatoa, not Mayon, so needs to be ported there too. So before there can be a GUI, there would need to be a port or implementation of a CAP broker, no? --Pat) |
| 45 | | |
| 46 | | '''Specific : ''' Build a [http://sixrevisions.com/user-interface/website-wireframing/ | wireframe] with functionality for the [http://www.incident.com/cookbook/index.php/Welcome_to_the_CAP_Cookbook | Common Alerting Protocol] messaging broker. It should follow a publisher subscriber model. Some specifications are in the [http://lirneasia.net/wp-content/uploads/2009/05/Sahana-CAP-Msg-Mod-v0.2.pdf | CAP Software Requirement Specifications] [[BR]] |
| 47 | | '''Measurable : ''' CAP messaging broker is becoming a much sort after tool by many organizations. It is an ITU recommendation. Such tool can be easily adopted by governments and emergency coordination agencies for managing their alerting and situational awareness. [[BR]] |
| 48 | | '''Attainable : ''' [[BR]] |
| 49 | | Step 1 :: Study the Sahana Agasti CAP Broker [[BR]] |
| 50 | | Step 2 :: document the requirements [[BR]] |
| 51 | | Step 3 :: develop the wireframe to provide the required functionality [[BR]] |
| 52 | | Step 4 :: run the wireframe through a set of test scenarios, to be documented as stories [[BR]] |
| 53 | | '''Relevant : ''' Part of the Sahana interoperability policy. [[BR]] |
| 54 | | '''Time-bound : ''' Given that the Sahana Agasti CAP broker has much of the functionality it should not take too long to develop the wireframe. [[BR]] |
| 55 | | '''Evaluate : ''' Requirements will be discussed with the Sahana community and a prototype wireframe will be presented.[[BR]] |
| 56 | | '''Reevaluate : ''' Once the wireframe is built on the concluded requirements that will be put to test through the scenario based testing. [[BR]] |
| 57 | | |
| 58 | | === Write a blueprint for a GUI (web) tool to build and test XSL files === |
| 59 | | Proposed by: [http://lirneasia.net/profiles/nuwan-waidyanatha | Nuwan][[BR]] |
| 60 | | |
| 61 | | '''Specific : ''' Given that Sahana is getting heavy on XML there should be a tool to develop text, html, etc. outputs based one's own XSL transformation file. The user should be presented with the option to select the XML file; i.e. tags and schema, then include/exclude those tags with inserts of fixed text. The user should be able to preview the output. The built XSL file can then be stored to be used for a particular function. In this case it would be producing CAP message based user specific outputs for email, web, rss, twitter, google, etc. [[BR]] |
| 62 | | '''Measurable : ''' This would allow super users to develop implementation specific CAP content delivery outputs. [[BR]] |
| 63 | | '''Attainable : ''' [[BR]] |
| 64 | | Step 1 :: research existing available solutions to get a feel for the type of functionality needed [[BR]] |
| 65 | | Step 2 :: document and discuss the set of requirements with Sahana community [[BR]] |
| 66 | | Step 3 :: develop the wireframe and test it with test scenarios [[BR]] |
| 67 | | Step 4 :: document the set of specifications [[BR]] |
| 68 | | '''Relevant : ''' The Irrigation department may want the CAP messages to be formed in one way in an email compared with that of the Health department. A rapid XSL development tool will put the burden of building and maintaining those finals in the hands of the users and implementers and not engineers. [[BR]] |
| 69 | | '''Time-bound : ''' [[BR]] |
| 70 | | '''Evaluate : ''' design requirements and settling on them. [[BR]] |
| 71 | | '''Reevaluate : ''' wireframe with the test scenarios [[BR]] |
| | 5 | See: Contribute/UI |
