Kubernetes website and documentation repo:
Go to file
Rajakavitha1 358fa5f54b Update replicationcontroller.md (#7973)
Fixed the 404 listed in : https://github.com/kubernetes/website/issues/7924
2018-04-04 10:23:08 -07:00
.github 1.10 PR template (#7131) 2018-02-14 14:35:51 -08:00
_data Fix redirections for generated api references (#7890) 2018-03-29 06:28:04 -07:00
_includes Blog Migration: Continuation of WIP PR #7144 (#7247) 2018-04-03 14:19:43 -07:00
_layouts Blog Migration: Continuation of WIP PR #7144 (#7247) 2018-04-03 14:19:43 -07:00
_plugins Update README.md (#7913) 2018-04-02 16:36:15 -07:00
_sass Fix small css layout bug in mobile 2017-12-27 10:32:14 +00:00
blog Add missing 1.10 release blog post (#7956) 2018-04-03 15:57:07 -07:00
case-studies add Zalando to Case Study index page (#7897) 2018-03-29 07:17:04 -07:00
cn Merge 1.10 to master for release (#7861) 2018-03-26 18:33:11 -07:00
community Replace outdated instructions with the maintained ones. (#7472) 2018-02-23 10:20:45 -08:00
css Blog Migration: Continuation of WIP PR #7144 (#7247) 2018-04-03 14:19:43 -07:00
docs Update replicationcontroller.md (#7973) 2018-04-04 10:23:08 -07:00
images Blog Migration: Continuation of WIP PR #7144 (#7247) 2018-04-03 14:19:43 -07:00
js Blog Migration: Continuation of WIP PR #7144 (#7247) 2018-04-03 14:19:43 -07:00
partners Updates to Partner Page and Kubecon Banners 2017-11-24 11:35:15 +11:00
staging-container
test Merge 1.10 to master for release (#7861) 2018-03-26 18:33:11 -07:00
update-imported-docs add generated docs for tools and components (#7845) (#7866) 2018-03-26 19:59:02 -07:00
.gitignore
.travis.yml Change repo name to website. (#6076) 2017-10-27 10:47:03 -07:00
404.md
CONTRIBUTING.md delete redundant space 2017-10-19 17:06:33 +08:00
Gemfile Blog Migration: Continuation of WIP PR #7144 (#7247) 2018-04-03 14:19:43 -07:00
Gemfile.lock Blog Migration: Continuation of WIP PR #7144 (#7247) 2018-04-03 14:19:43 -07:00
LICENSE
Makefile Blog Migration: Continuation of WIP PR #7144 (#7247) 2018-04-03 14:19:43 -07:00
OWNERS Merge 1.10 to master for release (#7861) 2018-03-26 18:33:11 -07:00
OWNERS_ALIASES Remove crassirostris as owner and reviewer (#7974) 2018-04-04 10:22:10 -07:00
README.md Fixes issue #5620 (#5869) 2017-10-23 15:08:47 -07:00
_config.yml Blog Migration: Continuation of WIP PR #7144 (#7247) 2018-04-03 14:19:43 -07:00
_redirects Fix link to 1.9 api docs (#7920) 2018-04-02 15:17:15 -07:00
code-of-conduct.md Add code-of-conduct.md (#6723) 2017-12-28 13:09:52 -08:00
editdocs.md Roles sigdocs (#7133) 2018-02-17 00:10:38 -08:00
google2b743c61aa37ebbe.html
google3a25d10f6aadcdc0.html
googlea92cf511a27d4f6b.html
googlead862a0628bec321.html
googlebea0044df4aa3179.html
googlece48a67808b497a5.html
index.html Fix reference to ConfigMap on the kubernetes.io homepage 2018-01-03 23:18:27 -08:00
jquery-ui.html
labels.yaml
netlify.toml
netlify_noindex_headers.txt
robots.txt
skip_title_check.txt Newly generated kubeadm includes. (#7882) 2018-03-28 12:33:05 -07:00
skip_toc_check.txt Newly generated kubeadm includes. (#7882) 2018-03-28 12:33:05 -07:00
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!