Add custom header/OG images to all 5 blog posts - #239
Closed
V-Figueroa wants to merge 1 commit into
Closed
Conversation
Each post now has its own on-brand banner + social card instead of sharing the site-wide default og-image.png — the original problem Kai-Uwe flagged (every post importing with the same generic image). - Adds headerImage (optional) alongside the existing image field in BlogPostFrontmatter — image feeds og:image/twitter:image/JSON-LD (already wired), headerImage is new: rendered inline inside the post's title card in BlogPostPage.tsx, which had no image slot before. - Images resized from the 2x/@retina source files (2-3.5MB each) down to their actual display size (1200x630 / 1600x640, ~500-650KB each) before committing, in line with the existing og-image.png's footprint. - public/images/blog/<slug>/{og,header}.png per post.
Contributor
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
smaramwbc
pushed a commit
that referenced
this pull request
Aug 10, 2026
Four page and content additions, landed together: - /benchmarks — LoCoMo and LongMemEval results for Statewave, mem0 cloud and mem0 OSS, run in-harness with a shared gpt-4o judge; numbers trace to the statewave-memory-benchmarks repo. - /vs/mem0 — comparison page: deterministic, token-bounded context assembly with policy enforcement and receipts vs. ranked similarity retrieval. - /use-cases/grounded-shop-assistant — use-case page for the grounded shop assistant reference build (links smaramwbc/statewave-grounded-shop-assistant). - Custom header and OG images for all five blog posts. Combined from PRs #226, #228, #235 and #239 (see those PRs for the full per-change history and discussion).
This was referenced Aug 10, 2026
Owner
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
2 participants
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.
Summary
Every blog post now has its own on-brand banner + social-share image, instead of all posts sharing the site-wide generic
og-image.png— the original problem behind "every post imports with the same image."public/images/blog/<slug>/:og.png(1200×630, social/Google preview) andheader.png(1600×640, shown inline inside the post itself).og-image.png's footprint.og.pnguses theimagefield onBlogPostFrontmatterthat was already wired toog:image/twitter:image/JSON-LD in the previous OG-meta PR — no new plumbing needed there.header.pnguses a new optionalheaderImagefield, rendered inline inside the post's title card inBlogPostPage.tsx(there was no image slot there before).og:title/<h1>, which already render as text).Test plan
npm run buildgreenog:imagemeta + the inline<img>tag both resolve to the right per-post file in the generated HTML