The images in packages/webapp/public/ are outdated and should be redrawn. Not urgent — filing so it is not forgotten.
They were committed as-is in #50, which tracked them for the first time. That PR deliberately preserved them byte-for-byte, because the goal was to stop a deploy from un-publishing the pages. Refreshing the artwork is the separate follow-up.
Files
| File |
Size |
Used by |
og.png |
187 KB |
og:image on all four public pages |
hero.png |
136 KB |
the /landing page |
apple-touch-icon.png |
37 KB |
iOS home-screen icon |
favicon.ico |
3.4 KB |
browser tab |
Where they are referenced
Every public page points og:image at the same asset:
<meta property="og:image" content="https://blitzos.com/og.png">
<meta name="twitter:card" content="summary_large_image">
That covers /landing, /terms, /privacy and /security. One file drives the preview card for all of them, so replacing og.png updates every page at once. If the pages should preview differently, that needs per-page assets and a og:image change in each file.
Notes for whoever picks this up
twitter:card is summary_large_image, so og.png wants a 1.91:1 ratio. 1200x630 is the usual size.
- Add any new image to
packages/webapp/published-assets.json. The deploy check and test/published-assets.test.ts both read that manifest, and an unlisted file is not guarded.
- Removing a file from the manifest is a deliberate un-publishing, so drop the entry and the file together.
- Social platforms cache preview images aggressively. Expect to re-scrape after the change lands.
🤖 Generated with Claude Code
The images in
packages/webapp/public/are outdated and should be redrawn. Not urgent — filing so it is not forgotten.They were committed as-is in #50, which tracked them for the first time. That PR deliberately preserved them byte-for-byte, because the goal was to stop a deploy from un-publishing the pages. Refreshing the artwork is the separate follow-up.
Files
og.pngog:imageon all four public pageshero.png/landingpageapple-touch-icon.pngfavicon.icoWhere they are referenced
Every public page points
og:imageat the same asset:That covers
/landing,/terms,/privacyand/security. One file drives the preview card for all of them, so replacingog.pngupdates every page at once. If the pages should preview differently, that needs per-page assets and aog:imagechange in each file.Notes for whoever picks this up
twitter:cardissummary_large_image, soog.pngwants a 1.91:1 ratio. 1200x630 is the usual size.packages/webapp/published-assets.json. The deploy check andtest/published-assets.test.tsboth read that manifest, and an unlisted file is not guarded.🤖 Generated with Claude Code