Hacktoberfest 2026: los issues que los mantenedores marcaron para octubre, abiertos y aptos para principiantes. Explorar issues de Hacktoberfest

[curriculum-eval] side-quest-01-02-environment-reference.md: active_learning — low activity density in a long glossary/reference page

Cerrado Apto para principiantes
  • ¿Algo no está bien?
#3,673 0 comentarios 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 1 día

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
2/5
Tiempo estimado
1-3 horas
Aptitud para principiantes
84/100
Tipo de issue
Documentación
Claridad
Bien especificado
Estado de actividad
Activo
Stack tecnológico
markdown
Área
documentation

Línea de trabajo

Edita workshop/side-quest-01-02-environment-reference.md, empezando por la tabla “Environment and tool glossary” y la sección existente “Verify your tools are ready”. Añade las actividades de autocomprobación solicitadas después de cada grupo temático, mueve antes la comprobación gh --version / git --version y deja el checkpoint sin cambios. Ejecuta npx --yes markdownlint-cli2 "**/*.md"; si termina correctamente, la página tiene más actividades intercaladas y supera la comprobación de lint de Markdown.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

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
Lenguaje dominante
JavaScript
Estrellas
53
Forks
35
Merge medio
13 h 50 min
PR fusionados (30 d)
14

Preparar el entorno

Abrir en Codespaces

Inicia el contenedor de desarrollo del proyecto en tu navegador, con tu propia cuenta de GitHub.

  • Sin Dockerfile ni archivo de Docker Compose
  • Sin plantilla de pull request
  • Sin guía de contribución

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de githubnext/gh-aw-workshop

Todos los issues de githubnext/gh-aw-workshop

Issues similares

Más issues de JavaScript

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.