How to Contribute
Identify area for contribution
There are several ways to identify the area where you can contribute to TON Docs:
- The easiest is to reach out to one of the Docs maintainers saying, "I'd like to contribute to TON Docs." They’ll work with you to find an area where you can contribute.
- If you have a specific contribution in mind but are unsure about it, confirm whether the contribution is appropriate by contacting one of the Docs maintainers directly.
- Get familiar with the most frequently asked questions in the TON Developers chats.
- Please read over the issues in the GitHub repository.
- If you need to add or edit something in TON Docs, create a pull request
- The documentation team will review the pull request or reach out as needed.
- Repository: https://github.com/ton-community/ton-docs
Online one-click contribution setup
You can use Gitpod (a free, online, VS code-like IDE) for contributing. It will launch a workspace with a single click and will automatically:
- Most important: look around. Match the overall style of the project. This includes formatting, naming files, naming objects in code, naming things in documentation, and so on.
- For documentation: When editing documentation, do not wrap lines at 80 characters; instead, configure your editor to soft-wrap.
Don't worry too much about styles in general; the maintainers will help you fix them as they review your code.
So you have decided to contribute code back to upstream by opening a pull request. You've put in a lot of effort, and we appreciate it. We will do our best to work with you and get the pull request reviewed.
When submitting a pull request, please ensure the following:
- Keep your pull request small. Smaller pull requests (~300 lines of diff) are easier to review and more likely to get merged. Make sure the pull request does only one thing, otherwise please split it.
- Use descriptive titles. It is recommended to follow the commit message style.
- Test your changes. Describe your test plan in your pull request description.
All pull requests should be opened against the
What Happens Next?
The TON Docs team will be monitoring pull requests. Please help us by following the guidelines above to keep the pull requests consistent.