Skip to main content

11 docs tagged with "Plugin documentation"

View all tags

Plugin code prechecks

In the Moodle Plugins directory, uploaded plugins versions are automatically tested against a set of formal criteria. These tests typically do not check the actual plugin functionality, security or code correctness. They are more focused on formal aspects of the coding style. As such, they are most valuable for the plugin maintainers themselves.

Plugin contribution checklist

The Plugins Directory has moved to Moodle Marketplace. This checklist describes the legacy Plugins Directory approval process and should not be used for new plugin submissions.

Plugin documentation

Plugin developers, maintainers and users are welcome to include documentation about their plugin in the English Moodle Docs. Of course it is fine to have documentation elsewhere, such as the Github wiki, however one advantage of including documentation in the English Moodle Docs is that 'Moodle Docs for this page' links in Moodle (when logged in as a teacher or admin) can lead directly to your plugin documentation (as explained in the Header and footer documentation). And, very important, it will then be very easy for translators of Moodle Docs to add translations for this information.

Plugin QA prechecks

This page describes Plugin QA prechecks from the previous Plugins Directory review process. We plan to bring plugin review guidance back for Moodle Marketplace in the future. We'll let the community know when updated guidance is available.

Plugins adoption programme

We plan to bring the programme back for Moodle Marketplace in the future. We'll let the community know when updated guidance is available.

Plugins directory

Moodle Marketplace is now the place to find, submit, and manage Moodle plugins. Go to Moodle Marketplace. For documentation, see Moodle Marketplace Provider Documentation

Plugins guardians

We plan to bring it back for Moodle Marketplace. We'll let the community know when updated guidance is available.