First off, thank you for considering contributing to nem2-docs.
nem2-docs is an open source project and we love to receive contributions from our community — you! There are many ways to contribute, from writing guides, improving the documentation, submitting errors and requests or writing new pieces of documentation which can be incorporated into nem2-docs itself.
Following these guidelines helps to communicate that you respect the time of the developers managing and developing this open source project. In return, they should reciprocate that respect in addressing your issue, assessing changes, and help you finalize your pull requests.
Please, don’t use the issue tracker for support questions.
Once you are accepted into the early access program, you can post support questions on Slack.
If you think you have found an error in nem2-docs, first make sure that you are testing against the latest version of nem2-docs - your issue may already have been fixed. If not, search our issues list on GitHub in case a similar issue has already been opened.
It is very helpful if you can prepare a reproduction of the error. It makes it easier to find the problem and to fix it.
Please, take into consideration the next template to report your issue:
Short and expressive sentence explaining what is wrong.
Url or screenshot
For faster issue detection, we would need where to find it.
Provide as much information as you can.
Open a new issue here.
If you find yourself wishing for contents that don’t exist in nem2-docs, you are probably not alone. Many of the documentation and guides that nem2-docs has today have been added because our users saw the need. Open an issue on our issues list on GitHub which describes the missing documentation or improvement you would like to see.
If the improvement is not related to documentation, but with a specific project, please check CONTRIBUTING.md in the project repository.
Contributing code and documentation changes¶
To expand and improve the nem2-docs, please find or open an issue about it first. Talk about what you would like to do. It may be that somebody is already working on it, or that there are particular issues that you should know about before implementing the change.
We enjoy working with contributors to get their pull-requests accepted.
Contributing License Notice¶
When you contribute code, you affirm that the contribution is your original work and that you license the work to the project under the project’s open source license.
Whether or not you state this explicitly, by submitting any copyrighted material via pull request, email, or other means you agree to license the material under the project’s open source license and warrant that you have the legal authority to do so.
Fork and clone the repository¶
Further instructions for specific projects are given below.
Submitting your changes¶
Once your changes and tests are ready to submit for review:
Test your changes
make livehtmland preview your changes.
Submit a pull request
Push your local changes to your forked copy of the repository and submit a pull request. In the pull request, choose a title which sums up the changes that you have made, and in the body provide more details about what your changes do. Also mention the number of the issue where discussion has taken place, eg “Closes #123”.
Then sit back and wait. There will probably be a discussion about the pull request and, if any changes are needed, we would love to work with you to get your pull request merged into nem2-docs.
See original CONTRIBUTING.md file.
NEM Catapult documentation for developers is not written from scratch. It is the sum of previous effort and documents written by the community and core developers, adapted for this new release. Thank you!
- NEM Technical Reference
- NEM NIS API Reference
- NEM Knowledge base
- Developer guide by rb2nem
- NEM Blog articles
We want to recognize the current contributors who provide content and improve the quality of this documentation.