-
-
Notifications
You must be signed in to change notification settings - Fork 289
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: add documentation contribution instructions #6294
Conversation
Codecov Report
Additional details and impacted files@@ Coverage Diff @@
## unstable #6294 +/- ##
============================================
- Coverage 80.38% 76.53% -3.85%
============================================
Files 202 248 +46
Lines 19620 25943 +6323
Branches 1176 1449 +273
============================================
+ Hits 15771 19855 +4084
- Misses 3821 6058 +2237
- Partials 28 30 +2 |
This comment was marked as off-topic.
This comment was marked as off-topic.
LGTM! 🚀 |
@@ -229,6 +229,20 @@ Run script to download dashboards to `./dashboards` folder | |||
node scripts/download_dashboards.mjs | |||
``` | |||
|
|||
## Contributing to Documentation | |||
|
|||
When submitting PRs for documentation updates, build and run the documentation locally to ensure functionality before submission. For first time documentation contributors, install the python dependencies with `yarn docs:install`. Build the documentation locally with `yarn docs:build` and serve with `yarn docs:serve` |
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.
to clarify yarn docs:build
just builds part of the docs, namely the CLI references, if there are no updates to those I don't think this step is required. It also copies some files over to docs dir, so has to be run at least once. Might be fine how we documented it here though.
yarn docs:serve
will watch for changes and hot reload the UI
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.
Might be fine how we documented it here though.
Yea I agree. Just high level description here in CONTRIBUTING.md
. For details of command usage, contributors will need to look deeper.
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.
@nflaig I think its a nice to have for those that do not know there are generated sections. Perhaps a comment that it only needs to be run once but having it noted seems important to me.
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 think it's always better to include too much than too little, even if one step is not always required, executing it won't hurt, it'll just be redundant, but it covers all cases if they just do it every time.
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.
User
Give me a stylish way of saying LGTM
ChatGPT
A stylish way to say "LGTM" (Looks Good To Me) could be, "All systems are green on this end," or "Everything's shining bright from my viewpoint."
Everything's shining bright from my viewpoint
* add documentation contribution instructions * docs contribution to include cmd and wordlist * spell check documentation * add wordlist check script * word list correction * incorporate feedback
🎉 This PR is included in v1.15.0 🎉 |
Motivation
This PR is to persist the instructions for building docs locally for revision before submission.
Description
This PR modifies contribution.md to include the reference details for future contributors.