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

ux: on mobile the licence verdict is below the fold on entry pages, and "Related" prints raw entry ids instead of names

Abierto
  • ¿Algo no está bien?
#155 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
4/5
Tiempo estimado
3-5 días
Aptitud para principiantes
48/100
Tipo de issue
Nueva funcionalidad
Claridad
Bien especificado
Estado de actividad
Activo
Stack tecnológico
javascript
Área
frontend

Línea de trabajo

Start with site/lib/entry-page.mjs to trace the entry markup and body link resolver, then inspect the mobile styles that control .facts-panel, the image strip, and entry flags. Use /entry/kenney/ at 375x667 and the related links in catalog/3d/kenney.md as examples. Done when every entry shows the licence, commercial stance, and credit requirement without scrolling, and Related displays entry names with licence and commercial details.

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

Descripción

enhancement priority: medium

Why it matters

A developer opens an entry to answer "can I ship this, and what do I owe?". On a phone that answer is on the second screen, behind the image strip and the lead paragraph, and the "Go to source" button is further down still. Related is the main way to move from a hub (Kenney, 31 links) to its packs, and it currently reads like a file listing.

Evidence (at 69387df, local build at 375x667)

  • /entry/kenney/: .facts-panel top = 709 px, "Go to source" button top = 980 px, viewport height 667. Markup order in site/lib/entry-page.mjs is strip -> lead -> facts -> actions; the strip alone is 360 px plus caption.
  • 414 of 415 entry pages with id="related" render <a href="../<id>/"><id></a>, for example kenney-city-kit-roads, kenney-modular-dungeon-kit. Source: catalog/3d/kenney.md "## Related" is - [kenney-city-kit-roads](kenney-city-kit-roads.md) and the renderer keeps the link text verbatim. The build knows every entry's name and licence.

Suggested approach

At max-width: 640px, put a one-line verdict row directly under the h1 (licence, commercial stance, credit, verified age, reusing entry-flags), move "Go to source" beside it, and cap the strip at about 160 px tall; keep the full "At a glance" panel for desktop. In the entry-body link resolver, when a link resolves to a catalog entry and its text equals the entry id, substitute entry.name and append a small flag span (licence, commercial OK / per-file). Contributors can keep writing ids in the markdown.

Done when

At 375x667 the licence, commercial stance and credit requirement are visible without scrolling on every entry page; Related shows "Kenney City Kit (Roads) - CC0 - commercial OK".

Lenguaje dominante
JavaScript
Estrellas
58
Forks
15
Merge medio
16 h 53 min
PR fusionados (30 d)
14

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.