Enable finer-grained control over progress page components

[xitij2000]

Abstract

It is currently possible to show or hide the "Course Completion" widget on the progress page/tab for a course. We propose to make it possible to further customise this page by making it possible to also hide the Related Links, Course Certificate, Grades, Grade summary, and Detailed grades sections of the page.

Detailed Product Proposal

No response

Context & Background (in brief, if a Product Proposal is linked above)

This is a requirement that was brought to us by a client, and we've used the opportunity to add plugin slots to that page to allow implementing this for this client without modifying the default experience, however, if there is a broader need for this we can upstream the ability to toggle these components (in addition to the slots).

Scope & Approach (in brief, if a Product Proposal is linked above)

The work will involve three parts:

• Backend support for storing these toggles. Currently, there is a course field called disable_progress_graph that can be used to disable the course graph. Instead of adding a new boolean for each component we'll add a single dictionary field to store the status of different components in the progress page allowing future expansion. This field will be exposed via the requisite APIs to allow usage in the learning MFE.
• Additional UI in the authoring MFE to allow togging these new components.
• Updates to learner page to allow use the API status to show or hide those components.
  The primary beneficiaries are course authors who would like more control over the learner course experience.

Value & Impact (in brief, if a Product Proposal is linked above)

This proposal will make the default experience more customisable for course authors.

Milestones and/or Epics

This is a relatively straightforward proposal that can be implemented in a single sprint with the three tasks as broken down above.

Named Release

Teak

Timeline (in brief, if a Product Proposal is linked above)

If this proposal is accepted this work can be completed in a 2-week sprint starting after the approval.

Proposed By

OpenCraft

Additional Info

No response

[github-actions]

Thanks for your submission, @openedx/openedx-product-managers will review shortly.