Course content
Syncjar’s content workflow is a loop:
- Pull Skilljar into files, and commit them.
- Edit the HTML and JSON in your editor.
- Preview them with your theme.
- Check that nobody has edited the same courses in the dashboard since your pull.
- Push, reviewing a diff of each change.
Quizzes, learning paths and settings follow the same loop, each with its own pull and push:
| What | Pulled by | Pushed by |
|---|---|---|
| Course and lesson titles, content items | pull | push |
| Quizzes | pull | push:quizzes |
| Learning paths | pull:paths | push:paths |
| Per-domain slugs and visibility | pull:slugs, pull:paths | push:published-settings |
| Course settings | pull | push:course-settings |
| Lesson settings | pull | push:lesson-settings |
Keep the content directory in its own git repository. Git history is what shows you what changed in Skilljar between two pulls, and the branch it’s on decides whether a push is allowed.