Moodle User Interface Guidelines: Difference between revisions
From MoodleDocs
| Line 19: | Line 19: | ||
* Data Listing | * Data Listing | ||
* Tabs | * Tabs | ||
* Jump Navigation | * Jump Navigation | ||
| Line 40: | Line 39: | ||
* Modules (not a technical guide but a guideline how what to take into account when using a module as a part of a design) | * Modules (not a technical guide but a guideline how what to take into account when using a module as a part of a design) | ||
* Help | * Help | ||
== Guidelines in development == | |||
* [[Switch Button|Switch Button]] | |||
* [[Add element|Add element]] | * [[Add element|Add element]] | ||
Revision as of 20:30, 17 July 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 feel you can not benefit from the guidelines, please tell me about it in the developer forum thread. See also: Introduction
- Introduction
- Some pages use the Guideline template, others are freeform prose
- Help requested: comment on these guidelines
Moodle basics
- Hierarchy of a Moodle site (one attempt)
- Page structure and different page types
- Roles
- Groups
Moodle UI library
UIs are built of Elements and Interaction Styles (bigger wholes, which are built of Elements).
Elements
- Big Select List
- Hierarchy Browsing List
- Data Listing
- Tabs
- Jump Navigation
- Tooltip
- Links and Buttons
- Command Popup Menu
- Dialog
- Popup Window
Interaction Styles
- Wizard (or Assistant?)
- Form
- Search (will be covered in some way but may be divided in smaller pieces)
- Editing modes (will be covered in some way but may be divided in smaller pieces)
- Blocks (not a technical guide but a guideline how what to take into account when using a block as a part of a design)
- Filters
- Modules (not a technical guide but a guideline how what to take into account when using a module as a part of a design)
- Help
Guidelines in development
Proposed
- Quick Inline Help ([1] for now)
General design guidelines
See also
- Usability
- Usability FAQ
- Major usability issues in Moodle (separate design projects)
Implementation advice
- Developer documentation
- UI coding: Interface_guidelines
Todo
- Problem-Solution Summary Table (TODO: See [2])
- Glossary
