[curriculum-eval] side-quest-01-02-environment-reference.md: cognitive_load & active_learning — 1433-word glossary with 9 backloaded, low-interact
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 88/100
- Issue type
- Documentation
- Clarity
- Clearly specified
- Activity status
- Active
- Tech stack
- markdown
- Domain
- documentation
Research direction
Open workshop/side-quest-01-02-environment-reference.md and inspect the Conceptual screenshots section, glossary table, and existing Checkpoint section. Review the two tool groups and glossary wording first, then verify that the completed page has collapsible groups, an intermediate self-check, reduced length, and unchanged image alt text and checkpoint content.
Written by the indexing model from the issue text.
Description
File: workshop/side-quest-01-02-environment-reference.md
Overall Score: 4.93 / 10.0 (corpus mean: 6.09) — lowest-scoring file in the corpus
Corrected Overall Score (after fixing the checkpoint/scaffolding regex bug reported separately): 7.68 / 10.0 — still below corpus mean even after correction, driven by genuine content issues below.
Flagged Dimensions:
| Dimension | Score | Benchmark | Delta |
|---|---|---|---|
| cognitive_load | 6.3 |
≤800 words | -1.7 (1433 words, ~1.8× the 800-word target) |
| active_learning | 2.1 |
density ≥ 3 | -0.9 (density 0.63; only 2 code blocks + 7 checklist items across 1433 words) |
Root Cause (≤ 2 sentences):
This page is structured as a long, mostly-passive glossary + 9 stacked conceptual screenshots (one per tool), which pushes word count to 1433 (79% over the 800-word cognitive-load ceiling) while offering almost no interactive checkpoints until the very end. Learners read through ~9 sequential image/description pairs with no intermediate "try this" or self-check prompts, so engagement is backloaded entirely into the final checkpoint.
Evidence (quoted from the file):
"You use Codespaces when you want a ready-to-go development environment in your browser."
"You use VS Code to browse files, edit workflows, and keep a terminal open beside your work."
"You use the terminal whenever the workshop asks you to rungh,gh aw, orgitcommands."
These three one-line captions (one of nine similar patterns) repeat the same "You use X when Y" template across 9 tools with no intervening activity, quiz, or interaction — pure exposition.
Learning Science Rationale:
Mayer's Multimedia Principle holds that pairing images with words aids learning, but the Coherence Principle (an extension of Mayer's framework) warns that extraneous or repetitive material — here, 9 near-identical image+caption pairs in a row — increases extraneous cognitive load without adding germane processing. Sweller's Cognitive Load Theory similarly predicts that long, low-interactivity stretches consume working memory on content organization rather than on schema construction, especially harmful on a reference page meant for quick lookup rather than deep study.
Improvement Prompt (for an agent):
Edit workshop/side-quest-01-02-environment-reference.md to reduce passive reading load and raise interactivity:
1. Split the "Conceptual screenshots" section (9 stacked tool cards) into two collapsible <details> groups — "Development environments" and "Workshop tools and model options" — so learners can expand only the tools they need instead of scrolling through all 9 sequentially. The existing subheadings already group them this way; wrap each group's cards in a single <details><summary>Development environments</summary> ... </details> block.
2. After the "Environment and tool glossary" table, add one short self-check activity, e.g. a 3-item matching exercise ("Match each term to its role") using a <details><summary>Check your answers</summary> reveal block, to raise activity_density before the final checkpoint.
3. Trim the glossary table's "What it means in this workshop" column to one clause per row where it currently spans two clauses, to bring total word count closer to 800-1000.
Preserve the existing Checkpoint section and all image alt text unchanged.
Expected Score After Fix: ≈8.7 / 10.0 (assuming the checkpoint/scaffolding regex fix from the companion tooling issue is also applied; word count and activity density improvements alone would raise cognitive_load and active_learning by roughly 2-3 points each).
Generated by 🔬 Curriculum Quality Evaluator · copilot · auto · 147.3 AIC · ⌖ 18.6 AIC · ⊞ 9K · ◷
- expires on Sep 28, 2026, 9:51 AM UTC
- Dominant language
- JavaScript
- Stars
- 49
- Forks
- 20
- Avg merge
- 7h 12m
- Merged PRs (30d)
- 26
Getting set up
We have not checked this project's setup files yet. Start from its README, and see our first-contribution guide for the general steps.
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from githubnext/gh-aw-workshop
-
agentic-workflows
Difficulty 1/5 Under an hour Newbie friendliness 85/100
githubnext/gh-aw-workshop#3933 ·
Maintainers usually reply within 1 day
-
documentation
Difficulty 1/5 Under an hour Newbie friendliness 92/100
githubnext/gh-aw-workshop#3932 ·
Maintainers usually reply within 1 day
-
feedback simulation workshop
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
githubnext/gh-aw-workshop#3931 ·
Maintainers usually reply within 1 day
-
agentic-workflows documentation workflow-editor
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
githubnext/gh-aw-workshop#3927 ·
Maintainers usually reply within 1 day
-
documentation
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
githubnext/gh-aw-workshop#3926 ·
Maintainers usually reply within 1 day
All issues in githubnext/gh-aw-workshop
Similar issues
-
Design only Leadership Survey SLFS
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
bcgov/digital-journeys#2293 ·
-
Toolkit
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
Maintainers usually reply within 1 day
-
API Bug
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
ProjectSidewalk/SidewalkWebpage#5556 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
jessepollak/home#1454 ·
Maintainers usually reply within 1 day
-
Mend: dependency security vulnerability untriaged
Difficulty 2/5 1-3 hours Newbie friendliness 64/100
opensearch-project/OpenSearch-Dashboards#12822 ·
Maintainers usually reply within 1 day