...
Architecturally, we’re still in a place where I think we can support this without too much difficulty. How worthwhile is it to explore this in the Teak timeline?
Example minimal implementation: key generated on a per-library basis, stored in the course data.
Course content Migration Strategy
Are we going to try to convert courses in-place using the existing UI, or do something similar to legacy libraries, where we’re importing potentially multiple courses into the same library?
Starting position per Jenna Makowskiis that the existing Studio UI for creating a single course in a top-down fashion will continue to exist, even if it’s possible to construct courses in Libraries: “… I think we will always need/have two pathways for authoring - creating a top-down course, and creating bottom-up content/stand-alone sequences”
See Migrating Courses to Learning Core for more details.