Interface guidelines
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.
This document is not authoritative, it is a collection of ideas and under construction.
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
Form layout]
See: Form UI guideline
Dealing with tables]
Use the print_table function whenever possible.
]
See:
The information that was here has been incorporated to those pages
URLs]
Buttons vs links]
See: Development:Button and Development:Link UI guidelines.
The information that was here has been integrated to those documents.
Language strings]
- 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]
]
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.
See also]
- Development:Usability
- Moodle User Interface Guidelines GSOC 2009 project
Source: docs.moodle.org/503/en/Interface guidelines — MoodleDocs (GPL) · Imported 2026-11-10.
谢谢你的反馈！