Student projects/Usability issues: Difference between revisions
From MoodleDocs
No edit summary |
|||
| Line 18: | Line 18: | ||
* Create usability tests to find new usability issues (optional). | * Create usability tests to find new usability issues (optional). | ||
* Take a look at [http://fluidproject.org/ Fluid Project] (who we are involved with already) to see where some of their components can be used in Moodle (optional). | * Take a look at [http://fluidproject.org/ Fluid Project] (who we are involved with already) to see where some of their components can be used in Moodle (optional). | ||
== Tasks == | |||
== Status == | == Status == | ||
Revision as of 17:39, 13 August 2008
This page is a specification under construction! If you have any comments or suggestions, please share them with us.
The main objective of this project is to detect and solve specific usability issues.
Index
Objectives
- Research in the tracker, forums, etc. to create a hitlist of the top 10 (or 20) specific usability issues.
- For each issue, identify the problem clearly (screenshots) and clearly describe one or more solutions (incl mock screenshots) for the community to evaluate.
- Create code to solve the problem with the best decided solution (optional, depending on Moodle community thoughts).
- Create usability tests to find new usability issues (optional).
- Take a look at Fluid Project (who we are involved with already) to see where some of their components can be used in Moodle (optional).
Tasks
Status
TO BE UPDATED
See also
- GSOC/2008
- Using Moodle GSOC: Moodle Usability Guidelines forum discussion
- GSoC 2008 Usability Issues Meta bug: MDL-14639
- Usability component in the tracker
