Hacktoberfest 2026: le issue che i maintainer hanno segnato per ottobre, aperte e adatte ai principianti. Sfoglia le issue Hacktoberfest

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

Chiusa
  • Qualcosa non va?
#155 0 commenti 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
4/5
Tempo stimato
3-5 giorni
Idoneità per principianti
48/100
Tipo di issue
Funzionalità
Chiarezza
Specificata chiaramente
Stato di attività
Attiva
Stack tecnologico
javascript
Ambito
frontend

Direzione di ricerca

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.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

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".

Lingua principale
JavaScript
Stelle
58
Fork
15
Merge medio
16h 53m
PR unite (30g)
14

Preparare l'ambiente

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di TMHSDigital/Free-Game-Dev-Assets

Tutte le issue di TMHSDigital/Free-Game-Dev-Assets

Issue simili

Altre issue su JavaScript

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.