Replace the hero photo with the current enclosure - #13
Merged
TigerTag-Project merged 1 commit intoAug 22, 2026
Merged
Conversation
The README hero image still showed an earlier build. Swapped in a studio photo of the current blue "Tiger Scale" enclosure with the screen mid-weighing (753 g, R3D PLA High Speed), same filename (assets/tigerscale-v3.png) and same 760x760 dimensions as the image it replaces, so nothing else needs to change. 1.36 MB source resized to 688 KB.
Ptitlouis6012
force-pushed
the
assets/replace-hero-photo
branch
from
August 22, 2026 07:55
eaaa7c8 to
7f34a5b
Compare
9 tasks
TigerTag-Project
pushed a commit
that referenced
this pull request
Aug 22, 2026
The three photos that landed in #13 and #14 were heavier than the ones they replaced -- the social card alone had doubled to 1.4 MB -- and all three carried an alpha channel. Measuring what that alpha actually held decided the treatment for each. og.png had 0.48% of its pixels below full opacity, clustered at alpha 237-238: an export artefact along an edge, not a design. Flattened onto the site's own background and saved as progressive JPEG at quality 92, it goes from 1432 KB to 163 KB with nothing visibly different. It becomes og.jpg, so both meta tags move with it and an og:image:type joins them. The hero is the opposite case: 55% of its pixels are fully transparent, a cut-out on no background. Converting it would have put a black or white box behind the scale in the README, so it stays PNG and is only re-encoded -- 688 KB to 522 KB, verified pixel-identical to what the contributor supplied. The same file serves the installer page, byte for byte, and gets the same treatment. A 256-colour version of that hero would have reached 99 KB. It is not here on purpose: quantising a product photograph bands its gradients, and that is a judgement about the product's own image rather than a size decision.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What does this change?
Replaces the README hero photo (
assets/tigerscale-v3.png) with a current studio shot of the blue "Tiger Scale" enclosure, screen mid-weighing (753 g, R3D PLA High Speed). Same filename and same 760x760 dimensions as the image it replaces, so no other file needs to reference a new path or size.Why?
The previous hero image no longer matched the current enclosure.
How was it tested?
Docs/assets only — no firmware code touched. Rendered the new image in the README's actual hero layout (buttons, links, image) locally to confirm it looks right at the existing
width="380"before opening this PR.Checklist
bash scripts/check-codemap.shpasses — N/A,.inonot touchedbash scripts/check-i18n.shpasses — N/A, no i18n files touchedbash scripts/update_toc.shrun — N/A, no// §N —banner touchedWORKLOG.mdupdated — N/A, WORKLOG.md is maintainer-scoped, not touched by this fork PRFor a UI change