Move link to docs under it's own heading #5720
Merged
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.
What kind of change does this PR introduce? (check at least one)
Does this PR introduce a breaking change? (check one)
If yes, please describe the impact and migration path for existing applications:
The PR fulfills these requirements:
dev
branch for v2.x (or to a previous version branch), not themaster
branchfix #xxx[,#xxx]
, where "xxx" is the issue number)If adding a new feature, the PR's description includes:
Other information:
This PR moves the link to the documentation site under it's own heading in the repo's README.
The reason I submitted this PR is that I often have trouble finding the Vue docs.
When googling I click the Vue github repo link by default.
When landing on the github repo I am confused as to where the docs are.
Currently there is a link to the documentation site, however it is not very noticeable.
In order to make it more noticeable and easier for other developers to find, I have moved the link to the documentation under it's own heading.
This will make it easier for developers to quickly find a link to the Vue documentation from the github repo.