The AVS list expands too much on large screens.

Here's what I see when I follow the README.md and run this.

If there's an .env file required for this to run, please explain that in the README.md and provide an .env.example.

Stand back and look at the website and see if we can move graphs around to give it a better look.

Collecting possible ideas:

• Sidebar index thing for navigating sections to improve discoverability
• Loader while charts load (data is available, time is just related to graph computation)

When you go to AVS details operator tab and then try to go back to the previous page, it does not work. it just gets stuck there.

UI improvements:

• Add some descriptions of important charts/data.
• Overview of the dashboard/project
• Link to Eiger Layer docs and anything relevant.
• Links to re-stake on the EigenLayer dapp
• Add link to repo for contributors

These UI issues and enhancements needs to be implemented:

• Sidebar also scrolls-down along with the page content, hiding the sidebar title. Ideally sidebar should be fixed wrt to page content, keeping all links and title visible on screen without scrolling.

• Padding between tabs sections on smaller screens

• Fix mobile responsiveness for overflowing content

• Close ham menu on smaller screens on navigating to a different path

Data needed:

• Account/address re-staking with their staked amount

Ideas:

• Pie chart of total re-staked Eth with each category of re-staked ETH
• Stacked bar chart of re-staked Eth over time

Suggest better ones

context https://demerzelsolutions.slack.com/archives/C078V9NB69Z/p1721981499105489

leaderboard table with address and staked eth across strategies similar to degenscore.com

• Ensure the navigation is available with the keyboard
• Ensure links retain the default browser behavior and can be opened in a new tab
• Ensure the focus outline is consistent and visible for interactive controls

The chart brush disappears when clicking or mousedown on its track. That doesn't affect the chart itself, but it's confusing.

Add a toggle to mainnet, if someone tries to toggle then it should mainnet is not ready yet and reset the toggle

Data we need

• Total re-staked LSDs
  • rETH
  • stETH
  • native Eth

@yasmine9 I just noticed the staker leaderboard views currently don't take withdrawals into account (which is not wrong as it's mostly an interpretation point, since we do talk about literally deposits, but the main idea IMO is the current main stakers), and we also don't make the shares -> amount conversion to get the ETH value (only makes a difference for stETH). This does not make a big difference atm, but we should fix this soon.

What I propose is we do both of these changes. If you agree, it'd be good if you could take a look at those views, change them so they take withdrawals into account and do all calculations with the share amount as opposed to the balance. The way to manage withdrawals is getting the queued share withdrawals and joining it with the withdrawals table so you know which ones were actually executed. Then, with the share amount in hand in the FE, you can get the exchange rate in a similar way as done in #38, calling sharesToUnderlyingView. With this, you'll have the token amount, and in the case of static tokens such as rETH and cbETH, as it's already done, you'll need to also use their exchange rate to ETH.

Let me know how it goes! Feel free to contact me before updating the views to be sure.

Generate an image to show in the image preview when sharing link.
The image should have the current stake in each strategy.

Something like this ^ looks good

Data we need

• Total LSDs withdrawed
  • rETH
  • stETH
• withdrawed native Eth

using visx ParentSize component sometimes causes the UI to overflow, and when testing responsiveness the page doesn't immediately adopt to screen width on smaller screens, need to refresh the page to properly see the content of page.

To display error messages and hide loading indicators, we must wrap server calls with try/catch/finally everywhere. It's better to do this in a separate PR. What do you think?

Originally posted by @rubo in #118 (comment)

• Home
• AVS list
• AVS details (#170)
• Operator list
• Operator details
• LRT (done in #129)
• LST

voyager.online uses re-charts
https://recharts.org/en-US/

Suggest a better tool if you know

• Add a Next.js with Supabase.
• Add example of how to make a supabase table query.

I reckon this is a must have for launch, even internally.

At the least the API docs should be linked in the footer for now. Next step would be a clear communication of the value proposition of the data API inline in the site content somewhere.