Jenkins has lots of documentation, and we appreciate any contributions to it: new docs, design and styling, copy-editing, reviews, etc.
We coordinate and discuss documentation efforts in the Documentation Special Interest Group. You can reach out to us in the mailing list or on link:[https://gitter.im/jenkinsci/docs[Gitter, and you can also join our link:/sigs/docs/#meetings[regular meetings. See the contacts on the right sidebar.
There are many documentation sources in Jenkins. This website and the plugins site are the most notable ones, but we also have docs in other places (GitHub repositories, various sites like javadoc.jenkins.io or Jenkins Wiki which is currently being deprecated). For the most of the repositories we try to follow the documentation-as-code approach.
|Documentation type||Repository||Comments and links|
Plugin repositories or Jenkins Wiki
See Developer documentation for more information about plugin docs and the ongoing migration from Wiki to GitHub.
If you are a newcomer, documentation is a great place to contribute. A lot of small patches can be done from the GitHub’s web interface even without forking repositories and cloning them locally. You can open any GitHub Markdown or Asciidoc page in any Jenkins repo, click Edit on the page, modify and preview changes in the web interface, and then propose a change.
Currently we are working on migrating the documentation from Jenkins Wiki to GitHub and jenkins.io. See this blog post for more information about the reasons why we do this migration. This migration involves modification of hundreds of pages and repositories, and we invite everyone to contribute.