Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

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

Closed
  • Is something wrong?
#155 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
48/100
Issue type
Feature
Clarity
Clearly specified
Activity status
Active
Tech stack
javascript
Domain
frontend

Research direction

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.

Written by the indexing model from the issue text.

Description

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

Dominant language
JavaScript
Stars
58
Forks
15
Avg merge
16h 53m
Merged PRs (30d)
14

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from TMHSDigital/Free-Game-Dev-Assets

All issues in TMHSDigital/Free-Game-Dev-Assets

Similar issues

More JavaScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.