whentimeslows/website
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Additional updates to the Staging sections of the README.

Browse Source
This commit is contained in:
steveperry-53
2016-10-18 16:40:10 -07:00
parent 65f244993c
commit ebbe5bbcc1
1 changed files with 0 additions and 11 deletions
Download Patch File Download Diff File Expand all files Collapse all files
README.md
-11
View File
@@ -11,14 +11,6 @@ For more information about contributing to the Kubernetes documentation, see:
* [Staging Your Documentation Changes](http://kubernetes.io/docs/contribute/stage-documentation-changes/)
* [Using Page Templates](http://kubernetes.io/docs/contribute/page-templates/)
## Release Branch Staging
The Kubernetes site maintains staged versions at a subdomain provided by Netlify. Every PR for the Kubernetes site, either against the master branch or the upcoming release branch, is staged automatically.
The staging site for the next upcoming Kubernetes release is here: [http://kubernetes-io-vnext-staging.netlify.com/](http://kubernetes-io-vnext-staging.netlify.com/)
The staging site reflects the current state of what's been merged in the release branch, or in other words, what the docs will look like for the next upcoming release. It's automatically updated as new PRs get merged.
## Automatic Staging for Pull Requests
When you create a pull request (either against master or the upcoming release), your changes are staged in a custom subdomain on Netlify so that you can see your changes in rendered form before the PR is merged. You can use this to verify that everything is correct before the PR gets merged. To view your changes:
@@ -36,9 +28,6 @@ The `release-1.x` branch stores changes for **upcoming releases of Kubernetes**.
The staging site for the next upcoming Kubernetes release is here: [http://kubernetes-io-vnext-staging.netlify.com/](http://kubernetes-io-vnext-staging.netlify.com/). The staging site reflects the current state of what's been merged in the release branch, or in other words, what the docs will look like for the next upcoming release. It's automatically updated as new PRs get merged.
When you create a pull request, either against the master branch or the upcoming release branch, your changes are staged automatically.
The Kubernetes site maintains staged versions at a subdomain provided by Netlify.
## Staging the site locally (using Docker)
Don't like installing stuff? Download and run a local staging server with a single `docker run` command.