laywill / laywill/laywill.github.io

chore: remove or stop deploying unreferenced top-level images

Open Beginner friendly
#135 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
HTML
Stars
0
Forks
0
Avg merge
8h 17m
Merged PRs (30d)
58

Description

Problem

Six images at the top level of images/ are referenced by no page, stylesheet, script or index:

  • images/IMG_6306.jpg
  • images/desk.jpg
  • images/harvey.jpg
  • images/jack.jpg (not the same file as images/gallery/photographer/portraits/*/jack.jpg, which is used)
  • images/lake.jpg
  • images/mixing_console.jpg

static.yml copies the whole images/ directory, so they ship on every deploy and get optimised for no reason.

Found by grepping *.html, *.scss, *.css, *.js, *.txt and *.xml for each basename. Spotted during the #131 alt-text sweep.

Proposal

Confirm that none is kept on purpose, for example as a future banner. Then either delete them or strip them in the deploy job alongside images/will/JPEGs/. Related: #102 (deploying from site/).

Acceptance criteria

  • Every image under images/ that ships is referenced by a deployed page, or the exception is documented

Contributor guide

No contributing guide indexed for this repository

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.

Research direction

Recheck references to the six listed files under images/ across the file types named in the issue, then inspect static.yml and the existing images/will/JPEGs/ deploy handling. Confirm whether any image is intentionally retained, choose the issue's deletion or deploy-stripping path, and verify that every shipped image is referenced or documented as an exception.

Written by the indexing model from the issue text.

Assessment

Tech stack
html, yaml
Domain
build-system, release
Issue type
Refactor
Difficulty
2/5
Estimated time
Half a day
Activity status
Active
Clarity
Mostly clear
Newbie friendliness
74/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.