Q3 2022 ethereum.org product roadmap #7166
Description
To make our work more accessible and to foster more community collaboration, our team publishes an overview of our quarterly roadmap goals. See last quarter's roadmap here: #6161.
Greetings fellow Ethereans!
Our vision with ethereum.org continues to be to create the best portal for Ethereum's growing community. We’re an educational resource focused on helping onboard millions of visitors to Ethereum each month. Here's a look at our major Q3 initiatives to advance this vision.
Quick point of clarification: this is the roadmap for ethereum.org the website, not Ethereum the protocol. If you’re looking for the Ethereum roadmap, check out information on upcoming network upgrades and learn more about Ethereum governance.
With that out of the way, let’s dive in.
The must-haves
The epics our core team is committing to shipping this quarter.
🔀 Post-Merge prep
Core Ethereum developers are in the final stages of testing and preparing for The Merge. Last quarter we shipped updates across ethereum.org (#6281) and the Ethereum Staking Launchpad (ethereum/staking-launchpad#493) to help prepare our community for this Ethereum protocol upgrade. These updates handled all pre-merge updates: content changes that can be made before The Merge takes place.
This quarter we’re turning our focus to post-merge content updates: content changes that should be rolled out after Ethereum completes The Merge successfully. In a similar fashion, we’ll run a page-by-page audit of ethereum.org and the Ethereum Staking Launchpad and rollout updates across both sites. We’ll also work to identify and fill gaps in site content - topics we should cover in a post-Merge world.
Want to get involved? Join the conversation in our #merge-prep Discord channel.
🌏 Translate the EF blog
We'll finish the site rebuild we started in Q2 and deploy a fresh blog codebase with internationalization support this quarter.
The blog repo is currently private, so not much to share at this point, but we're hoping to open source the codebase as part of the launch. In the meantime, you can view our design updates and test out the latest preview deploys. Feedback is always welcome - feel free to comment directly in Figma or join the conversation in Discord.
After launch, we'll publish a blog post detailing how to get involved with the community translations, so stay tuned!
🎨 Open design system
The open design system is and will continue to be an ongoing effort that we kicked off in Q2. The design system will help establish and document our design language, which anyone in the community can use to create reusable resources. The aim here is to increase our UI's consistency and productivity for our design and development community.
In Q2, we mapped and divided our roadmap for the design system into 1) foundations, 2) components, and 3) layouts. With the foundations in place, in Q3, we’ll focus on building reusable components that help make layouts.
These components will be divided into two buckets:
- Base components: small elements that can be used in different positions and can be forms, buttons, navigation, and cards.
- Composed components: combinations of various base components that form the core of layouts, including header, footer, and page hero.
By the end of the quarter, we will release a new update to the design system ready with some base layouts made out of combinations of components. We’re aiming to have a base layout, a markdown layout, a use case page layout, and the homepage.
Want to get involved? Follow along in Figma and join the conversation in our #design Discord channel.
🖥 Implement UI library
Another Q2 carryover initiative (#6374) closely tied to the design system - to improve our code quality, improve productivity, website accessibility and overall UX, we’re adding a UI library to our codebase.
We’ll kick off the implementation work this quarter and start rolling out Chakra UI components across the codebase. This is a significant undertaking, which will likely involve large refactors to clean up duplicate code and to integrate the new design system that we expect to be working on into Q4.
Want to get involved? Join the conversation in our #website-code Discord channel.
🦔 Build a new Geth website
The current Geth site (geth.ethereum.org) has served its purpose for a long while but is far from perfect - it contains some out-of-date and incomplete information, lacks modern website features like built-in search and the overall aesthetics lack a modern look that undersells what Geth has become - a core piece of Ethereum infrastructure and public good for the ecosystem.
This quarter we’ll kick off design, content, and code to build a new Geth site. We plan to provide expanded educational information, accurate and robust documentation, and a modern design fitting for such a crucial resource in the space.
💖 Implement HEART framework
The HEART framework is a well-established, proven, UX-focused methodology to improve software products. We plan to apply the HEART framework to different user groups and aspects of our products, starting in Q3 with the translation program.
We’ll implement the HEART framework across all aspects of this contributor funnel - Happiness, Engagement, Adoption, Retention, and Task success. We’ll pull data, surface insights, and identify key takeaways that will guide our operation and product priorities for the translation program next quarter. With the translation program as a testing ground, we’ll also consider applying the HEART framework more broadly across all our contributor and end-user funnels.
Want to get involved? Join the conversation in our #translate Discord channel.
💰 Wallet upgrades
In Q2, we revamped our Find Wallet page (#6274).
While this was a large release that introduced substantial enhancements to the data gathered on wallets and how users can filter and find an Ethereum wallet, there are still remaining features and cleanup items that we identified to improve the find wallet page. This quarter we’ll continue introducing additional improvements that were scoped out of the initial release.
Want to get involved? Join the conversation in our #wallets Discord channel.
💯 Learning quizzes
Many aspects of Ethereum are complex and can be difficult to grasp. A great way to ensure important content is understood is by immediately testing knowledge after it is presented. We’ll introduce optional quizzes across ethereum.org pages to ensure that readers grasp the essential concepts to allow them to be meaningful participants in the Ethereum ecosystem. Along with our feedback surveys, we expect these quizzes to drive insights into how to improve our content resources further.
Over the long term, we envision this will set the foundation for more structured, sequential learning resources (perhaps with web3 gamification) on ethereum.org.
🗣️ User insights
Last quarter we shipped a new feedback widget (#6252) integrated with custom surveys across all pages on ethereum.org and started collecting data. This quarter we will focus on validating and analyzing your responses and formulating useful insights to improve our site. We’ll build reports and consider how we might publish research findings as a public good to the Ethereum product community. We will also use this data to influence our content strategy decisions and priorities.
Want to get involved? Join the conversation in our #design Discord channel.
🌍 Revamp translation program resources
The Translation Program page is dedicated to the ethereum.org Translation Program and contains key information on what the program is, how to get involved, how to succeed as a translator and even guides on building out your own translation initiative.
It’s been constantly growing in size and value but lacks structure. We’ll review the information architecture and user flow on the page, break out some sections into dedicated subpages, create subpages for other web properties that we are translating (specifically the Staking Launchpad and the EF blog), and refresh the information on the page.
Want to get involved? Join the conversation in our #translate Discord channel.
The nice-to-haves
These epics are up next on our priority list. We’re not committing to shipping anything this quarter, but we plan to make progress on these and want to share these publicly so the community can give input and get involved!
🏫 Ethereum for educators
We’re narrowing in on how to best build resources for educators looking to teach about Ethereum. In Q2, we collected a lot of resources for educators - like university courses, case studies, and open access academic papers - and actively engaged with academics for their feedback, ideas, and input. This quarter we hope to pick up the work to design and build a page to offer these free resources to teachers and learners across the globe.
Want to get involved? Join the conversation on #6283 or in our #content Discord channel.
📖 Content strategy
Thanks to the incredible contributions from hundreds of community members, we’ve created a large swath of excellent educational resources on ethereum.org. However, we still have gaps in our content where we are not addressing some fundamental questions about how Ethereum works. Meanwhile great new content ideas constantly surface in our Discord and on GitHub but we don’t yet have a solid framework on how to prioritize these within our content roadmap.
Through SEO tools and manual content auditing, we’re aimig to identify such gaps and build an editorial calendar that helps prioritize content opportunities by their impact, allowing us to create more critical content faster.
Want to get involved? Join the conversation in our #content Discord channel.
🪜 Restructure documentation
With the help of a community of technical content contributors, our developer documentation resources have exploded to nearly 100 pages. These resources live within a site structure that was originally targeted at web3 dapp developers yet over time, we’ve received feedback that many resources are useful to a broad range of visitors - hobbyists, designers, node operators, end-users, economists, entrepreneurs, and more user types beyond pure “developers”.
This quarter we hope to rethink the overall information architecture of our documentation to best support a broader base of users and to ensure we surface key information that is often buried deep within technical topics.
Want to get involved? Join the conversation in our #content Discord channel.
💰 Wallet resources
Through our recent work on our new Find Wallet page (#6274), we surfaced opportunities to improve and expand the educational resources on the world of Ethereum wallets, which are critical onboarding products to all Ethereum users.
We’ll work to expand our content around wallets, such as explainers on self-custody and how keys work, resources on the different kinds of accounts (EOAs vs. contracts), and the respective wallet interfaces they can use (private-key wallet, smart contract wallet, and MPC wallets).
Want to get involved? Join the conversation in our #content Discord channel.
🎡 JSON-RPC playground
The JSON-RPC API is a crucial list of endpoints provided by all Ethereum clients yet is not widely or consistently documented. Several folks have been working valiantly to improve the state of affairs, building out new resources such as the specification and the interactive playground.
These resources are a great start, and we’d like to help push things forward. We’re hoping to work with @lightclient and other community members to improve the JSON-RPC playground, allowing developers to find, learn about, and test various endpoints to build products for end-users. We’re hoping these efforts will improve the lives of client teams, dapp and infrastructure developers, and end-users across the Ethereum ecosystem.
Want to get involved? Join the conversation in the #json-rpc-api channel of the Eth R&D Discord.
How does that sound?
We always appreciate feedback on our roadmap - if there's something you think we should work on, please let us know! We welcome ideas and PRs from anyone in the community.
Get involved: Learn more about contributing, hit us up on Twitter, or join the community discussions in our Discord.