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

Add the Call for Speakers event template (`event-call-for-speakers`)

Abierto
#177 2 comentarios 0 reacciones 1 asignado Ver en GitHub

Los mantenedores suelen responder en 1 día

@Saifjafri212213 ya está trabajando en esto.

Desde el 22/10/2026.

Evaluación

Este issue todavía no se ha evaluado.

Descripción

good first issue hacktoberfest templates

Part of #5. For conferences and meetups that are looking for talks.

Idea
A small "Call for speakers" label sits at the top, with the event name large under it. Below that is a row of up to 4 topic chips ("AI", "Web", "DevOps"). At the bottom left, "Deadline" with the date, and at the bottom right, an accent "Submit a talk" button.

Template details

  • File: src/templates/event/call-for-speakers.ts, id event-call-for-speakers
  • Fields: commonFields.title (the event name), topics (text, comma separated), deadline (text, for example "Nov 30, 2026"), ctaText (text, default "Submit a talk"), commonFields.siteName, commonFields.bgColor, commonFields.accentColor, commonFields.textColor

Where to look

  • Closest reference: src/templates/event/conference.ts, src/templates/event/ticket-cta.ts (the button), and src/templates/github/issue-card.ts (chips from a comma separated field, line 60)

Acceptance criteria

  • Empty topics are dropped, at most 4 chips show, and each chip is truncated
  • The deadline line hides when deadline is empty, and the button falls back to "Submit a talk" when ctaText is empty
  • Re-exported in src/templates/event/index.ts and registered in the Event block of src/templates/registry.ts
  • Meets the shared template checklist in #5

One template per contributor at a time, so more people get a chance.


Want to work on this? Comment below and I'll assign it to you. Please take one issue at a time, branch off dev, and open your PR against dev with Closes #177 in the description.

Lenguaje dominante
TypeScript
Estrellas
8
Forks
4
Merge medio
5 h 44 min
PR fusionados (30 d)
83

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 codercops/ogcops

Todos los issues de codercops/ogcops

Issues similares

Más issues de TypeScript

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.