reorg nav, link refs to usage #1449
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Contributor
Vercel Previews Deployed
|
Contributor
Broken Link CheckerNo broken links found! 🎉 |
| ] | ||
| }, | ||
| { | ||
| "title": "Install providers", |
Contributor
There was a problem hiding this comment.
What do you think about "Use providers", "Configure providers", etc rather than install? To me, "install" feels like the CLI side of things.
Contributor
Author
There was a problem hiding this comment.
To me, installing most closely matches the action, but we can try "Configure providers". I was trying to avoid potential confusion in terms of developing providers. IMO, "Use" is almost always way to generic, but it fits in this case better than most.
rkoron007
approved these changes
Dec 9, 2025
Contributor
rkoron007
left a comment
rkoron007
left a comment
There was a problem hiding this comment.
Approving to unblock, but left a few suggestions in our slack thread!
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR updates navigation labels for the language docs. We are going to return to a labeling principle based on language construct, instead of JTBD. The second-order principle is to label groups of topics based on workflows. Our North Star principle for creating topics based on information type (Diataxis) is unchanged.
In addition to updating labels and linking to relevant reference pages in the navigation groups, I made sure to cross-link reference pages to usage pages so that people who land on a reference topic from search have an escape hatch to a how-to topic.