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

The help pages never say "pause", so organizers looking for it miss Close or reopen a signup

Abierto Apto para principiantes
  • ¿Algo no está bien?
#653 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
82/100
Tipo de issue
Documentación
Claridad
Bien especificado
Estado de actividad
Activo
Stack tecnológico
typescript
Área
documentation

Línea de trabajo

Empieza por la entrada «Cerrar o reabrir una inscripción» en src/help/articles.ts; después, lee docs/writing-help.md y las comprobaciones relacionadas en src/help/articles.test.tsx. Actualiza el resumen, la descripción y el primer párrafo para mencionar la pausa, manteniendo intacta la redacción del título y del botón; añade una línea al changelog bajo Unreleased › Changed. El trabajo estará terminado cuando el resumen de ayuda y la meta descripción incluyan «Pause», el artículo mencione la pausa de las inscripciones y pasen las pruebas del artículo.

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

Descripción

enhancement pipeline:proposed pipeline:ux

Needs your OK: this changes the summary and search description of the help page "Close or reopen a signup". Swap pipeline:proposed for pipeline:ready to have it built.

What happens

  • The help pages have no search. An organizer finds a page by its title and its one-line summary on /help.
  • "Close or reopen a signup" is the page for stopping sign-ups for a while. Its summary in src/help/articles.ts is "Stop anyone new signing up, and let people sign up again at the same link when you're ready."
  • "Pause" isn't anywhere on it: not in its title, summary, description or text, and not anywhere else in src/help.
  • A tester looking for it missed it. In the UX walkthrough on #610, a tester wanting to pause sign-ups searched the page for "pause" and "stop sign" and found nothing. They found the page only by reading every title.

Fix, in outline

  • Summary: for example, "Pause or stop sign-ups, and let people sign up again at the same link when you're ready."
  • Description, which search results and link previews show: for example, "Pause or close your signup so nobody new can sign up, and everyone already signed up keeps their spot. Reopen it later, at the same link." (137 characters.)
  • First paragraph of the article: add pausing to when you'd close it. For example: "…when you have enough people, when it's too late to sign up, or to pause sign-ups for a while."

Watch for

  • docs/writing-help.md: a "sign-up" is what someone does, and a "signup" is the page. src/help/articles.test.tsx checks the description's length (110 to 160 characters) and the style rules.
  • The title stays, so the slug and every link to the page stay the same.
  • The button is still Close signup. The page mustn't suggest there's a Pause button.
  • CHANGELOG: add a line under Unreleased › Changed.

Choices this makes

  • "Pause" goes in the summary, description and first paragraph, not the title. The title names the task by its button, as the other help pages do.
  • The wording above, which the owner can edit here first.

Done when

  • /help shows the new summary, and the page's meta description includes "Pause".
  • The first paragraph mentions pausing sign-ups.
  • articles.test.tsx passes.
  • pnpm lint && pnpm typecheck && pnpm knip && pnpm test pass.

From the UX walkthrough comment on #610 (https://github.com/richshaw/OpenSignup/pull/610#issuecomment-6402399737). Checked against src/help on main at 1d4ff3a. https://claude.ai/code/session_01LrYa57fvbqWjZj89iH975K

Lenguaje dominante
TypeScript
Estrellas
19
Forks
4
Merge medio
20 h 9 min
PR fusionados (30 d)
156

Preparar el entorno

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 richshaw/OpenSignup

Todos los issues de richshaw/OpenSignup

Issues similares

Más issues de TypeScript

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.