diff --git a/general/app_releases.md b/general/app_releases.md index 3e270dc6d5..4576e1702d 100644 --- a/general/app_releases.md +++ b/general/app_releases.md @@ -98,4 +98,4 @@ Version 2 was based on Ionic 1 and it supported Moodle versions from 2.4 onwards ## See also {/* #see-also */} -- [Roadmap](./community/roadmap.md) +- [Roadmap](./community/roadmap/index.md) diff --git a/general/community/_roadmap/roadmap-summary.png b/general/community/_roadmap/roadmap-summary.png deleted file mode 100644 index 1da7a24f41..0000000000 Binary files a/general/community/_roadmap/roadmap-summary.png and /dev/null differ diff --git a/general/community/contribute.md b/general/community/contribute.md index fda47714a8..c5bf73edd1 100644 --- a/general/community/contribute.md +++ b/general/community/contribute.md @@ -33,7 +33,7 @@ You'll find them in the [How do I contribute to Moodle?](https://moodle.com/faq/ ## What happens next? {/* #what-happens-next */} - The [list of most voted-for new features](https://moodle.atlassian.net/secure/IssueNavigator.jspa?mode=hide&requestId=10512) is regularly reviewed by Moodle HQ and other core developers. -- Promising ideas are added to the [Roadmap](roadmap.md) (depending on funding availability). +- Promising ideas are added to the [Roadmap](./roadmap/index.md) (depending on funding availability). - Small feature ideas and improvements may be added to core by the component maintainer. ## How to maximise the chance of your idea being implemented {/* #how-to-maximise-the-chance-of-your-idea-being-implemented */} diff --git a/general/community/intro.md b/general/community/intro.md index 46f5d48f6c..43fa88193e 100644 --- a/general/community/intro.md +++ b/general/community/intro.md @@ -22,7 +22,7 @@ There are many other people contributing to Moodle in many ways, such as coding, ## How we develop the Roadmap {/* #how-we-develop-the-roadmap */} -The [Roadmap](./roadmap.md) lists the new features being developed for the next major version. This list is derived mostly from issues with large numbers of votes in the Moodle [Tracker](../development/tracker/guide.md), so please vote for what you want! Other influences include general discussion, surveys and feature requests at MoodleMoots and in the Moodle forums. +The [Roadmap](./roadmap/index.md) lists the new features being developed for the next major version. This list is derived mostly from issues with large numbers of votes in the Moodle [Tracker](../development/tracker/guide.md), so please vote for what you want! Other influences include general discussion, surveys and feature requests at MoodleMoots and in the Moodle forums. Component leads decide on features in individual components, so make your case to them! diff --git a/general/community/meetings/2019/03.md b/general/community/meetings/2019/03.md index 988147f862..e3f1fe5d78 100644 --- a/general/community/meetings/2019/03.md +++ b/general/community/meetings/2019/03.md @@ -19,4 +19,4 @@ sidebar_position: -03 ## Agenda {/* #agenda */} 1. Reminder: "Clean" theme is being deprecated! Bootstrap Base themes will no longer be supported in Moodle Core. A "Classic" theme, visually similar to "Clean" but based on Bootstrap 4, will be released with Moodle 3.7. -1. Review [Moodle Roadmap](../../roadmap.md) +1. Review [Moodle Roadmap](../../roadmap/index.md) diff --git a/general/community/meetings/index.md b/general/community/meetings/index.md index c34b836fcd..4eb34c4eee 100644 --- a/general/community/meetings/index.md +++ b/general/community/meetings/index.md @@ -177,4 +177,4 @@ If you have a topic you would like volunteer to speak about, please reach out vi ## See also {/* #see-also */} -- [Roadmap](../roadmap.md) +- [Roadmap](../roadmap/index.md) diff --git a/general/community/roadmap.md b/general/community/roadmap.md deleted file mode 100644 index c189327546..0000000000 --- a/general/community/roadmap.md +++ /dev/null @@ -1,98 +0,0 @@ ---- -title: Roadmap -tags: - - Core development -sidebar_position: 4 ---- - -Our Moodle Products roadmap is designed to provide visibility on the development priorities of the Moodle HQ Product teams portfolio, consisting of Moodle LMS, Moodle Workplace, MoodleCloud, Moodle Apps, Moodle Community Sites, Moodle Academy and Tech Transformation. - -import Link from '@docusaurus/Link'; - -:::tip[View our living Roadmap] - -Our Roadmap is public, open, and living - you can see it at any time on our [Roadmap Kanban board](https://moodle.atlassian.net/jira/software/c/projects/IDEA/boards/104?ignoreStickyVersion=true). - - - - ![A summary of the current roadmap](./_roadmap/roadmap-summary.png) - - - -::: - -## What is a roadmap and why is it important? {/* #what-is-a-roadmap-and-why-is-it-important */} - -The Moodle Products roadmap is our shared source of truth at Moodle HQ which we use to define our product direction, priorities and progress. - -It is the plan that aligns our teams around common goals and outcomes. - -## Who creates the roadmap and how often does it get updated? {/* #who-creates-the-roadmap-and-how-often-does-it-get-updated */} - -The Moodle HQ Product teams curate every idea on the roadmap during our quarterly planning processes. - -Every three months, the team takes a week off development to complete detailed planning of the work to be delivered during our next increment and map out our areas of focus for a rolling 12 to 18 months ahead. - -Before each planning week, our Product leads conduct engagement sessions with our stakeholders and review a range of data sources to collect ideas and prioritise the roadmap. - -## Where do the ideas come from? {/* #where-do-the-ideas-come-from */} - -We curate our ideas from a wide range of sources including; - -1. Moodle HQ Product teams continuously review issues created by our users who can log new feature requests and ideas for improvements in our [public tracker](https://moodle.atlassian.net/projects/MDL/issues/MDL-75914?filter=allopenissues). The issues can also be voted on by our community to mark interest in the suggestions made by others. -1. Our [public forums](https://moodle.org/course/) are available to all community members to obtain support and discuss ideas. They are a rich source of feedback that is used to inform our roadmap. -1. The official voice of our users is the [Moodle Users Association](https://moodleassociation.org/), a group of passionate Moodlers from around the world who suggest and vote for new ideas to be delivered at each new release of the Moodle LMS platform. -1. Many of our Products have Product Advisory Groups (PAGs) which meet on a regular basis to help inform the priorities of our roadmap ideas. These groups are formed by representatives from our user base and our [Moodle Partners](https://moodle.com/solutions/certified-service-providers/) network with whom we work closely to define the needs of our markets in education and workplace learning. -1. Each of our products offers the opportunity to provide feedback via short questionnaires, we review the responses regularly and use the insights to shape our thinking. -1. All members of the Moodle HQ team are encouraged to share their thoughts on the future of our open source platform. From new innovations to maintenance tasks, every idea is welcomed and is considered for prioritisation during our planning process. - -## How should the roadmap be interpreted? {/* #how-should-the-roadmap-be-interpreted */} - -Our roadmap is not strictly speaking a delivery plan - we don't explicitly provide dates for each of our deliverables. The reason for this is that we know that the world around us is changing at pace, new ideas are constantly emerging and urgent issues pop up from time to time. - -Rather, we publish our roadmap using the 'Now, Next, Later' methodology, detailing the current order we plan to follow in delivering new features and enhancements across our product portfolio. - -The purpose of sharing the roadmap is to drive understanding in the community on where Moodle HQ's priorities lie. Our teams are often asked 'Why are you not working on X, it is really important', and the answer to that question is most frequently 'We agree that X is really important, but right now A is more important to more of our users and the future of our platform'. - -That's because, at Moodle HQ, we have to balance the needs of our broad range of stakeholders and think long-term about our products. The point of sharing the roadmap is to make our prioritisation balancing act more transparent. - -## What are Moodle HQ's current priorities? {/* #what-are-moodle-hqs-current-priorities */} - -Moodle is a platform that is dedicated to empowering educators, trainers and learners all around the world. Our goal is to create solutions that make learning accessible to everyone, regardless of their location or financial situation. - -To achieve this goal, the areas we will focus on when developing our future versions of Moodle are: - -### Unlocking Creativity {/* #unlocking-creativity */} - -We aim to empower educators and learners to shape their learning according to their imagination and aspirations, leading to a more inclusive and personalised educational experience. This will be achieved through: - -- Optimisation of our current course interface and activities -- Introduction of new course experiences -- Diversification of content creation options - -### Facilitating Collaboration {/* #facilitating-collaboration */} - -We will focus on enabling supportive and connected learning environments by continuously improving Moodle's ability to integrate and collaborate effectively with other solutions and leverage common standards. This will be achieved through: - -- Supporting plugin development -- Leveraging of common standards -- Capitalising on open source solutions - -### Optimising outcomes {/* #optimising-outcomes */} - -Providing our users with tools that optimise their efforts is paramount. We aim to create a toolset that not only reduces the time and cost of managing and creating courses but also helps learners overcome challenges more effectively. This will be achieved through: - -- Ecosystem support for advanced analytics -- A more modern & leaner platform -- New tools to support learners - -## Where can I find out more? {/* #where-can-i-find-out-more */} - -To see all the details for our upcoming developments, you can visit the roadmap at any time simply by logging into Tracker and [viewing our public board](https://moodle.atlassian.net/jira/software/c/projects/IDEA/boards/104?ignoreStickyVersion=true). - -To stay up to date with all the latest developments, please keep an eye out for our Showcase Shorts, a bird's eye view of our latest design and development outcomes, announced on moodle.org [Community News](https://moodle.org/news) every few weeks. - -To find out more about Moodle release time-frames, please visit our [Releases](../releases.md#general-release-calendar) page. diff --git a/general/community/roadmap/_roadmaps/cc_roadmap.png b/general/community/roadmap/_roadmaps/cc_roadmap.png new file mode 100644 index 0000000000..eb7739900c Binary files /dev/null and b/general/community/roadmap/_roadmaps/cc_roadmap.png differ diff --git a/general/community/roadmap/_roadmaps/lms_roadmap.png b/general/community/roadmap/_roadmaps/lms_roadmap.png new file mode 100644 index 0000000000..66ae2a0624 Binary files /dev/null and b/general/community/roadmap/_roadmaps/lms_roadmap.png differ diff --git a/general/community/roadmap/_roadmaps/mktplc_roadmap.png b/general/community/roadmap/_roadmaps/mktplc_roadmap.png new file mode 100644 index 0000000000..64b69866bc Binary files /dev/null and b/general/community/roadmap/_roadmaps/mktplc_roadmap.png differ diff --git a/general/community/roadmap/_roadmaps/tt_roadmap.png b/general/community/roadmap/_roadmaps/tt_roadmap.png new file mode 100644 index 0000000000..69aa75cdc1 Binary files /dev/null and b/general/community/roadmap/_roadmaps/tt_roadmap.png differ diff --git a/general/community/roadmap/index.md b/general/community/roadmap/index.md new file mode 100644 index 0000000000..b788baa059 --- /dev/null +++ b/general/community/roadmap/index.md @@ -0,0 +1,52 @@ +--- +title: Roadmap +tags: + - Core development +--- + +Our detailed roadmaps are designed to provide visibility into the development priorities for Moodle LMS and Moodle Marketplace. These roadmaps are are open and living. Click on the links below for more details about them. + +- [Moodle LMS Roadmaps](./lmsroadmap.md) +- [Marketplace Roadmap](./mktplc_roadmap.md) + +## What is a roadmap and why is it important? + +At Moodle HQ we use roadmaps as the source of truth where we document our product direction, priorities and progress. + +We use these roadmaps as the plans that align our teams, ensuring our work is focused on common goals and clear outcomes. + +## Who creates the roadmap and how often does it get updated? + +The Moodle HQ Product teams curate every idea on the roadmap during our quarterly planning processes. + +Every three months, the team takes a week off development to complete detailed planning of the work to be delivered during our next increment and map out our areas of focus for a rolling 12 to 18 months ahead. + +Before each planning week, our Product leads conduct engagement sessions with our stakeholders and review a range of data sources to collect ideas and prioritise the roadmap. + +## Where do the ideas come from? + +We curate our ideas from a wide range of sources including; + +1. Moodle Product teams continuously review issues created by our users who can log new feature requests and ideas for improvements in our [public tracker](https://moodle.atlassian.net/). The issues can also be voted on by our community to mark interest in the suggestions made by others. +2. Our [public forums](https://moodle.org/course/) are available to all community members to obtain support and discuss ideas. They are a rich source of feedback that is used to inform our roadmap. +3. Our Product Advisory Groups (PAGs), which meet on a regular basis, help inform the priorities of our roadmap ideas. These groups are formed by representatives from our user base and our [Moodle Partner](https://moodle.com/solutions/certified-service-providers/) network with whom we work closely to define the needs of our markets in education and workplace learning. +4. All members of the Moodle HQ team and our Community are encouraged to share their thoughts on the future of our open source platform and Moodle Marketplace. From new innovations to maintenance tasks, every idea is welcomed and is considered for prioritisation during our planning process. + +## How should the roadmaps be interpreted? + +Our roadmaps are not, strictly speaking, delivery plans - we don't explicitly provide dates for each of our deliverables. The reason for this is that we know that the world around us is changing at pace, new ideas are constantly emerging and urgent issues pop up from time to time. + +At Moodle HQ, we have to balance the needs of a broad range of stakeholders; the point of sharing the roadmaps is to make our prioritisation balancing act more transparent. + +That's why we publish our roadmaps using the 'Now, Next, Later' methodology, detailing the current order we plan to follow in delivering new features and enhancements across our product portfolio. These phases should be interpreted as: + +
+| Roadmap Phase | Description | +| --- | --- | +| 🏁 **Awaiting Release** | These are ideas/features that have been completed but aren't released for General Availability.

It should be expected that they are in the next major release of Moodle LMS or Moodle Marketplace. | +| **Now** | These are ideas/features that are currently being worked on.

It should be expected that these should be delivered in the upcoming release, and no more than 2 releases away. | +| **Next** | These ideas/features are what will be worked on once the items in "Now" are completed. They are likely currently being worked on in 'Discovery' mode only.

Ideas/features in this phase would be 6-12 months away. | +| **Later** | These are ideas/features that we believe are important to get onto as soon as capacity allows. We want to work on them, but after the Now and Next items. | +| **Later Still** | These are ideas/features that we think are valid, but currently sit behind other ideas in our roadmap. We will investigate and consider them for the future. | + +
diff --git a/general/community/roadmap/lmsroadmap.md b/general/community/roadmap/lmsroadmap.md new file mode 100644 index 0000000000..3a8007775a --- /dev/null +++ b/general/community/roadmap/lmsroadmap.md @@ -0,0 +1,99 @@ +--- +title: LMS Roadmaps +tags: + - Core development +sidebar_position: 1 +--- +Our Moodle LMS Products roadmaps are designed to provide visibility on the development priorities of each of our Moodle LMS teams, consisting of Moodle LMS Core, Community Contributions and Tech Transformation. + +Our roadmaps for Moodle LMS are public, open, and living - you can see them at any time by clicking on the links below. + +import Link from '@docusaurus/Link'; + +:::tip[LMS Core Roadmap] + +Our Moodle LMS Core team focuses on work that enhances the usability and core functionality of the platform. + + + + ![A summary of the current LMS roadmap](./_roadmaps/lms_roadmap.png) + + +::: + +:::tip[Community Contributions Roadmap] +Our Community Contributions team works on core functionality via project-based collaboration with developers from our community, including Moodle Certified Partners. + + + ![A summary of the current LMS Community Contributions roadmap](./_roadmaps/cc_roadmap.png) + + +::: + +:::tip[Tech Transformation Roadmap] +Our Tech Transformation team focuses on work that modernises the technical foundations of the platform. + + + ![A summary of the current Tech Transformation roadmap](./_roadmaps/tt_roadmap.png) + + +::: + +## What is Moodle's LMS product strategy? + +Moodle exists to make learning accessible to everyone, regardless of location or financial situation, cultivating a community of lifelong learners and helping every person unlock their full potential. + +Every product decision is guided by our commitment to creating solutions that are user-focused, mindfully changing our platform to avoid unnecessary disruption to our users, and a non-negotiable commitment to security, accessibility and compliance. + +These principles sit alongside our belief that AI should support teaching and learning, not replace it, always human-centred and always leaving educators in control. + +Moodle LMS carries that mission into reality by equipping educators to design courses grounded in good practice. As learning content becomes commoditised and AI can generate a course in minutes, our focus is on what AI can't replace: learning designed with intent, connected to outcomes, and worth a learner's time. + +By FY29, Moodle LMS will be both intuitive and powerful: the most educator-focused LMS in the world, chosen because it drives better teaching outcomes at scale. + +To get there, we will focus on the following areas when developing future versions of Moodle LMS + +**Unlocking Creativity** + +We aim to help educators focus on what they want to teach, not how to use the platform, making Moodle LMS more intuitive so imagination and pedagogy come first. This will be achieved through: + +- A platform-wide visual uplift, delivering a smoother first impression and a consistent, modern design language +- Outcomes-first course design, with guided design and modern authoring support built in +- Embedding Learning Design frameworks directly into course creation, diversifying how educators build content + +**Facilitating Collaboration** + +We will keep Moodle LMS working seamlessly within broader technology ecosystems, making it easier to extend and upgrade, without compromising our open source foundation. This will be achieved through: + +- Supporting plugin development, giving partners and developers a stable foundation to innovate on +- Deepening LTI integration, moving LTI into the core so tools embed flexibly rather than as bolt-ons +- Capitalising on our open source model for AI integrations, choice and diversity of model options, no lock-in + +**Optimising Outcomes** + +We aim to reduce the friction educators face in managing courses and helping learners succeed, so that Moodle continues to earn their advocacy. This will be achieved through: + +- Premium marking workflows, including multiple marking, individual feedback management, and moderated double marking +- A leaner, more modern platform that reduces time and cost in course management +- Helping educators align activities to learning outcomes with confidence, giving learners clearer paths to success + +**How can I get involved?** + +To join the voice of our community, provide input on our roadmaps and guide what we build next, you can join our different LMS PAGs. To find out more, visit the sites below: + +    [Moodle LMS Community PAG](https://moodle.org/lms-community-pag) + +    [Developer meetings](https://moodle.org/mod/bigbluebuttonbn/view.php?id=8596) + +    [Technical Transformation PAG](https://moodle.org/course/view.php?id=17257) + +To find out more about Moodle release timeframes, please visit our [Releases](../../releases.md#general-release-calendar) page. diff --git a/general/community/roadmap/mktplc_roadmap.md b/general/community/roadmap/mktplc_roadmap.md new file mode 100644 index 0000000000..ce138e3504 --- /dev/null +++ b/general/community/roadmap/mktplc_roadmap.md @@ -0,0 +1,41 @@ +--- +title: Marketplace Roadmap +tags: + - Core development +sidebar_position: 2 +--- + +Our Moodle Marketplace roadmap is designed to provide Moodle users and the Community Developers who contribute to the Moodle plugin and extensions ecosystem with visibility of upcoming enhancements and changes to that platform. + +import Link from '@docusaurus/Link'; + +:::tip[Marketplace Roadmap] +Our Moodle Marketplace roadmap is public, open, and living - you can see them at any time by clicking on the links below. + + + + ![A summary of the current Marketplace roadmap](./_roadmaps/mktplc_roadmap.png) + + +::: + +## What is the Moodle Marketplace product strategy? + +Moodle exists to make learning accessible to everyone, regardless of location or financial situation, cultivating a community of lifelong learners and helping every person unlock their full potential. + +Every product decision is guided by our commitment to creating solutions that are user-focused, mindfully changing our platform to avoid unnecessary disruption to our users, and a non-negotiable commitment to security, accessibility and compliance. + +Moodle Marketplace is the new platform for discovering, evaluating and accessing Moodle-compatible plugins and integrations. + +We created Moodle Marketplace to make it easier for Moodle users to find high-quality free and paid plugins and integrations to enhance their Moodle sites. + +Moodle Marketplace prioritises the health and vibrancy of the Moodle ecosystem; it supports the HQ-led development of Moodle LMS while giving developers in our community a way to showcase and sustain their work. + +**How can I get involved?** + +To join the voice of our community, provide input on our roadmap and guide what we build next, you can join our Marketplace PAG. To find out more, visit the site below: + +   [Moodle Marketplace PAG](https://moodle.org/course/view.php?id=17260) diff --git a/general/releases.md b/general/releases.md index 294f85f805..9252b99cdf 100644 --- a/general/releases.md +++ b/general/releases.md @@ -567,7 +567,7 @@ Bug fixes for security issues in 1.9.19+ branch by [Catalyst IT](http://catalyst ## See also {/* #see-also */} -- [Roadmap](./community/roadmap.md) - future versions +- [Roadmap](./community/roadmap/index.md) - future versions - [Moodle versions](https://docs.moodle.org/dev/Moodle_versions) - an explanation of how our versions work plus version numbers for each release (for $plugin->requires) ## Translations {/* #translations */} diff --git a/src/css/custom.css b/src/css/custom.css index ba85c82450..8daba563b9 100644 --- a/src/css/custom.css +++ b/src/css/custom.css @@ -164,3 +164,9 @@ ul ol { /* Prevent overlapping custom components, such as ProjectSummary */ clear: both; } + +.roadmap-table table tbody tr:nth-child(1) { background-color: #baf3db; } +.roadmap-table table tbody tr:nth-child(2) { background-color: #dcfff1; } +.roadmap-table table tbody tr:nth-child(3) { background-color: #fef7c8; } +.roadmap-table table tbody tr:nth-child(4) { background-color: #ffeceb; } +.roadmap-table table tbody tr:nth-child(5) { background-color: #f8eefe; }