initial check in for a gang of cluster creation and general configuration docs.

layouts/shortcodes/prereq_cluster.html

@@ -0,0 +1,5 @@
+<blockquote>
+	<p>
+		<strong>Prerequisites:</strong> Review the [requirements](placeholder.md) for your Linux host.
+	</p>
+</blockquote>

layouts/shortcodes/product.html

@@ -0,0 +1 @@
+<span>Rancher</span>

layouts/shortcodes/result_create-cluster.html

@@ -0,0 +1,8 @@
+<div>
+	<p><strong>Result:</strong></p>
+	<ul>
+		<li>Your cluster is created and assigned a state of <strong>Provisioning</strong>. Rancher is standing up your cluster.</li>
+		<li>You can access your cluster after its state is updated to <strong>Active</strong>.</li>
+		<li><strong>Active</strong> clusters are assigned a Project and Namespace, both of which are named <code>Default</code>.</li>
+	</ul>
+</div>

layouts/shortcodes/step_create-cluster_cluster-options.html

@@ -0,0 +1 @@
+<div><p>Use <strong>Cluster Options</strong> to choose the version of Kubernetes installed on each cluster node, along with some other options for you cluster.</p></div>

layouts/shortcodes/step_create-cluster_member-roles.html

@@ -0,0 +1,8 @@
+<div>
+<p>Use <strong>Member Roles</strong> to configure user authorization for the cluster.</p>
+	<ul>
+		<li>Click <strong>Add Members</strong> to add users that can access the cluster.</li>
+		<li>Use the <strong>Role</strong> drop-down to set permissions for each user.</li>
+	</ul>
+	<br/>
+</div>

layouts/shortcodes/step_create-cluster_node-pools.html

@@ -0,0 +1,10 @@
+<p>Add one or more <strong>Node Pools</strong> to your cluster. A <em>node pool</em> is a set of virtual machines configured identically to your Linux host. However, each node in the pool also has additional Kubernetes master and worker components installed.<p>
+
+<blockquote>
+	<p><strong>Notes:</strong></p>
+	<ul>
+		<li>After you create each node template, you can use it to create additional node pools.</li>
+		<li>Each Kubernetes role (i.e. <code>etcd</code>, <code>Control</code>, and <code>Worker</code>) must be filled. You can either apply all three roles to one pool or spread them around.</li>
+		<li>Ideally, you should have at least three <code>etcd</code> nodes so that your cluster can fail over to another if a etcd node goes down.</li>
+	</ul>
+</blockquote>

layouts/shortcodes/step_rancher-template.html

@@ -0,0 +1,14 @@
+	<p>Complete the <strong>Rancher Template</strong> form to add metadata so that you can find your template in Rancher later.</p>
+	<ul>
+		<li>
+			<p><strong>Labels</strong> apply metadata to your Docker objects.</p>
+
+			<p><a href="https://docs.docker.com/config/labels-custom-metadata/">Docker object label documentation</a></p>
+		</li>
+		<li>
+			<!-- TODO: Improve the engine options -->
+			<p><strong>Engine Options</strong> customize the configuration of the <a href="https://docs.docker.com/engine/docker-overview/#the-docker-daemon">Docker daemon</a>.</p>
+
+			<p><a href="https://docs.docker.com/engine/reference/commandline/dockerd/">daemon option reference</a></p>
+		</li>
+	</ul>

layouts/shortcodes/version.html

@@ -0,0 +1 @@
+<span>v2.0</span>