Skip to content

structure.md

Latest commit

 

History

History
96 lines (69 loc) · 7.42 KB

structure.md

File metadata and controls

96 lines (69 loc) · 7.42 KB

Redstone University: The Complete Course Structure Guide

This document outlines the complete, five-level hierarchical structure for the Redstone University curriculum. Following this guide will ensure that every module, lesson, and section is consistent, creating a seamless and professional learning experience.

Structural Overview

The course is organized into five nested levels:

  • Level 1: The Course - The entire curriculum from start to finish.
  • Level 2: The Part - A major thematic section of the course, comprising several modules.
  • Level 3: The Module - A self-contained chapter focused on building a key component.
  • Level 4: The Lesson - A specific session within a module teaching a core concept or build.
  • Level 5: The Topic - A repeatable pattern for breaking down complex lessons.

Level 1: The Course

Purpose: To define the grand narrative arc of the entire journey. It establishes the vision, shares the personal motivation behind the course, sets a clear roadmap for the student, and handles the initial logistics of getting started.

Structure:

  • Course Introduction: A comprehensive welcome that orients and inspires the student. It should be broken down into the following key sections:

    • The Vision and Personal Motivation ("Welcome!"): This section serves as the hook. It should begin with a compelling question that taps into the student's curiosity. It then introduces the course's core mission (e.g., "making the abstract tangible") and shares the personal origin story of why the course was created. This builds a strong connection with the student and establishes the unique educational philosophy.
    • The Curriculum Roadmap ("The Journey Ahead"): This section acts as a high-level table of contents for the entire course. It should briefly introduce the concept of "Parts" and provide a bulleted list of each Part with a concise, exciting description of the major goal for that stage of the journey.
    • The Target Audience ("Who Is This For?"): A welcoming section that explicitly lists the different kinds of learners who will benefit from the course (e.g., students, professionals, the curious). This helps potential students see themselves in the curriculum.
    • Course Logistics and Accessibility ("How to Get Started"): This is a critical section that answers practical questions upfront. It must explain the primary method for following the course (e.g., in Minecraft) but also provide clear, alternative pathways for those without the software (the "No-Minecraft Track," using simulators). It should also mention what resources will be provided (e.g., World Downloads).
    • The Final Call to Action: A short, concluding paragraph that serves as a powerful, motivational send-off, reinforcing the course's ultimate goal (e.g., "Let's build a machine that thinks.").

  • Course Conclusion ("Graduation"):

    • The Achievement: A final section at the very end of the course celebrating the student's accomplishment. It should summarize the journey from the first logic gate to the final working machine.
    • Beyond the Course: Offers suggestions for advanced projects or further learning to encourage continued exploration.

Level 2: The Part

Purpose: To group related modules into a major, logical milestone. Completing a Part should feel like a significant achievement.

Structure:

  • ## Part X: [Part Title] (e.g., Part 1: The Foundations - Speaking to the Machine)
  • Part Introduction: A narrative bridge that recaps the last Part's achievement and introduces the new grand challenge for the current Part, explaining how the upcoming modules work together to solve it.
  • List of Modules within the Part.

Level 3: The Module

Every module is a self-contained chapter. It begins with a high-level overview to orient the student and ends with a checkpoint to synthesize all the lessons within it.

  • ### Module X: [Module Title] (or ### Module Xa: [Module Title] when a large module is intentionally split into two linked submodules, such as 12a and 12b)
  • Module Summary Block: A quick, scannable block that sets clear expectations.
    • Narrative Beat: The story of this module in one or two compelling sentences.
    • Learning Goals: A bulleted list of what the student will be able to do after completing the module.
    • Lesson Overview: A bulleted list of the lesson titles within the module. This provides an upfront roadmap.
    • Minecraft Artifact: The primary component(s) the student will have built by the module's end.
  • Module Introduction: A strong, story-driven paragraph that explains why this module is the next critical step and what problem it solves in our journey.
  • Numbered Lessons: The core content of the module. Each lesson follows the "Standard Lesson Structure" detailed below.
    • #### Lesson X.1: [Title]
    • #### Lesson X.2: [Title]
    • etc...
  • Module Checkpoint: A final, consolidated section to reinforce and test the module's concepts as a whole.
    • Quiz: 2-4 conceptual questions covering material from all lessons.
    • Debug/Design Challenge: A practical, hands-on problem that requires the student to apply the module's main skills.
    • Real-World Connection: A paragraph connecting the module's main artifact to real-world computer hardware, synthesizing the lessons.
    • Software Connection: A paragraph connecting the module's core principle to a programming concept, algorithm, or common interview problem.
  • Module Conclusion: A summary of what was accomplished and a narrative hook that provides a compelling transition to the next module.

Level 4: The Lesson

Each numbered lesson within a module is a focused session. Crucially, a lesson can be purely theoretical, purely practical, or a mix of both. The Theory/Lab/Experiment sections are components to be used as needed.

  • #### Lesson X.Y: [Lesson Title]
  • The Theory (The "Why"): (Use when needed) Explains the foundational concepts, history, or principles. Answers, "Why do we need this?"
  • The Lab (The "How"): (Use when needed) The hands-on portion where theory becomes practice.
    • Goal: A one-sentence description of the build's objective.
    • Materials Needed: A bulleted list of Minecraft items.
    • The Blueprint: (Optional) Schematics, truth tables, or Boolean expressions to guide the build.
    • The Build Guide: Numbered, step-by-step instructions.
  • The Experiment (The "What"): (Use when needed) Guided testing to verify the build and deepen understanding.
    • The Test Plan: Clear drills to run on the new circuit.
    • Verification / "Aha!" Moment: Explanation of the expected outcomes and what they prove.
  • Lesson-Specific Connections: (Optional) A brief, targeted connection to the real world or software, placed here for immediate relevance.

**Level 5: The Topic **

This is a flexible pattern, not a rigid structure, used inside a Lesson to break down several similar items (like the core logic gates). The exact format should be adapted to the content.

  • ##### [Topic Title] (e.g., Operator 1: AND Gate)
  • Key Descriptors: (e.g., Formal Definition, Rule, Truth Table).
  • Mini "Lab & Experiment": A small, self-contained build and test for just that topic.