Repository navigation
6: feat: add the whiteboard image, blurred - #37
Merged
Merged
Conversation
…e is not published
# Conflicts: # packages/web/src/app/page.tsx # packages/web/test/pages.test.ts
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
1 participant
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. Puts one real photograph on the site: a whiteboard from a real engagement, cropped to
remove the person and blurred so no word on it is readable.
Why blurred. The diagram was legible: a build server, a container registry, a deploy target and
the steps between them. That is a client's architecture, and publishing it sits badly beside not
publishing their metrics. Blurred, it still reads as a hand drawn system diagram, which is the part
that says what we do, while disclosing nothing.
I tried four blur strengths and checked each. At sigma 2.5 the box labels were still readable. At 6
nothing is, and the boxes and arrows survive.
Why a photograph at all. The reference site you sent has three images and 337 words against our
zero and 194. Imagery was the largest remaining gap and this closes part of it.
How it is served. Through the image function that already exists in the stack, so it arrives as
AVIF or WebP at the size the layout asks for, with width and height set so nothing shifts as it
loads. 13 KB at source.
Tests. 40 now. Three added: the image is fetched through the optimiser and comes back in a
modern format, it carries dimensions, and its alternative text actually describes it. The last was
mutation checked by emptying the alt attribute.
Part of #2. Relates to #6.