[curriculum-eval] 04-github-actions-intro.md: cognitive_load — labeling exercise deferred to end instead of interleaved after each concept chunk
维护者通常 1 天内回复
还没有人认领这个 Issue。
评估
- 难度
- 2/5
- 预计耗时
- 1-3 小时
- 新手友好度
- 65/100
- Issue 类型
- 文档
- 描述清晰度
- 基本清楚
- 活跃度
- 活跃
- 技术栈
- github-actions, markdown
- 领域
- content, documentation
调研方向
从 workshop/04-github-actions-intro.md 开始：包含 hello-workflow.yml 示例的「Quick Refresher」小节、「Why This Matters for Agentic Workflows」表格，以及末尾附近的「Label a sample workflow」练习。将该练习移至 refresher 小节之后，在比较表格后添加一个检索问题，并检查 Checkpoint 小节是否仍然匹配。当页面按该顺序阅读且 npx --yes markdownlint-cli2 "workshop/04-github-actions-intro.md" 通过时完成。
由索引模型根据 Issue 内容生成。
描述
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
- 主要语言
- JavaScript
- 星标
- 56
- 派生
- 40
- 平均合并
- 2 天 14 小时
- 30 天内合并 PR
- 13
环境准备
在浏览器里用你自己的 GitHub 账号启动这个项目的开发容器。
- 没有 Dockerfile 或 Docker Compose 文件
- 没有 Pull Request 模板
- 没有贡献指南
从这里开始
- 先读完整个 Issue，再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库，在一个分支上完成修改。
- 提交 Pull Request，并在描述里引用这个 Issue 编号。
githubnext/gh-aw-workshop 的其他 Issue
-
feedback simulation workshop
难度 2/5 1-3 小时 新手友好度 60/100
githubnext/gh-aw-workshop#5264 ·
维护者通常 1 天内回复
-
curriculum documentation quality
难度 2/5 1-3 小时 新手友好度 72/100
githubnext/gh-aw-workshop#5258 ·
维护者通常 1 天内回复
-
curriculum documentation quality
难度 2/5 1-3 小时 新手友好度 62/100
githubnext/gh-aw-workshop#5257 ·
维护者通常 1 天内回复
-
curriculum documentation quality
难度 2/5 1-3 小时 新手友好度 62/100
githubnext/gh-aw-workshop#5254 ·
维护者通常 1 天内回复
-
curriculum documentation quality
难度 2/5 1-3 小时 新手友好度 72/100
githubnext/gh-aw-workshop#5255 ·
维护者通常 1 天内回复
查看 githubnext/gh-aw-workshop 的全部 Issue
相似的 Issue
-
难度 1/5 1 小时以内 新手友好度 65/100
维护者通常 1 天内回复
-
Add toro4n to the data modeling tools可能已有人在做 @henriklantzhedstrom-prog 今天认领。 未关闭
难度 1/5 1 小时以内 新手友好度 62/100
neo4j/docs-getting-started#546 ·
-
难度 2/5 1-3 小时 新手友好度 65/100
维护者通常 25 天内回复
-
难度 2/5 1-3 小时 新手友好度 70/100
libnativeapi/nativeapi#21 ·
-
area: core complexity: easy impact: medium
难度 2/5 1-3 小时 新手友好度 86/100
ueberdosis/tiptap#8668 ·
维护者通常 1 天内回复