Contributing to Docs

Timo Abele rmi2hi Ralf D. Müller

5 minutes to read

The easiest way to contribute to this project is to contribute to the documentation.

Here is a quick step-by-step guide on how to fix something on a documentation page.


Go to page you want to edit or fix

You already found this tutorial, so you already know how to go to the page you want to edit or fix. All documentation can be found at . The source code of each page is available at in the /src/docs/ folder. But there is an easier way to find the exact source.

The documentation pages all look something like this:

full docs page

In the upper right corner you can see the Improve this doc link:

improve this doc

This will take you directly to the source of the page, already in edit mode. If you are not logged in, GitHub will ask you to do so.

The Create an issue link will be helpful if you want to report a bug or request a feature for a page. It takes you directly to the issue tracker with a pre-filled issue.

For now, let’s click on the Improve this doc link.

Fork the Repository

If you click the link for the first time, you will be asked to fork the repository.

create fork

A fork is a copy of the repository. Maybe you are used to working on the main repository or a branch within the main repository. This is not possible in this case, because you don’t have write access, only read access.

The solution is to fork the repository. This way, you create a copy in your own space, and you will have write access to it.

create fork diag

Edit the Page

You will now be taken to the page you want to edit already in edit mode.


What you see is asciidoctor markup. Check out the {url-asciidoc-quick-reference}[AsciiDoc quick reference] for more information.

The blue box on top tells you what you already know: a copy has been created for you and you are editing it.

since you work on your own copy of the docs, you can’t break anything. You even don’t have write access to the main repository. So feel free to edit the page as you like.

Use the Preview button to see what your edits will look like. Since this is only a preview and GitHub doesn’t know about docToolchain, this preview will only show you if your AsciiDoc syntax is correct. Some other features like the TOC or include statements will not be available in the preview.


Do your edit and then

Commit the Changes

Below the editor, there is a small Propose Changes form.

propose changes

Enter a headline and a description of the changes you made and click Propose changes.

This will save your changes to your fork of the repository.

create fork diag
Git works with diffs - it only saves the changes you made, not a full copy of the new page. This is important to know if you want to understand the inner workings of Git.

After you’ve clicked the button, you will be taken to a page which shows you what you changed.

Comparing changes

This view lets you review your changes.

comparing changes

These diffs are not easy to read, but I promise that over time you get used to it.

Red lines are deletions, green lines are additions. As you can see in the screenshot, I added an empty space in line 17. Line 17 has been deleted (red line) and replaced with a new line (green line).

Line 1 looks mysterious, because it seems that it has been replaced with an identical copy. This is because the line ending changed but is not visible in the diff.

The grey box on top shows you

merge branches

It is quite likely that you still know what you did a minute ago, so let’s click on the Create pull request button.