Content Comparison

TI3 Deliverables:

• Prepare Moodle 4.1 codebaseUX - UI/UX review of Titus Theme  - Image ModifiedCTP-15291801: Prepare Moodle 4.1 codebaseUX - UI/UX review of Titus Theme

  • What: Prepare Moodle 4.1 codebaseWhy: ???Review the global approach to Moodle redesign - Not just theme, but to include course formats, navigation etc. Focused feedback UX interviews with stakeholder groups. Common task workshops. Identify issues and note comments—feedback into Titus design process.

  • Why: To ensure that the new Moodle Theme and combination of Moodle course formats and UCL System designer give our end user the best UI/UX experience we will be working with a Moodle specialist UI/UX to provide an "informed" point of view of our development and advise us on any additional changes we should implement to the UCL Moodle. We will also use this opportunity to document the license under which we are engaged with Titus learning in providing the UCL "leased theme" to ensure we understand what changes UCL can make to the Theme either directly via Titus or via UCL staff or another 3rd party.

  • Dependency: ? / Risk: ?

• Fixes for 4.ux - Image RemovedCTP-1969: TI2-3 Fixes for 4.ux

• What: ???.

Why: ???

Moodle 4.2 - codebase UX - MyFeedback rework - Image ModifiedCTP-20231992: Moodle 4.2 - codebase

• What: Work through any breaking issues in the 4.2 build on release day. Resolve remaining open issues logged with community plugins. Fix remaining warnings and failing tests in the build. All fixes where merge requests are pending are documented and applied to the Moodle 4 build for the prod upgrade.

• Why: Moodle 4.2 will be released on the 24th April 2023, this is the major version UCL will be upgrading to (from 3.11), while a lot of effort has gone into fixing the UCL codebase since 3.9, the intermediary 3.11 upgrade and dev builds of Moodle 4.0/4.1 - 4.2 is the one we will go live with so will need a final push to deal with the remainder of the associated technical debt.

• Dependency: ? / Risk: ?

UX - MyFeedback rework

• What: Scope out UI/UX  development work for an improved MyFeedback. Produce wireframe/mockups. Agree mockups. Identify development partner. Develop UI/UX. Iterative feedback cycle on development. Agree release MVP. Release and Deploy as part of Moodle 4.x. Update Documentation. Communicate change.

• Why: Review UCL MyFeedback report plugin to improve user experience. From work identified in the 4.UI/UX, we will rework the UCl MyFeedback UI/UX to work with the new Moodle Theme and improve its overall accessibility and user experience.

• Dependency: ? / Risk: ?

• Block development - Image AddedCTP-2045: Block development

  • What: Development for UCL’s dashboard. Blocks include marketing block, site announcements, and feedback.

  • Why: ???.

  • Dependency: ???.

• Moodle 4.UX Titus Development of new UCL Theme - Image AddedCTP-1791: Moodle 4.UX Titus Development of new UCL Theme

  • What: Design of new Moodle theme. Clear agreement and terms of use for the Titus theme. 
    Engagement with Titus learning to ensure Theme matches UCL desired expectations and requirements. Stakeholder feedback. Adherance to UCL Design-System. Deployment of preview instances.

  • Why: As a user of Moodle 4.x I will have an excellent user experience in look, feel, navigation and over all use of the Moodle 4.x platform. As a senior stakeholder UCL Moodle will look “modern” “high quality” “premium” and match the insitutions reputation for excellence. As a member of UCL Digital Presence the UCL theme will adhere to the UCL banding and system design as much as is possible within the Moodle application.

  • Dependency: ???.

• Development of the new UCL Theme by Titus Learning - Image AddedTCTP-1990: Development of the new UCL Theme by Titus Learning

• • What: Design discussions between UCL and Titus to continue to refine UCL requirements and deliverables. To actively seek feedback upon the theme development via engagement with stakeholder groups. Timely responsive and relevant communication to be delivered to appropriate stakeholder groups e.g Blogs, Townhalls, staff news etc
    • Senior stakleholders
    • User focus groups
    • Moodle Development User group
    • Digital Accessibility team
    • UCl Design team
    • General staff and student

• • Why: Engage with both focus groups and wider community. Ensure clear and appropriate communication with stakeholder groups. Obtain feedback feed into continuous improvement process. Make selected themes available to Digi-Ed staff and to wider user group to elicit feedback. This should be staged with user group expanding as choices narrow on theme design.

  • Dependency: ???.