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

Four gallery thumbnails are committed but referenced by nothing

Open Beginner friendly
  • Is something wrong?
#106 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
68/100
Issue type
Refactor
Clarity
Mostly clear
Activity status
Active
Tech stack
html
Domain
content, web-dev

Research direction

Start by comparing images/gallery/photographer/event/thumbs/ and images/gallery/photographer/landscapes/thumbs/ with the entries in photographer.html, then check whether matching fulls/ files exist. Decide whether the gallery entries can be restored or the unused assets should be removed, and verify that no orphaned thumbnails or full-size counterparts remain; review scripts/optimize-images.mjs for the build path.

Written by the indexing model from the issue text.

Description

Found while measuring every image for #95/#104 (PR #105).

images/gallery/**/thumbs/ holds 33 files, but only 29 have an <img> pointing at them. These four are orphaned:

  • images/gallery/photographer/event/thumbs/pounded-group.jpg
  • images/gallery/photographer/event/thumbs/pounded-sparks.jpg
  • images/gallery/photographer/event/thumbs/score_01.jpg
  • images/gallery/photographer/landscapes/thumbs/london.jpg

All four are 720x500 like the rest, so they look like thumbs for gallery entries that were dropped from photographer.html at some point. Worth checking whether the matching fulls/ exist too.

They are copied into _site/images by the deploy allowlist and then run through scripts/optimize-images.mjs, so they cost build time and artifact size for nothing.

Either restore the gallery entries or delete the files (and any orphaned fulls/ counterparts). Left alone in #105, which only touched referenced images.

Dominant language
HTML
Stars
0
Forks
0
Avg merge
9h 52m
Merged PRs (30d)
59

Getting set up

Open in Codespaces

Starts the project's dev container in your browser, under your own GitHub account.

  • No Dockerfile or Docker Compose file
  • No pull request template
  • No contributing guide

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 laywill/laywill.github.io

All issues in laywill/laywill.github.io

Similar issues

More Content issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.