1# Documentation Contribution 2 3You are welcome to make contributions to OpenHarmony documentation, in any of the methods provided below. You can help us improve the existing documents or submit new, original content. 4 5Excellent contributors will be awarded and the contributions will be publicized in the developer community. 6 7- [Contribution Methods](#contribution-methods) 8 9## Content Copyright 10 11The content and images submitted by you must be original and must not infringe others' intellectual property rights. 12 13OpenHarmony has the right to modify the adopted content according to the community regulations and specifications. 14 15## License 16 17Creative Commons License version 4.0 18 19## Contribution Methods 20 21### Submitting Issues for Existing Documents 22 23Your feedback matters. Submit issues and leave as detailed information as possible, so we can better fix the issues and improve our documents. 24 251. On the Gitee page, click the **Issues** tab. On the displayed page, click **New issue**. Then enter the issue title and issue details. 262. Click **New** to submit the issue. The Docs team will confirm the issue. 27 28> **NOTE** 29> 30> **How can I provide a high-quality issue?** 31> 32> - Provide a clear description of the issue, including the missing, outdated, incorrect, or to-be-improved content. 33> - Explain the impact of this issue on users. 34> - Limit the scope of the given issue to a specific task. If multiple fields are involved, break the issue down into smaller ones. For example, "Documents need to be optimized" is a broad issue, whereas "XX development guide lacks introduction to step XXX" is specific and operable. 35> - Search the list of existing issues to see if any related or similar issues have been submitted. 36> - If an issue is associated with another issue or a pull request (PR), you can use its full URL or the combination of the number sign (#) and PR number to reference it. 37 38### Editing Existing Documents 39 40You can perform the following steps to modify or supplement a file: 41 421. In the upper right corner of the document page, click **Edit** to go to the source file page in the Gitee project. 432. On the page of the source file in .md format, modify or supplement the file. 443. After the modification, click **Preview** to confirm the modification result. 454. Enter your comments, supplementary information, and Signed-off-by information in the **Extended Information** text box, and click **Commit**. 46 47 Format of Signed-off-by information is as follows: 48 49 Signed-off-by: user.name <user.email> // Note that *user.name* and *user.email* must be the same as those used for DCO signing. 50 51 52 53The Docs team will review your edits and update the file accordingly. 54 55 56For more information, see [Contribution Process](contribution-process.md). 57 58### Contributing Documents to a Release 59 60To help developers efficiently use each release, OpenHarmony provides related documents (such as development guidelines, API reference, codelabs, release notes, API changelog, and FAQs) based on the requirements planned for the release. Some requirements involve new features and documents, and some require updates to the existing features and documents. 61 62You are welcome to contribute documents to the release. For details, see [Writing Documents for a Release](docs-release-process.md). 63 64### Sharing Experience 65 66You are welcome to share your experience and expertise with other developers to help them get started. For example, you can contribute tutorials and FAQs by using the following templates: 67 68- [Tutorial Template](template/tutorial-template.md). You can contribute tutorials in the `contribute/tutorial` folder. 69- [FAQ Template](template/faq-template.md). You can contribute FAQs in the `contribute/faqs` folder. 70 71More writing templates are available in the **contribute** folder in the **Docs** repository. 72
