If you want to create a new page for developers, you should create it on the Moodle Developer Resource site.


From MoodleDocs

<< Back to MoodleNet index



The first year of the MoodleNet project focused on the Conceive, Plan, and Develop parts of the Product Lifecycle. An overview of what we achieved can be found in this 2018 retrospective post on the MoodleNet blog.


Our main aim for 2019 was to ensure that we carry out extensive testing of both MoodleNet's value proposition and ability to set up federated instances, before delivering a version of MoodleNet for internal testing.


This year, we aim to build out the functionality and features of MoodleNet based on the recommendations from the original white paper, feedback from the community (via Changemap, and our prioritisation grid (August 2019).

We need to be responsive to users while thinking strategically about the order in which to build the following. We need to balance features that users demand and functionality that ensure MoodleNet is sustainable. With our current budget and resourcing, we are prioritising:


  • Moodle LMS integration
  • Federation testing
  • Resource uploading
  • Moderation by admins
  • Toast notifications


  • User testing (on Moodle HQ-run instances) - including data export and deletion
  • Extensible architecture
  • Tagging and categorisation
  • Roles and access controls
  • Push notifications


  • Private communities/collections
  • Direct messaging
  • Collaborative blocklists
  • Theming
  • Display Open Badges on user profiles


  • Share resource from Moodle LMS to MoodleNet collection
  • Request resources
  • Moodle HQ provided cloud hosting for MoodleNet
  • Social sign-in
  • User-requested extensions & improvements


  • Events/meet-ups
  • Communities can define their own taxonomies
  • Crowdfunding resources into existence
  • Version control for OER (incl. forking and merging)
  • Uploading videos (integration with third-party services)