Curriculum Map

This is the single working map for the curriculum refactor.

Use this table to see the strands, child subjects, lesson topics, readiness levels, refactored lesson targets, and source coverage.

If Refactored Lesson Page is blank, the lesson has not yet been migrated into the staged refactor folder. Staged lesson pages should contain their own copied assets and embedded activity previews.

Visual overview:

• Curriculum Visual Overview

Strand Overview

Working Curriculum Map

This is the primary planning view. K3, E2+, and older Year 1/2/3 files are source histories. The teachable curriculum should use Level 1, Level 2, and Level 3 pathways inside each lesson topic.

Topic Logic

• A subject is a stable navigation bucket, such as Animation, Sensors, or Digital Art.
• A topic names one teachable concept, such as Physical Motion, Stop Motion, or Layers.
• An activity is a modular classroom expression of a topic, such as flipbook, bouncing ball, zoetrope, or moving stamps.
• Avoid topic titles that combine two concepts with and unless the combined phrase is already the concept students need, such as Input & Output.
• When one idea scaffolds another, split the topics and order them in the map.
• Use index.md only at the refactored root and strand roots. Do not create subject-level or topic-level index pages; strand indexes should contain the subject/topic navigation table.

Coverage Summary

This section tracks source coverage without linking lesson pages back to the original source locations. Required files should be copied into the staged lesson package before a refactored lesson is considered usable.

Migration Checklist

Use this checklist to make sure every existing source is placed, copied, staged, and reviewed. Needs HTML means the source is currently PDF/DOCX/PPTX-only or otherwise hard to extract cleanly, so it may need conversion before final markdown rewriting.

Local Asset Policy

Each staged lesson should keep lesson pages clean and place attachments in the single root assets tree:

_LESSONS_REFACTORED/
  assets/
    strand/
      subject/
        lesson-topic/
          teacher-slides.pdf
          activity-page.pdf
          example-image.png
          editable-source.docx
  strand/
    subject/
      lesson-topic.md

Use expandable previews for PDFs and images directly in the lesson page. Keep source history in YAML when useful, but do not rely on links back to _TO DO or old lesson packets for teaching delivery.

Map Rules

1. Organize lessons by content topic, not source unit/week.
2. Use Level 1, Level 2, and Level 3 as readiness levels, not grade labels.
3. K3, E2+, and old Year 1/2/3 files are source histories only.
4. Keep source unit/week/class information in lesson YAML after migration.
5. Leave Refactored Lesson Page blank until a staged lesson exists.
6. Lesson pages in _LESSONS_REFACTORED must copy PDFs, slides, DOCX files, and activity sheets into _LESSONS_REFACTORED/assets/, mirroring the lesson's strand/subject/topic path.
7. Lesson pages should embed PDF and image activities with expandable preview blocks where practical.
8. Do not replace current _LESSONS pages until the staged page is reviewed for completeness, formatting, local assets, and publish safety.