Skip to content

feat(docs): give every page its own share image - #970

Merged
juandolealt merged 3 commits into
mainfrom
chase/site-33-docs-og-images
Oct 11, 2026
Merged

juandolealt merged 3 commits into
mainfrom
chase/site-33-docs-og-images

Conversation

@chasegrayoffice

@chasegrayoffice chasegrayoffice commented Oct 10, 2026 •

Copy link
Copy Markdown
Contributor

Developers pages used the generated /api/og text card. Each page now gets its own image from the 2026-Q4 OG set.

Summary

  • 247 docs pages and the blog index set ogImage; the files are in public/og/2026-q4
  • Dev blog posts set a new shareImage, because the blog cards read ogImage and the art is too fine at card size. The cards are unchanged
  • docsStructuredDataHead applies ogImage on every page and resolves root-relative paths against tempo.xyz/developers
  • The 29 generated API reference pages have no source file, so their images are listed in the head
  • File names end in v02 so X, Slack and LinkedIn fetch the new image instead of a cached one
  • Pages without an image (new pages) keep the /api/og card
  • The SEO head e2e expects each page's own file
  • Strip formatting whitespace from the inline route bootstrap so the added image metadata stays within the existing HTML-response budget; runtime behavior is unchanged

Validation

  • Biome, types, unit tests, build, check:markdown
  • Full build in CI-equivalent E2E mode passes on the corrected commit
  • All 16 focused HTML-budget and SEO-head browser tests pass, including all six dev blogs and image endpoints
  • /docs/protocol/transactions: 224,708 bytes against the unchanged 225,000-byte limit
  • 24 focused normalization, metadata, and SEO unit tests pass
  • No tests added

Tracking

Fixes SITE-33 · tempo.xyz pages: tempoxyz/tempo.xyz#148

Note

Chase reviews before merge.

🤖 Generated with Claude Code

- 247 docs pages set ogImage to a 2026-Q4 image; the blog index sets it in routeMetadata
- Dev blog posts set a new shareImage, so the blog cards keep their ogImage
- Generated API reference pages take theirs from a list in the docs head
- Root-relative ogImage values resolve against tempo.xyz/developers
- Files end in v02 so X and Slack refetch instead of serving a cached card
- Pages without an image keep the generated /api/og card

Refs SITE-33

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@vercel

vercel Bot commented Oct 10, 2026 •

Copy link
Copy Markdown

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated
tempo-docs Ready Ready Preview Oct 11, 2026 8:04pm UTC

Request Review

Vocs embeds the docs head callback in initial HTML. Store the same API image slugs compactly to reduce the serialized callback by 279 bytes without changing image URLs, metadata, or the HTML size budget.
@juandolealt
juandolealt merged commit e1575e0 into main Oct 11, 2026
14 checks passed
@juandolealt
juandolealt deleted the chase/site-33-docs-og-images branch October 11, 2026 20:13
emmajam added a commit that referenced this pull request Oct 12, 2026
Resolve conflicts with #970 (share images) and #972 (API reference and
developer tools navigation):
- blogs/introducing-stable-bench-v1.md: keep comma-separated authors, add shareImage
- src/pages/index.mdx: use main's SDKs & CLI section; point its overview link at /docs/sdk
- e2e/docs-workspace.test.ts: header layout check now covers the Blog-only destinations

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

This branch was successfully deployed

1 active deployment
Preview — 0e7b0ede Deployed Oct 11, 2026 by vercel[bot]
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.

2 participants