Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

[curriculum-eval] side-quest-01-02-environment-reference.md: active_learning — long glossary page lacks interleaved practice

Closed Beginner friendly
#4,308 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
78/100
Issue type
Documentation
Clarity
Clearly specified
Activity status
Active
Tech stack
github-actions, markdown
Domain
documentation

Research direction

Start with workshop/side-quest-01-02-environment-reference.md and review its glossary, conceptual screenshots, and existing verification exercise. Add 2–3 short checks interleaved with the glossary and trim or collapse optional material, while preserving the existing “Before You Start” and “Checkpoint” sections. Done when the page has more distributed practice and a shorter main reading while retaining the full glossary.

Written by the indexing model from the issue text.

Description

curriculum documentation quality

File: workshop/side-quest-01-02-environment-reference.md
Overall Score: 4.93 / 10.0 (corpus mean: 6.09)

Flagged Dimensions:

Dimension Score Benchmark Delta
active_learning 2.1 density ≥ 3 → 10 -7.9
cognitive_load 6.3 ≤800 words, ≤15 concepts → 10 -3.7

Root Cause (≤ 2 sentences):
At 1,433 words (79% over the 800-word ideal) with only 2 code blocks and a single verification exercise, this reference page is dominated by passive reading (a large glossary table and "conceptual screenshots" section) with very little hands-on practice, giving an activity density of just 0.63 per 100 words against the 3.0 target.

Evidence (quoted from the file):

"Knowing which name maps to which role helps you follow workshop instructions without stopping to wonder what "the terminal" or "Codespaces" means in context." — followed by a 9-row glossary table and a "Conceptual screenshots" section with no interactive checks between them.

Learning Science Rationale:
Mayer's Multimedia Principle holds that learners build stronger mental models when verbal and visual information is paired with active processing (e.g., self-testing) rather than passive reception; a 1,400-word glossary-plus-screenshots page with only one small "verify your tools" exercise risks the "illusion of knowing" effect, where learners feel informed after reading but cannot yet apply the material, because there is no retrieval practice distributed across the long content.

Improvement Prompt (for an agent):

Edit workshop/side-quest-01-02-environment-reference.md to raise its active-learning density.
Break the long environment/tool glossary table into 2-3 shorter sections, each followed by a
small "Quick check" interactive task (e.g., a short command to run, or a 1-question
multiple-choice-style prompt phrased as a checklist item) so code_blocks + checklist_items
rises relative to word_count. Also trim the "Conceptual screenshots" section or move the least
essential rows (e.g., the Claude/OpenAI Codex rows, which are optional-model asides) into a
collapsible <details> block to reduce word_count toward 800-1000 while preserving the full
glossary content for reference. Keep the existing ":clipboard: Before You Start" and
":white_check_mark: Checkpoint" sections intact; just add 2-3 new small verification steps
interleaved with the glossary content rather than only at the end.

Expected Score After Fix: 6.5-7.0 / 10.0

Generated by 🔬 Curriculum Quality Evaluator · copilot · auto · 96.9 AIC · ⌖ 19.9 AIC · ⊞ 10.4K · ◷

  • expires on Oct 8, 2026, 11:43 PM UTC
Dominant language
JavaScript
Stars
52
Forks
26
Avg merge
11h 32m
Merged PRs (30d)
22

Getting set up

Open in Codespaces

Starts the project's dev container in your browser, under your own GitHub account.

  • No Dockerfile or Docker Compose file
  • No pull request template
  • No contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from githubnext/gh-aw-workshop

All issues in githubnext/gh-aw-workshop

Similar issues

More JavaScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.