Skip to content

[workshop-sim] Repair: Add skip-ahead path for experienced users (step 4) and annotate build step (step 11) #232

Description

@github-actions

Problem

Step 4 (Actions Intro) has an 18.2% dropout rate — the third-highest in the workshop. Disproportionately affects skeptical and advanced students (Lane Harris, Max Clark, Ocean Lewis all dropped here) who already know GitHub Actions and need to quickly understand what is new and different before investing time in conceptual content. The step currently leads with Actions history before explaining the agentic differentiation.

Additionally, step 11 (Build daily-status, 20% dropout) loses methodical learners who want to understand code before copying it — Sam Patel's journey illustrates that presenting a full workflow file without annotations is a content gap.

Proposed Change

Step 4 (04-github-actions-intro.md):

  • Add a collapsible "Already know GitHub Actions? Skip to what's different →" section at the top that links directly to step 5.

  • Add a comparison table early in the body:

    Classic Actions Agentic Workflows
    You write YAML steps You write a plain-English brief
    Deterministic execution AI agent reasons and adapts
    Fixed tool calls Agent selects and chains tools

Step 11 (11-build-daily-status.md):

  • Add inline <!-- annotations --> or > [!NOTE] blocks after each major YAML section explaining the intent (e.g., "This on: schedule block triggers the agent every morning at 07:00 UTC").

Acceptance Criteria

  • Step 4 opens with a skip link for readers who already know Actions
  • Step 4 includes a Classic vs Agentic comparison table within the first 40 lines
  • Step 11 includes at least 3 inline explanatory callouts within the workflow source block
  • npx markdownlint-cli2 "workshop/04-github-actions-intro.md" "workshop/11-build-daily-status.md" passes

Suggested Owner

copilot coding agent (content addition + table formatting)

Generated by 🔬 Workshop Student Simulator · 39 AIC · ⌖ 5.8 AIC · ⊞ 8K ·

Metadata

Metadata

Type

No type

Fields

No fields configured for issues without a type.

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions