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 — low activity density in a long glossary/reference page

Closed Beginner friendly
  • Is something wrong?
#3,673 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
84/100
Issue type
Documentation
Clarity
Clearly specified
Activity status
Active
Tech stack
markdown
Domain
documentation

Research direction

Edit workshop/side-quest-01-02-environment-reference.md, starting with the “Environment and tool glossary” table and the existing “Verify your tools are ready” section. Add the requested self-check activities after each thematic cluster, move the gh --version / git --version check earlier, and leave the checkpoint unchanged. Run npx --yes markdownlint-cli2 "**/*.md"; done means the page has more interleaved activity and passes the Markdown lint check.

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.9 / 10.0 (corpus mean: 6.1)

Flagged Dimensions:

Dimension Score Benchmark Delta
active_learning 2.1 ≥ activity density 3 (score 10) -7.9
cognitive_load 6.3 ≤ 800 words / ≤ 15 concepts (score 10) -3.7

Note: the rubric also flags missing_checkpoint/checkpoint_quality: 0.0, but this is a confirmed tooling bug — the file contains a well-formed ## :white_check_mark: Checkpoint section with 7 specific checklist items. The rubric's CHECKPOINT_RE only matches a literal ✅ character, not the :white_check_mark: shortcode used throughout this workshop. That flag should be dismissed for scoring purposes (see the scorecard issue for the tooling fix).

Root Cause (≤ 2 sentences):
At 1,433 words with 17 new concepts and only 2 code blocks / 9 checklist items, this reference page has very low activity density (0.63 vs. the ≥3 ideal) because it is a long prose-and-table glossary with almost no hands-on interaction until the very end. The nine-item tool/environment table and eight paired screenshot sections are read-only content stretched across most of the page.

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.

| Term | What it means in this workshop | When you use it | Official documentation |

Learning Science Rationale:
Mayer's multimedia principle on generative activity (and the broader active-learning literature) shows that passive reading of reference tables and paired screenshots — without an interleaved retrieval or verification step — produces shallow, non-durable encoding. A 1,400-word glossary read start-to-finish, with the only "do this" action (gh --version / git --version) buried near the end, gives learners little opportunity to actively process the terms as they're introduced, increasing the risk that the glossary is skimmed rather than internalized.

Improvement Prompt (for an agent):

Edit workshop/side-quest-01-02-environment-reference.md to raise activity density. After each thematic cluster in the "Environment and tool glossary" table (development environments; workshop tools and model options), insert a short self-check activity such as a 2-3 item micro-quiz or "match the tool to its use" prompt (e.g., "Which tool would you use to compile a workflow file? Which tool would you use to view a compiled .lock.yml?") with an answer in a collapsible <details> block. Also move the "Verify your tools are ready" gh --version / git --version check earlier, right after the glossary table, instead of leaving it as the only interactive element near the end. Keep the existing checkpoint section unchanged. Run npx --yes markdownlint-cli2 "**/*.md" after editing.

Expected Score After Fix: 6.0 / 10.0

Generated by 🔬 Curriculum Quality Evaluator · copilot · auto · 74.5 AIC · ⌖ 11.9 AIC · ⊞ 9K · ◷

  • expires on Sep 23, 2026, 3:48 AM UTC
Dominant language
JavaScript
Stars
52
Forks
26
Avg merge
12h 54m
Merged PRs (30d)
17

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.