This page shows how to stage content that you want to contribute to the Kubernetes documentation.
Create a fork of the Kubernetes documentation repository as described in Creating a Documentation Pull Request.
GitHub provides staging of content in your master branch. Note that you might not want to merge your changes into your master branch. If that is the case, choose another option for staging your content.
In your GitHub account, in your fork, merge your changes into the master branch.
Change the name of your repository to <your-username>.github.io
, where
<your-username>
is the username of your GitHub account.
Delete the CNAME
file.
View your staged content at this URL:
https://<your-username>.github.io
When you create pull request against the Kubernetes documentation repository, you can see your changes on a staging server.
In your GitHub account, in your new branch, submit a pull request to the kubernetes/kubernetes.github.io repository. This opens a page that shows the status of your pull request.
Click Show all checks. Wait for the deploy/netlify check to complete. To the right of deploy/netlify, click Details. This opens a staging site where you see your changes.
You can use the k8sdocs Docker image to run a local staging server. If you’re interested, you can view the Dockerfile for this image.
Install Docker if you don’t already have it.
Clone your fork to your local development machine.
In the root of your cloned repository, enter this command to start a local web server:
docker run -ti --rm -v "$PWD":/k8sdocs -p 4000:4000 gcr.io/google-samples/k8sdocs:1.0
View your staged content at http://localhost:4000.
Verify that Ruby and RubyGems are installed:
gem --version
Install the GitHub Pages package, which includes Jekyll:
gem install github-pages
Clone your fork to your local development machine.
In the root of your cloned repository, enter this command to start a local web server:
jekyll serve
View your staged content at http://localhost:4000.