-
Notifications
You must be signed in to change notification settings - Fork 4.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Revamp the Staking page #5647
Comments
+100 on this! As a staking participant, it was non-obvious to identify all the trade-off's between the various types of staking mechanisms on the website. It'd be great if the we can incorporate a way to clearly compare and contrast the trade-off's in the new page design, including but not limited to:
Would love to help with this 🏗 what's the best way for me to learn about the latest development status? This seems like a large overhaul, not sure where I can break off a piece and chew :) |
We've created a Figma prototype to get more detailed feedback on this. Please add your contribution using the comments in Figma Any other ideas or questions just get them here. 🙂 |
Thanks for the input @lingzhong! I think that's a great list of considerations to include 😍
Amazing! @nloureiro just posted a design protoype (see comment above). I encourage you to check that out & add your feedback. We also have a public Discord - feel free to join the discussion in the |
Is your feature request related to a problem? Please describe.
As mentioned in our Q1 roadmap (#5105), improving the UX of staking is a key goal of our team. Part of this effort should be to revamp the Staking page.
Two clear areas of improvement we've identified are to expand our resources for both 1) pooled staking & 2) solo staking to make both processes easier to understand & easier to accomplish for visitors.
Describe the solution you'd like
Content & design solutions are being actively developed so input is welcome here but the high-level improvements we're thinking is:
Describe alternatives you've considered
Many 😅 - feel free to comment with feedback or alternatives of your own. We always appreciate input!
Additional context
Some discussion & input around this can be found in #5633
The text was updated successfully, but these errors were encountered: