Makes RR3 documentation headings and links more descriptive #5288
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
|
Seems sensible to me. Hopefully Google picks up on this! |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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 is sort of a weird pull-request, but it's sort of an experiment. Currently, when i google search for "react router 3 docs" i get
but neither the 'api' or 'docs' links there are actually correct.
My pet theory is that by aggressively adding the words 'react router 3' in choice locations google will know to point to this documentation more easily (fingers crossed). But in any case, it can't hurt even just from a descriptive point of view (i have a separate commit which would also change the readme in master to point to "react router 3.x docs" instead of "3.x docs" but this one should probably get merged first if it gets merged at all.
thoughts?