-
Notifications
You must be signed in to change notification settings - Fork 75
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
docs: New Supported networks page #610
Conversation
Branch preview✅ Deployed successfully in branch deployment: |
Overall readability score: 31.94 (🔴 -6.82)
View detailed metrics🟢 - Shows an increase in readability
Averages:
View metric targets
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@louis-md can you please update all the "Supported Network" links (from the Features section and the API section)? They give a 404 right now.
Can you also please pull in the latest changes from main
, so that we can run the Vale workflow as well?
…supported-networks
@tanay1337 I just fixed some broken links, however the two that you linked (from link checker) will still error as the link checker cannot handle links with a query string in the relative path (if you try the link manually it works though). |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
- The links to the page (from 4337, API, etc.) don't have the filter applied. As an example, see this link.
- The lazy loading does not work properly - it will unveil three pages and then stop. There's no way to view the whole list.
Unify all "Supported networks" pages across the site into a better, discoverable design.