Administrator console for Open edX

Abstract

The proposed project involves the creation of an administrator console for the Open edX platform, a dedicated interface for site administrators to manage and configure their Open edX instances. While the platform currently provides LMS for learners and Studio for course authors, there is a gap in the administrative capabilities that calls for a separate, user-friendly console.

Detailed Product Proposal

https://openedx.atlassian.net/wiki/spaces/OEPM/pages/4412473358/Administrator+console+for+Open+edX

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

In general terms, this initiative wants to bring:

a place for administrators to efficiently manage the Open edX platform
a framework for future extensions of the admin console to be build

More information can be found in the product proposal.

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

The use cases for an administrator console are very diverse and we are not proposing a single project will address them all. The first thing we are proposing is to have a centralized and extensible place for all these use cases to be addressed.

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

Given the lack of hard data about the global use of Open edX it is hard to build strong success metrics at this point, but the main undrelying assumptions are:

The admin console will increase adoption rates, by helping initiatives during the initial and testing stages, which are heavy on configuration requirements.
The admin console will increase retention rates (as in number of initiatives that continue using the platform), by helping initiatives during the operation stages, that are heavy on day to day tasks and user support requirements.

Milestones and/or Epics

Milestone 1: [Community review] Given this is an important piece fills a gap many have experienced in different ways, feedback and discussion from the community will be collected and processed to improve the initiatal proposal.

Milestone 2: [Core solution design] We’ll start with the first version of the admin core and perhaps a few extensions, as well as a well defined set of ground rules for additional extensions to be created later on.

Named Release

Teak

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

The aim will be for the fist version of the admin core + basic extensions to land in the platform in Teak with the goal of strenghtening the product narrative of this mid year release.

Proposed By

edunext

Additional Info

No response

openedx / platform-roadmap