Go to file
Masaya Aoyama (@amsy810) bd78a98ee2 add date blog metadata for indexing (#8830)
Issues:
https://github.com/kubernetes/website/issues/8823
and more article has same problem, I fix all.
2018-06-04 14:27:55 -07:00
.github Update PR template for 1.11 (#8057) 2018-04-11 12:01:55 -07:00
archetypes Convert site to Hugo (#8316) 2018-05-05 09:00:51 -07:00
content add date blog metadata for indexing (#8830) 2018-06-04 14:27:55 -07:00
data Remove data/glossary (#8321) 2018-05-17 14:41:50 -07:00
layouts Fix some issues with ToC (#8797) 2018-06-04 08:35:54 -07:00
src/sass Convert site to Hugo (#8316) 2018-05-05 09:00:51 -07:00
staging-container Bump alpine version of the staging container to use newer ruby version (#8178) 2018-04-26 10:49:02 -07:00
static Typo fix: propogating -> propagating (#8832) 2018-06-01 20:36:59 -07:00
test fix some unsatisfied. (#8746) 2018-06-04 14:24:54 -07:00
update-imported-docs add generated docs for tools and components (#7845) (#7866) 2018-03-26 19:59:02 -07:00
.gitignore Update .gitignore to ignore vscode stuffs (#8510) 2018-05-12 07:53:25 -07:00
.travis.yml Restore gate jobs (#8388) 2018-05-18 11:14:51 -07:00
CONTRIBUTING.md delete redundant space 2017-10-19 17:06:33 +08:00
LICENSE fix a series punctuation errors 2016-12-22 11:24:05 +08:00
Makefile Convert site to Hugo (#8316) 2018-05-05 09:00:51 -07:00
OWNERS Add myself to approvers (#8745) 2018-05-29 20:58:55 -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.toml update versions (#8662) 2018-05-22 23:56:32 -07:00
google2b743c61aa37ebbe.html Get access to search console. (#3901) 2017-05-25 14:21:16 -07:00
google3a25d10f6aadcdc0.html Add a google verfication for kubernetes.io (#4294) 2017-07-05 21:14:13 -07:00
googlea92cf511a27d4f6b.html add site verification file 2017-04-27 14:17:09 -07:00
googlead862a0628bec321.html temporary access to webmaster tools 2017-01-04 20:32:41 -08:00
googlebea0044df4aa3179.html Move Google domain verification to a file 2017-07-05 13:03:33 -07:00
googlece48a67808b497a5.html Adds Answerdash, Analytics, feed.xml, LICENSE, robots.txt, and Google Site Verification files 2016-03-04 13:50:51 -08:00
labels.yaml Issue #124: Automatically create labels. 2016-08-04 22:57:44 -07:00
netlify.toml Update to Hugo 0.40.3 (#8436) 2018-05-10 11:01:53 -07:00
netlify_noindex_headers.txt fix noindex for vnext-staging (#4640) 2017-08-04 16:35:21 -07:00
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 WIP: Cleanup /docs/contribute/ migration (#3278) 2017-04-10 13:24:14 -07:00

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!