One of the most important ways that Hiro can build out the Stacks developer community and ecosystem is by having feedback and contributions from the developer community. Having this feedback loop and insight into what works and what does not work is helpful in prioritizing what content should be written, what content needs to be updated, and what content may be missing.
This guide describes how to contribute to Hiro's documentation and content so feedback is received. Hiro can then incorporate these comments to improve the overall developer documentation experience.
Contributing to Hiro's documentation
Hiro welcomes all contributions to Hiro documentation. These contributions come in two forms: issues and pull requests.
If the content is obsolete, technically inaccurate, or unclear, please create a GitHub Issue. This is a great way to give specific feedback and ensure the technical content is up-to-date and technically accurate.
To suggest more comprehensive changes or updates to the content, make documentation changes and then submit a pull request.
For minor changes like typos, click "Edit This Page" at the bottom of each page. This leads to the source file on GitHub, where a pull request can be submitted.
Edit the docs locally for larger edits or new documents, following the steps described below.
Editing docs locally
To submit a pull request to update the docs, fork the Hiro Docs repository and clone it. Currently, all Hiro docs are located in
Create a branch and switch to that branch:
git checkout -b <branch-name>
Add or modify the GitHub Markdown files in the directories.
When the suggested changes are complete, commit them with a message with a brief summary message:
git commit -m "commit message"
Push the branch up:
git push origin <branch-name>
When the changes are final, create a pull request from the working branch by following GitHub's guide.
Titles and descriptions
For pull requests, please keep the following in mind:
Pull request titles should be descriptive enough for reviewers to understand what is being changed. Some ways of doing this are better than others.
Every pull request should have a description that explains why the change is being made. The description adds context that is critical for reviewers when giving feedback.
For a quick GitHub refresher, please refer to the GitHub Get Started Guide.
For more tips, see GitHub's blog entry on how to write the perfect pull request.