Framework: Bloom's Taxonomy (Revised — Anderson & Krathwohl, 2001)
Progression: Sessions 1–2 (Remember/Understand) → Sessions 3–6 (Apply/Analyze) → Sessions 7–9 (Analyze/Evaluate) → Sessions 10–12 (Evaluate/Create)
Assessment Method: All objectives are assessed via hands-on demonstration during practice portions, not written tests.
Date: 2026-01-30
Bloom's Level: Remember / Understand Theme: "What is GitHub and why should my farm use it?"
- Identify the key components of the GitHub web interface (navigation bar, repository page, file browser, README) by pointing to each element during a guided tour
- Describe what a repository is using the farm analogy ("digital barn") and explain its purpose for organizing farm information
- Navigate a sample farm repository to locate specific files (planting schedule, equipment log, README) without instructor assistance
- Create a GitHub account and configure basic profile settings (display name, avatar) following step-by-step instructions
- Explain in their own words one way GitHub could help their farm, using a concrete example from their own operations
Bloom's Level: Remember / Understand / Apply (introduction) Theme: "Turning farm tasks into trackable work orders"
- Define what a GitHub Issue is and describe when to create one, using the farm analogy ("digital work order")
- Create a new Issue with a descriptive title, detailed description, and at least one photo attachment relevant to a farm task
- Apply labels to Issues to categorize farm tasks (equipment, livestock, crops, maintenance, urgent) and assign an Issue to themselves
- Comment on an existing Issue with a status update and close an Issue that is complete
- Distinguish between open and closed Issues and use the Issue list to find specific tasks by label or keyword
Bloom's Level: Apply Theme: "Planning your farm season visually"
- Create a new GitHub Project and select an appropriate view type (Board, Table, or Timeline) for a given farm planning scenario
- Add existing Issues to a Project and organize them into meaningful columns or groups (e.g., To Do, In Progress, Done)
- Use the Board view to track task status by dragging cards between columns during a simulated farm workflow
- Compare Board, Table, and Timeline views and select the most appropriate view for different farm planning needs (daily tasks vs. seasonal calendar)
- Build a basic spring planting project board with at least 4 Issues organized by status
Bloom's Level: Apply / Analyze Theme: "Working together on shared farm plans"
- Fork a shared farm repository using the GitHub web interface and explain the purpose of forking ("making your own copy to customize")
- Edit a file in a forked repository using the GitHub web editor (no CLI) and describe the change made
- Create a Pull Request from a forked repository to the original, including a descriptive title and summary of changes
- Review a peer's Pull Request by reading the changes, leaving a comment with feedback, and approving or requesting changes
- Analyze the difference between direct editing and the fork-edit-PR workflow, and explain when each approach is appropriate for farm collaboration
Bloom's Level: Apply / Analyze Theme: "Staying connected without information overload"
- Configure GitHub notification settings to watch specific repositories and customize email/web notification preferences
- Use @mentions in Issue comments to notify a specific team member about a task or question
- Participate in a GitHub Discussion by posting a question and replying to a peer's post
- Manage notification volume by adjusting watch settings and using notification filters to focus on relevant updates
- Evaluate which communication method (Issue comment, @mention, Discussion, or in-person) is most appropriate for different farm communication scenarios
Bloom's Level: Apply / Analyze Theme: "Building reusable processes so you never start from scratch"
- Create an Issue Template with pre-filled fields for a common farm process (e.g., equipment maintenance request with checklist)
- Use a saved reply to respond to a recurring question or status update efficiently
- Apply a project board template to set up a new seasonal planning board without manual configuration
- Differentiate between Issue Templates, Project Templates, and Repository Templates and describe when each is useful
- Design a set of 2–3 Issue Templates tailored to their own farm's most common recurring tasks
Bloom's Level: Analyze / Evaluate Theme: "Automatic farm helpers that work while you sleep"
- Describe what GitHub Actions are using the farm analogy ("automatic helpers that do tasks on a schedule or when something happens")
- Navigate to the Actions tab of a repository and identify the status of a workflow run (success, failure, in progress)
- Read a simple YAML workflow file and identify its key components: trigger event, job name, and steps (without writing YAML)
- Evaluate a pre-built workflow's output to determine whether it ran successfully and what it accomplished
- Identify 3 farm tasks that could benefit from automation and explain which trigger type (schedule, event, manual) would be appropriate for each
Bloom's Level: Evaluate / Apply Theme: "Setting up your first automated workflow"
- Enable a starter workflow template in a repository by selecting it from the Actions marketplace and committing it
- Customize a scheduled workflow by modifying the cron schedule (e.g., changing from daily to weekly) using the web editor
- Verify that an automated workflow runs correctly by checking the Actions tab for successful execution and reviewing the output
- Troubleshoot a failed workflow run by reading the error log and identifying the cause of failure
- Create a working automated reminder workflow that creates a weekly Issue for a recurring farm task (e.g., "Weekly Equipment Check")
Bloom's Level: Analyze / Evaluate Theme: "Seeing your whole season at a glance"
- Add custom fields (date, dropdown, number) to a GitHub Project to capture farm-specific data (crop type, field name, expected yield)
- Configure iterations in a Project to represent planting windows, growing periods, or harvest weeks
- Build a seasonal roadmap using the Timeline view that spans 6+ months with milestones for key farm activities
- Link Issues from multiple repositories into a single Project to create cross-functional farm visibility
- Evaluate a completed Project roadmap and identify scheduling conflicts, resource bottlenecks, or missing dependencies
Bloom's Level: Evaluate / Create Theme: "Your AI assistant for farm task writing"
- Describe what GitHub Copilot is and how it assists with drafting text, using the analogy of "a knowledgeable helper who suggests what to write next"
- Use Copilot to generate a draft Issue description for a farm task by providing a brief prompt (e.g., "spring planting prep checklist")
- Evaluate Copilot's output for accuracy, completeness, and relevance to their specific farm context
- Edit a Copilot-generated draft to customize it for their farm's specific needs, adding or removing items as appropriate
- Compare the time and quality of creating a task description manually vs. using Copilot assistance, and articulate when AI help is most valuable
Bloom's Level: Create / Evaluate Theme: "Building your own farm tools without code"
- Describe what GitHub Spark is and how it allows non-developers to create simple applications using natural language
- Create a simple farm-related app using Spark by describing the desired functionality in plain English (e.g., "a daily farm weather checklist")
- Customize a Spark-generated app by modifying the description and iterating on the output
- Explain the concept of GitHub Agents and identify one way an Agent could assist with farm repository management
- Evaluate the usefulness of their Spark app for actual farm operations and suggest improvements
Bloom's Level: Create Theme: "Putting it all together — your farm on GitHub"
- Create a complete farm management repository with: README describing the farm operation, 5+ Issues for real farm tasks, a Project board organizing those Issues, appropriate labels, and at least 1 Issue Template
- Configure at least one automated workflow (e.g., scheduled reminder) in their capstone repository
- Present their capstone project to the group, explaining how they would use GitHub for their farm and demonstrating 3+ features learned during the curriculum
- Teach one GitHub skill to a peer farmer in a 5–10 minute peer teaching exercise, using clear farm analogies and guided practice
- Reflect on their learning journey from Session 1 to Session 12, identifying their most valuable takeaway and one area for continued growth
| Session | Bloom's Level | Objectives | Cumulative |
|---|---|---|---|
| 1 | Remember / Understand | 5 | 5 |
| 2 | Remember / Understand / Apply | 5 | 10 |
| 3 | Apply | 5 | 15 |
| 4 | Apply / Analyze | 5 | 20 |
| 5 | Apply / Analyze | 5 | 25 |
| 6 | Apply / Analyze | 5 | 30 |
| 7 | Analyze / Evaluate | 5 | 35 |
| 8 | Evaluate / Apply | 5 | 40 |
| 9 | Analyze / Evaluate | 5 | 45 |
| 10 | Evaluate / Create | 5 | 50 |
| 11 | Create / Evaluate | 5 | 55 |
| 12 | Create | 5 | 60 |
Total: 60 learning objectives across 12 sessions (5 per session)
Sessions 1-2: Remember ████░░░░░░░░░░░░░░░░ Foundational
Sessions 3-6: Apply ░░░░████████░░░░░░░░ Application
Sessions 7-9: Analyze ░░░░░░░░░░░░██████░░ Analysis
Sessions 10-12: Create ░░░░░░░░░░░░░░░░████ Synthesis
Each session builds on skills from previous sessions. Session 12 requires cumulative application of all skills learned across the curriculum.
Session 1 (navigate repos) →
Session 2 (create Issues) →
Session 3 (organize with Projects) →
Session 4 (collaborate via PRs) →
Session 5 (communicate via notifications) →
Session 6 (build templates) →
Session 7 (understand Actions) →
Session 8 (create workflows) →
Session 9 (advanced Projects) →
Session 10 (use Copilot) →
Session 11 (build with Spark) →
Session 12 (capstone — all skills)
These objectives should be validated against learner profile data and adjusted after pilot testing (STORY-013/014).