Type of Request
Fast Track Change (small, low-risk improvements)
Feature Description
Redesigns the Advanced Settings page in Studio for course authors. Right now the page shows about 82 course settings in a flat, alphabetical list of raw JSON fields. It's hard to navigate and easy to make mistakes when editing. The redesign groups the settings into collapsible sections by category (General, Grading, Schedule, Certificates, and so on), and swaps the raw JSON textarea for inputs that match each data type: toggles for booleans, number fields, dropdowns for fixed options, and a CodeMirror editor for the more complex JSON. The goal is to make the page easy to use for non-technical authors without taking anything away from power users.
This is a small, low-risk change focused on the interface. The input type and the options for each setting come from the backend, they are not hardcoded in the frontend. There's a demo video showing the new page in action in the frontend PR (#3019).
Pull Requests:
Frontend (Course Authoring MFE): openedx/frontend-app-authoring#3019
Backend (platform API, exposes type and options for each setting): openedx/openedx-platform#38784
Context:
Discourse discussion: https://discuss.openedx.org/t/modernize-ui-options-for-advanced-settings/17269
Schema proposal "Relocating Advanced Settings": https://openedx.atlassian.net/wiki/spaces/COMM/pages/5236785155/Relocating+Advanced+Settings
Link to Product Proposal
https://discuss.openedx.org/t/modernize-ui-options-for-advanced-settings/17269
Status
New
Proposed By
Schema
Type of Request
Fast Track Change (small, low-risk improvements)
Feature Description
Redesigns the Advanced Settings page in Studio for course authors. Right now the page shows about 82 course settings in a flat, alphabetical list of raw JSON fields. It's hard to navigate and easy to make mistakes when editing. The redesign groups the settings into collapsible sections by category (General, Grading, Schedule, Certificates, and so on), and swaps the raw JSON textarea for inputs that match each data type: toggles for booleans, number fields, dropdowns for fixed options, and a CodeMirror editor for the more complex JSON. The goal is to make the page easy to use for non-technical authors without taking anything away from power users.
This is a small, low-risk change focused on the interface. The input type and the options for each setting come from the backend, they are not hardcoded in the frontend. There's a demo video showing the new page in action in the frontend PR (#3019).
Pull Requests:
Frontend (Course Authoring MFE): openedx/frontend-app-authoring#3019
Backend (platform API, exposes type and options for each setting): openedx/openedx-platform#38784
Context:
Discourse discussion: https://discuss.openedx.org/t/modernize-ui-options-for-advanced-settings/17269
Schema proposal "Relocating Advanced Settings": https://openedx.atlassian.net/wiki/spaces/COMM/pages/5236785155/Relocating+Advanced+Settings
Link to Product Proposal
https://discuss.openedx.org/t/modernize-ui-options-for-advanced-settings/17269
Status
New
Proposed By
Schema