This project has adopted the Adobe Open Source Code of Conduct or the .NET Foundation Code of Conduct. See the Contributing article.
If you are contributing minor updates, open the article and click the Edit link, which takes you to the GitHub source for the article. Use the GitHub UI to make your updates. See the general Adobe Docs contributor guide.
Minor corrections or clarifications you submit for documentation and code examples in this repo are covered by the Adobe terms of use.
If you are part of the Adobe community and you want to create an article or submit major changes, submit an issue on the Issues tab to start a conversation with the documentation team. Once you've agreed to a plan, work with an employee to build and place the content.
If you are a technical writer, program manager, or developer from an Adobe product team, and it is your job to contribute to or author technical articles, use the private repository at https://git.corp.adobe.com/AdobeDocs.
Community contributors can use the GitHub UI for basic editing or fork the repo to make major contributions.
See the Adobe Docs Contributor Guide for details.
All the articles in this repository use GitHub flavored markdown. If you are not familiar with markdown, see:
In the public repository, automated labels are assigned to pull requests to help us manage the pull request workflow and to help inform you on the status of your pull request:
- Change sent to author: The author has been notified of the pending pull request.
- ready-to-merge: Ready for review by the pull request review team.