Split Schedule and Details Page and Relocate Advanced Settings Accordingly

Feature Ideas
1

:backhand_index_pointing_right: For the full context of the overall project to migrate all Advanced Settings into more suitable locations, see https://openedx.atlassian.net/wiki/x/AwAjOAE

Overview

This project proposes splitting the current Schedule and Details page into two separate pages: Details and Schedule. Alongside this split, several configurations currently in Advanced Settings will be relocated into the appropriate new page. The Details page will contain general course configurations, while the Schedule page will focus exclusively on date-related settings.

Problem

Today, course setup mixes general course information with scheduling options under one combined page, while related fields still live in Advanced Settings. This creates confusion about where to manage specific settings, forces unnecessary navigation, and increases the risk of misconfiguration.

Use Cases

  • As a course author, I want general course settings and scheduling options clearly separated so that I can configure each without scanning through unrelated fields.

  • As an instructor, I need all date-related options grouped together so I can quickly review and manage the course timeline.

  • As an administrator, I need a logical structure that makes it easier to explain where course details versus scheduling settings live.

Supporting Data

The following Advanced Settings will be relocated:

To Details Page (General Course Configurations):

  1. Course display name

  2. Course number display string

  3. Course organization display string

  4. Enable subsection prerequisites

To Schedule Page (Date-Related Configurations):

  1. Due date

  2. Number of relative weeks due by

Relocating these fields into the new pages will:

  • Centralize general course configurations into the Details page.

  • Consolidate all date-related options into the Schedule page.

  • Reduce confusion by clearly separating types of settings.

  • Simplify navigation for course authors and instructors.

2

We should have a serious discussion about whether we want to support this at all. I’m not sure what the originating use case is, but this seems potentially dangerous and misleading.

  • Enable subsection prerequisites

This is one where I think we should get rid of the toggle and just always turn it on all the time, though that will take Product approval.

These exist in Advanced settings because they’re in the InheritanceMixin, i.e. the thing that specifies that a field can be defined anywhere and will inherit through to child elements. They’re only really intended to be used on Subsections. I think we can remove them entirely from the top-level course view. There might be an edge case where people want the convenience of making everything in the course due on the same date, but that seems like a very obscure case relative to the confusion that putting these settings on the Schedule page would cause.