Adds some potential nav side bars, logo, and sample content (spinnaker#2)

Author: Travis Tomsu

_config.yml

@@ -111,6 +111,8 @@ author:
 include:
   - .htaccess
   - _pages
+  - concepts
+  - docs
 exclude:
   - "*.sublime-project"
   - "*.sublime-workspace"
@@ -135,8 +137,6 @@ exclude:
   - Rakefile
   - README
   - tmp
-  - /docs # ignore Minimal Mistakes /docs
-  - /test # ignore Minimal Mistakes /test
 keep_files:
   - .git
   - .svn

_data/navigation.yml

@@ -13,22 +13,38 @@ main:
   - title: Concepts
     url: /concepts
   - title: Documentation
-    url: /documentation
+    url: /docs
+  - title: Community
+  - title: Resources
 
 concepts:
   - title: Overview
-  - title: Stuff
-  - title: Moar Stuff
+    url: /concepts
+  - title: Groupings
+    url: /concepts/groupings
+  - title: Pipelines
+    url: /concepts/pipelines
+    children:
+      - title: Expressions Guide
+        url: /concepts/pipelines/expressions-guide
 
 docs:
   - title: Overview
+    url: /docs
   - title: Installation
+    url: /docs/installation
     children:
       - title: Linux
-        children:
-          - title: Foo
-            children:
-              - title: Bar
       - title: AWS
       - title: GCE
   - title: Releases
+  - title: Provider Configuration
+    children:
+      - title: Halyard
+      - title: AWS
+      - title: GCE
+      - title: Kubernetes
+  - title: Bells and Whistles
+    children:
+      - title: Jacob
+      - title: Jessica

_includes/masthead.html

@@ -2,7 +2,9 @@
   <div class="masthead__inner-wrap">
     <div class="masthead__menu">
       <nav id="site-nav" class="greedy-nav">
-        <a class="site-title" href="{{ '/' | absolute_url }}">{{ site.title }}</a>
+        <a class="site-title" href="{{ '/' | absolute_url }}">
+          <img src="{{ site.url}}/assets/images/spinnaker-logo-transparent.png">
+        </a>
         <ul class="visible-links">
           {% for link in site.data.navigation.main %}
             {% if link.url contains 'http' %}
@@ -18,4 +20,4 @@
       </nav>
     </div>
   </div>
-</div>
+</div>

_layouts/home.html

@@ -2,7 +2,7 @@
 layout: archive
 ---
 
-<h3 class="archive__subtitle">{{ site.data.ui-text[site.locale].recent_posts | default: "Recent Posts" }}</h3>
+<!-- <h3 class="archive__subtitle">{{ site.data.ui-text[site.locale].recent_posts | default: "Recent Posts" }}</h3> -->
 
 {% for post in paginator.posts %}
   {% include archive-single.html %}

_sass/_masthead.scss

@@ -10,6 +10,7 @@
   -webkit-animation-delay: 0.15s;
           animation-delay: 0.15s;
   z-index: 20;
+  background-color: $masthead-color;
 
   &__inner-wrap {
     @include container;
@@ -74,4 +75,4 @@
     padding-right: 2em;
     font-weight: 700;
   }
-}
+}

_sass/_navigation.scss

@@ -179,7 +179,7 @@
   display: flex;
   -webkit-box-align: center;
         align-items: center;
-  background: $background-color;
+  background: $masthead-color;
 
   a {
     display: block;
@@ -555,4 +555,4 @@
       display: block;
     }
   }
-}
+}

_sass/_variables.scss

@@ -93,7 +93,8 @@ $xing-color                 : #006567 !default;
 $link-color                 : $info-color !default;
 $link-color-hover           : mix(#000, $link-color, 25%) !default;
 $link-color-visited         : mix(#fff, $link-color, 25%) !default;
-$masthead-link-color        : $primary-color !default;
+$masthead-color             : #000 !default;
+$masthead-link-color        : #fff !default;
 $masthead-link-color-hover  : mix(#000, $primary-color, 25%) !default;
 
 
@@ -125,4 +126,4 @@ $border-radius              : 4px !default;
 $box-shadow                 : 0 1px 1px rgba(0, 0, 0, 0.125) !default;
 $navicon-width              : 1.5rem !default;
 $navicon-height             : 0.25rem !default;
-$global-transition          : all 0.2s ease-in-out !default;
+$global-transition          : all 0.2s ease-in-out !default;

assets/images/spinnaker-logo-og.png

@@ -0,0 +1,50 @@
+---
+layout: single
+title:  "Groupings"
+sidebar:
+  nav: concepts
+---
+
+{% include toc %}
+
+Spinnaker's top level groupings are Projects, Applications and Infrastructure.
+
+## Applications
+
+Applications are a logical grouping of infrastructure components - Server Groups and Clusters, Load Balancers, Security Groups and Pipelines. All components under a given Application share infrastructure credentials and top-level permissions. There are a few areas where cross-Application activities occur (e.g. a Stage that starts a Pipeline in another application), however in most areas, references are relegated to within the Application.
+
+An Application typically corresponds to a particular microservice.
+
+## Projects
+
+Projects are arbitrary collections of infrastructure resources and pipelines. This is a convenience feature which allows you to create a dashboard containing Applications, Clusters and Pipelines by wildcard.
+
+## Infrastructure
+
+This is a catch net area from which potentially lists all infrastructure components across all of Spinnaker that you have access to. You can search for Applications, Clusters, Server Groups, Instances, Load Balancers and Security Groups by wildcard.
+
+## Server Groups
+
+A Server Group is a group of compute resource instances (VMs, container pods). The instances of a Server Group are identical and are managed as a group by the cloud platforms (e.g. ASGs, Kubernetes Replica Sets).
+
+Server Groups mandatorily take on the naming convention *application-stack-detail-version*, where *stack* and *detail* are optional and *version* is system-assigned (incrementing version number). Spinnaker has no particular opinion on how the *stack* and *detail* fields are used, however it's common to use *stack* to represent a particular environment for a given microservice (e.g. dev, test, prod) and to use *detail* as an additional descriptor (e.g. feature branch, "experimental"). Finally, *version* indicates the specific Server Group, and individual instances of a Server Group are given a hash suffix in their names (e.g. "c9nzt") to uniquely identify each.
+
+## Clusters
+
+Clusters are logical groupings of Server Groups, by *application-stack-detail*. Clusters are used in situations where multiple Server Groups for a given microservice need to be coordinated in a single context, for example, during a red/black deployment.
+
+## Load Balancers
+
+Load Balancers route incoming traffic to associated and enabled Server Groups.
+
+## Security Groups
+
+Security Groups define traffic ingress rules for Server Groups.
+
+## Resource Mappings from Spinnaker to Provider
+
+Spinnaker | AWS | GCE | Kubernetes | Azure | OpenStack | Cloud Foundry
+---|---|---|---|---|---|---
+Server Group | ASG | MIG | Replica Set
+Load Balancer | Load Balancer | L3/L4/HTTP/internal Load Balancer | Service
+Security Group | Security Group | Firewall Rule | Ingress Rule

assets/images/spinnaker-logo-transparent.png

@@ -0,0 +1,49 @@
+---
+layout: single
+title:  "Concepts"
+sidebar:
+  nav: concepts
+---
+
+{% include toc %}
+
+Spinnaker is an open source, multi-cloud continuous delivery platform for releasing software changes with high velocity and confidence.
+
+It provides two core sets of features: *cluster management* and *deployment management*. Below we give a top-level overview of these features.
+
+## Cluster Management
+
+Spinnaker's cluster management features are used to manage resources in the cloud.
+
+* **Server Group**: The base resource to be managed is the *Server Group*. A Server Group identifies the machine instance profile on which to execute images along with the number of instances, and is associated with a Load Balancer and a Security Group. A Server Group is also identified with basic configuration settings, such as user account information and the region/zone in which images are deployed. When deployed, a Server Group is a collection of virtual machines running software.
+
+![image](https://files.readme.io/4l9kTko1SVSIcI26iBSR_server_group.png)
+
+* **Security Group**: A *Security Group* defines network traffic access. It is effectively a set of firewall rules defined by an IP range (CIDR) along with a communication protocol (e.g., TCP) and port range.
+* **Load Balancer**: A *Load Balancer* is associated with an ingress protocol and port range, and balances traffic among instances in the corresponding Server Group. Optionally, you can enable health checks for a load balancer, with flexiblity to define health criteria and specify the health check endpoint.
+* **Cluster**: A *Cluster* is a user-defined, logical grouping of Server Groups in Spinnaker.
+
+## Deployment Management
+
+Spinnaker's deployment management features are used to construct and manage continuous delivery workflows.
+
+* **Pipeline**: *Pipelines* are the key deployment management construct in Spinnaker. They are defined by a sequence of stages, along with automated triggers (optional) that kick off the pipeline, parameters that get passed to all stages in the pipeline, and can be configured to issue notifications as the pipeline executes.<br><br>Automatic triggers can be a Jenkins job, a CRON schedule, or another pipeline. You can also manually start a pipeline. Notifications can be sent out to email, SMS or HipChat on pipeline start/complete/fail.
+
+![image](https://files.readme.io/Y1X8CO7KTkO7vO9x3ZZi_pipeline.png)
+
+* **Stage**: A *Stage* in Spinnaker is an atomic building block for a pipeline. Stages in a Pipeline can be sequenced in any order, though some stage sequences may be more common than others. Spinnaker comes pre-packaged with a number of stages, including:
+  * **Bake**: Bakes an image in the specified region.
+  * **Deploy**: Deploys a previously baked or found image.
+  * **Destroy Server Group**: Destroys a server group.
+  * **Disable Server Group**: Disables a server group.
+  * **Enable Server Group**: Enables a server group.
+  * **Find Image**: Finds a previously-baked image to deploy into an existing cluster.
+  * **Jenkins**: Runs a Jenkins job.
+  * **Manual Judgment**: Waits for user approval before continuing.
+  * **Modify Scaling Process**: Suspend or resume server group scaling processes.
+  * **Pipeline**: Runs a pipeline. This allows pipelines to be composed hierarchically.
+  * **Quick Patch Server Group**: Quick patches a server group. Used for emergency patches.
+  * **Resize Server Group**: Resizes a server group.
+  * **Script**: Runs an arbitrary shell script.
+  * **Shrink Cluster**: Shrinks a cluster.
+  * **Wait**: Waits a specified period of time.

concepts/groupings.md

@@ -0,0 +1,8 @@
+---
+layout: single
+title:  "Pipelines"
+sidebar:
+  nav: concepts
+---
+
+{% include toc %}