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
Line 6: Line 6:


==Moodle basics==
==Moodle basics==
* Hierarchy of a Moodle site
* Hierarchy of a Moodle site [http://moodle.org/mod/forum/discuss.php?d=115620 one attempt]
* Page types and structure
* Page types and structure
* Roles
* Roles

Revision as of 15:55, 7 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 might not use the guidelines, please tell me about it in the developer forum thread. See also: Introduction


Moodle basics

  • Hierarchy of a Moodle site one attempt
  • Page types and structure
  • Roles
  • Groups

Moodle UI library

UIs are built of Elements and Interaction Styles (bigger wholes, which are built of Elements).

Elements

  • Tabs
  • Jump Navigation
  • Tooltip
  • Links and Buttons
  • Switch (or Toggle?)
  • Command Popup Menu
  • Dialog
  • Popup Window

Interaction Styles

  • Wizard (or Assistant?)
  • Form (will be covered in some way but may be divided in smaller pieces)
  • 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

Proposed

  • Quick Inline Help ([1] for now)

General design guidelines

See also

Implementation advice

Todo