Note: You are currently viewing documentation for Moodle 3.8. Up-to-date documentation for the latest stable version of Moodle may be available here: Interface guidelines.

Development:Interface guidelines: Difference between revisions

From MoodleDocs
mNo edit summary
Line 1: Line 1:
{{Work in progress}}
{{Work in progress}}
This document is not authoritative, it is a collection of ideas and under construction.
This document is not authoritative, it is a collection of ideas and under construction.
See also: [[Development:Usability]]
See also:  
 
* [[Development:Usability]]
* [[Development:Moodle_User_Interface_Guidelines|Moodle User Interface Guidelines]]
==Keeping it simple==
==Keeping it simple==



Revision as of 13:58, 12 August 2009

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 document is not authoritative, it is a collection of ideas and under construction. See also:

Keeping it simple

Use the minimum interface required to get the job done. Order the elements by contexts. Give the user a strong orientation where the places are to do several things.

Standard pages

See Address Bar/URL UI guideline

One script per major function/page

...

Page layout

See: Basic page _structure UI guideline

The information that was here has been included there.

Form layout

See: Form UI guideline

Dealing with tables

Use the print_table function whenever possible.

Standard navigation tools

See:

The information that was here has been incorporated to those pages

URLs

See Address Bar UI guideline

Buttons vs links

See: Development:Button and Development:Link UI guidelines.

The information that was here has been integrated to those documents.

Language strings

  1. Use your own language strings in a separate file. Don't use existing language files from moodle.php or other lang files. So translators can translate in the contexts in different ways as terms are used in the special learning culture.

CSS naming

  • Don't add font, color or layout definitions in code. This belongs to CSS theme files.
  • See theme standards

Linking to help

  • Help buttons should be on the right of the thing (as an exception it can be left, if the thing is right-aligned)

Related topics

Robin Good's Latest News. "Interaction Design Meets Online Real Estate" 1 Mar. 2005 http://www.masternewmedia.org/news/2005/03/01/interaction_design_meets_online_real.htm

The article presents a view of virtual spaces with the focus on human actions. It reminded me of communicative approaches like Moodle. The interface serves as the handle of all the communication tools.