Kyle McCormick

@pdpinch You weren't confused, the scope of the deprecation is the entire legacy text editor (aka, the modal HTMLBlock editor). Your screenshots are correct. The `EditImageModal` part is relevant because...

@pdpinch @SIdnani , thank you for your detailed feedback! As far as I can tell, there is nothing inherent in the implementation new text editor that would prevent us from...

Product proposal relevant to this feedback: https://openedx.atlassian.net/wiki/spaces/COMM/pages/4517920789/Help+course+authors+understand+the+context+of+the+text+and+problems+they+are+editing

Communicated via: https://discuss.openedx.org/t/deprecation-removal-all-legacy-studio-frontends/15049

^ This has been addressed. The ticket is in Transition Unblocked.

We had planned to replace devstack.py with a simpler, YAML-free development.py. But, we found that Tutor's use of devstack.py is tightly coupled to production.py and the YAML-based settings schema. Replacing...

Thanks Braden! Could you clarify what happens if this is Accepted? Would we archive course-discovery, so that it is not part of Teak?

@MichaelRoytman Are there any flags that one needs activate in order to switch from the legacy edx-proctoring frontend to frontend-lib-special-exams? Or is it the case that if a site operator...

Great, thanks @MichaelRoytman ! When we go to remove the legacy edx-proctoring frontend, we should check that Studio Course Preview (the only remaining feature which uses legacy courseware) doesn't blow...

Linking in the wiki comment thread that led to the creation of this DEPR, with some valuable background info: https://openedx.atlassian.net/wiki/spaces/COMM/pages/4262363137/MFE+Rewrite+Tracker?focusedCommentId=4395532312