final tweaks to add version, more accessible archive link

Author: vsoch

_config.yml

@@ -21,6 +21,7 @@ google_analytics: "UA-84672381-1" # Google Analytics code
 twitter_username:     SingularityApp
 github_username:      singularityware
 repo: "https://github.com/singularityware/singularity" # The main repo, should not end with slash
+singularity_version: "2.4"
 
 # Exclude
 # these are the files and directories that jekyll will exclude from the build

_data/sidebars/main_sidebar.yml

@@ -109,4 +109,6 @@ entries:
       url: /admin-guide
       output: web, pdf
 
-
+    - title: Archive
+      url: /archive
+      output: web, pdf

_layouts/page.html

@@ -4,6 +4,8 @@
 
 <div class="post-header">
    <h1 class="post-title-main">{{ page.title }}</h1>
+   <small style="color: #666; margin-top:50px; font-variant:italic">These docs are for Singularity Version {{ site.singularity_version }}. For older versions, see our <a class="no-after" 
+                                                               href="https://singularityware.github.io/archive">archive</a></small>
 </div>
 
 {% if page.simple_map == true %}

_posts/releases/2017-10-02-release-2.4.md

@@ -5,7 +5,7 @@ permalink: "release-2-4"
 version: "2.4"
 ---
 
-Singularity 2.4 is relesed, and here are the important notes for you to know about!
+Singularity 2.4 is released, and here are the important notes for you to know about!
 
 <img src="/assets/img/posts/releases/singularity-egg-easy.png">
 
@@ -20,19 +20,20 @@ sudo singularity build container.simg Singularity
 If you are tired of needing to estimate your image size, that issue goes away with build. The default format for a Singularity image base is now a smaller, compressed file format called **SquashFS**.  This format is also a much better fit for reproducible containers, as it is immutable. For more details, see our [build](/docs-build-container) documentation.
 
 **Build Bases**
-We originally supported just using an existing distribution package or docker as a base for building images. With 2.4, we have extended that set to include another Singularity image (`localimage`), a Singularity Hub or Registry image (`shub`) or the host operating system (`self`).
+We originally supported just using an existing distribution package or docker as a base for building images. With 2.4, we have extended that set to include another Singularity image (`localimage`), or a Singularity Hub or Registry image (`shub`).
 
 **Instance Support**
 Singularity now has support for instances, which means services! Images instances can be started, stopped, and listed. Along with instances comes **Network Namespace Isolation**. We are excited to see the kinds of use cases that this will afford for our users. 
 
 **Singularity Registry**
 If you want to host your own Registry, we listened and you are in luck! Singularity <a href="https://www.github.com/singularityhub/sregistry">Registry</a> is ready for your use, along with a <a href="https://singularityhub.github.io/containers">portal</a> for you to "register your registry" to make it easier to share your images. Singularity Hub, along with improved building and updated builders, will follow this release.
 
-**Internal Modalarity**
+**Internal Modularity**
 This release includes support for the <a href="/docs-apps">Standard Container Integration Format (SCI-F)</a> that makes it easy for you to produce single, internally modular and programmatically discoverage containers. More information is provided on it's <a href="https://containers-ftw.github.io/SCI-F/">main site</a>.
 
 **Better Documentation**
-We've added an entire page on the different customizations you can do to the [build environment](/build-environment), including changing the cache and specifying credentials for Docker. 
+We've added an entire page on the different customizations you can do to the [build environment](/build-environment), including changing the cache and specifying credentials for Docker. We now also have new sidebars for the Image and Instances command groups.
+
 
 **Deprecated**
 We are deprecating the original `create` command to be replaced with `image.create`, along with `bootstrap` in favor with build. These commands will still work for 2.4, however we recommend you start testing the updated ones.

pages/info/singularity-registry.md

@@ -21,10 +21,10 @@ to deploy on their resources to manage and serve singularity images.  With Singu
 Public images in your registry are immediately available via the Singularity command line software via the `shub://` unique resource identifier:
 
 ```
-singularity pull shub://vsoch/hello-world
+singularity pull shub://127.0.0.1/vsoch/hello-world
 ```
 
-If you don't want to build or host your own images, then you would be interested to use <a href="https://www.singularity-hub.org" target="_blank">Singularity Hub</a>,
+Where `127.0.0.1` would be in reference to your registry on localhost. If you don't want to build or host your own images, then you would be interested to use <a href="https://www.singularity-hub.org" target="_blank">Singularity Hub</a>,
 
 <a target="_blank" class="btn btn-primary navbar-btn cursorNorm" style="color:white;height: 42px;padding-top: 10px;" role="button" href="https://singularityhub.github.io/sregistry">Documentation</a> 
 <a target="_blank" href="https://www.github.com/singularityhub/sregistry" class="btn btn-primary navbar-btn cursorNorm no-after" role="button"><i style="color:white" class="fa fa-github fa-2x"></i></a>