Skip to Content
Technical Articles
Author's profile photo Oliver Mueller

Open Documentation Initiative for SAPUI5 and SAP Fiori Elements – Help Us to Help You!

Almost exactly 3 years ago, we went open source with the OpenUI5 developer documentation: OpenUI5 Developer Guide: Have Your Say!

Next up: SAPUI5!

What is the Open Documentation Initiative?

In a nutshell, the Open Documentation Initiative is SAP’s way of opening up its documentation sets for outside contributions. Here’s how DJ Adams puts it:

Looking at some documentation and you’re not sure that it’s quite hitting the mark? Send us some feedback and start a conversation in the form of an issue.

Found something that doesn’t look quite right, and you know how it could be addressed? Contribute a small piece of content, and start a conversation with us in the form of a pull request.

We’re bringing the content to you, in the form of Markdown resources in repositories on GitHub, where we can all benefit from standard issue and pull request workflow mechanisms that are used in countless collaborative processes.

But let’s hear it from the masterminds themselves – DJ Adams and Jens Haley:

As you can see: It’s never been easier to directly influence the content designed to help you.

Next Pilot: SAPUI5 and SAP Fiori Elements

As I mentioned in the beginning: We’ve been offering this sort of collaboration for the OpenUI5 documentation in the OpenUI5 Demo Kit for 3 years now. Every documentation page has an Edit on GitHub link that takes you directly to the corresponding Markdown file on GitHub. All you need to contribute is a user on – and off you go! This has led to some valuable contributions from the community.

However, the SAPUI5 Demo Kit, including the developer documentation for SAP Fiori elements, hasn’t offered this possibility so far. The Open Documentation Initiative is a great way to change this. So as of SAPUI5 1.107, we are on board as well!

So how does it work?

Easy: If you see something in the developer documentation for SAPUI5 or SAP Fiori elements in the SAPUI5 Demo Kit that you think could be improved, just choose the Edit on GitHub link at the top of the page:


Link to GitHub in the SAPUI5 Demo Kit

This will take you to the Markdown version of this documentation page in the following repository: Here, you can make changes under your user, fork the repository, and create a pull request. For more general feedback, you can also create an issue. We will take over and get back to you.

And that’s it!

After we have implemented your contribution, the corresponding changes will become part of the official SAPUI5 (and OpenUI5 if included) documentation with the next possible release. Any new UI5 release also syncs two GitHub repos (for OpenUI and SAPUI5), so after every release, everything should have the same state.

What’s in it for you?

You can directly influence the content we offer you and other users. If you have a good idea on how to improve our documentation, this is your direct line to us. Sure, we’ve always offered options to provide anonymous feedback, but without the possibility to interact with the contributor, it’s not always easy to transform this into genuine improvements for the documentation.

The new GitHub repository makes this much easier. OpenUI5 has a great community, and a great number of improvements to the framework were suggested by the community. Let’s carry this spirit over to!

More Information

Other SAP Products Participating in the Open Documentation Initiative

Assigned Tags

      You must be Logged on to comment or reply to a post.
      Author's profile photo Volker Buzek
      Volker Buzek

      and user-/PR-initiated and merged changes in SAPUI5 docs populate into the OpenUI5 docs and vice versa, right? Right?!? 🤞

      If hopefully so, might be worth mentioning 😀

      Author's profile photo Oliver Mueller
      Oliver Mueller
      Blog Post Author

      Hi Volker, thanks for your comment.

      Yep, I can confirm your assumption!

      Some background if you're interested: When we process contributions from either the SAPUI5 or OpenUI5 GitHub repo, we need to take a little detour via our central CMS, which is still the source of everything. As soon as we've implemented changes there, which usually happens at the same time as merging the PR or closing an issue, the different outputs will be populated automatically, i.e. the different Demo Kits (OpenUI5 Nightly, OpenUI5, SAPUI5) and the respective "other" repo. The relevant changes will be visible everywhere with the next UI5 version that's released after our internal documentation close for that version. In the OpenUI5 Nightly, you should usually see the changes on the day after the merge.