Note: You are currently viewing documentation for Moodle 2.0. Up-to-date documentation for the latest stable version is available here: Student projects/Usability issues.

Student projects/Usability issues

From MoodleDocs

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

  • [Student_projects/Usability_issues/Plan Plan]
  • [Student_projects/Usability_issues/Timeline Timeline]
  • [Student_projects/Usability_issues/Tasks Tasks]
  • [Student_projects/Usability_issues/FAQ FAQ]
  • [Student_projects/Usability_issues/Downloads Downloads]

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).

Status

TO BE UPDATED

See also