Skip to content

fix(website): use tabular benchmark numerals in dynamic og - #2394

Open
cmpadden wants to merge 1 commit into
mainfrom
fix/evals-og-tabular-nums
Open

fix(website): use tabular benchmark numerals in dynamic og#2394
cmpadden wants to merge 1 commit into
mainfrom
fix/evals-og-tabular-nums

Conversation

@cmpadden

Copy link
Copy Markdown
Collaborator

Summary

Follow-up to #2387 based on maintainer feedback. The benchmark social card now uses tabular numerals in both percentage columns so results align consistently across rows.

Validation

Generated the Next.js route types and confirmed the docs TypeScript compiler passes. Automated tests and documentation are not applicable to this visual-only adjustment.

Checklist

  • This change was requested or approved by a maintainer
  • I ran the relevant checks from CONTRIBUTING.md
  • I added tests and documentation where relevant
  • I added a changeset if this touches the published eve package
  • DCO sign-off passes for every commit (git commit --signoff)

Diff size

Docs — 0 files · +0 / -0

Not applicable.

Implementation — 1 file · +2 / -0

Keeps the typography adjustment scoped to the two numeric result columns.

Tests — 0 files · +0 / -0

Not applicable for this visual-only adjustment.

@vercel

vercel Bot commented Aug 21, 2026

Copy link
Copy Markdown
Contributor

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

Project Deployment Actions Updated (UTC)
eve-docs Ready Ready Preview Aug 21, 2026 7:41pm
eve-docs-4759 Ready Ready Preview, v0 Aug 21, 2026 7:41pm
1 Skipped Deployment
Project Deployment Actions Updated (UTC)
eve-pkg Skipped Skipped Aug 21, 2026 7:41pm

@cmpadden cmpadden changed the title fix(website): use tabular benchmark numerals fix(website): use tabular benchmark numerals in dynamic og Aug 21, 2026
Signed-off-by: Colton Padden <colton.padden@vercel.com>
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