chore: remove or stop deploying unreferenced top-level images
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- Half a day
- Newbie friendliness
- 74/100
- Issue type
- Refactor
- Clarity
- Mostly clear
- Activity status
- Active
- Tech stack
- html, yaml
- Domain
- build-system, release
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.
Description
Problem
Six images at the top level of images/ are referenced by no page, stylesheet, script or index:
images/IMG_6306.jpgimages/desk.jpgimages/harvey.jpgimages/jack.jpg(not the same file asimages/gallery/photographer/portraits/*/jack.jpg, which is used)images/lake.jpgimages/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
- Dominant language
- HTML
- Stars
- 0
- Forks
- 0
- Avg merge
- 9h 52m
- Merged PRs (30d)
- 59
Getting set up
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
- 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.
More from laywill/laywill.github.io
-
design
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
laywill/laywill.github.io#186 ·
Maintainers usually reply within 1 day
-
design
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
laywill/laywill.github.io#183 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
laywill/laywill.github.io#106 ·
Maintainers usually reply within 1 day
-
infra needs-william
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
laywill/laywill.github.io#35 · 1 comment ·
Maintainers usually reply within 1 day
-
infra
Difficulty 3/5 1-2 days Newbie friendliness 65/100
laywill/laywill.github.io#187 ·
Maintainers usually reply within 1 day
All issues in laywill/laywill.github.io
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 66/100
AppImage/appimage.github.io#9676 ·
Maintainers usually reply within 1 day
-
Flutter Improvement Waiting for: Product Owner
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
getsentry/sentry-dart#4061 · 2 comments ·
Maintainers usually reply within 3 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Cocoanetics/SwiftBash#95 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
ml-explore/mlx-c#136 ·
-
Xcode 27Open
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
airbnb/HorizonCalendar#349 ·