Found a mistake in our documentation? Always wanted to add a step in one of our procedures that could save many others a lot of time? Then you're at the right place! All contributions made to the Markdown files in the docs directory are reviewed, and if deemed valuable be added to our official documentation on SAP Help Portal. The easiest way is to start there, and choose Edit to find the right Markdown file to contribute to.
Contributions to the scenario documentation must still be done by providing feedback on the SAP Help Portal.
For contributions, it's required that you've a GitHub account. For more information, see Signing up for a new GitHub account in the GitHub documentation.
We recommend using the SAP Business Application Studio documentation on SAP Help Portal as a starting point for contributions:
- Open the SAP Business Application Studio Documentation.
- You can either:
- Choose Edit to suggest a change for the current page you see in the Help Portal viewer, or
- Choose Feedback to open a GitHub issue in this repository.
If you only make a small contribution, that's the quickest way to propose a change. For larger contributions, we recommend forking this repository to work locally. The filenames in the docs directory are created based on the title of the page on SAP Help Portal.
More information: Contribution Guidelines
In the context of content contribution, you need to sign a Developer's Certificate of Origin (DCO). During the submission process for your first pull request, the CLA Assistant helps you to get it done. Once signed, you don't need to sign it again for contributions to the same repository.
More information: The Contributor License Agreement Process
See our LICENSE for copyright and license information.