openedx / openedx/openedx-platform
Sweep for dead legacy Studio frontend code
Open
@feanil is already working on this.
Since Aug 5, 2026.
- Dominant language
- Python
- Stars
- 8.2k
- Forks
- 4.4k
- Avg merge
- 6d 18h
- Merged PRs (30d)
- 42
Description
Once the Legacy Studio DEPR is done, we should go back and remove dangling JS/HTML/underscore/CSS/Sass/etc.
Legacy CMS things that need to continue working:
- The contents of the IFrame on the Library Authoring Unit editor
- The contents of the IFrame in the Library Authoring component editor
- Warning banner when editing legacy library content blocks
- 404.html and 500.html (could be simplified)
- ...I think that's it?
Dangling Legacy CMS things that I think we can drop:
- https://github.com/openedx/openedx-platform/blob/master/cms/templates/export.html
- https://github.com/openedx/openedx-platform/blob/master/cms/templates/export_git.html
- https://github.com/openedx/openedx-platform/blob/master/cms/static/js/views/pages/course_outline.js
- https://github.com/openedx/openedx-platform/blob/master/cms/templates/import.html
- https://github.com/openedx/openedx-platform/blob/master/cms/templates/library.html
- https://github.com/search?q=repo%3Aopenedx%2Fopenedx-platform+%22VideoBlockEditor%22&type=code
- All JS, underscore, CSS, Sass, and JS specs which are not referenced by anything
Not sure (need to check usage):
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Assessment
This issue has not been assessed yet.