-
Notifications
You must be signed in to change notification settings - Fork 146
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
Change the "Network" section title #495
Comments
I think to many devs, the title "Products" would bring to mind that these are things that must be purchased. |
What about "Network Infrastructure" or just "Infrastructure"? |
Infrastructure has been proposed in the past, I can't remember why we moved away from it, but I do think "Network Infrastructure" would just be too long for the top nav. |
I think the distinction made was that things like the anchor/disbursement platform aren't really the infrastructure that operates the network, but are more like services/applications that operate on the network (if I'm remembering correctly). |
Preliminary findings from @alexisdowney1 have shown that there is not a spike in people searching for RPC, Horizon, or other items listed in the Network section since the docs merge. So no data-driven motivation to change the name at this time. |
We discussed at length during the call today and agreed on Network is too fuzzy a term for this. Based on engineering's continued feedback, we agreed on using Data or Data Service for this bucket, and move core validator out from this tab |
Fixing with v2 of docs merge. |
We've had some comments that the Network title isn't the obvious location for the data availability sections (like RPC and Horizon). The section title "Products" has been suggested instead.
Other suggestions and discussion welcome.
The text was updated successfully, but these errors were encountered: