Give each chain its own social banner - #3056
Merged
Merged
Conversation
Chain pages set an `image:` frontmatter that Docusaurus emits as `og:image`, so a wrong or missing value is what people see when they share a link. Arc and Monad were both copied from the Ethereum page and kept Ethereum's banner, so sharing either link showed Ethereum branding. Seven more chains referenced banner files that were never added, making their preview a 404: base, bnb, astar-zkevm, astar-zkyoto, neon, nibiru, and opbnb. TON pointed at a stale `guides/` path prefix. The Unity pages for Ethereum and Solana used the generic Unity banner while all 44 other chains use their own chain banner there. Add the eight missing banners, built to the existing 756x350 template: a horizontal gradient from #68A2FF to a chain accent, the Web3Auth mark in a 144px disc at (247, 175), the MetaMask wordmark at x 337-418, and the chain logo in a 144px disc at (509, 175). The template and the accent rule (keep the logo's hue and saturation, lift lightness to ~0.70) were derived from the 76 banners already in the repo; regenerating shipped banners from scratch reproduces them to within ~3/255 mean per-pixel error. opBNB has no mark of its own in the repo, so its pages share the BNB banner rather than carry no chain branding. astar-zkyoto reuses the Astar zkEVM mark, since zKyoto is that network's testnet. Both are worth replacing if design supplies dedicated artwork. Co-authored-by: Cursor <cursoragent@cursor.com>
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
This branch was successfully deployed
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
Chain pages under
connect-blockchain/set animage:frontmatter that Docusaurus emits asog:image, so a wrong or missing value is exactly what people see when they share a link. An audit of every page in that tree turned up four distinct problems:banners/ethereum.png.base,bnb,astar-zkevm,astar-zkyoto,neon,nibiru,opbnb.other/ton.mdxpointed at aguides/prefix that doesn't resolve.Every page under
connect-blockchain/now resolves to a banner that exists and belongs to that chain.How the new banners were made
The eight new PNGs match the existing 756x350 template rather than approximating it. The template was recovered from the 76 banners already in the repo: a horizontal sRGB gradient from
#68A2FFto a chain accent, the Web3Auth mark in a 144px disc at (247, 175), the MetaMask wordmark at x 337-418, and the chain logo in a 144px disc at (509, 175).Regressing each pixel against its background gradient across all existing banners separates the fixed chrome's coverage from its colour exactly. The accent rule fell out of the same data: keep the logo's hue and saturation, lift lightness to about 0.70. Regenerating already-shipped banners from scratch reproduces them to within roughly 3/255 mean per-pixel error, which is the evidence that the reconstruction is faithful rather than merely close.
Chain logos come from
static/logos/. Monad's only exists as SVG, so its path was flattened to a bitmap.Two judgement calls worth reviewing
Both should be swapped out if design supplies dedicated artwork.
Test plan
npm startand confirm the new banners render at the expected size and contrastog:imagein the built HTML forevm/arc/,evm/monad/,evm/base/,evm/opbnb/, andother/ton/npm run format:checkpasses (verified locally on all 32 changed Markdown files)Made with Cursor