Move README content to contribution section.

docs/contribute/create-pull-request.md

@@ -80,6 +80,12 @@ site where you can verify that your changes have rendered correctly.
 If needed, revise your pull request by committing changes to your
 new branch in your fork.
 
+The staging site for the 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.
+
 {% endcapture %}
 
 {% capture whatsnext %}

docs/contribute/stage-documentation-changes.md

@@ -33,16 +33,18 @@ the master branch.
 
 ### Staging a pull request
 
-When you create pull request against the Kubernetes documentation
-repository, you can see your changes on a staging server.
+When you create a pull request, either against the master or <vnext>
+branch, your changes are staged in a custom subdomain on Netlify so that
+you can see your changes in rendered form before the pull request is merged.
 
 1. 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.
 
-1. 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.
+1. Scroll down to the list of automated checks. 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
+can see your changes.
 
 ### Staging locally using Docker
 

docs/contribute/write-new-topic.md

@@ -34,7 +34,7 @@ is the best fit for your content:
     <td>A concept page explains some aspect of Kubernetes. For example, a concept page might describe the Kubernetes Deployment object and explain the role it plays as an application is deployed, scaled, and updated. Typically, concept pages don't include sequences of steps, but instead provide links to tasks or tutorials.</td>
   </tr>
 
-</table> 
+</table>
 
 Each page type has a
 [template](/docs/contribute/page-templates/)
@@ -72,6 +72,50 @@ Depending page type, create an entry in one of these files:
 * /_data/tutorials.yaml
 * /_data/concepts.yaml
 
+### Including code from another file
+
+To include a code file in your topic, place the code file in the Kubernetes
+documentation repository, preferably in the same directory as your topic
+file. In your topic file, use the `include` tag:
+
+<pre>&#123;% include code.html language="&lt;LEXERVALUE&gt;" file="&lt;RELATIVEPATH&gt;" ghlink="/&lt;PATHFROMROOT&gt;" %&#125;</pre>
+
+where:
+
+* `<LEXERVALUE>` is the language in which the file was written. This must be
+[a value supported by Rouge](https://github.com/jneen/rouge/wiki/list-of-supported-languages-and-lexers).
+* `<RELATIVEPATH>` is the path to the file you're including, relative to the current file, for example, `gce-volume.yaml`.
+* `<PATHFROMROOT>` is the path to the file relative to root, for example, `docs/tutorials/stateful-application/gce-volume.yaml`.
+
+Here's an example of using the `include` tag:
+
+<pre>&#123;% include code.html language="yaml" file="gce-volume.yaml" ghlink="/docs/tutorials/stateful-application/gce-volume.yaml" %&#125;</pre>
+
+### Showing how to create an API object from a configuration file
+
+If you need to show the reader how to create an API object based on a
+configuration file, place the configuration file in the Kubernetes documentation
+repository, preferably in the same directory as your topic file.
+
+In your topic, show this command:
+
+    kubectl create -f http://k8s.io/<PATHFROMROOT>
+
+where `<PATHFROMROOT>` is the path to the configuration file relative to root,
+for example, `docs/tutorials/stateful-application/gce-volume.yaml`.
+
+Here's an example of a command that creates an API object from a configuration file:
+
+    kubectl create -f http://k8s.io/docs/tutorials/stateful-application/gce-volume.yaml
+
+For an example of a topic that uses this technique, see
+[Running a Single-Instance Stateful Application](/docs/tutorials/stateful-application/run-stateful-application/).
+
+### Adding images to a topic
+
+Put image files in the `/images` directory. The preferred
+image format is SVG.
+
 {% endcapture %}
 
 {% capture whatsnext %}