[DEPR]: studio-frontend repo

[KristinAoki]

Proposal Date

02 June 2023

Ticket Acceptance Date

15 August 2023

Technology Removal Date

11 April 2024

First Open edX Named Release Without This Functionality

Sumac

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
• checklists.html
• course status in course_outline.html

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

No response

[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.

[KristinAoki]

Redwood will be the first release with the new pages and the old pages. The old pages for the Checklist page and the Accessibility Request page have redirects in edx-plaform that always redirect to the new page. The Files and Uploads page redirect can be toggled with the contentstore.new_studio_mfe.use_new_files_uploads_page waffle flag. The new pages are at feature-parity with the old pages.

[kdmccormick]

Awesome! Do you have any opposition if Tutor toggles on the new Files & Uploads page by default? We could add opt-out instructions to the Redwood release notes. That would allow removal to begin as early as the day after the Redwood cut date.

[KristinAoki]

No opposition.

[kdmccormick]

Cool, I will take care of making sure Tutor runs the new page in Redwood, can you update the timeline in the issue description?

[kdmccormick]

Thanks Kristin. Here's where I'll be working on adding this to Tutor: overhangio/tutor-mfe#201