Conversation
ce511c4 to
74f97d5
Compare
leviport
requested changes
Mar 23, 2026
Member
leviport
left a comment
There was a problem hiding this comment.
Is the plan to add launch_heavy_3b in a separate PR?
74f97d5 to
4ccb5e5
Compare
Member
Author
Yes, or we can sit on this for a few more days until the Heavy section's ready if you'd prefer not to publish them separately. |
leviport
approved these changes
Mar 24, 2026
Member
leviport
left a comment
There was a problem hiding this comment.
Nope, I'm fine with them being merged separately. Just making sure that's what the plan was. This looks great, thanks!
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
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.
This adds the Launch 3B (
launch_3b) to tech docs. I simply dropped in new photos with the updated keycaps & powder coating, and didn't touch the text aside from adding a note about that (which I think is useful since we don't actually show thebon the physical engraving, per my photo of the photo unit).By switching from WebP @ 80% quality to AVIF @ 60% quality (which has similar visual fidelity), the size of the section's photos was reduced from 8.3 MB to 5.6 MB (about 33% smaller). This savings probably isn't worth immediately re-encoding older images, but can help slightly slow the growth of the repo's size going forward.
(The only exception that I left in WebP format was the hero image; something about its compression from how it was produced on marketing's side, or possibly its fading effect, causes it to be a much larger size in AVIF to achieve the same quality.)