[pull] dev from ethereum:dev#1125
Merged
Merged
Conversation
Full section-by-section rewrite of the stablecoins page as a Server Component matching the 2026 Figma design. - New PathwayCard design-system preset composed on ui/card, plus a bordered Card axis and an XCircle icon - ProductList gains a two-column variant and a mobile CTA alignment fix - StablecoinsTable reduced to 3 columns, no filters, clickable rows (product table variant); StablecoinAccordion removed - New hero, getting-started, interest, and bitcoin-pizza illustrations - English page-stablecoins copy updated (intl-pipeline propagates locales)
# Conflicts: # app/[locale]/stablecoins/page.tsx # src/components/ui/card.tsx
section h2 -> text-4xl/5xl black, h3 subheads -> text-3xl/4xl black, all card titles -> text-2xl black; split feedbackcard into its own section for standard spacing
Resolved conflicts: - app/[locale]/stablecoins/page.tsx: kept redesign (HEAD); dev's edits were to the now-replaced old layout - src/components/StablecoinAccordion/index.tsx: kept deleted (redesign removed the accordion; no remaining references)
- Convert feature/types/methods grids to ui/grid <Grid balanced> - Use CardParagraph size="sm" prop instead of text-sm class - flex-col for the getting-started column - Inline single-use heroButtons directly into PageHero - Rename stablecoins assets to descriptive names; upgrade canonical man-and-dog-playing.png with the higher-res version and drop the duplicate - Pad pathway-card banner; switch its banner/text layout to a container query so cards stack instead of cramping in narrow grid columns - Migrate CardTitle variant=* usage to dev's refactored card API (post-merge)
Co-Authored-By: Gemini <gemini@google.com>
Co-Authored-By: Gemini <gemini@google.com>
Co-Authored-By: Gemini <gemini@google.com>
Co-Authored-By: Gemini <gemini@google.com>
Co-Authored-By: Gemini <gemini@google.com>
Co-Authored-By: Gemini <gemini@google.com>
Co-Authored-By: Gemini <gemini@google.com>
Co-Authored-By: Gemini <gemini@google.com>
Co-Authored-By: Gemini <gemini@google.com>
Co-Authored-By: Gemini <gemini@google.com>
Co-Authored-By: Gemini <gemini@google.com>
Co-Authored-By: Gemini <gemini@google.com>
Co-Authored-By: Gemini <gemini@google.com>
Co-Authored-By: Gemini <gemini@google.com>
Co-Authored-By: Gemini <gemini@google.com>
Co-Authored-By: Gemini <gemini@google.com>
Co-Authored-By: Gemini <gemini@google.com>
Co-Authored-By: Gemini <gemini@google.com>
Co-Authored-By: Gemini <gemini@google.com>
Co-Authored-By: Gemini <gemini@google.com>
Co-Authored-By: Gemini <gemini@google.com>
Co-Authored-By: Gemini <gemini@google.com>
Co-Authored-By: Gemini <gemini@google.com>
Co-Authored-By: Gemini <gemini@google.com>
Co-Authored-By: Gemini <gemini@google.com>
Co-Authored-By: Gemini <gemini@google.com>
Co-Authored-By: Gemini <gemini@google.com>
Co-Authored-By: Gemini <gemini@google.com>
Co-Authored-By: Gemini <gemini@google.com>
Co-Authored-By: Gemini <gemini@google.com>
The intl-pipeline introduced 77 MDX syntax errors across all 24 languages that broke the Netlify build. Two root causes: (1) an outer wrapper's closing tag was replaced by a duplicate of its last child's closer (ExpandableCard/Callout closed with </ButtonLink> or </DocLink>) on roadmap/statelessness, community/online, and community/support/scams; (2) angle-bracket link destinations whose URL contains parentheses dropped their closing > on security (cs, ta, vi, zh) and ethereum-forks (bn). Each fix aligns the file's JSX/link structure to the stable English source. Verified: all 1769 changed translation files now compile cleanly via @mdx-js/mdx 3.1.0, the same parser the build uses. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com> Co-Authored-By: wackerow <54227730+wackerow@users.noreply.github.com>
The intl-pipeline emitted a duplicate "Work in Ethereum" section in the German community/grants page: a spurious heading without an anchor ID (informal "du" register) directly above the correct {#work-in-ethereum} version (formal "Sie"). The English source has a single heading. Removed the spurious duplicate to match the English structure and restore the missing anchor.
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Co-Authored-By: wackerow <54227730+wackerow@users.noreply.github.com>
The intl-pipeline emitted duplicate section headings across all 24 languages after the base branch's h1 -> frontmatter.title migration shifted block structure. Each affected section appeared twice: a ghost copy without the {#anchor} (often an older or differently-worded translation) immediately followed by the correct anchored copy. Removed 254 ghost heading blocks across 69 files (community/grants, contributing/adding-videos, roadmap/glamsterdam), keeping the canonical anchored version that matches the English source. Verified all 1769 translation files compile cleanly via @mdx-js/mdx and no anchor-less headings remain. Root cause (pipeline block-matching duplicating sections on structural change) is tracked separately for a sanitizer fix.
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Co-Authored-By: wackerow <54227730+wackerow@users.noreply.github.com>
Three translated frontmatter scalars introduced an unquoted ": " (colon-space) where the English source used a hyphen or had no colon, so yaml@2 (the parser next-mdx-remote uses for parseFrontmatter) read a second mapping key and failed the build with BLOCK_AS_IMPLICIT_KEY. Quoted the values: description in es and it roadmap/danksharding, and metaTitle in uk contributing/translation-program/faq. Verified all 1769 changed files now parse frontmatter cleanly. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com> Co-Authored-By: wackerow <54227730+wackerow@users.noreply.github.com>
- Re-applying after lost in merge commit Co-Authored-By: wackerow <54227730+wackerow@users.noreply.github.com>
fix: MainArticle and Static layout h1 handling
Redesign stablecoins page with 2026 Figma design
…-redesign i18n: translation pipeline (all languages)
i18n: translation pipeline - Static layout pages (all languages)
…260608032355 i18n: sync external descriptions - June 8
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 subscribe to this conversation on GitHub.
Already have an account?
Sign in.
4 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.
See Commits and Changes for more details.
Created by
pull[bot] (v2.0.0-alpha.4)
Can you help keep this open source service alive? 💖 Please sponsor : )