...
Replace legacy Studio Content Library UI with performant, modern React-based MFEs.
Maintain continuity of Content Library feature offerings and experience.
Introduce the ability to statically reference library content in courses.
Move current content libraries data from course-oriented Modulestore to block-oriented Blockstore.
...
We want to maintain continuity of Studio feature offerings and experience. The existing breadth, flexibility, and reliability of Studio is a draw for content authors. We will have to implement a few frontend features (like xblock editing in V2 libraries) to do so. We are hoping to perform a seamless conversion of content. To do so, we will craft runbooks and exercise them in increasingly complex environments.
To prioritize release of the high-value static content reference feature, we will implement parity for the following features after the initial release:
Import and export of Blockstore-backed content libraries.
Copy-paste in the library authoring experience.
Text templates in the library-authoring experience.
Get Ready to slash-n-burn!
...