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

marketing: per-entry embeddable badge ("Licence read YYYY-MM-DD") and per-entry social cards

Abierto
  • ¿Algo no está bien?
#117 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
5/5
Tiempo estimado
Más de una semana
Aptitud para principiantes
35/100
Tipo de issue
Nueva funcionalidad
Claridad
Bastante claro
Estado de actividad
Activo
Stack tecnológico
javascript
Área
web-dev

Línea de trabajo

Start by reading site/lib/entry-page.mjs around lines 92–98 and site/build.mjs around lines 270–277, then inspect how entry IDs, licence families, and verified dates are represented. The issue proposes per-entry SVG badges, copyable Markdown and HTML snippets, unique PNG cards using the existing writer, and an outreach note in docs/. Done means every entry page has its own OG image and badge snippet; publisher adoption is also listed as a completion condition.

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

Descripción

enhancement marketing priority: medium

Why it matters
Listed publishers (Kenney, Quaternius, KayKit, small itch creators) have a reason to link back if they get something: a badge saying their licence was independently read and dated. Each backlink is discoverability for the catalog and a trust signal for them. Separately, all 414 entry pages share one og-card.png, so a shared link to a specific entry looks identical to the home page on Discord, X and Slack.

Evidence

  • site/lib/entry-page.mjs:92-98 uses the site-wide card for every entry.
  • site/build.mjs:270-277 renders the single og-card.png with a dependency-free PNG writer.

Suggested approach

  1. Badge: a static SVG per entry at dist/badge/<id>.svg ("Free Game Dev Assets · CC0 · read 2026-10-13", coloured by licence family) plus a "Link to this entry" box with copyable Markdown and HTML.
  2. Cards: generate dist/entry/<id>/card.png at build (name, licence, commercial badge, verified date) with the existing writer and point og:image at it.
  3. A short "You're listed" note template in docs/ for outreach.

Done when
Each entry page has a unique OG image and a copyable badge snippet, and a few publishers display it.

Lenguaje dominante
JavaScript
Estrellas
58
Forks
15
Merge medio
1 d 7 h
PR fusionados (30 d)
12

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 TMHSDigital/Free-Game-Dev-Assets

Todos los issues de TMHSDigital/Free-Game-Dev-Assets

Issues similares

Más issues de JavaScript

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.