Derive module hierarchy from curriculum
Translates the finished curriculum outline into a concrete platform module/section/lesson hierarchy with naming conventions the platform will accept.
In / outFinished curriculum outline + platform naming constraints → platform module/section/lesson hierarchy
You might say…
“The curriculum outline and the platform's content tree are different shapes — this maps one to the other before I start creating content slots.”
What it does
Translate the finished curriculum outline into a concrete platform module/section/lesson hierarchy with ordering, mapping each content asset to its slot. Used when first structuring the course shell before upload.
Trigger: Use after base platform config is done and before creating any content slots, to translate the curriculum structure into platform-ready hierarchy.
Recognise the problem?
The primitives are the commodity part. The fastest next step is a conversation about composing them into something that works for you.
Start a conversation