plugin development
-
Moodle 5.3 AI: what core does and when you need a plugin
Moodle 5.3 ships four AI actions, two placements and seven providers. What that covers, what it does not, and when a custom AI plugin is the right call.
-
Moodle 5.3 LTS review: what it changes for plugin code
Moodle 5.3 shipped on time with a first REST API, React navigation and dark mode. What breaks in custom plugins, what is new, and what is still missing for 6.0.
-
GitHub Universe 2026: what agents mean for Moodle plugins
GitHub shipped agents that fix, review, approve and merge pull requests. What is real, what it costs, the risks, and what plugin maintainers should adopt.
-
Testing Moodle plugins when AI agents write the code
Unit, Behat, coverage, mutation and static analysis explained in plain words, how Moodle runs each one, and why tests matter more when an agent writes the code.
-
Moodle's architecture from 1.0 to 5.3, and what it broke
Moodle has been rebuilt in place three times since 2002. What each rebuild changed, from the 2.0 rewrite to hooks, DI and React, and what plugins had to rewrite.
-
A Moodle plugin in days: how it works and what done means
How we take a Moodle plugin from idea to production in days with AI agents and senior review, and the checks every plugin passes before handover.
-
React in Moodle core: what it means for your custom plugins
Moodle 5.2 added React, TypeScript and ES modules to core, and 5.3 started moving core screens over. What changes for plugins you own, and what you can leave alone.