Standards Moodledocs

Leo Migdal

-Dec 12, 2025, 12:38 AM

My favorite and personal go-to resource is provided by Moodle HQ – MoodleDocs. Moodle has a vibrant and diverse community that works together to maintain documentation in MoodleDocs and other community-driven outlets. Aside from manually navigating to the MoodleDocs website, MoodleDocs is integrated into our LMS environment. In the footer of Trine University’s Moodle pages, you will see a little block of information that looks like this: It briefly displays the user that you are logged in as, the course you are visiting, as well as some other helpful hyperlinks. The top link in this block of information is described as ‘Help and documentation.’

This link should appear on any page of our Moodle LMS: Clicking this link will pull up the corresponding MoodleDocs or help documentation. For example, if you are editing a forum within your course and you navigate down to this link, you will be directed to the MoodleDocs resource page for all things related to forums. This repository includes the source for the Moodle Developer Resources - a collection of resources aimed at making your life as a Moodle Developer easier. These resources are written by developers, for developers. We value your input and your help in adding to them.

There are many ways that you can help, from reporting inaccuracies, and missing documentation, to making small corrections and, of course, creating new resources for others to make use of. If you plan to contribute, then you may wish to setup a local development environment to make it easier to do so. We highly recommend that you read our documentation contributions guide, which includes important information on getting started. Moodle is Free, Open Source software (read the GPL licence). It's copyright © 1999 onwards, Martin Dougiamas with portions contributed by many others (see Credits). Moodle Docs is the documentation for Moodle written by the Moodle community.

It's based on wiki technology and is powered by MediaWiki. It's copyright © 2005 onwards by the individual authors of each page (see History link on each page) and is provided to all under the same terms of the GPL as the Moodle software. These Offline Moodle Docs Packages are copyright © 2006 onwards, Antonio Vicent & Eloy Lafuente (stronk7), with all the individual copyrights of the authors of each page as specified above and, of course, are... These packages allow you to browse Moodle documentation offline. Certain links, such as "edit", "history" or "recent changes" still lead to the online version of the documentation. Packages are built using HTTrack website copier plus custom shell scripts for packaging the contents.

If you find a problem or have any feedback or suggestions for improvement, please email docs [at] wimski [dot] org. All comments are welcome! Please noted that neither this site nor the packages for download have any contractual/commercial/economic relationship with Moodle or Moodle Docs, other than as explained above. This site is maintained and supported by devoted Moodlers wishing to experiment and share their ideas. Moodle (/ˈmuːdəl/ MOO-dəl) is a free and open-source learning management system written in PHP and distributed under the GNU General Public License.[3][4] Moodle is used for blended learning, distance education, flipped classroom and other... Moodle is used to create custom websites with online courses and allows for community-sourced plugins.[8][9][10]

Moodle was originally developed by Martin Dougiamas to help educators and scholars create online courses and focus on interaction and collaborative construction of content. The first version of Moodle was released on 20 August 2002 (23 years ago) (2002-08-20), and it continues to be actively developed.[11] The Moodle Project is led and coordinated by Moodle HQ, an Australian company, that is financially supported by a network of eighty Moodle Partner service companies worldwide. Development is also assisted by the open-source community.[12] Moodle is a learning platform used to augment and move existing learning environments online.[13] As an E-learning tool, Moodle developed several features[14] now considered standard for learning management systems, such as a calendar and... This document describes style guidelines for developers working on or with Moodle code.

It talks purely about the mechanics of code layout and the choices we have made for Moodle. The intent of this specification is to reduce cognitive friction when scanning code from different authors. It does so by enumerating a shared set of rules and expectations about how to format PHP code. Unless otherwise specified, this Coding Style document will defer to PSR-12, and PSR-1 in that order. Where a de-facto Moodle standard is encountered but is undocumented, an appropriate MDLSITE issue should be raised to have the standard either documented within this Coding style guide, or rejected and the PSR recommendations... A "de-facto Moodle standard" is any coding style which is commonly and typically used in Moodle.

Consistent coding style is important in any development project, and particularly when many developers are involved. A standard style helps to ensure that the code is easier to read and understand, which helps overall quality. The TinyMCE text editor allows teachers and students to write and edit text in Moodle, including on pages, assignments, questions, forum posts, etc. In addition to editing text, you can use the editor to insert mathematical equations or special characters, add links, embedded media, and check accessibility. The TinyMCE text editor is relevant for: Tip: Make sure to click the three dots on the right corner of the editor to expand the full toolbar.

The TinyMCE text editor contains numerous features. Moodle's internal library of support documents — MoodleDocs — has a page with a complete list of these features. A few of these features are particularly worth highlighting: Caution: Exercise caution when changing font colors. Color contrast needs to meet WCAG standards in order to ensure the contrast is legible. To test color contrast, use a color contrast analyzing tool.

Avoid using color as the only means of conveying information, so that viewers who cannot discern color can also see the distinction. Please review these best practices on Font, Size, Color Contrast, and Plain Language before writing your text.

Standards Moodledocs

People Also Search

My Favorite And Personal Go-to Resource Is Provided By Moodle

This Link Should Appear On Any Page Of Our Moodle

There Are Many Ways That You Can Help, From Reporting

It's Based On Wiki Technology And Is Powered By MediaWiki.

If You Find A Problem Or Have Any Feedback Or