You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Export a json representation of a Path and all it's children.
Original Request to Product
Paths, made up of lessons, and grouped in units are a large amount of structured data. This content tends to be authored in context of others with lots of navigation between lessons, and may already exist in another format. A static folder structure would allow use of git/github allowing collaboration between instructors to maintain, discuss and collaborate on content outside of the learn / online platform. A formal importer will embrace intercampus collaboration to produce better content, and allow offline authoring.
Implementation Thoughts
Folder - (Path, folder name, is titleized and set to name + description)
Folder (Unit, same method as containing path)
lesson_name.md
Front Matter containing each field required for online
title: A cool thing
description: It’s actually ice cold
type: (assignment or lesson)
due_date: (Ideally using something like chronic to allow natural language as dates will be relative coming from a repo)
order: 1
Body of file is… the body
Thoughts
Adding a config.yml or config.json, file to each folder (path / unit) could allow for better importing of titles and descriptions.
This could be as simple as a a file upload of a zip folder, or something fancy like a github integration.
It could be trivial to allow an export / import and handle a round trip for a path.
The text was updated successfully, but these errors were encountered:
Export a json representation of a Path and all it's children.
Original Request to Product
Paths, made up of lessons, and grouped in units are a large amount of structured data. This content tends to be authored in context of others with lots of navigation between lessons, and may already exist in another format. A static folder structure would allow use of git/github allowing collaboration between instructors to maintain, discuss and collaborate on content outside of the learn / online platform. A formal importer will embrace intercampus collaboration to produce better content, and allow offline authoring.
Implementation Thoughts
Thoughts
Adding a config.yml or config.json, file to each folder (path / unit) could allow for better importing of titles and descriptions.
This could be as simple as a a file upload of a zip folder, or something fancy like a github integration.
It could be trivial to allow an export / import and handle a round trip for a path.
The text was updated successfully, but these errors were encountered: