Hacktoberfest 2026: die Issues, die Maintainer für den Oktober markiert haben – offen und einsteigerfreundlich. Hacktoberfest-Issues durchsuchen

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

Offen
  • Stimmt etwas nicht?
#155 0 Kommentare 0 Reaktionen 0 zugewiesene Personen Auf GitHub ansehen

Maintainer antworten meist innerhalb von 1 Tag

Dieses Issue hat noch niemand übernommen.

Bewertung

Schwierigkeit
4/5
Geschätzter Aufwand
3-5 Tage
Anfängerfreundlichkeit
48/100
Issue-Typ
Feature
Klarheit
Klar beschrieben
Aktivitätsstatus
Aktiv
Tech-Stack
javascript
Bereich
frontend

Rechercherichtung

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.

Vom Indexierungsmodell aus dem Issue-Text verfasst.

Beschreibung

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

Vorherrschende Sprache
JavaScript
Sterne
58
Forks
15
Ø Merge
16 Std. 53 Min.
Gemergte PRs (30 T.)
14

Entwicklungsumgebung

Erste Schritte

  1. Lesen Sie das ganze Issue und danach den Beitragsleitfaden des Projekts.
  2. Schreiben Sie ins Issue, dass Sie es übernehmen — das erspart doppelte Arbeit.
  3. Forken Sie das Repository und arbeiten Sie in einem Branch.
  4. Öffnen Sie einen Pull Request, der die Issue-Nummer nennt.

Mehr aus TMHSDigital/Free-Game-Dev-Assets

Alle Issues in TMHSDigital/Free-Game-Dev-Assets

Ähnliche Issues

Weitere Issues zu JavaScript

Neue Issues direkt in Ihr Postfach

Eine kurze Übersicht über anfängerfreundliche GitHub-Issues.