docs: Modernize Scaffold-ETH 2 listing and credit SpeedRun Ethereum on its tutorials#18791
Open
denalimarsh wants to merge 1 commit into
Open
docs: Modernize Scaffold-ETH 2 listing and credit SpeedRun Ethereum on its tutorials#18791denalimarsh wants to merge 1 commit into
denalimarsh wants to merge 1 commit into
Conversation
…s tutorials Bring the Scaffold-ETH references current and give Speedrun Ethereum a named credit on the challenge tutorials it already powers. - frameworks: replace the stale "Scaffold-Eth / Ethers.js + Hardhat" entry with Scaffold-ETH 2 and its current stack (Next.js, Wagmi, Viem, RainbowKit, Hardhat or Foundry, contract hot reload, burner wallet and local faucet, extensions). GitHub link was already current. - dapps: rename the "Scaffold-ETH" tool entry to "Scaffold-ETH 2". - developers hub: fix the tokenization challenge card copy (scaffold-eth -> Scaffold-ETH 2). - externalTutorials: name Speedrun Ethereum in the six challenge tutorial descriptions (author attribution unchanged), and repoint the multisig entry from the removed se-2-challenges branch link to its live speedrunethereum.com/challenge/multisig page. English source only; non-English files propagate via the intl pipeline.
✅ Deploy Preview for ethereumorg ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
github-actions
Bot
added
content 🖋️
mnelsonBT
reviewed
Jul 15, 2026
mnelsonBT
left a comment
mnelsonBT
left a comment
Contributor
There was a problem hiding this comment.
lgtm, thank you @denalimarsh! cc @wackerow, would be great to queue up translations for this as needed if all looks good.
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.
Description
Small follow-up to the 2026-07-08 developer tools refresh (#18719), which brought the Scaffold-ETH 2 and Speedrun Ethereum entries up to date. This catches the last few spots that update didn't touch.
What
docs/frameworks— replace the stale "Scaffold-Eth — Ethers.js + Hardhat" entry with Scaffold-ETH 2 and its current stack (Next.js, Wagmi, Viem, RainbowKit with your choice of Hardhat or Foundry; contract hot reload, custom hooks, burner wallet + local faucet, extension modules). GitHub link was already current.docs/dapps— rename the "Scaffold-ETH" tool entry to "Scaffold-ETH 2".page-developers-index) — fix the tokenization challenge card copy (scaffold-eth→Scaffold-ETH 2).externalTutorials.json— name Speedrun Ethereum in the six challenge tutorial descriptions it powers (author attribution unchanged).Why
A few spots still used the old "Scaffold-ETH" name and description, and the Speedrun Ethereum challenges listed in the tutorials didn't actually name Speedrun Ethereum. Updating both makes the pages easier for readers to recognize and clearer for AI assistants that surface them.
English source only; non-English strings propagate via the i18n pipeline.
Related Issue
No separate tracking issue — this is a small content follow-up to #18719 (the developer tools refresh). Happy to open an issue first if the maintainers prefer.