[curriculum-eval] 04-github-actions-intro.md: cognitive_load — labeling exercise deferred to end instead of interleaved after each concept chunk
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 65/100
- Issue type
- Documentation
- Clarity
- Mostly clear
- Activity status
- Active
- Tech stack
- github-actions, markdown
- Domain
- content, documentation
Research direction
Start in workshop/04-github-actions-intro.md: the "Quick Refresher" section with the hello-workflow.yml example, the "Why This Matters for Agentic Workflows" table, and the "Label a sample workflow" exercise near the end. Move that exercise to directly after the refresher, add one retrieval question after the comparison table, and check that the Checkpoint section still matches. Done when the page reads in that order and npx --yes markdownlint-cli2 "workshop/04-github-actions-intro.md" passes.
Written by the indexing model from the issue text.
Description
File: workshop/04-github-actions-intro.md
Overall Score: 5.39 / 10.0 (corpus mean: 6.09)
Flagged Dimensions:
| Dimension | Score | Benchmark | Delta |
|---|---|---|---|
| cognitive_load | 6.8 |
≤15 new concepts → 10 | −3.2 |
| active_learning | 3.9 |
density ≥ 3.0 → 10 | −0 (borderline; flagged alongside concept overload) |
Root Cause (≤ 2 sentences):
The page defines 28 new concepts in 756 words (≈3.7 concepts per 100 words), introducing the entire Actions vocabulary (trigger, job, runner, step, action, on, runs-on, self-hosted runner, YAML structure) plus a parallel agentic-workflow comparison table in one pass, which is unusually dense for a page explicitly framed as a "5 Minutes" refresher for likely-familiar material. The skip-ahead <details> at the top signals this is meant to be fast for experienced learners, but the full page still front-loads nearly twice the ideal concept count for anyone who doesn't skip.
Evidence (quoted from the file):
when to run (
on) ... what to run (jobs) ... how each job executes (steps)| Concept | Classic Actions | Agentic Workflow | ... (five-row comparison table introduced immediately after the five Actions primitives, before any practice)
Learning Science Rationale:
Bloom's Taxonomy places this page at "Understand" (confirmed by the tool's own bloom_reclassification), which is appropriate for a refresher, but Cognitive Load Theory still applies: presenting five new primitives (trigger/job/runner/step/action) immediately followed by a second five-row comparison table before any hands-on labeling task creates two dense conceptual layers with only one practice checkpoint ("Label a sample workflow") positioned after both, rather than one practice moment per layer — germane load is better managed when practice is interleaved per chunk rather than deferred to the end of accumulated new material.
Improvement Prompt (for an agent):
Open workshop/04-github-actions-intro.md and interleave practice earlier:
1. Move the existing "Label a sample workflow" labeling exercise (currently near the end, after the "Why This Matters for Agentic Workflows" comparison table) to appear directly after the "Quick Refresher" section and its annotated hello-workflow.yml example — i.e., right after the five Actions primitives are introduced, before the agentic-workflow comparison table.
2. Keep the "Why This Matters for Agentic Workflows" comparison table but add one short retrieval question immediately after it (e.g., "Which row changes between classic and agentic — the trigger, the runner, or the output path?") in a <details> reveal, so the comparison table gets its own practice moment instead of deferring to the final "Try it" activity.
3. Consider trimming the "What is a runner?" collapsible aside to a single sentence plus the existing code snippet, since self-hosted runners are a side detail relative to the core five primitives this page is teaching.
4. Verify the "## :white_check_mark: Checkpoint" section still matches the reordered content.
5. Run `npx --yes markdownlint-cli2 "workshop/04-github-actions-intro.md"` and fix any lint errors.
Expected Score After Fix: 6.2–6.6 / 10.0
Generated by 🔬 Curriculum Quality Evaluator · copilot · auto · 117 AIC · ⌖ 19.4 AIC · ⊞ 10.4K · ◷
- expires on Oct 11, 2026, 2:04 AM UTC
- Dominant language
- JavaScript
- Stars
- 52
- Forks
- 26
- Avg merge
- 12h 58m
- Merged PRs (30d)
- 15
Getting set up
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
- 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
-
documentation
Difficulty 1/5 Under an hour Newbie friendliness 88/100
githubnext/gh-aw-workshop#4496 ·
Maintainers usually reply within 1 day
-
feedback simulation workshop
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
githubnext/gh-aw-workshop#4495 ·
Maintainers usually reply within 1 day
-
feedback simulation workshop
Difficulty 2/5 1-3 hours Newbie friendliness 77/100
githubnext/gh-aw-workshop#4494 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
githubnext/gh-aw-workshop#4491 ·
Maintainers usually reply within 1 day
-
[workshop-sync] workshop/06-install-gh-aw.md: inaccurate gh aw init output and stale version exampleOpendocumentation
Difficulty 1/5 1-3 hours Newbie friendliness 86/100
githubnext/gh-aw-workshop#4490 ·
Maintainers usually reply within 1 day
All issues in githubnext/gh-aw-workshop
Similar issues
-
Difficulty 1/5 Under an hour Newbie friendliness 76/100
521xueweihan/HelloGitHub#3939 ·
-
Difficulty 1/5 Under an hour Newbie friendliness 84/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 79/100
aemsites/author-kit#19 ·
-
needs-website-changes
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
Maintainers usually reply within 1 day