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
Currently, by editors, the lessons are manually created using Postman and then videos are individually uploaded on each lesson's edit page
Lesson wizard is also used on app.egghead. Multiple lessons are created from a form, then you can upload videos directly to each lesson. This lacks bulk uploading features and the ability to create a course and immediately associate lessons to it https://app.egghead.io/lesson_uploads/new
This process basically guarantees instructors will never be able to partake in lesson uploading since it's complex and unclear
Once lessons are uploaded they each have to individually be searched for on the course edit page and added to the course. This process takes a lot of time and requires you to remember each lesson title
Desired state
Zac needs to be able to create a course and lessons from a folder full of videos sent by an instructor.
More specifically he needs to be able to create a course and immediately be able to add a title and associate it with an instructor and tags. Then be able to drag and drop a folder full of video files and create a lesson for each video.
Lessons also need to be given titles and tags.
What needs to be done
Migrating instructors into Sanity is a potential prerequisite for this course builder
Instructors need to be associated with a course but as of now instructor collaborators in Sanity do not have their instructor_id, preventing Sanity from being used as the source of data for instructors
A course model in Sanity that supports lesson references needs to be created.The current resource model expects other resources and Zac has noted that he doesn't use most fields in Resource.
Add course title and tag fields to form on /upload
Handle course fields on API route. Extra call to sanity during batch mutation.
Use a Sanity/GROQ webhook to notify Rails of any creates, updates, and changes to courses and lessons so that the representative records in Rails can be updated. https://www.sanity.io/docs/webhooks
Scope and boundaries
This needs to be backwards compatible with existing Resources with course and lesson types.
We can avoid migrating our video processing here and just stick to using our existing Rails API.
Stick to bulk lesson uploading with a course. One video means one lesson. In the future we potentially want to support multiple types of lesson and resources that aren't directly tied to a lesson.
Keep tagging to course level for now. We can default to giving each lesson the same tag as the course. Tags can be changed in the Sanity studio if they don't fit a particular lesson.
Along with instructors, we may also have to migrate tags into Sanity.
For now, we'll restrict access to the page to all users except for editors and admins. In the future we would like instructors to have access to the course builder but we'll need to restrict access to certain features which is outside the scope of the current project.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Summary
Create a course builder with bulk video upload.
Problem
Currently, by editors, the lessons are manually created using Postman and then videos are individually uploaded on each lesson's edit page
Lesson wizard is also used on app.egghead. Multiple lessons are created from a form, then you can upload videos directly to each lesson. This lacks bulk uploading features and the ability to create a course and immediately associate lessons to it https://app.egghead.io/lesson_uploads/new
This process basically guarantees instructors will never be able to partake in lesson uploading since it's complex and unclear
Once lessons are uploaded they each have to individually be searched for on the course edit page and added to the course. This process takes a lot of time and requires you to remember each lesson title
Desired state
Zac needs to be able to create a course and lessons from a folder full of videos sent by an instructor.
More specifically he needs to be able to create a course and immediately be able to add a title and associate it with an instructor and tags. Then be able to drag and drop a folder full of video files and create a lesson for each video.
Lessons also need to be given titles and tags.
What needs to be done
Migrating instructors into Sanity is a potential prerequisite for this course builder
Instructors need to be associated with a course but as of now instructor collaborators in Sanity do not have their instructor_id, preventing Sanity from being used as the source of data for instructors
A course model in Sanity that supports lesson references needs to be created.The current resource model expects other resources and Zac has noted that he doesn't use most fields in Resource.
Add course title and tag fields to form on
/upload
Handle course fields on API route. Extra call to sanity during batch mutation.
Use a Sanity/GROQ webhook to notify Rails of any creates, updates, and changes to courses and lessons so that the representative records in Rails can be updated. https://www.sanity.io/docs/webhooks
Scope and boundaries
This needs to be backwards compatible with existing Resources with course and lesson types.
We can avoid migrating our video processing here and just stick to using our existing Rails API.
Stick to bulk lesson uploading with a course. One video means one lesson. In the future we potentially want to support multiple types of lesson and resources that aren't directly tied to a lesson.
Keep tagging to course level for now. We can default to giving each lesson the same tag as the course. Tags can be changed in the Sanity studio if they don't fit a particular lesson.
Along with instructors, we may also have to migrate tags into Sanity.
For now, we'll restrict access to the page to all users except for editors and admins. In the future we would like instructors to have access to the course builder but we'll need to restrict access to certain features which is outside the scope of the current project.
Beta Was this translation helpful? Give feedback.
All reactions