hacktoberfest: migrate docs to github

[kaltepeter]

Following this blog post: https://www.jenkins.io/blog/2019/10/21/plugin-docs-on-github/ I would like to migrate documentation to GitHub. Fixes: jenkins-infra/jenkins.io#3789

[MarkEWaite]

Would prefer to have no wiki links inside the documentation if possible. In this case, the links can all be provided by the plugins site.

Thanks for the pull request!

Definitely worthy of the hacktoberfest-accepted label. Thanks

[MarkEWaite]

Would prefer that we refer to the plugins site rather than the wiki for references to other plugins.

Suggested change

	- Select the Docker image to run the build as a **Docker image** to be pulled. This is comparable to the [docker-plugin](https://wiki.jenkins.io/display/JENKINS/Docker+Plugin) approach to offer docker agents within Jenkins, but without any prerequisites on the Docker image nor need for Administrator privileges to configure the adequate agent template.
	- Select the Docker image to run the build as a **Docker image** to be pulled. This is comparable to the [docker-plugin](https://plugins.jenkins.io/docker-plugin/) approach to offer docker agents within Jenkins, but without any prerequisites on the Docker image nor need for Administrator privileges to configure the adequate agent template.

[kaltepeter]

ah, i will fix.

[MarkEWaite]

Prefer to link to the plugins site rather than the wiki.

Suggested change

	CloudBees Docker Custom Build Environment let you use arbitrary docker image to host the build. You can use such an image you build on your own (or using [CloudBees Docker Build and Publish](https://wiki.jenkins.io/display/JENKINS/Docker+build+publish+Plugin) plugin) to define the set of prerequisites for your project and share with the development team, as well as reuse for your CI job. In
	CloudBees Docker Custom Build Environment let you use arbitrary docker image to host the build. You can use such an image you build on your own (or using [CloudBees Docker Build and Publish](https://plugins.jenkins.io/docker-build-publish/) plugin) to define the set of prerequisites for your project and share with the development team, as well as reuse for your CI job. In

[MarkEWaite]

Prefer to refer to the plugins site.

Suggested change

	CloudBees Docker Custom Build Environment integrates with [Docker-commons](https://wiki.jenkins.io/display/JENKINS/Docker+Commons+Plugin) plugin so you can define the docker cli executable to be used to interact with Docker daemon, as well as select TLS credentials to be used to access a secured infrastructure (which is highly recommended)
	CloudBees Docker Custom Build Environment integrates with [Docker-commons](https://plugins.jenkins.io/docker-commons/) plugin so you can define the docker cli executable to be used to interact with Docker daemon, as well as select TLS credentials to be used to access a secured infrastructure (which is highly recommended)

[MarkEWaite]

Prefer to use plugins site rather than wiki

Suggested change

	Compared to [docker plugin](https://wiki.jenkins.io/display/JENKINS/Docker+Plugin),
	Compared to [docker plugin](https://plugins.jenkins.io/docker-plugin/),

[kaltepeter]

@MarkEWaite I believe I have resolved the issues with the wiki links. Thanks for the feedback.

[MarkEWaite]

They look great to me. Thanks @kaltepeter !

@oleg-nenashev do you or someone else need to label this pull request as hacktoberfest-accepted?

[oleg-nenashev]

I added the label, have not reviewed the content yet

[oleg-nenashev]

Thanks a lot @kaltepeter ! Just a few minor change suggestions

The plugin renaming was not consistent, would be great to fix it during the migration. Also, there is one "slave" occurrence which could be cleaned up.