同步操作将从 OpenHarmony/docs 强制同步,此操作会覆盖自 Fork 仓库以来所做的任何修改,且无法恢复!!!
确定后同步将在后台操作,完成时将刷新页面,请耐心等待。
You 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.
Excellent contributors will be awarded and the contributions will be publicized in the developer community.
The content and images submitted by you must be original and must not infringe others' intellectual property rights.
OpenHarmony has the right to modify the adopted content according to the community regulations and specifications.
Creative Commons License version 4.0
Your feedback matters. Submit issues and leave as detailed information as possible, so we can better fix the issues and improve our documents.
NOTE
How can I provide a high-quality issue?
- Provide a clear description of the issue, including the missing, outdated, incorrect, or to-be-improved content.
- Explain the impact of this issue on users.
- 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.
- Search the list of existing issues to see if any related or similar issues have been submitted.
- 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.
You can perform the following steps to modify or supplement a file:
In the upper right corner of the document page, click Edit to go to the source file page in the Gitee project.
On the page of the source file in .md format, modify or supplement the file.
After the modification, click Preview to confirm the modification result.
Enter your comments, supplementary information, and Signed-off-by information in the Extended Information text box, and click Commit.
Format of Signed-off-by information is as follows:
Signed-off-by: user.name <user.email> // Note that user.name and user.email must be the same as those used for DCO signing.
The Docs team will review your edits and update the file accordingly.
For more information, see Contribution Process.
To 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.
You are welcome to contribute documents to the release. For details, see Writing Documents for a Release.
You 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:
contribute/tutorial
folder.contribute/faqs
folder.More writing templates are available in the contribute folder in the Docs repository.
此处可能存在不合适展示的内容,页面不予展示。您可通过相关编辑功能自查并修改。
如您确认内容无涉及 不当用语 / 纯广告导流 / 暴力 / 低俗色情 / 侵权 / 盗版 / 虚假 / 无价值内容或违法国家有关法律法规的内容,可点击提交进行申诉,我们将尽快为您处理。