[MSITE-1010] Add documentation how site repository inheritance

[Bukama]

Proposed commit message:

[MSITE-1010] Add documentation how site repository inheritance

More information including an example how the site repository configuration is inherited,
when using a parent-pom.

closes #MSITE-1010

Following this checklist to help us incorporate your
contribution quickly and easily:

• Make sure there is a JIRA issue filed
  for the change (usually before you start working on it). Trivial changes like typos do not
  require a JIRA issue. Your pull request should address just this issue, without
  pulling in other changes.
• Each commit in the pull request should have a meaningful subject line and body.
• Format the pull request title like [MSITE-XXX] - Fixes bug in ApproximateQuantiles,
  where you replace MSITE-XXX with the appropriate JIRA issue. Best practice
  is to use the JIRA issue title in the pull request title and in the first line of the
  commit message.
• Write a pull request description that is detailed enough to understand what the pull request does, how, and why.
• Run mvn clean verify to make sure basic checks pass. A more thorough check will
  be performed on your pull request automatically.
• You have run the integration tests successfully (mvn -Prun-its clean verify).

If your pull request is about ~20 lines of code you don't need to sign an
Individual Contributor License Agreement if you are unsure
please ask on the developers list.

To make clear that you license your contribution under
the Apache License Version 2.0, January 2004
you have to acknowledge this by using the following check-box.

• I hereby declare this contribution to be licenced under the Apache License Version 2.0, January 2004

• In any other case, please file an Apache Individual Contributor License Agreement.

[Bukama]

Thanks for the review. Requested changes done.

[michael-o]

Yet another issue. The problem is not a repository, we do not even have that notion for sites. It is solely about site deployment vs local generation -- as laid out in the JIRA issue. We shouldn't try to introduce the term site repository. I'll review our code to make wording better.

[michael-o]

See: #195

[Bukama]

Yet another issue. The problem is not a repository, we do not even have that notion for sites. It is solely about site deployment vs local generation -- as laid out in the JIRA issue. We shouldn't try to introduce the term site repository. I'll review our code to make wording better.

I get your point and totally understand it. I updated the PR to avoid the term repository, changed the name of the page (and therefore the menu entry) to distribution management and also fixed some grammar mistakes/bad wording. Would you please have another look?

[michael-o]

Will review tomorrow again.

[michael-o]

@Bukama I have added a few improvements, please have a look.

[Bukama]

@Bukama I have added a few improvements, please have a look.

Thanks! I like them!