Skip to main content

24 docs tagged with "Coding guidelines"

View All Tags

Automated code review

Moodle issues submitted for review and inclusion into core are examined by our continuous integration (ci) system and checked against various automated tests. We use the automated checks to help improve the code quality in Moodle.

Component Library

The Component Library is a tool designed for developers to identify frequently used user interface (UI) components and encourage their reuse within Moodle. It includes both components from Twitter Bootstrap and Moodle itself. The library provides an organized display of these components, showcasing them with your current Moodle theme.

Data-loss

This page forms part of the Moodle security guidelines.

Policies

This is the top-level page describing Moodle's coding standards and guidelines. It's the place to start if you want to know how to write code for Moodle.

Security

This page describes how to write secure Moodle code that is not vulnerable to anything that evil people may try to throw at it.

SQL coding style

This page describes recommended coding style for complex database queries.

SQL injection

This page forms part of the Moodle security guidelines.

Style guides

We are looking to implement both a coding style guide, and a writing style guide, for this documentation. This will include appropriate tooling and information.