Note:

If you want to create a new page for developers, you should create it on the Moodle Developer Resource site.

Moodle User Interface Guidelines: Difference between revisions

From MoodleDocs
mNo edit summary
mNo edit summary
Line 18: Line 18:
* [[User Data Always (Always) Safe|User Data Always (Always) Safe]]
* [[User Data Always (Always) Safe|User Data Always (Always) Safe]]


== Implementation advice ==
== See also ==
* [[Usability|Usability]]
* [[Usability_FAQ|Usability FAQ]]
=== Implementation advice ===
* [[Interface_guidelines]]
* [[Interface_guidelines]]


== Todo ==
== Todo ==
* [[Moodle User Interface Guidelines:Problem-Solution Summary Table|Problem-Solution Summary Table]] (TODO: See [http://www.hillside.net/patterns/writing/patterns.htm#E.1.1])
* [[Moodle User Interface Guidelines:Problem-Solution Summary Table|Problem-Solution Summary Table]] (TODO: See [http://www.hillside.net/patterns/writing/patterns.htm#E.1.1])
* [[Moodle User Interface Guidelines:Glossary|Glossary]]
* [[Moodle User Interface Guidelines:Glossary|Glossary]]

Revision as of 16:01, 29 June 2009

Note: This page is a work-in-progress. Feedback and suggested improvements are welcome. Please join the discussion on moodle.org or use the page comments.

The greatest risk of this effort is that developers may not find it when they need it, while designing parts of Moodle. Please help: 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? If there is any reason you might not use the guidelines, please tell me about it in the developer forum thread. See also: Introduction

About these guidelines

User Interface Guidelines

Moodle UI library

Proposed

  • Quick Inline Help ([1] for now)

General design guidelines

See also

* Usability
* Usability FAQ

Implementation advice


Todo