Skip to content

Fix share thumbnail: show full logo (heart + 1) on white - #6

Merged
pushpsood merged 1 commit into
mainfrom
fix/share-thumbnail-og-image
Oct 22, 2026
Merged

pushpsood merged 1 commit into
mainfrom
fix/share-thumbnail-og-image

Conversation

@pushpsood

Copy link
Copy Markdown
Owner

Summary

Link previews/thumbnails for the site showed just the transparent heart shape (no "1"). Root cause: the Open Graph and Twitter <meta> blocks had no image tag, so crawlers fell back to the preloaded, transparent, heart-only /media/LogoHeart.png.

This adds explicit share-image tags pointing to the full logo — silver heart with the navy "1" inside, on a white background.

Changes (index.html)

  • Add og:image (+ og:image:secure_url, :type, :width, :height, :alt)
  • Add twitter:image (+ twitter:image:alt)
  • Add canonical og:url
  • Image: onehook_white_inside-512.png (full logo on white)

Why the 512px variant

vite.config.ts's leanMediaPrunePlugin deletes onehook_white_inside-1024.png from the build output, so that URL would 404 in production. The 512px file is not pruned and is confirmed to ship in dist/media/.

Testing

  • npm run build succeeds; tags present in built dist/index.html; dist/media/onehook_white_inside-512.png ships.
  • Pre-push hook: 58 unit tests passed, telemetry contract OK.

Notes

  • The browser-tab favicon markup was already correct (full logo on white); any stale tab icon is client-side favicon caching.
  • After deploy, social caches may need a refresh via Facebook Sharing Debugger / X Card Validator.

Link-preview crawlers had no designated share image (no og:image or
twitter:image), so they fell back to the preloaded transparent,
heart-only /media/LogoHeart.png. Add og:image/twitter:image (plus
secure_url, type, dimensions, alt) and og:url pointing to
onehook_white_inside-512.png: the full logo (silver heart with navy 1)
on a white background. Uses the 512px variant because the 1024px file
is removed from the build by leanMediaPrunePlugin.
@pushpsood
pushpsood merged commit b9c0d62 into main Oct 22, 2026
1 check passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant