Development:Moodle User Interface Guidelines
The greatest risk of this project is that developers may not find it when they need it, while designing parts of Moodle. Please help: please look at what is here already now, and comment: How could it serve your development work better? What aspects of user interface design would you need clear guidelines on? See also: Introduction
Risks: they will not find it, they will not trust it, they will not read it, they will not understand it, they put development realities first and not go by it, they will not comment it when it does not fit; use the guidelines. If you have a reason not to, comment on it in the forums.
Note: This page is a work-in-progress. Feedback and suggested improvements are welcome. Please [ http://moodle.org/course/view.php?id=5 join the discussion on moodle.org] or use the page comments.
This is a starting point for the front page of the forthcoming Moodle User Interface Guidelines. (See: Development:Usability/Improve_Moodle_User_Experience_Consistency project.
About these guidelines
- Introduction (TODO: See Pattern Language Structuring Patterns)
- Problem-Solution Summary Table (TODO: See [1]
- Glossary
Moodle UI style and elements
- Big Select List
- Search
- ...