= !BluePrint: Eden UX/UI Guidelines for the Wiki = [[TOC]] === Work in progress === ==== To come ==== 1. Identify the objectives by brainstorming [ ] Begin work to define Personas for "Stakeholders" section. ---- == Introduction == ==== This guide ==== * Is a tool for ensuring **consistency across Eden UX/UI** * A way to get groups to **work together on UX/UI aspects** * **The repository for design** guidelines and standards * **A training aid for new members** of the team ==== Prototype (Nothing new for the moment) ==== * [wiki:WireframeMockupPrototype/BluePrint2013_10 Blueprints] * [wiki:WireframeMockupPrototype/WikiStart2013_10 Home] * [wiki:WireframeMockupPrototype/SiteMap2013_10 Site Map] ==== References ==== * [wiki:BluePrint/Guidelines BluePrint Guidelines] * [wiki:BluePrint/Guidelines/Template BluePrint Template] * [http://www.usability.gov/] * [http://www.konigi.com/wiki/user-interface-style-guides] ==== References for web accessibility ==== * [http://wave.webaim.org/report#/http%3A%2F%2Feden.sahanafoundation.org%2Fwiki%2FBluePrint%2FEdenUxUiGuidelines Web accessibility evaluation] of this page * [http://hr.umich.edu/webaccess/ Web accessibility at the U-M] * [http://webaim.org/standards/508/checklist WebAIM Section 508 Checklist] * [http://dev.opera.com/articles/view/introduction-to-wai-aria/ Introduction to WAI ARIA] * [http://www.w3.org/TR/wai-aria-practices/ WAI-ARIA 1.0 Authoring Practices] * [https://webaccessibility.withgoogle.com/course Google Introduction to Web Accessibility] === Process === ==== Analysis ==== 1. Identify the objectives by brainstorming * [X] 2013-10-11 - Begin work on "Stakeholders" section. 2. Look for “the why of the objectives” to see if it is possible to replace some with objectives of higher level 3. Make a comparative study to see good ideas of other organizations for similar solutions 4. Analyze the data of use to quantify and qualify what is known about user interaction * [X] 2013-10-10 - Begin construction of the Mindmap to make my analysis. ==== Design ==== 1. Prototyping of the solutions to see various approaches allowing reaching the goals 2. Test the best alternatives according to the team 3. Analyze the results of the tests 4. Document the solution (Specification) * [X] 2013-10-09 - Addition of the section UX/UI on the page BluePrint to document the Wiki evolution. * [X] 2013-10-10 - Work on the structure of this page. ==== Construction ==== 1. Develop the solution == Stakeholders == Search result for the possible stakeholders of Sahana and Eden Wiki. Hypothesis: we suppose that the Wiki and Eden are two technological components of the same information system. Only the probability of the usage for a specific component varies for stakeholders. The advantage of this hypothesis is that the reflection which we make for the Wiki also applies for Eden. Developers Developers should read the entire book as they should have an overview of how the software can be used and will need to maintain their local deployment. Basic customization doesn't require any more skills than those required for a Deployer, however, more advanced development will require being familiar with or learning the following skills: Python JavaScript Cascading Style Sheets (CSS) Decision Makers Preparing and planning for crisis and disaster scenarios is an important part of every community. Whether it is at a global, national, regional or local level, leaders who understand the complexities of disaster response make better decisions and can quickly respond to changing situations. Decision Makers should read the "Introduction" section. This content covers the Sahana Eden platform overview, capabilities and selected case studies. This material will help decision makers in strategic planning and give them important insight into the deployment process. Deployers Those who are thinking about or who are ready to deploy Sahana Eden should read the "Introduction", "Getting Started" and "Administration" sections. In order to deploy Sahana Eden, a deployer should be comfortable with the following system administration processes: Installation of an operating system (such as Debian Linux) Command line usage (for package installation) System configuration involving editing of text files End Users - End users are a heterogeneous mass and would like to search to any type of specific queries. new users seasoned user manager translators Site Administrator, Site Operators, Sys Admin System documentors Volunteer groups Team leader/Manager GROUPS AND USER ROLES Guest –guests will be able to view the Active Problems List, Scale, and Item List. Guest - will NOT be able to vote. Guest - can NOT view or contribute to the Discussion Forum. Contributors – Contributors inherit the permissions of the Guest. Contributors – can see and post/reply in the Discussion Forum. Contributors – can add items to the Item List. Contributors – can NOT vote. Participant – inherits both the Guest and Contributor privileges. However, the Participant can Vote. Moderator – A moderator inherits all available permissions. Moderator – can create a new problem Moderator – can edit or delete any item as an option. Moderator - can set up groups by allowing or inviting individuals to the group. Moderator – can email all participants. Moderator – can designate members in a group able to review and accept another person who wishes to join the group. Any member of the system in any role can be an observer in a given group and request a participant or contributor role. People who want to deploy Sahana Bug Marshalls Admin team (general support for SSF infrastructure, including user accounts, systems administration, IRC, demo sites, DNS administration) Community Call Coordinator GSOC Administrators: Accounts Administrator Security response team Sahana Wiki Administrators FIREFIGHTERS == User Stories == TBD == Requirements == TBD === Functional === === Non-functional === TBD === Interoperability === === Standards === === System Constraints === == Design == TBD === Data Model === TBD === Workflows === TBD === Site Map === TBD === Wireframes === TBD === Technologies === == Current Implementation == TBD == Planned Implementation == TBD == Future Extensions == TBD == Outstanding Questions == TBD == References == TBD ---- BluePrint