Development:Moodle User Interface Guidelines: Difference between revisions
From MoodleDocs
mNo edit summary |
|||
| (2 intermediate revisions by 2 users not shown) | |||
| Line 2: | Line 2: | ||
<p class="note"> | <p class="note"> | ||
DRAFT DOCUMENT | |||
<br /><br /> | |||
Many of the pages below are incomplete or obsolete. | |||
<br /><br /> | |||
These guidelines were produced as part of a student project in 2009, and are not yet official Moodle guidelines. | |||
</p> | </p> | ||
| Line 52: | Line 55: | ||
* [http://library.gnome.org/devel/hig-book/stable/principles-forgiveness.html.en Forgive the User] | * [http://library.gnome.org/devel/hig-book/stable/principles-forgiveness.html.en Forgive the User] | ||
* [http://library.gnome.org/devel/hig-book/stable/principles-direct-manipulation.html.en Provide Direct Manipulation] | * [http://library.gnome.org/devel/hig-book/stable/principles-direct-manipulation.html.en Provide Direct Manipulation] | ||
* [http://developer.fellowshipone.com/patterns/ Design Patterns Library & Code Standards] by Fellowship technologies | |||
== See also == | == See also == | ||
Latest revision as of 11:46, 22 May 2010
DRAFT DOCUMENT
Many of the pages below are incomplete or obsolete.
These guidelines were produced as part of a student project in 2009, and are not yet official Moodle guidelines.
These guidelines are to be used as a UI reference library by Moodle developers when creating user interfaces.
It does not catalogue all the elements in use in Moodle, but is intended a reference of reusable elements sharing that common Moodle style. We aim to update this reference as new common practices appear. More...
Moodle basics
Moodle UI library
UIs are built of Elements and Interaction Styles (bigger wholes, which are built of Elements).
Elements
- Tooltip
- Link
- Button
- Address Bar (URLs)
Interaction Styles
- Wizard
- Help Popups (See Linking to help for now)
- Feedback page
- Form (incomplete)
- Radio button
- Checkbox
- Dropdown lists (incomplete)
General design guidelines
- Progressive Disclosure
- User Data Always (Always) Safe
- Feedback (Incomplete)
Relevant guidelines from other sites
- Design for People
- Don't Limit Your User Base
- Create a Match Between Your Application and the Real World
- Make Your Application Consistent
- Keep the User Informed
- Keep It Simple and Pretty
- Put the User in Control
- Forgive the User
- Provide Direct Manipulation
- Design Patterns Library & Code Standards by Fellowship technologies
See also
- Further development on Talk page: Development_talk:Moodle_User_Interface_Guidelines
- Using Moodle book
