{"id":18281,"date":"2026-03-14T11:46:22","date_gmt":"2026-03-14T11:46:22","guid":{"rendered":"https:\/\/cryptoted.net\/index.php\/2026\/03\/14\/development-update-4-ethereum-org\/"},"modified":"2026-03-14T11:46:22","modified_gmt":"2026-03-14T11:46:22","slug":"development-update-4-ethereum-org","status":"publish","type":"post","link":"https:\/\/cryptoted.net\/index.php\/2026\/03\/14\/development-update-4-ethereum-org\/","title":{"rendered":"Development update #4 \u2013 ethereum.org"},"content":{"rendered":"


\n<\/p>\n

\n

Hey Ethereum community! It’s been a few months since our last update so it’s about time we let you know what’s been happening over at ethereum.org.<\/p>\n

<\/g><\/svg><\/a>First up, we’re now using Gatsby<\/h2>\n

\"The<\/p>\n

Under the hood at ethereum.org we’ve switched from Vuepress to Gatsby<\/a>. Now, this won’t be immediately obvious to anyone visiting the website but it’s going to help us scale ethereum.org. Our team prefers React (a lot of people do) and has experience with MDX \u2013 so we should be able to ship better content, faster.<\/p>\n

If you’re up-to-date on your Eth2 timeline, you could say that Gatsby is our Phase 0. It’s setting us up for future success.<\/p>\n

If you were never a fan of Vuepress and Gatsby is more your thing, we’d love you to contribute<\/a>. This new section outlines ways in which you can help ethereum.org<\/a> grow and improve.<\/p>\n

<\/g><\/svg><\/a>Fresh illustrations<\/h2>\n

\"Illustration<\/p>\n

We’ve been working with some independent artists to bring Ethereum to life. With nods to doge, the open-source bazaar, and the money-legos meme, we hope you’re loving the new vibe of the site.<\/p>\n

You’re free to use any of the illustrations \u2013 they’re for the community.<\/p>\n

<\/g><\/svg><\/a>New page designs<\/h2>\n

We’re also working on revamping our onboarding content, like the pages that introduce you to Ethereum, Ether (ETH), wallets, and dapps. Over the next few months we want to make ethereum.org a better resource for new users. To that end, we’ve been adding more information to these pages, making them feel less like a “Github README<\/span>“, and adding helpful features.<\/p>\n

One feature we shipped recently is our Get ETH page<\/a>. This helps you find wallets and exchanges you can use to buy ETH, based on where you live. We hope this prevents new users trying to sign up for an exchange they won’t be able to use, or from downloading a wallet that they can’t buy ETH from. It’s all about reducing that friction!<\/p>\n

\"Screenshot<\/p>\n

So far we’ve shipped:<\/p>\n

Check them out and let us know what you think!<\/p>\n

<\/g><\/svg><\/a>A new framework<\/h2>\n

Part of our duty at ethereum.org is to shine a light on the fantastic work being done by the community \u2013 from dapps to wallets to articles. But we also want to ensure that we’re directing users to information that won’t confuse or overwhelm them.<\/p>\n

This is sometimes a bit of a balancing act. So we have come up with a framework to help us figure out what we should list and what we shouldn’t. The framework covers wallets and dapps, stating our inclusion criteria and our reasons.<\/p>\n

The framework looks into a product’s commitment to security and support as well as some nice-to-have features that can help new users.<\/p>\n

Check out the framework<\/a><\/p>\n

As with everything ethereum.org \u2013 we welcome feedback from the community if you have any thoughts.<\/p>\n

<\/g><\/svg><\/a>ethereum.org hits 30 languages<\/h2>\n

You may have already read about this in a previous post, but we now provide content to users in 30 languages.<\/p>\n

467 volunteers from 52 language groups have helped us get here. It’s been an incredible community effort \u2013 on to the next 30!<\/p>\n

You can read more about the translation program and this milestone in the celebration post<\/a>.<\/p>\n

<\/g><\/svg><\/a>What’s next?<\/h2>\n

While lots of you have been farming yield, we’ve been sowing the seeds of some exciting new content.<\/p>\n

Over the next few months we’ll be shipping pages that cover:<\/p>\n