We welcome contributions from our community as well as from Adobe employees from outside the documentation teams.
This repository includes automated pre-commit hooks that optimize images before committing. All contributors should enable these hooks to ensure consistent image optimization and reduced repository size.
After cloning the repository, run:
.githooks/setup-hooks.sh- Automatically detect staged image files (PNG, JPG, JPEG, GIF, SVG)
- Run
image_optimto compress and optimize images - Re-stage optimized images automatically
- Ensure all committed images are properly optimized
- Reduced repository size
- Faster page loads for documentation
- Consistent image quality across all contributors
- No manual optimization required
For detailed setup instructions, troubleshooting, and configuration, see .githooks/README.md.
This project has adopted the Adobe Open Source Code of Conduct or the .NET Foundation Code of Conduct. For more information, see the Contributing article.
See the Adobe Docs Contributor Guide.
How you contribute depends on who you are and the sort of changes you'd like to contribute:
If you are contributing minor updates, visit the article and click the feedback area that appears at the bottom of the article, click Detailed feedback options, and then click Suggest an edit to go to the markdown source file on GitHub. Use the GitHub UI to make your updates. See the general Adobe Docs contributor guide for more information.
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 a new article or submit major changes, please use the Issues tab in the Git repository to submit an issue to start a conversation with the documentation team. Once you have agreed to a plan, you will need to work with an employee to help bring that new content in through a combination of work in the public and private repositories.
If you are a technical writer, program manager, or developer from the product team for an Adobe Experience Cloud solution and it is your job to contribute to or author technical articles, you should 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: