Development:Developer documentation: Difference between revisions
(Section for contributed code) |
(→How you can contribute: extended the list of ways to contribute) |
||
| Line 1: | Line 1: | ||
==How you can contribute== | ==How you can contribute== | ||
Even if you are not a programmer there are things you can change or help with. | 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. Even if you are not a programmer there are things you can change or help with. | ||
*[[Activity modules]] | *[[Activity modules]] | ||
*[[Blocks Howto|Blocks]] | |||
*[[Themes]] | *[[Themes]] | ||
*[[Translation]] | *[[Translation|Translations]] | ||
*[[Text filters]] | |||
*[[Resource types]] | |||
*[[Assignment types]] | |||
*[[Question types]] | |||
*[[Question import/export formats]] | |||
*[[Quiz reports]] | |||
*[[Database Schemas|Database schemas]] | *[[Database Schemas|Database schemas]] | ||
*[[Course formats]] | *[[Course formats]] | ||
You can also help a lot by | |||
*[[Bug tracker|Participating in the bug tracker]] | *[[Bug tracker|Participating in the bug tracker]] | ||
Revision as of 10:33, 13 February 2006
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. Even if you are not a programmer there are things you can change or help with.
- Activity modules
- Blocks
- Themes
- Translations
- Text filters
- Resource types
- Assignment types
- Question types
- Question import/export formats
- Quiz reports
- Database schemas
- Course formats
You can also help a lot by
Guides for developers
- Moodle architecture
- Coding guidelines
- Interface_guidelines
- Moodle CVS for developers
- A Step-by-step Guide To Creating Blocks
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.
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 branch of the Moodle CVS repository. Developer documentation for these components should be listed here.
- .
Developer resources and tools
- Moodle bug tracker - bug reports, feature requests and other tracked issues
- CVS code
- Cross reference - phpxref output for browsing Moodle source code
- Core API
- Moodle PHP doc reference
- 1.4 and 1.5 un-merged files
See also
- Moodle Security Centre
- Moodle Partners - providers of custom Moodle development services
- Presentations
- Moodle manuals
- Using Moodle book
