Move content_libraries to cms? #33428
Labels
code health
Proactive technical investment via refactorings, removals, etc.
content libraries misc
Libraries Overhaul tech work not captured in the stories
Background
The content_libraries django app, exists in the openedx/ source dir, which is used by both LMS and CMS. This means that all content_libraries-related code is available to be imported and invoked in LMS, which could lead to some unintended bugs or architectural issues down the line.
Opinion: Content libraries are used by authors, but NOT learners or instructions. The entire purpose of content libraries is for authors to create content that is NOT visible to the LMS, and then use that content in their courses. There is no reason that content-libraries-supporting code should need to execute in LMS. (We don't have consensus on this opinion.)
Tasks
Figure out whether content_libraries belongs in openedx/ or cms/.
If it belongs in cms/:
Details
TBD. Needs refinement.
The text was updated successfully, but these errors were encountered: