-
-
Notifications
You must be signed in to change notification settings - Fork 273
Docs contributing and style guides #982
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
Docs contributing and style guides #982
Conversation
Add more info on how to contribute to JSON Schema documentation
Improve docs contribution guidance: Reference CONTRIBUTING-docs.md and style-guide.md
Add more info on how to contribute to JSON Schema documentation
…ebsite into web-feat-diataxis
These files document documentation contribution processes and style guidelines.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thank you for the great work @valeriahhdez, I have added a couple of comments.
|
||
### Example | ||
All code should be written and not included in the documentation as images. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Following Google's Sentence structure guide, I recommend rewording to "All code should be written and not included as images in the documentation.
|
||
The reviewers might ask for additional changes. When the reviewers approve your pull request, you can merge your changes into the main branch and your contribution to the project will be complete! | ||
|
||
We created this guide based on templates from [The Good Docs Project](https://www.thegooddocsproject.dev/). |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I believe that this sentence is the last line of the documentation guide, however, visually it appears to be part of the last section 'Create a pull request'.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Just closing the PR review
What kind of change does this PR introduce?
Documentation contribution workflows and expectations are documented in the file CONTRIBUTING-docs.md. For style guidelines, we adopted the Google developers style guide and documented instructions for using markdown tags. This is now documented in the file md-style-guide.md. We hope these documents help docs contributors get started and create consistent documentation.
Issue Number: #902
Screenshots/videos:
If relevant, did you update the documentation?
Summary
Does this PR introduce a breaking change? No