laywill / laywill/laywill.github.io
Four gallery thumbnails are committed but referenced by nothing
Nobody has claimed this yet.
- Dominant language
- HTML
- Stars
- 0
- Forks
- 0
- Avg merge
- 8h 17m
- Merged PRs (30d)
- 58
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.jpgimages/gallery/photographer/event/thumbs/pounded-sparks.jpgimages/gallery/photographer/event/thumbs/score_01.jpgimages/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.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
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.
Assessment
- Tech stack
- html
- Domain
- content, web-dev
- Issue type
- Refactor
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 68/100