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

marketing: a distribution checklist (awesome lists, engine communities, dataset hubs) and a launch post

Abierto
  • ¿Algo no está bien?
#118 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
25/100
Tipo de issue
Nueva funcionalidad
Claridad
Bastante claro
Estado de actividad
Activo
Stack tecnológico
github, javascript
Área
content

Línea de trabajo

Start by reading the README positioning paragraph and the existing website, launch assets, and FUNDING.yml; the issue names no code entry point or tests. Create docs/distribution.md and track dated links for completed listings, dataset publications, and launch posts. Done means the checklist records each completed item and stars or referral traffic show a step change.

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

Descripción

marketing priority: medium

Why it matters
57 stars and 9 forks, with a clear differentiator (dated, quoted licence readings) against the much larger lists the README names. Nothing records where the project has been announced or listed. Getting into the lists people already use, and into the places where "is this free for commercial use?" is asked weekly, is the cheapest growth available, and FUNDING.yml is in place to convert some of it.

Evidence

  • README positioning paragraph names magictools and awesome-gamedev.
  • Topics (12), website badge and OG card exist; the launch assets are ready.

Suggested approach
Create docs/distribution.md as a living checklist and work it:

  • PRs adding the catalog to magictools, awesome-gamedev, awesome-godot, awesome-unity, awesome-unreal, awesome-cc0, and engine docs "community resources" pages.
  • Publish data.json/catalog.csv as a CC0 dataset on Hugging Face and Kaggle with the schema.
  • One post each: r/gamedev and r/godot, the Godot forum, itch.io community, Hacker News "Show HN", Mastodon/Bluesky gamedev.
  • A short page on the site ("Why every entry quotes the licence") for the posts to land on.
  • Ask listed publishers to link back (badge issue).

Done when
The checklist has dates and links for each completed item, and stars or referral traffic show a step change.

Lenguaje dominante
JavaScript
Estrellas
58
Forks
15
Merge medio
18 h 42 min
PR fusionados (30 d)
11

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.