Relocate "How to Contribute" section to improve content structure #301
Conversation
This file contains 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
andoriyaprashant
requested review from
divya-mohan0209,
ksatchit and
k8s-dev
as code owners
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
Signed-off-by: andoriyaprashant <[email protected]>
✅ Deploy Preview for docs-litmuschaos ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
andoriyaprashant
force-pushed
the
contribute
branch
from
f81b41b
to
3425ced
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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 this PR does / why we need it:
Moved the "How to Contribute" section from the "What is Litmus" page to the "Community" page under the "Contribute" section. This aligns the documentation with CNCF Tech Doc recommendations by separating introductory content from advanced contributor information.
Which issue this PR fixes (optional, in
fixes #<issue number>(, fixes #<issue_number>, ...)format, will close that issue when PR gets merged): fixes #299 #294Special notes for your reviewer:
Checklist: