1f5bcfb50c
closes #28 The owner supplied a redrawn lockup, docs/design/dist/splash.webp, which sets the name as "Privacy: Period Tracker" — with the space after the colon. NECESSARY AND NOT SUFFICIENT The tempting move was to look at the new artwork and close the issue. #28's Verify names the two DERIVED assets, not the lockup: the wordmark in docs/data/img/logo.webp and banner.webp had to match app_full_name, and both still carried the old spaceless form because they were generated from the earlier source. Regenerated from the new lockup and checked by cropping the colon out of each finished webp and reading it at 1350px wide. THE BANNER IS COMPOSED, NEVER CROPPED The lockup is square and the banner is 3:1, so a crop takes the ends off the wordmark — the trap the first pass at these assets hit. A 660px square card centred on 2176x725, matching how the existing asset did it. No flood-fill this time either: splash.webp has real transparency where the earlier sources rendered their rounded corners against black. icon.webp is deliberately untouched. It carries no wordmark, it is the same visual family, and #28 is about the name — regenerating it would be churn dressed as consistency. BRAND_GUIDE.md §10 carried a callout stating the drawn mark disagreed with the written name. That is now false, so it records what happened instead and marks lockup-light-source.png and lockup-dark-source.png as superseded rather than deleting them; they are the owner's files. Also corrects a path in the previous log entry, which named splash.png in backticks — doc-claims reads that as a claim the file is present, and it is now splash.webp. Named bare, per the convention DOC_TRUST_MAP.md documents for a path that deliberately does not exist. Second time this session; the lesson is that converting a file means grepping the docs for its old name. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> |
||
|---|---|---|
| .. | ||
| README.md | ||
| banner.webp | ||
| icon.webp | ||
| logo.webp | ||
README.md
Project images
Status: Current
Owner: _null
Last reviewed: 2026-08-18
Governs: docs/data/img/** — the three files and their sizes
Review trigger: A rebrand; any change to a required name, dimension or ceiling;
any change to what the consumer accepts.
Three files, all webp, all required, at exactly these names:
| File | Dimensions | Aspect | Typical weight |
|---|---|---|---|
icon.webp |
512 × 512 | 1:1 | 8–60 KB |
logo.webp |
1024 on the long edge | whatever the lockup is | 20–190 KB |
banner.webp |
2176 × 725 | 3:1 | 30–130 KB |
Not icon.ico. The consumer checks the file's magic bytes, not its name: a
.ico, or a PNG renamed to .webp, is refused with a 415 and the project falls
back to an initials tile. That signature check is what makes it safe to render
these inline, so it is not going to be relaxed.
512 KB is a hard ceiling per file, enforced in code — the size is read from the listing before the bytes are fetched, so an oversized asset is never downloaded and simply never appears. Nothing enforces the dimensions, which is why they are written down.
Making them
magick logo-source.png -resize 512x512 -quality 82 icon.webp
identify -format '%f %wx%h %b\n' *.webp # check before committing
Quality 80–85 suits a flat mark. If a file lands over ~200 KB it is usually a photographic banner that wants a lower quality rather than fewer pixels.
Why these numbers
The icon renders small — a 44 px tile in a list, 58 px on a project header — so 512 covers the densest display several times over; the reference project deliberately halved it from 1024. The banner spans a card about 760 px wide, so ~2176 covers it at 2×, and its 3:1 shape matters more than its width because the header crops to fill. The logo has no fixed frame, so only its long edge is specified.
Extra sizes and variants are welcome beside these — icon-512.webp,
logo-dark.webp. Only the three exact names are checked for.
No placeholders ship here. An empty file is the worst of the three states: a check that asks whether the path exists calls it present, and anything reading the bytes rejects it. Absent is honest, and the conformance check reports it as absent — which is what gets it filled in.
Why the requirement exists, and what reads it: ../README.md.