To the Source Code, Translations, and Documentation
We would love you to contribute to our source code and documentation, and help us to translate Oro products into multiple languages. The following guidelines and recommendations enable the community to synchronize actions and provide a blueprint for seamless and non-intrusive collaboration.
Version control is a way to track all the changes made to the product. This topic tells you about the code version system used and describes the way to communicate enough context for every committed code change to fellow developers.
Code style is a set of conventions about how to write the source code. The following code styles are used in all Oro projects.
This article describes best practices in setting up a development environment. It up to you whether to follow the listed recommendation, however take a note that they can greatly facilitate the development process.
Oro applications support localization and internationalization for multiple languages and locales. In this topic you will find general instructions on how to join the Oro translation team and submit you translations.
The documentation is an important part of the product that greatly improve the user experience regarding how to configure and use the product. The information in this topic help you understand the documentation structure, useful rst directives, and a simple workflow that helps quickly publish a new topic.
Signing a Contributor License Agreement
Although signing the Contributor License Agreement is a prerequisite for accepting your pull request, you only need to do it once. So, if you’ve done this for any of our open source projects, you’re good to go with all of them. If you are submitting a pull request for the first time, our friendly orocla robot will automatically add a reminder to your pull request.
Looking to capitalize on the recent trend in digital commerce? Find out more about here, their benefits, and real-life examples.