Work is currently underway to create comprehensive Product Requirement Documentation that clarifies the scope of new functionality to support modular, unstructured learning sequence authoring and delivery.
Milestone deliverables will be shared in this space. They will also be cross-posted in the Open edX Product Management wiki.
Big picture goals/impact/context of initiative (no particular order):
Atomic Learning Units are the building blocks of unstructured course (or even non-course) authoring, and unstructured course authoring is the solution for micro-learning
Platform needs to be more neutral about how content is authored and delivered, with simple and more flexible ways of stringing content together
Possible learner and author improvements this work could unlock (drawing directly from: Discovery: Courses Based on Atomic Learning Units )
flexible content reuse
adaptive learning/dynamic content
template courses without limitations of CCX
flexible course experiences
simpler APIs
What is/are the goal(s) of this first phase of work?
(Phase 1): To deliver product/feature requirement documentation that defines and clarifies the scope, approach, impact and goals of the ALU project, in order to guide and support technical discovery work, implementation and delivery (which would be be phase 2)
eg by the end of this phase of work, we would want to be able to say something like: an author would be able to do XYZ - build, tag, sequence, etc, ie articulate the full range of functionality expected and clearly define the intended outcome