Workflow overview¶
One pipeline, three authoring tracks. Everyone ends with the same commands: validate → preview → build.
Pick your track¶
flowchart TD
start[New to LXPack]
q1{Comfortable in an IDE?}
q2{Using Claude in the editor?}
design[Claude Design]
cursorOnly[Cursor only]
claudeCode[Claude Code]
start --> q1
q1 -->|No| design
q1 -->|Yes| q2
q2 -->|No| cursorOnly
q2 -->|Yes| claudeCode
design --> pipe[validate → preview → build]
cursorOnly --> pipe
claudeCode --> pipe
-
Instructional designers: Claude for drafts, any editor + Terminal for
lxpack. -
IDE file tree and integrated terminal; you write the content.
-
Cursor + Claude Agent, optional Git, monorepo-friendly.
Shared pipeline¶
| # | Step | Command / action |
|---|---|---|
| 1 | Plan | Objectives, storyboard, LMS target |
| 2 | Edit | course.yaml, lessons/, assessments/, interactions/ |
| 3 | Validate | lxpack validate |
| 4 | Review | lxpack preview |
| 5 | Export | lxpack build --target … |
| 6 | Deploy | LMS admin imports .lxpack/*.zip |
From Storyline, Rise, or Captivate?¶
Start with Migrating from legacy tools — you keep instructional design skills; the file model changes from slides to folders + web pages.
Related guides¶
See Build courses for lesson, quiz, and export depth. For AI:
v0.6.4 / LessonKit 1.0
v0.6.4 supports LessonKit 1.0 via @lessonkit/lxpack and lxpack build --lessonkit. React authors should start at github.com/eddiethedean/lessonkit (lessonkit package). YAML/markdown authors use lxpack directly. Phase 5 may add more LXPack-side automation.