[DEPR]: studio-frontend repo

[KristinAoki]

Update: This DEPR has been subsumed into [DEPR]: All Legacy Studio Frontends.

---

Proposal Date

2025-02-19

Target Ticket Acceptance Date

2025-03-05

First Open edX Named Release Without This Functionality

2025-09-08

Ulmo

Rationale

This repo is currently only used inside the edX Studio. The React code is imported into Django templates and rendered inside of Studio. The React code is only used on four pages, Assets, Accessibility Form, Course Outline Status, and Checklist. The pages in edX Studio are being update to use React and moved to frontend-app-course-authoring. To reduce the redundancy of two studio frontend repos, this one will be removed and the components that are not slated to be redesigned will be copied over to frontend-app-course-authoring.

Removal

The entire repo will be removed and the following references inside edx-platform:

• accessibility.html
• health check, including references from:
  • checklists.html
  • course status in course_outline.html
• legacy files and uploads page
• image upload from the legacy Text editor
  • Removing the image upload is contingent on the legacy Text editor deprecation: [DEPR]: Legacy Text Editor edx-platform#34692
    • Note that this does not affect the other usages of the tinyMCE editors, eg Announcements.

Replacement

The majority of the code will be rewritten in frontend-app-course-authoring. The accessibility and checklist will be moved to frontend-app-course-authoring. The code won't change, but will live in the frontend-app-course-authoring.

Deprecation

No response

Migration

No response

Additional Info

Communicated here: https://discuss.openedx.org/t/deprecation-removal-studio-frontend-381/10280

Blocked by openedx/edx-platform#34692

[kdmccormick]

I'm excited for this one 🔥

[dianakhuang]

@KristinAoki We are in the process of assigning owners for DEPR tickets to ensure that we have a point of contact on the current status of them. I assigned you to this one since you seem to be handling most of the movement of the ticket. Out of curiosity, why is this in 'deprecated' instead of 'removing'? Is it just because we're not doing active work on it?

[KristinAoki]

@dianakhuang I was not fully sure which it belonged under. The code has been moved to course authoring, but the act of removing the repo and references to it in edx-platform has not begun

[kdmccormick]

@KristinAoki , I think Deprecated is the right status. I see you marked it as deprecated already, which is great.

How can we move it forward? Ideally, 1 release should go by where both the old pages and the new pages are available for operators to use; has that happened yet? And are the new pages at feature-parity with the old pages?

If it's Yes on both counts, then your team or anyone else in the community would be all-clear to start removing studio-frontend.