diff --git a/site/Gemfile.lock b/site/Gemfile.lock
index b36ce1e4f..fc56e1b9d 100644
--- a/site/Gemfile.lock
+++ b/site/Gemfile.lock
@@ -6,8 +6,8 @@ GEM
       minitest (~> 5.1)
       thread_safe (~> 0.3, >= 0.3.4)
       tzinfo (~> 1.1)
-    addressable (2.6.0)
-      public_suffix (>= 2.0.2, < 4.0)
+    addressable (2.7.0)
+      public_suffix (>= 2.0.2, < 5.0)
     coffee-script (2.4.1)
       coffee-script-source
       execjs
@@ -16,7 +16,7 @@ GEM
     commonmarker (0.17.13)
       ruby-enum (~> 0.5)
     concurrent-ruby (1.1.5)
-    dnsruby (1.61.2)
+    dnsruby (1.61.3)
       addressable (~> 2.5)
     em-websocket (0.5.1)
       eventmachine (>= 0.12.9)
@@ -25,18 +25,18 @@ GEM
       ffi (>= 1.3.0)
     eventmachine (1.2.7)
     execjs (2.7.0)
-    faraday (0.15.4)
+    faraday (0.17.0)
       multipart-post (>= 1.2, < 3)
     ffi (1.11.1)
     forwardable-extended (2.6.0)
     gemoji (3.0.1)
-    github-pages (198)
+    github-pages (201)
       activesupport (= 4.2.11.1)
       github-pages-health-check (= 1.16.1)
       jekyll (= 3.8.5)
       jekyll-avatar (= 0.6.0)
       jekyll-coffeescript (= 1.1.1)
-      jekyll-commonmark-ghpages (= 0.1.5)
+      jekyll-commonmark-ghpages (= 0.1.6)
       jekyll-default-layout (= 0.1.4)
       jekyll-feed (= 0.11.0)
       jekyll-gist (= 1.5.0)
@@ -47,7 +47,7 @@ GEM
       jekyll-readme-index (= 0.2.0)
       jekyll-redirect-from (= 0.14.0)
       jekyll-relative-links (= 0.6.0)
-      jekyll-remote-theme (= 0.3.1)
+      jekyll-remote-theme (= 0.4.0)
       jekyll-sass-converter (= 1.5.2)
       jekyll-seo-tag (= 2.5.0)
       jekyll-sitemap (= 1.2.0)
@@ -72,8 +72,8 @@ GEM
       listen (= 3.1.5)
       mercenary (~> 0.3)
       minima (= 2.5.0)
-      nokogiri (>= 1.8.5, < 2.0)
-      rouge (= 2.2.1)
+      nokogiri (>= 1.10.4, < 2.0)
+      rouge (= 3.11.0)
       terminal-table (~> 1.4)
     github-pages-health-check (1.16.1)
       addressable (~> 2.3)
@@ -81,7 +81,7 @@ GEM
       octokit (~> 4.0)
       public_suffix (~> 3.0)
       typhoeus (~> 1.3)
-    html-pipeline (2.11.0)
+    html-pipeline (2.12.0)
       activesupport (>= 2)
       nokogiri (>= 1.4)
     http_parser.rb (0.6.0)
@@ -108,10 +108,10 @@ GEM
     jekyll-commonmark (1.3.1)
       commonmarker (~> 0.14)
       jekyll (>= 3.7, < 5.0)
-    jekyll-commonmark-ghpages (0.1.5)
+    jekyll-commonmark-ghpages (0.1.6)
       commonmarker (~> 0.17.6)
-      jekyll-commonmark (~> 1)
-      rouge (~> 2)
+      jekyll-commonmark (~> 1.2)
+      rouge (>= 2.0, < 4.0)
     jekyll-default-layout (0.1.4)
       jekyll (~> 3.0)
     jekyll-feed (0.11.0)
@@ -133,7 +133,8 @@ GEM
       jekyll (~> 3.3)
     jekyll-relative-links (0.6.0)
       jekyll (~> 3.3)
-    jekyll-remote-theme (0.3.1)
+    jekyll-remote-theme (0.4.0)
+      addressable (~> 2.0)
       jekyll (~> 3.5)
       rubyzip (>= 1.2.1, < 3.0)
     jekyll-sass-converter (1.5.2)
@@ -203,7 +204,7 @@ GEM
       jekyll (~> 3.5)
       jekyll-feed (~> 0.9)
       jekyll-seo-tag (~> 2.1)
-    minitest (5.11.3)
+    minitest (5.12.2)
     multipart-post (2.1.1)
     nokogiri (1.10.4)
       mini_portile2 (~> 2.4.0)
@@ -211,16 +212,16 @@ GEM
       sawyer (~> 0.8.0, >= 0.5.3)
     pathutil (0.16.2)
       forwardable-extended (~> 2.6)
-    public_suffix (3.0.3)
+    public_suffix (3.1.1)
     rb-fsevent (0.10.3)
     rb-inotify (0.10.0)
       ffi (~> 1.0)
-    redcarpet (3.4.0)
-    rouge (2.2.1)
+    redcarpet (3.5.0)
+    rouge (3.11.0)
     ruby-enum (0.7.2)
       i18n
     ruby_dep (1.5.0)
-    rubyzip (1.2.2)
+    rubyzip (2.0.0)
     safe_yaml (1.0.5)
     sass (3.7.4)
       sass-listen (~> 4.0.0)
diff --git a/site/_config.yml b/site/_config.yml
index a374946e7..5ed486a6d 100644
--- a/site/_config.yml
+++ b/site/_config.yml
@@ -3,7 +3,7 @@ title: Velero
 email:
 author: Velero Authors
 description: Backup and migrate Kubernetes resources and persistent volumes
-url: velero.io
+#url: velero.io
 logo: Velero.svg
 twitter:
   username: projectvelero
@@ -163,7 +163,7 @@ versions:
 - v0.3.0
 
 # Build settings
-permalink: :title/
+permalink: /blog/:title/
 sass:
   sass_dir: css
   style: :compressed
diff --git a/site/_layouts/redirect.html b/site/_layouts/redirect.html
index 2a41bf0c1..a1758f747 100644
--- a/site/_layouts/redirect.html
+++ b/site/_layouts/redirect.html
@@ -1,7 +1,7 @@
 <!DOCTYPE html>
 <html lang="en">
 <head>
-  {% if page.name == "survey.md" %}
+  {% if page.dir != "/docs/" %}
   <meta http-equiv="refresh" content="0; url={{ page.redirect.to }}" />
   <script type="text/javascript">
     window.location.href = "{{ page.redirect.to }}"
@@ -13,7 +13,7 @@ Redirecting to {{ page.redirect.to }}. If it doesn't load, click <a href="{{ pag
 </body>
 </html>
   {% endif %}
-  {% if page.name != "survey" %}
+  {% if page.dir == "/docs/" %}
   <meta http-equiv="refresh" content="0; url=/docs/{{ site.latest }}/{{ page.destination }}" />
   <script type="text/javascript">
     window.location.href = "/docs/{{ site.latest }}/{{ page.destination }}"
diff --git a/site/_posts/2019-04-09-Velero-is-an-Open-Source-Tool-to-Back-up-and-Migrate-Kubernetes-Clusters.md b/site/_posts/2019-04-09-Velero-is-an-Open-Source-Tool-to-Back-up-and-Migrate-Kubernetes-Clusters.md
index efb6a8950..1a2e47498 100644
--- a/site/_posts/2019-04-09-Velero-is-an-Open-Source-Tool-to-Back-up-and-Migrate-Kubernetes-Clusters.md
+++ b/site/_posts/2019-04-09-Velero-is-an-Open-Source-Tool-to-Back-up-and-Migrate-Kubernetes-Clusters.md
@@ -1,5 +1,6 @@
 ---
 title: Velero is an Open Source Tool to Back up and Migrate Kubernetes Clusters
+redirect_from: /Velero-is-an-Open-Source-Tool-to-Back-up-and-Migrate-Kubernetes-Clusters/
 # image: https://placehold.it/200x200
 excerpt: Velero is an open source tool to safely back up, recover, and migrate Kubernetes clusters and persistent volumes. It works both on premises and in a public cloud.
 author_name: Velero Team
diff --git a/site/_posts/2019-05-20-velero-1.0-has-arrived.md b/site/_posts/2019-05-20-velero-1.0-has-arrived.md
index fc99e8d50..7f5b0dce8 100644
--- a/site/_posts/2019-05-20-velero-1.0-has-arrived.md
+++ b/site/_posts/2019-05-20-velero-1.0-has-arrived.md
@@ -1,5 +1,6 @@
 ---
 title: Velero 1.0 Has Arrived&#58; Delivering Enhanced Stability, Usability and Extensibility Features
+redirect_from: /velero-1.0-has-arrived/
 # image: https://placehold.it/200x200
 excerpt: Just three months after the release of Velero 0.11, the community’s momentum continues with the delivery of the landmark version 1.0 release.
 author_name: Tom Spoonemore
diff --git a/site/_posts/2019-08-22-announcing-velero-1.1.md b/site/_posts/2019-08-22-announcing-velero-1.1.md
index 8e3622f45..573df97fd 100644
--- a/site/_posts/2019-08-22-announcing-velero-1.1.md
+++ b/site/_posts/2019-08-22-announcing-velero-1.1.md
@@ -1,5 +1,6 @@
 ---
 title: Announcing Velero 1.1&#58; Improved restic Support and More Visibility 
+redirect_from: /announcing-velero-1.1/
 # image: https://placehold.it/200x200
 excerpt: For this release, we’ve focused on improving Velero’s restic integration - making repository locks shorter lived, giving more visibility into restic repositories when migrating clusters, and expanding support to more volume types.
 author_name: Nolan Brubaker
diff --git a/site/_posts/2019-10-01-announcing-gh-move.md b/site/_posts/2019-10-01-announcing-gh-move.md
index bb23848c1..5916235da 100644
--- a/site/_posts/2019-10-01-announcing-gh-move.md
+++ b/site/_posts/2019-10-01-announcing-gh-move.md
@@ -1,5 +1,6 @@
 ---
 title: Announcing a new GitHub home for Velero
+redirect_from: /announcing-gh-move/
 image: /img/posts/vmware-tanzu.png
 excerpt: The next Velero release (v1.2) will be built out of a new GitHub organization, and we have significant changes to our plugins.
 author_name: Carlisia Campos
diff --git a/site/_posts/2019-10-08-Velero-v1-1-on-vSphere.md b/site/_posts/2019-10-08-Velero-v1-1-on-vSphere.md
index 13333a45e..eb94cec25 100644
--- a/site/_posts/2019-10-08-Velero-v1-1-on-vSphere.md
+++ b/site/_posts/2019-10-08-Velero-v1-1-on-vSphere.md
@@ -1,5 +1,6 @@
 ---
 title: Velero v1.1 backing up and restoring apps on vSphere
+redirect_from: /Velero-v1-1-on-vSphere/
 image: /img/posts/vsphere-logo.jpg
 excerpt: A How-To guide to run Velero on vSphere.
 author_name: Cormac Hogan
@@ -95,7 +96,7 @@ minio   NodePort   10.100.200.82   <none>        9000:32109/TCP   5s
 
 In the above outputs, the node on which the Minio Object Storage is deployed has IP address `192.168.192.5`. The NodePort that the Minio Service is exposed is `32109`. If we now direct a browser to that `Node:port` combination, we should see the Minio Object Store web interface. You can use the credentials provided in the `credentials-velero` file earlier to login.
 
-![Minio Object Store](../img/vsphere-tutorial-icons/Minio.png)
+![Minio Object Store](/img/vsphere-tutorial-icons/Minio.png)
 
 ## Install Velero
 
@@ -163,7 +164,7 @@ my-nginx   LoadBalancer   10.100.200.147   100.64.0.1,192.168.191.70   80:30942/
 
 In this example, a Load Balancer has provided the `nginx` service with an external IP address of 192.168.191.70. If I point a browser to that IP address, I get an nginx landing page identical to that shown below.
 
-![nginx landing page](../img/vsphere-tutorial-icons/nginx.png)
+![nginx landing page](/img/vsphere-tutorial-icons/nginx.png)
 
 We're now ready to do a backup and restore of the `nginx` application.
 
@@ -183,7 +184,7 @@ nginx-backup   Completed   2019-08-07 16:13:44 +0100 IST   29d       default
 
 You can now login to the Minio Object Storage via a browser and verify that the backup actually exists. You should see the name of the backup under the `velero/backups` folder:
 
-![Minio Backup Details](../img/vsphere-tutorial-icons/minio-nginx-backup.png)
+![Minio Backup Details](/img/vsphere-tutorial-icons/minio-nginx-backup.png)
 
 ## Destroy your application
 
@@ -247,7 +248,7 @@ You can see that the restore has now completed. Check to see if the namespace, D
 
 Now let’s see if we can successfully reach our `nginx` web server on that IP address. Yes we can! Looks like the restore was successful.
 
-![nginx restored](../img/vsphere-tutorial-icons/nginx-restore-new-ip.png)
+![nginx restored](/img/vsphere-tutorial-icons/nginx-restore-new-ip.png)
 
 Backups and Restores are now working on Kubernetes deployed on vSphere using Velero v1.1.
 
diff --git a/site/_posts/2019-10-10-Velero-v1-1-Stateful-Backup-vSphere.md b/site/_posts/2019-10-10-Velero-v1-1-Stateful-Backup-vSphere.md
index d2bbbcf00..e3fb7152f 100644
--- a/site/_posts/2019-10-10-Velero-v1-1-Stateful-Backup-vSphere.md
+++ b/site/_posts/2019-10-10-Velero-v1-1-Stateful-Backup-vSphere.md
@@ -1,5 +1,6 @@
 ---
 title: Velero v1.1 backing up and restoring Stateful apps on vSphere
+redirect_from: /Velero-v1-1-Stateful-Backup-vSphere/
 image: /img/posts/cassandra.gif
 excerpt: This post demonstrates how Velero can be used on Kubernetes running on vSphere to backup a Stateful application. For the purposes of this example, we will backup and restore a Cassandra NoSQL database management system.
 author_name: Cormac Hogan