| Guide ID | T-8 |
|---|---|
| Audience | Teachers, Curriculum designers |
| Prerequisites | T-7: Working with Knowledge Packs |
| Time | 20 minutes |
| Difficulty | Intermediate |
Building Course Materials
Knowledge packs provide the raw content structure for building educational courses. This tutorial walks you through selecting packs for a curriculum, mapping modules to lessons, creating assessment rubrics, and building cross-pack curricula that use the dependency graph for sequencing. By the end, you will understand how to assemble a complete course from knowledge pack components.
Step 1: Select Packs for Your Curriculum
Start by identifying which knowledge packs align with your course objectives. Consider the subject matter, the target audience level, and how packs connect through the dependency graph.
For example, an introductory coding course might draw from:
- CODE-101 (Computer Science & Coding) — Primary pack covering computational thinking, programming fundamentals, and algorithms
- MATH-101 (Mathematics) — Supporting pack for mathematical thinking that underlies programming
- PROB-101 (Problem Solving) — Supporting pack for structured problem-solving approaches
Check the dependency graph to ensure prerequisites are satisfied. CODE-101 recommends MATH-101 and PROB-101 as prerequisites, so including all three creates a coherent learning path.
Step 2: Read Module Structures
Open each selected pack's .skillmeta file and examine the modules. Each module contains:
- Learning objectives — What the learner will understand or be able to do after completing the module
- Activities — Hands-on exercises and explorations, scaled by age group
- Assessment criteria — How to evaluate whether the learning objectives were met
For CODE-101, the five modules are:
- Module 1: Computational Thinking & Algorithms
- Module 2: Programming Fundamentals
- Module 3: Building Projects & Problem-Solving
- Module 4: Algorithms & Efficiency
- Module 5: Computing & Society
Each module's activities use progressive disclosure — the same concept is presented at age-appropriate levels from elementary through college.
Checkpoint 1
Verify: Open the .skillmeta file for your primary pack and list all its modules. Each module should have clear learning objectives and at least one activity. Confirm the module count matches what is listed in the INDEX.md (most packs have 5 modules).
Step 3: Map Modules to Lessons
Transform pack modules into a lesson plan by mapping them onto a course schedule. A typical mapping approach:
- One module per 1-2 weeks — Gives learners time to absorb and practice each concept
- Interleave supporting packs — When CODE-101 Module 4 (Algorithms) requires mathematical reasoning, schedule the relevant MATH-101 modules beforehand
- Scale by audience level — Use the pack's progressive disclosure to select age-appropriate activities from each module
Example: 12-week introduction to coding course:
| Week | Pack | Module | Focus |
|---|---|---|---|
| 1-2 | PROB-101 | Problem Definition | How to break down problems into steps |
| 3-4 | MATH-101 | Patterns & Algebraic Thinking | Pattern recognition that underlies coding |
| 5-6 | CODE-101 | Computational Thinking & Algorithms | Algorithms, sequences, conditionals |
| 7-8 | CODE-101 | Programming Fundamentals | Variables, loops, functions |
| 9-10 | CODE-101 | Building Projects & Problem-Solving | Apply skills to a real project |
| 11 | CODE-101 | Algorithms & Efficiency | Sorting, searching, Big-O basics |
| 12 | CODE-101 | Computing & Society | Ethics, impacts, responsible computing |
Step 4: Create Assessment Rubrics
Each pack module includes assessment criteria that you can adapt into course rubrics. Assessment criteria are designed to be observable and measurable. To create a rubric:
- Extract the learning objectives from each module
- Define performance levels (e.g., Beginning, Developing, Proficient, Advanced)
- Map specific observable behaviors to each level using the module's activity descriptions
- Ensure alignment between what was taught (activities) and what is assessed (rubric criteria)
The pack's progressive disclosure means you can create rubrics at different complexity levels for the same subject, supporting differentiated instruction.
Step 5: Build Cross-Pack Curricula
For comprehensive programs, use the dependency graph to sequence multiple packs into a multi-course curriculum. The dependency graph ensures prerequisites are satisfied before advanced topics are introduced.
Guidelines for cross-pack curriculum design:
- Start with zero-prerequisite packs — MATH-101, READ-101, SCI-101, TECH-101, and ART-101 require no prior knowledge
- Follow the dependency graph — Each pack's "enables" field lists what becomes available after completion
- Allow parallel tracks — Independent packs can be taken simultaneously (e.g., READ-101 and MATH-101)
- Consider the learner's path — A student interested in engineering might follow: MATH-101, SCI-101, PHYS-101, ENGR-101, MFAB-101, TRADE-101
Checkpoint 2
Verify: You have created a lesson plan that maps at least two packs' modules to a course schedule. Each lesson has a clear learning objective drawn from the pack modules, and the prerequisites in the dependency graph are satisfied by the course sequence.
Accessibility Considerations
All 35 knowledge packs are built with accessibility in mind:
- Screen reader support: Content is structured for screen reader navigation with proper heading hierarchies
- Keyboard navigation: All interactive elements are accessible via keyboard
- Language support: Most packs are available in English, with MATH-101 offering partial Spanish support (45%)
When building course materials, maintain these accessibility standards in your lesson plans and assessments.
What's Next
- Working with Knowledge Packs — Review the full pack inventory and dependency graph
- Specialized Systems — Explore Den Ops for integrated educational environment management