Developer documentation

Guidelines

The following guidelines are crucial reading for anyone wanting to contribute to the Moodle code base:

• Coding guidelines have to be followed by all Moodle developers
• Moodle architecture spells out the basic design goals behind Moodle
• Interface guidelines aim to provide a common feel to the Moodle user interface
• Moodle CVS for developers explains how to work with the Moodle code in CVS

Resources and tools

• Moodle bug tracker - bug reports, feature requests and other tracked issues
• General developer forum
• CVS code - browse the Moodle code via the web
• Cross reference - phpxref output for browsing Moodle source code
• Moodle PHP doc reference - automatically generated documentation
• Development news and discussion section of Using Moodle course
• Unmerged files - changes on the stable branch in CVS that have not been merged to HEAD

How you can contribute

The M in Moodle stands for 'Modular'. There are many different types of components that you can contribute that can be plugged into Moodle to provide additional funtionality. When you have developed a new component please publish it in the database of Moodle modules and plugins. The following types of plugins currently exist (in alphabetical order):

• Activity modules
• Assignment types
• Authentication methods
• Blocks
• Course formats
• Database fields
• Database presets
• Enrollment methods
• Filters
• Question import/export formats
• Question types
• Quiz reports
• Resource types
• SSO plugins

There are also ways you can contribute that don't involve PHP programming:

• Themes
• Translations
• Database schemas

You can also help a lot by

• Testing
• Participating in the bug tracker

Plans for the future

Ideas for and details of planned future features of Moodle are initially discussed on the forums in the Using Moodle course at moodle.org. That developer discussions are intermixed with user discussions in the same forums may seem strange at first but is one of the reasons for the success of Moodle. It is important that both end-users and developers discuss the future features together.

Once ideas begin to crystalize on the forums they can be summarized in this wiki, either as part of the Roadmap or in the form of Developer notes. These pages then form the basis for further discussion in the forums.

• Roadmap
• Developer notes
• Developer conferences

Documentation for core components

This section is for documentation of specific components of the existing core Moodle code. Discussion of components that are under discussion or in development can be found in the Developer notes or on the Roadmap.

• Migration to UTF-8
• Quiz module
• SCORM module 1.5 schema
• Authentication API
• Stats package
• Email processing
• Cookieless Sessions

Documentation for contributed code

Many Moodle users contribute code for the benefit of other Moodle users. This can take the form of new activity modules, blocks, themes, resource plug-ins, assignment plug-ins, question type plug-ins, question import/export formats, quiz report plug-ins, course formats, ... This code is initially posted on the forums in the Using Moodle course and then often go into the contrib area of the Moodle CVS repository. Developer documentation for these components should be listed here.

See also

• Moodle Security Centre
• Moodle Partners - providers of custom Moodle development services