You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
An issue to discuss a possible redesign of the developer's center landing page. We'll start gathering requirements in this issue.
Jeff's comment in Slack:
The Landing Page
The goal is to keep this as beautiful as possible and highlight links, boxes, shortcuts, and provide shortcuts and direct access to the most commonly used docs.
This is done by combining the current landing page which is a great start and References page which is styled similarly.
We can add another section for guides and/or education or other important link categories in the future to compliment the content already there.
The text was updated successfully, but these errors were encountered:
Here there is the new landing proposed and some navigation changes that will be published along with dragon-01 docs. Feedback is welcomed and appreciated!
Landing page
The landing page gives more relevance to guides and getting started sections. Once you click a programming language, you are redirected to the "Setting up your workstation section". The developer center stores the user's preference and renders the code examples for the language selected first.
After reaching RC, the call to action will be changed to something like "Add blockchain tech to your project". In a subsequent release, featured card guides will come with representative icons.
Improved layout
We are giving more importance to the navigation bar powered by Algolia. The left navbar is now fully rendered and keeps fixed at the top when the developer scrolls, being visible all the time.
I think these are great suggestions and will make it easier for people to quickly get to the content they need while also understanding the overall content available at a first glance.
An issue to discuss a possible redesign of the developer's center landing page. We'll start gathering requirements in this issue.
Jeff's comment in Slack:
The text was updated successfully, but these errors were encountered: