Kubernetes website and documentation repo:
Go to file
lovejoy 9034e1b2b4 fix-direct-link (#9179) 2018-06-21 00:35:09 -07:00
.github
archetypes
content fix-direct-link (#9179) 2018-06-21 00:35:09 -07:00
data
layouts Add links to forum (#8945) 2018-06-11 17:26:27 -07:00
src/sass [css] Remove bullet styling from "tab-nav" components. (#9020) 2018-06-15 13:42:28 -07:00
staging-container
static Fix k8s logo in Blog (#9113) 2018-06-20 16:00:06 -07:00
test Remove unused yaml files. (#9135) 2018-06-19 04:53:30 -07:00
update-imported-docs
.gitignore
.travis.yml
CONTRIBUTING.md
LICENSE
Makefile
OWNERS Add two new reviewers (#9090) 2018-06-19 08:24:34 -07:00
OWNERS_ALIASES Overall cleanup for kubeadm setup guide. (#8981) 2018-06-13 11:23:29 -07:00
README.md
SECURITY_CONTACTS
config.toml
google2b743c61aa37ebbe.html
google3a25d10f6aadcdc0.html
googlea92cf511a27d4f6b.html
googlead862a0628bec321.html
googlebea0044df4aa3179.html
googlece48a67808b497a5.html
labels.yaml
netlify.toml Set noindex header for builds except for master (+1 squashed commit) (#9150) 2018-06-19 15:22:32 -07:00
netlify_noindex_headers.txt
skip_title_check.txt
skip_toc_check.txt
verify-docs-format.sh

README.md

Instructions for Contributing to the Kubernetes Documentation

Welcome! We are very pleased you want to contribute to the Kubernetes documentation.

You can click the Fork button in the upper-right area of the screen to create a copy of this repository in your GitHub account called a fork. Make any changes you want in your fork, and when you are ready to send those changes to us, go to your fork and create a new pull request to let us know about it.

Once your pull request is created, a Kubernetes reviewer will take responsibility for providing clear, actionable feedback. As the owner of the pull request, it is your responsibility to modify your pull request to address the feedback that has been provided to you by the Kubernetes reviewer. Also note that you may end up having more than one Kubernetes reviewer provide you feedback or you may end up getting feedback from a Kubernetes reviewer that is different than the one originally assigned to provide you feedback. Furthermore, in some cases, one of your reviewers might ask for a technical review from a Kubernetes tech reviewer when needed. Reviewers will do their best to provide feedback in a timely fashion but response time can vary based on circumstances.

For more information about contributing to the Kubernetes documentation, see:

Thank you!

Kubernetes thrives on community participation, and we really appreciate your contributions to our site and our documentation!