`s.
+
+.nav {
+ display: flex;
+ flex-wrap: wrap;
+ padding-left: 0;
+ margin-bottom: 0;
+ list-style: none;
+}
+
+.nav-link {
+ display: block;
+ padding: $nav-link-padding-y $nav-link-padding-x;
+
+ @include hover-focus {
+ text-decoration: none;
+ }
+
+ // Disabled state lightens text
+ &.disabled {
+ color: $nav-link-disabled-color;
+ }
+}
+
+//
+// Tabs
+//
+
+.nav-tabs {
+ border-bottom: $nav-tabs-border-width solid $nav-tabs-border-color;
+
+ .nav-item {
+ margin-bottom: -$nav-tabs-border-width;
+ }
+
+ .nav-link {
+ border: $nav-tabs-border-width solid transparent;
+ @include border-top-radius($nav-tabs-border-radius);
+
+ @include hover-focus {
+ border-color: $nav-tabs-link-hover-border-color;
+ }
+
+ &.disabled {
+ color: $nav-link-disabled-color;
+ background-color: transparent;
+ border-color: transparent;
+ }
+ }
+
+ .nav-link.active,
+ .nav-item.show .nav-link {
+ color: $nav-tabs-link-active-color;
+ background-color: $nav-tabs-link-active-bg;
+ border-color: $nav-tabs-link-active-border-color;
+ }
+
+ .dropdown-menu {
+ // Make dropdown border overlap tab border
+ margin-top: -$nav-tabs-border-width;
+ // Remove the top rounded corners here since there is a hard edge above the menu
+ @include border-top-radius(0);
+ }
+}
+
+
+//
+// Pills
+//
+
+.nav-pills {
+ .nav-link {
+ @include border-radius($nav-pills-border-radius);
+ }
+
+ .nav-link.active,
+ .show > .nav-link {
+ color: $nav-pills-link-active-color;
+ background-color: $nav-pills-link-active-bg;
+ }
+}
+
+
+//
+// Justified variants
+//
+
+.nav-fill {
+ .nav-item {
+ flex: 1 1 auto;
+ text-align: center;
+ }
+}
+
+.nav-justified {
+ .nav-item {
+ flex-basis: 0;
+ flex-grow: 1;
+ text-align: center;
+ }
+}
+
+
+// Tabbable tabs
+//
+// Hide tabbable panes to start, show them when `.active`
+
+.tab-content {
+ > .tab-pane {
+ display: none;
+ }
+ > .active {
+ display: block;
+ }
+}
diff --git a/site/_scss/bootstrap-4.1.3/_navbar.scss b/site/_scss/bootstrap-4.1.3/_navbar.scss
new file mode 100755
index 000000000..52de5050a
--- /dev/null
+++ b/site/_scss/bootstrap-4.1.3/_navbar.scss
@@ -0,0 +1,299 @@
+// Contents
+//
+// Navbar
+// Navbar brand
+// Navbar nav
+// Navbar text
+// Navbar divider
+// Responsive navbar
+// Navbar position
+// Navbar themes
+
+
+// Navbar
+//
+// Provide a static navbar from which we expand to create full-width, fixed, and
+// other navbar variations.
+
+.navbar {
+ position: relative;
+ display: flex;
+ flex-wrap: wrap; // allow us to do the line break for collapsing content
+ align-items: center;
+ justify-content: space-between; // space out brand from logo
+ padding: $navbar-padding-y $navbar-padding-x;
+
+ // Because flex properties aren't inherited, we need to redeclare these first
+ // few properties so that content nested within behave properly.
+ > .container,
+ > .container-fluid {
+ display: flex;
+ flex-wrap: wrap;
+ align-items: center;
+ justify-content: space-between;
+ }
+}
+
+
+// Navbar brand
+//
+// Used for brand, project, or site names.
+
+.navbar-brand {
+ display: inline-block;
+ padding-top: $navbar-brand-padding-y;
+ padding-bottom: $navbar-brand-padding-y;
+ margin-right: $navbar-padding-x;
+ font-size: $navbar-brand-font-size;
+ line-height: inherit;
+ white-space: nowrap;
+
+ @include hover-focus {
+ text-decoration: none;
+ }
+}
+
+
+// Navbar nav
+//
+// Custom navbar navigation (doesn't require `.nav`, but does make use of `.nav-link`).
+
+.navbar-nav {
+ display: flex;
+ flex-direction: column; // cannot use `inherit` to get the `.navbar`s value
+ padding-left: 0;
+ margin-bottom: 0;
+ list-style: none;
+
+ .nav-link {
+ padding-right: 0;
+ padding-left: 0;
+ }
+
+ .dropdown-menu {
+ position: static;
+ float: none;
+ }
+}
+
+
+// Navbar text
+//
+//
+
+.navbar-text {
+ display: inline-block;
+ padding-top: $nav-link-padding-y;
+ padding-bottom: $nav-link-padding-y;
+}
+
+
+// Responsive navbar
+//
+// Custom styles for responsive collapsing and toggling of navbar contents.
+// Powered by the collapse Bootstrap JavaScript plugin.
+
+// When collapsed, prevent the toggleable navbar contents from appearing in
+// the default flexbox row orientation. Requires the use of `flex-wrap: wrap`
+// on the `.navbar` parent.
+.navbar-collapse {
+ flex-basis: 100%;
+ flex-grow: 1;
+ // For always expanded or extra full navbars, ensure content aligns itself
+ // properly vertically. Can be easily overridden with flex utilities.
+ align-items: center;
+}
+
+// Button for toggling the navbar when in its collapsed state
+.navbar-toggler {
+ padding: $navbar-toggler-padding-y $navbar-toggler-padding-x;
+ font-size: $navbar-toggler-font-size;
+ line-height: 1;
+ background-color: transparent; // remove default button style
+ border: $border-width solid transparent; // remove default button style
+ @include border-radius($navbar-toggler-border-radius);
+
+ @include hover-focus {
+ text-decoration: none;
+ }
+
+ // Opinionated: add "hand" cursor to non-disabled .navbar-toggler elements
+ &:not(:disabled):not(.disabled) {
+ cursor: pointer;
+ }
+}
+
+// Keep as a separate element so folks can easily override it with another icon
+// or image file as needed.
+.navbar-toggler-icon {
+ display: inline-block;
+ width: 1.5em;
+ height: 1.5em;
+ vertical-align: middle;
+ content: "";
+ background: no-repeat center center;
+ background-size: 100% 100%;
+}
+
+// Generate series of `.navbar-expand-*` responsive classes for configuring
+// where your navbar collapses.
+.navbar-expand {
+ @each $breakpoint in map-keys($grid-breakpoints) {
+ $next: breakpoint-next($breakpoint, $grid-breakpoints);
+ $infix: breakpoint-infix($next, $grid-breakpoints);
+
+ &#{$infix} {
+ @include media-breakpoint-down($breakpoint) {
+ > .container,
+ > .container-fluid {
+ padding-right: 0;
+ padding-left: 0;
+ }
+ }
+
+ @include media-breakpoint-up($next) {
+ flex-flow: row nowrap;
+ justify-content: flex-start;
+
+ .navbar-nav {
+ flex-direction: row;
+
+ .dropdown-menu {
+ position: absolute;
+ }
+
+ .nav-link {
+ padding-right: $navbar-nav-link-padding-x;
+ padding-left: $navbar-nav-link-padding-x;
+ }
+ }
+
+ // For nesting containers, have to redeclare for alignment purposes
+ > .container,
+ > .container-fluid {
+ flex-wrap: nowrap;
+ }
+
+ .navbar-collapse {
+ display: flex !important; // stylelint-disable-line declaration-no-important
+
+ // Changes flex-bases to auto because of an IE10 bug
+ flex-basis: auto;
+ }
+
+ .navbar-toggler {
+ display: none;
+ }
+ }
+ }
+ }
+}
+
+
+// Navbar themes
+//
+// Styles for switching between navbars with light or dark background.
+
+// Dark links against a light background
+.navbar-light {
+ .navbar-brand {
+ color: $navbar-light-active-color;
+
+ @include hover-focus {
+ color: $navbar-light-active-color;
+ }
+ }
+
+ .navbar-nav {
+ .nav-link {
+ color: $navbar-light-color;
+
+ @include hover-focus {
+ color: $navbar-light-hover-color;
+ }
+
+ &.disabled {
+ color: $navbar-light-disabled-color;
+ }
+ }
+
+ .show > .nav-link,
+ .active > .nav-link,
+ .nav-link.show,
+ .nav-link.active {
+ color: $navbar-light-active-color;
+ }
+ }
+
+ .navbar-toggler {
+ color: $navbar-light-color;
+ border-color: $navbar-light-toggler-border-color;
+ }
+
+ .navbar-toggler-icon {
+ background-image: $navbar-light-toggler-icon-bg;
+ }
+
+ .navbar-text {
+ color: $navbar-light-color;
+ a {
+ color: $navbar-light-active-color;
+
+ @include hover-focus {
+ color: $navbar-light-active-color;
+ }
+ }
+ }
+}
+
+// White links against a dark background
+.navbar-dark {
+ .navbar-brand {
+ color: $navbar-dark-active-color;
+
+ @include hover-focus {
+ color: $navbar-dark-active-color;
+ }
+ }
+
+ .navbar-nav {
+ .nav-link {
+ color: $navbar-dark-color;
+
+ @include hover-focus {
+ color: $navbar-dark-hover-color;
+ }
+
+ &.disabled {
+ color: $navbar-dark-disabled-color;
+ }
+ }
+
+ .show > .nav-link,
+ .active > .nav-link,
+ .nav-link.show,
+ .nav-link.active {
+ color: $navbar-dark-active-color;
+ }
+ }
+
+ .navbar-toggler {
+ color: $navbar-dark-color;
+ border-color: $navbar-dark-toggler-border-color;
+ }
+
+ .navbar-toggler-icon {
+ background-image: $navbar-dark-toggler-icon-bg;
+ }
+
+ .navbar-text {
+ color: $navbar-dark-color;
+ a {
+ color: $navbar-dark-active-color;
+
+ @include hover-focus {
+ color: $navbar-dark-active-color;
+ }
+ }
+ }
+}
diff --git a/site/_scss/bootstrap-4.1.3/_pagination.scss b/site/_scss/bootstrap-4.1.3/_pagination.scss
new file mode 100755
index 000000000..9349f3f90
--- /dev/null
+++ b/site/_scss/bootstrap-4.1.3/_pagination.scss
@@ -0,0 +1,78 @@
+.pagination {
+ display: flex;
+ @include list-unstyled();
+ @include border-radius();
+}
+
+.page-link {
+ position: relative;
+ display: block;
+ padding: $pagination-padding-y $pagination-padding-x;
+ margin-left: -$pagination-border-width;
+ line-height: $pagination-line-height;
+ color: $pagination-color;
+ background-color: $pagination-bg;
+ border: $pagination-border-width solid $pagination-border-color;
+
+ &:hover {
+ z-index: 2;
+ color: $pagination-hover-color;
+ text-decoration: none;
+ background-color: $pagination-hover-bg;
+ border-color: $pagination-hover-border-color;
+ }
+
+ &:focus {
+ z-index: 2;
+ outline: $pagination-focus-outline;
+ box-shadow: $pagination-focus-box-shadow;
+ }
+
+ // Opinionated: add "hand" cursor to non-disabled .page-link elements
+ &:not(:disabled):not(.disabled) {
+ cursor: pointer;
+ }
+}
+
+.page-item {
+ &:first-child {
+ .page-link {
+ margin-left: 0;
+ @include border-left-radius($border-radius);
+ }
+ }
+ &:last-child {
+ .page-link {
+ @include border-right-radius($border-radius);
+ }
+ }
+
+ &.active .page-link {
+ z-index: 1;
+ color: $pagination-active-color;
+ background-color: $pagination-active-bg;
+ border-color: $pagination-active-border-color;
+ }
+
+ &.disabled .page-link {
+ color: $pagination-disabled-color;
+ pointer-events: none;
+ // Opinionated: remove the "hand" cursor set previously for .page-link
+ cursor: auto;
+ background-color: $pagination-disabled-bg;
+ border-color: $pagination-disabled-border-color;
+ }
+}
+
+
+//
+// Sizing
+//
+
+.pagination-lg {
+ @include pagination-size($pagination-padding-y-lg, $pagination-padding-x-lg, $font-size-lg, $line-height-lg, $border-radius-lg);
+}
+
+.pagination-sm {
+ @include pagination-size($pagination-padding-y-sm, $pagination-padding-x-sm, $font-size-sm, $line-height-sm, $border-radius-sm);
+}
diff --git a/site/_scss/bootstrap-4.1.3/_popover.scss b/site/_scss/bootstrap-4.1.3/_popover.scss
new file mode 100755
index 000000000..3ef5f628b
--- /dev/null
+++ b/site/_scss/bootstrap-4.1.3/_popover.scss
@@ -0,0 +1,183 @@
+.popover {
+ position: absolute;
+ top: 0;
+ left: 0;
+ z-index: $zindex-popover;
+ display: block;
+ max-width: $popover-max-width;
+ // Our parent element can be arbitrary since tooltips are by default inserted as a sibling of their target element.
+ // So reset our font and text properties to avoid inheriting weird values.
+ @include reset-text();
+ font-size: $popover-font-size;
+ // Allow breaking very long words so they don't overflow the popover's bounds
+ word-wrap: break-word;
+ background-color: $popover-bg;
+ background-clip: padding-box;
+ border: $popover-border-width solid $popover-border-color;
+ @include border-radius($popover-border-radius);
+ @include box-shadow($popover-box-shadow);
+
+ .arrow {
+ position: absolute;
+ display: block;
+ width: $popover-arrow-width;
+ height: $popover-arrow-height;
+ margin: 0 $border-radius-lg;
+
+ &::before,
+ &::after {
+ position: absolute;
+ display: block;
+ content: "";
+ border-color: transparent;
+ border-style: solid;
+ }
+ }
+}
+
+.bs-popover-top {
+ margin-bottom: $popover-arrow-height;
+
+ .arrow {
+ bottom: calc((#{$popover-arrow-height} + #{$popover-border-width}) * -1);
+ }
+
+ .arrow::before,
+ .arrow::after {
+ border-width: $popover-arrow-height ($popover-arrow-width / 2) 0;
+ }
+
+ .arrow::before {
+ bottom: 0;
+ border-top-color: $popover-arrow-outer-color;
+ }
+
+ .arrow::after {
+ bottom: $popover-border-width;
+ border-top-color: $popover-arrow-color;
+ }
+}
+
+.bs-popover-right {
+ margin-left: $popover-arrow-height;
+
+ .arrow {
+ left: calc((#{$popover-arrow-height} + #{$popover-border-width}) * -1);
+ width: $popover-arrow-height;
+ height: $popover-arrow-width;
+ margin: $border-radius-lg 0; // make sure the arrow does not touch the popover's rounded corners
+ }
+
+ .arrow::before,
+ .arrow::after {
+ border-width: ($popover-arrow-width / 2) $popover-arrow-height ($popover-arrow-width / 2) 0;
+ }
+
+ .arrow::before {
+ left: 0;
+ border-right-color: $popover-arrow-outer-color;
+ }
+
+ .arrow::after {
+ left: $popover-border-width;
+ border-right-color: $popover-arrow-color;
+ }
+}
+
+.bs-popover-bottom {
+ margin-top: $popover-arrow-height;
+
+ .arrow {
+ top: calc((#{$popover-arrow-height} + #{$popover-border-width}) * -1);
+ }
+
+ .arrow::before,
+ .arrow::after {
+ border-width: 0 ($popover-arrow-width / 2) $popover-arrow-height ($popover-arrow-width / 2);
+ }
+
+ .arrow::before {
+ top: 0;
+ border-bottom-color: $popover-arrow-outer-color;
+ }
+
+ .arrow::after {
+ top: $popover-border-width;
+ border-bottom-color: $popover-arrow-color;
+ }
+
+ // This will remove the popover-header's border just below the arrow
+ .popover-header::before {
+ position: absolute;
+ top: 0;
+ left: 50%;
+ display: block;
+ width: $popover-arrow-width;
+ margin-left: ($popover-arrow-width / -2);
+ content: "";
+ border-bottom: $popover-border-width solid $popover-header-bg;
+ }
+}
+
+.bs-popover-left {
+ margin-right: $popover-arrow-height;
+
+ .arrow {
+ right: calc((#{$popover-arrow-height} + #{$popover-border-width}) * -1);
+ width: $popover-arrow-height;
+ height: $popover-arrow-width;
+ margin: $border-radius-lg 0; // make sure the arrow does not touch the popover's rounded corners
+ }
+
+ .arrow::before,
+ .arrow::after {
+ border-width: ($popover-arrow-width / 2) 0 ($popover-arrow-width / 2) $popover-arrow-height;
+ }
+
+ .arrow::before {
+ right: 0;
+ border-left-color: $popover-arrow-outer-color;
+ }
+
+ .arrow::after {
+ right: $popover-border-width;
+ border-left-color: $popover-arrow-color;
+ }
+}
+
+.bs-popover-auto {
+ &[x-placement^="top"] {
+ @extend .bs-popover-top;
+ }
+ &[x-placement^="right"] {
+ @extend .bs-popover-right;
+ }
+ &[x-placement^="bottom"] {
+ @extend .bs-popover-bottom;
+ }
+ &[x-placement^="left"] {
+ @extend .bs-popover-left;
+ }
+}
+
+
+// Offset the popover to account for the popover arrow
+.popover-header {
+ padding: $popover-header-padding-y $popover-header-padding-x;
+ margin-bottom: 0; // Reset the default from Reboot
+ font-size: $font-size-base;
+ color: $popover-header-color;
+ background-color: $popover-header-bg;
+ border-bottom: $popover-border-width solid darken($popover-header-bg, 5%);
+ $offset-border-width: calc(#{$border-radius-lg} - #{$popover-border-width});
+ @include border-top-radius($offset-border-width);
+
+ &:empty {
+ display: none;
+ }
+}
+
+.popover-body {
+ padding: $popover-body-padding-y $popover-body-padding-x;
+ color: $popover-body-color;
+}
diff --git a/site/_scss/bootstrap-4.1.3/_print.scss b/site/_scss/bootstrap-4.1.3/_print.scss
new file mode 100755
index 000000000..1df948735
--- /dev/null
+++ b/site/_scss/bootstrap-4.1.3/_print.scss
@@ -0,0 +1,141 @@
+// stylelint-disable declaration-no-important, selector-no-qualifying-type
+
+// Source: https://github.com/h5bp/html5-boilerplate/blob/master/src/css/main.css
+
+// ==========================================================================
+// Print styles.
+// Inlined to avoid the additional HTTP request:
+// https://www.phpied.com/delay-loading-your-print-css/
+// ==========================================================================
+
+@if $enable-print-styles {
+ @media print {
+ *,
+ *::before,
+ *::after {
+ // Bootstrap specific; comment out `color` and `background`
+ //color: $black !important; // Black prints faster
+ text-shadow: none !important;
+ //background: transparent !important;
+ box-shadow: none !important;
+ }
+
+ a {
+ &:not(.btn) {
+ text-decoration: underline;
+ }
+ }
+
+ // Bootstrap specific; comment the following selector out
+ //a[href]::after {
+ // content: " (" attr(href) ")";
+ //}
+
+ abbr[title]::after {
+ content: " (" attr(title) ")";
+ }
+
+ // Bootstrap specific; comment the following selector out
+ //
+ // Don't show links that are fragment identifiers,
+ // or use the `javascript:` pseudo protocol
+ //
+
+ //a[href^="#"]::after,
+ //a[href^="javascript:"]::after {
+ // content: "";
+ //}
+
+ pre {
+ white-space: pre-wrap !important;
+ }
+ pre,
+ blockquote {
+ border: $border-width solid $gray-500; // Bootstrap custom code; using `$border-width` instead of 1px
+ page-break-inside: avoid;
+ }
+
+ //
+ // Printing Tables:
+ // http://css-discuss.incutio.com/wiki/Printing_Tables
+ //
+
+ thead {
+ display: table-header-group;
+ }
+
+ tr,
+ img {
+ page-break-inside: avoid;
+ }
+
+ p,
+ h2,
+ h3 {
+ orphans: 3;
+ widows: 3;
+ }
+
+ h2,
+ h3 {
+ page-break-after: avoid;
+ }
+
+ // Bootstrap specific changes start
+
+ // Specify a size and min-width to make printing closer across browsers.
+ // We don't set margin here because it breaks `size` in Chrome. We also
+ // don't use `!important` on `size` as it breaks in Chrome.
+ @page {
+ size: $print-page-size;
+ }
+ body {
+ min-width: $print-body-min-width !important;
+ }
+ .container {
+ min-width: $print-body-min-width !important;
+ }
+
+ // Bootstrap components
+ .navbar {
+ display: none;
+ }
+ .badge {
+ border: $border-width solid $black;
+ }
+
+ .table {
+ border-collapse: collapse !important;
+
+ td,
+ th {
+ background-color: $white !important;
+ }
+ }
+
+ .table-bordered {
+ th,
+ td {
+ border: 1px solid $gray-300 !important;
+ }
+ }
+
+ .table-dark {
+ color: inherit;
+
+ th,
+ td,
+ thead th,
+ tbody + tbody {
+ border-color: $table-border-color;
+ }
+ }
+
+ .table .thead-dark th {
+ color: inherit;
+ border-color: $table-border-color;
+ }
+
+ // Bootstrap specific changes end
+ }
+}
diff --git a/site/_scss/bootstrap-4.1.3/_progress.scss b/site/_scss/bootstrap-4.1.3/_progress.scss
new file mode 100755
index 000000000..0ac3e0c93
--- /dev/null
+++ b/site/_scss/bootstrap-4.1.3/_progress.scss
@@ -0,0 +1,34 @@
+@keyframes progress-bar-stripes {
+ from { background-position: $progress-height 0; }
+ to { background-position: 0 0; }
+}
+
+.progress {
+ display: flex;
+ height: $progress-height;
+ overflow: hidden; // force rounded corners by cropping it
+ font-size: $progress-font-size;
+ background-color: $progress-bg;
+ @include border-radius($progress-border-radius);
+ @include box-shadow($progress-box-shadow);
+}
+
+.progress-bar {
+ display: flex;
+ flex-direction: column;
+ justify-content: center;
+ color: $progress-bar-color;
+ text-align: center;
+ white-space: nowrap;
+ background-color: $progress-bar-bg;
+ @include transition($progress-bar-transition);
+}
+
+.progress-bar-striped {
+ @include gradient-striped();
+ background-size: $progress-height $progress-height;
+}
+
+.progress-bar-animated {
+ animation: progress-bar-stripes $progress-bar-animation-timing;
+}
diff --git a/site/_scss/bootstrap-4.1.3/_reboot.scss b/site/_scss/bootstrap-4.1.3/_reboot.scss
new file mode 100755
index 000000000..f297d095c
--- /dev/null
+++ b/site/_scss/bootstrap-4.1.3/_reboot.scss
@@ -0,0 +1,483 @@
+// stylelint-disable at-rule-no-vendor-prefix, declaration-no-important, selector-no-qualifying-type, property-no-vendor-prefix
+
+// Reboot
+//
+// Normalization of HTML elements, manually forked from Normalize.css to remove
+// styles targeting irrelevant browsers while applying new styles.
+//
+// Normalize is licensed MIT. https://github.com/necolas/normalize.css
+
+
+// Document
+//
+// 1. Change from `box-sizing: content-box` so that `width` is not affected by `padding` or `border`.
+// 2. Change the default font family in all browsers.
+// 3. Correct the line height in all browsers.
+// 4. Prevent adjustments of font size after orientation changes in IE on Windows Phone and in iOS.
+// 5. Setting @viewport causes scrollbars to overlap content in IE11 and Edge, so
+// we force a non-overlapping, non-auto-hiding scrollbar to counteract.
+// 6. Change the default tap highlight to be completely transparent in iOS.
+
+*,
+*::before,
+*::after {
+ box-sizing: border-box; // 1
+}
+
+html {
+ font-family: sans-serif; // 2
+ line-height: 1.15; // 3
+ -webkit-text-size-adjust: 100%; // 4
+ -ms-text-size-adjust: 100%; // 4
+ -ms-overflow-style: scrollbar; // 5
+ -webkit-tap-highlight-color: rgba($black, 0); // 6
+}
+
+// IE10+ doesn't honor `` in some cases.
+@at-root {
+ @-ms-viewport {
+ width: device-width;
+ }
+}
+
+// stylelint-disable selector-list-comma-newline-after
+// Shim for "new" HTML5 structural elements to display correctly (IE10, older browsers)
+article, aside, figcaption, figure, footer, header, hgroup, main, nav, section {
+ display: block;
+}
+// stylelint-enable selector-list-comma-newline-after
+
+// Body
+//
+// 1. Remove the margin in all browsers.
+// 2. As a best practice, apply a default `background-color`.
+// 3. Set an explicit initial text-align value so that we can later use the
+// the `inherit` value on things like `` elements.
+
+body {
+ margin: 0; // 1
+ font-family: $font-family-base;
+ font-size: $font-size-base;
+ font-weight: $font-weight-base;
+ line-height: $line-height-base;
+ color: $body-color;
+ text-align: left; // 3
+ background-color: $body-bg; // 2
+}
+
+// Suppress the focus outline on elements that cannot be accessed via keyboard.
+// This prevents an unwanted focus outline from appearing around elements that
+// might still respond to pointer events.
+//
+// Credit: https://github.com/suitcss/base
+[tabindex="-1"]:focus {
+ outline: 0 !important;
+}
+
+
+// Content grouping
+//
+// 1. Add the correct box sizing in Firefox.
+// 2. Show the overflow in Edge and IE.
+
+hr {
+ box-sizing: content-box; // 1
+ height: 0; // 1
+ overflow: visible; // 2
+}
+
+
+//
+// Typography
+//
+
+// Remove top margins from headings
+//
+// By default, ``-`` all receive top and bottom margins. We nuke the top
+// margin for easier control within type scales as it avoids margin collapsing.
+// stylelint-disable selector-list-comma-newline-after
+h1, h2, h3, h4, h5, h6 {
+ margin-top: 0;
+ margin-bottom: $headings-margin-bottom;
+}
+// stylelint-enable selector-list-comma-newline-after
+
+// Reset margins on paragraphs
+//
+// Similarly, the top margin on ``s get reset. However, we also reset the
+// bottom margin to use `rem` units instead of `em`.
+p {
+ margin-top: 0;
+ margin-bottom: $paragraph-margin-bottom;
+}
+
+// Abbreviations
+//
+// 1. Remove the bottom border in Firefox 39-.
+// 2. Add the correct text decoration in Chrome, Edge, IE, Opera, and Safari.
+// 3. Add explicit cursor to indicate changed behavior.
+// 4. Duplicate behavior to the data-* attribute for our tooltip plugin
+
+abbr[title],
+abbr[data-original-title] { // 4
+ text-decoration: underline; // 2
+ text-decoration: underline dotted; // 2
+ cursor: help; // 3
+ border-bottom: 0; // 1
+}
+
+address {
+ margin-bottom: 1rem;
+ font-style: normal;
+ line-height: inherit;
+}
+
+ol,
+ul,
+dl {
+ margin-top: 0;
+ margin-bottom: 1rem;
+}
+
+ol ol,
+ul ul,
+ol ul,
+ul ol {
+ margin-bottom: 0;
+}
+
+dt {
+ font-weight: $dt-font-weight;
+}
+
+dd {
+ margin-bottom: .5rem;
+ margin-left: 0; // Undo browser default
+}
+
+blockquote {
+ margin: 0 0 1rem;
+}
+
+dfn {
+ font-style: italic; // Add the correct font style in Android 4.3-
+}
+
+// stylelint-disable font-weight-notation
+b,
+strong {
+ font-weight: bolder; // Add the correct font weight in Chrome, Edge, and Safari
+}
+// stylelint-enable font-weight-notation
+
+small {
+ font-size: 80%; // Add the correct font size in all browsers
+}
+
+//
+// Prevent `sub` and `sup` elements from affecting the line height in
+// all browsers.
+//
+
+sub,
+sup {
+ position: relative;
+ font-size: 75%;
+ line-height: 0;
+ vertical-align: baseline;
+}
+
+sub { bottom: -.25em; }
+sup { top: -.5em; }
+
+
+//
+// Links
+//
+
+a {
+ color: $link-color;
+ text-decoration: $link-decoration;
+ background-color: transparent; // Remove the gray background on active links in IE 10.
+ -webkit-text-decoration-skip: objects; // Remove gaps in links underline in iOS 8+ and Safari 8+.
+
+ @include hover {
+ color: $link-hover-color;
+ text-decoration: $link-hover-decoration;
+ }
+}
+
+// And undo these styles for placeholder links/named anchors (without href)
+// which have not been made explicitly keyboard-focusable (without tabindex).
+// It would be more straightforward to just use a[href] in previous block, but that
+// causes specificity issues in many other styles that are too complex to fix.
+// See https://github.com/twbs/bootstrap/issues/19402
+
+a:not([href]):not([tabindex]) {
+ color: inherit;
+ text-decoration: none;
+
+ @include hover-focus {
+ color: inherit;
+ text-decoration: none;
+ }
+
+ &:focus {
+ outline: 0;
+ }
+}
+
+
+//
+// Code
+//
+
+pre,
+code,
+kbd,
+samp {
+ font-family: $font-family-monospace;
+ font-size: 1em; // Correct the odd `em` font sizing in all browsers.
+}
+
+pre {
+ // Remove browser default top margin
+ margin-top: 0;
+ // Reset browser default of `1em` to use `rem`s
+ margin-bottom: 1rem;
+ // Don't allow content to break outside
+ overflow: auto;
+ // We have @viewport set which causes scrollbars to overlap content in IE11 and Edge, so
+ // we force a non-overlapping, non-auto-hiding scrollbar to counteract.
+ -ms-overflow-style: scrollbar;
+}
+
+
+//
+// Figures
+//
+
+figure {
+ // Apply a consistent margin strategy (matches our type styles).
+ margin: 0 0 1rem;
+}
+
+
+//
+// Images and content
+//
+
+img {
+ vertical-align: middle;
+ border-style: none; // Remove the border on images inside links in IE 10-.
+}
+
+svg {
+ // Workaround for the SVG overflow bug in IE10/11 is still required.
+ // See https://github.com/twbs/bootstrap/issues/26878
+ overflow: hidden;
+ vertical-align: middle;
+}
+
+
+//
+// Tables
+//
+
+table {
+ border-collapse: collapse; // Prevent double borders
+}
+
+caption {
+ padding-top: $table-cell-padding;
+ padding-bottom: $table-cell-padding;
+ color: $table-caption-color;
+ text-align: left;
+ caption-side: bottom;
+}
+
+th {
+ // Matches default ` | ` alignment by inheriting from the ``, or the
+ // closest parent with a set `text-align`.
+ text-align: inherit;
+}
+
+
+//
+// Forms
+//
+
+label {
+ // Allow labels to use `margin` for spacing.
+ display: inline-block;
+ margin-bottom: $label-margin-bottom;
+}
+
+// Remove the default `border-radius` that macOS Chrome adds.
+//
+// Details at https://github.com/twbs/bootstrap/issues/24093
+button {
+ border-radius: 0;
+}
+
+// Work around a Firefox/IE bug where the transparent `button` background
+// results in a loss of the default `button` focus styles.
+//
+// Credit: https://github.com/suitcss/base/
+button:focus {
+ outline: 1px dotted;
+ outline: 5px auto -webkit-focus-ring-color;
+}
+
+input,
+button,
+select,
+optgroup,
+textarea {
+ margin: 0; // Remove the margin in Firefox and Safari
+ font-family: inherit;
+ font-size: inherit;
+ line-height: inherit;
+}
+
+button,
+input {
+ overflow: visible; // Show the overflow in Edge
+}
+
+button,
+select {
+ text-transform: none; // Remove the inheritance of text transform in Firefox
+}
+
+// 1. Prevent a WebKit bug where (2) destroys native `audio` and `video`
+// controls in Android 4.
+// 2. Correct the inability to style clickable types in iOS and Safari.
+button,
+html [type="button"], // 1
+[type="reset"],
+[type="submit"] {
+ -webkit-appearance: button; // 2
+}
+
+// Remove inner border and padding from Firefox, but don't restore the outline like Normalize.
+button::-moz-focus-inner,
+[type="button"]::-moz-focus-inner,
+[type="reset"]::-moz-focus-inner,
+[type="submit"]::-moz-focus-inner {
+ padding: 0;
+ border-style: none;
+}
+
+input[type="radio"],
+input[type="checkbox"] {
+ box-sizing: border-box; // 1. Add the correct box sizing in IE 10-
+ padding: 0; // 2. Remove the padding in IE 10-
+}
+
+
+input[type="date"],
+input[type="time"],
+input[type="datetime-local"],
+input[type="month"] {
+ // Remove the default appearance of temporal inputs to avoid a Mobile Safari
+ // bug where setting a custom line-height prevents text from being vertically
+ // centered within the input.
+ // See https://bugs.webkit.org/show_bug.cgi?id=139848
+ // and https://github.com/twbs/bootstrap/issues/11266
+ -webkit-appearance: listbox;
+}
+
+textarea {
+ overflow: auto; // Remove the default vertical scrollbar in IE.
+ // Textareas should really only resize vertically so they don't break their (horizontal) containers.
+ resize: vertical;
+}
+
+fieldset {
+ // Browsers set a default `min-width: min-content;` on fieldsets,
+ // unlike e.g. ``s, which have `min-width: 0;` by default.
+ // So we reset that to ensure fieldsets behave more like a standard block element.
+ // See https://github.com/twbs/bootstrap/issues/12359
+ // and https://html.spec.whatwg.org/multipage/#the-fieldset-and-legend-elements
+ min-width: 0;
+ // Reset the default outline behavior of fieldsets so they don't affect page layout.
+ padding: 0;
+ margin: 0;
+ border: 0;
+}
+
+// 1. Correct the text wrapping in Edge and IE.
+// 2. Correct the color inheritance from `fieldset` elements in IE.
+legend {
+ display: block;
+ width: 100%;
+ max-width: 100%; // 1
+ padding: 0;
+ margin-bottom: .5rem;
+ font-size: 1.5rem;
+ line-height: inherit;
+ color: inherit; // 2
+ white-space: normal; // 1
+}
+
+progress {
+ vertical-align: baseline; // Add the correct vertical alignment in Chrome, Firefox, and Opera.
+}
+
+// Correct the cursor style of increment and decrement buttons in Chrome.
+[type="number"]::-webkit-inner-spin-button,
+[type="number"]::-webkit-outer-spin-button {
+ height: auto;
+}
+
+[type="search"] {
+ // This overrides the extra rounded corners on search inputs in iOS so that our
+ // `.form-control` class can properly style them. Note that this cannot simply
+ // be added to `.form-control` as it's not specific enough. For details, see
+ // https://github.com/twbs/bootstrap/issues/11586.
+ outline-offset: -2px; // 2. Correct the outline style in Safari.
+ -webkit-appearance: none;
+}
+
+//
+// Remove the inner padding and cancel buttons in Chrome and Safari on macOS.
+//
+
+[type="search"]::-webkit-search-cancel-button,
+[type="search"]::-webkit-search-decoration {
+ -webkit-appearance: none;
+}
+
+//
+// 1. Correct the inability to style clickable types in iOS and Safari.
+// 2. Change font properties to `inherit` in Safari.
+//
+
+::-webkit-file-upload-button {
+ font: inherit; // 2
+ -webkit-appearance: button; // 1
+}
+
+//
+// Correct element displays
+//
+
+output {
+ display: inline-block;
+}
+
+summary {
+ display: list-item; // Add the correct display in all browsers
+ cursor: pointer;
+}
+
+template {
+ display: none; // Add the correct display in IE
+}
+
+// Always hide an element with the `hidden` HTML attribute (from PureCSS).
+// Needed for proper display in IE 10-.
+[hidden] {
+ display: none !important;
+}
diff --git a/site/_scss/bootstrap-4.1.3/_root.scss b/site/_scss/bootstrap-4.1.3/_root.scss
new file mode 100755
index 000000000..ad550df3b
--- /dev/null
+++ b/site/_scss/bootstrap-4.1.3/_root.scss
@@ -0,0 +1,19 @@
+:root {
+ // Custom variable values only support SassScript inside `#{}`.
+ @each $color, $value in $colors {
+ --#{$color}: #{$value};
+ }
+
+ @each $color, $value in $theme-colors {
+ --#{$color}: #{$value};
+ }
+
+ @each $bp, $value in $grid-breakpoints {
+ --breakpoint-#{$bp}: #{$value};
+ }
+
+ // Use `inspect` for lists so that quoted items keep the quotes.
+ // See https://github.com/sass/sass/issues/2383#issuecomment-336349172
+ --font-family-sans-serif: #{inspect($font-family-sans-serif)};
+ --font-family-monospace: #{inspect($font-family-monospace)};
+}
diff --git a/site/_scss/bootstrap-4.1.3/_tables.scss b/site/_scss/bootstrap-4.1.3/_tables.scss
new file mode 100755
index 000000000..5fa6a8662
--- /dev/null
+++ b/site/_scss/bootstrap-4.1.3/_tables.scss
@@ -0,0 +1,187 @@
+//
+// Basic Bootstrap table
+//
+
+.table {
+ width: 100%;
+ margin-bottom: $spacer;
+ background-color: $table-bg; // Reset for nesting within parents with `background-color`.
+
+ th,
+ td {
+ padding: $table-cell-padding;
+ vertical-align: top;
+ border-top: $table-border-width solid $table-border-color;
+ }
+
+ thead th {
+ vertical-align: bottom;
+ border-bottom: (2 * $table-border-width) solid $table-border-color;
+ }
+
+ tbody + tbody {
+ border-top: (2 * $table-border-width) solid $table-border-color;
+ }
+
+ .table {
+ background-color: $body-bg;
+ }
+}
+
+
+//
+// Condensed table w/ half padding
+//
+
+.table-sm {
+ th,
+ td {
+ padding: $table-cell-padding-sm;
+ }
+}
+
+
+// Border versions
+//
+// Add or remove borders all around the table and between all the columns.
+
+.table-bordered {
+ border: $table-border-width solid $table-border-color;
+
+ th,
+ td {
+ border: $table-border-width solid $table-border-color;
+ }
+
+ thead {
+ th,
+ td {
+ border-bottom-width: (2 * $table-border-width);
+ }
+ }
+}
+
+.table-borderless {
+ th,
+ td,
+ thead th,
+ tbody + tbody {
+ border: 0;
+ }
+}
+
+// Zebra-striping
+//
+// Default zebra-stripe styles (alternating gray and transparent backgrounds)
+
+.table-striped {
+ tbody tr:nth-of-type(#{$table-striped-order}) {
+ background-color: $table-accent-bg;
+ }
+}
+
+
+// Hover effect
+//
+// Placed here since it has to come after the potential zebra striping
+
+.table-hover {
+ tbody tr {
+ @include hover {
+ background-color: $table-hover-bg;
+ }
+ }
+}
+
+
+// Table backgrounds
+//
+// Exact selectors below required to override `.table-striped` and prevent
+// inheritance to nested tables.
+
+@each $color, $value in $theme-colors {
+ @include table-row-variant($color, theme-color-level($color, -9));
+}
+
+@include table-row-variant(active, $table-active-bg);
+
+
+// Dark styles
+//
+// Same table markup, but inverted color scheme: dark background and light text.
+
+// stylelint-disable-next-line no-duplicate-selectors
+.table {
+ .thead-dark {
+ th {
+ color: $table-dark-color;
+ background-color: $table-dark-bg;
+ border-color: $table-dark-border-color;
+ }
+ }
+
+ .thead-light {
+ th {
+ color: $table-head-color;
+ background-color: $table-head-bg;
+ border-color: $table-border-color;
+ }
+ }
+}
+
+.table-dark {
+ color: $table-dark-color;
+ background-color: $table-dark-bg;
+
+ th,
+ td,
+ thead th {
+ border-color: $table-dark-border-color;
+ }
+
+ &.table-bordered {
+ border: 0;
+ }
+
+ &.table-striped {
+ tbody tr:nth-of-type(odd) {
+ background-color: $table-dark-accent-bg;
+ }
+ }
+
+ &.table-hover {
+ tbody tr {
+ @include hover {
+ background-color: $table-dark-hover-bg;
+ }
+ }
+ }
+}
+
+
+// Responsive tables
+//
+// Generate series of `.table-responsive-*` classes for configuring the screen
+// size of where your table will overflow.
+
+.table-responsive {
+ @each $breakpoint in map-keys($grid-breakpoints) {
+ $next: breakpoint-next($breakpoint, $grid-breakpoints);
+ $infix: breakpoint-infix($next, $grid-breakpoints);
+
+ &#{$infix} {
+ @include media-breakpoint-down($breakpoint) {
+ display: block;
+ width: 100%;
+ overflow-x: auto;
+ -webkit-overflow-scrolling: touch;
+ -ms-overflow-style: -ms-autohiding-scrollbar; // See https://github.com/twbs/bootstrap/pull/10057
+
+ // Prevent double border on horizontal scroll due to use of `display: block;`
+ > .table-bordered {
+ border: 0;
+ }
+ }
+ }
+ }
+}
diff --git a/site/_scss/bootstrap-4.1.3/_tooltip.scss b/site/_scss/bootstrap-4.1.3/_tooltip.scss
new file mode 100755
index 000000000..1286ebfcf
--- /dev/null
+++ b/site/_scss/bootstrap-4.1.3/_tooltip.scss
@@ -0,0 +1,115 @@
+// Base class
+.tooltip {
+ position: absolute;
+ z-index: $zindex-tooltip;
+ display: block;
+ margin: $tooltip-margin;
+ // Our parent element can be arbitrary since tooltips are by default inserted as a sibling of their target element.
+ // So reset our font and text properties to avoid inheriting weird values.
+ @include reset-text();
+ font-size: $tooltip-font-size;
+ // Allow breaking very long words so they don't overflow the tooltip's bounds
+ word-wrap: break-word;
+ opacity: 0;
+
+ &.show { opacity: $tooltip-opacity; }
+
+ .arrow {
+ position: absolute;
+ display: block;
+ width: $tooltip-arrow-width;
+ height: $tooltip-arrow-height;
+
+ &::before {
+ position: absolute;
+ content: "";
+ border-color: transparent;
+ border-style: solid;
+ }
+ }
+}
+
+.bs-tooltip-top {
+ padding: $tooltip-arrow-height 0;
+
+ .arrow {
+ bottom: 0;
+
+ &::before {
+ top: 0;
+ border-width: $tooltip-arrow-height ($tooltip-arrow-width / 2) 0;
+ border-top-color: $tooltip-arrow-color;
+ }
+ }
+}
+
+.bs-tooltip-right {
+ padding: 0 $tooltip-arrow-height;
+
+ .arrow {
+ left: 0;
+ width: $tooltip-arrow-height;
+ height: $tooltip-arrow-width;
+
+ &::before {
+ right: 0;
+ border-width: ($tooltip-arrow-width / 2) $tooltip-arrow-height ($tooltip-arrow-width / 2) 0;
+ border-right-color: $tooltip-arrow-color;
+ }
+ }
+}
+
+.bs-tooltip-bottom {
+ padding: $tooltip-arrow-height 0;
+
+ .arrow {
+ top: 0;
+
+ &::before {
+ bottom: 0;
+ border-width: 0 ($tooltip-arrow-width / 2) $tooltip-arrow-height;
+ border-bottom-color: $tooltip-arrow-color;
+ }
+ }
+}
+
+.bs-tooltip-left {
+ padding: 0 $tooltip-arrow-height;
+
+ .arrow {
+ right: 0;
+ width: $tooltip-arrow-height;
+ height: $tooltip-arrow-width;
+
+ &::before {
+ left: 0;
+ border-width: ($tooltip-arrow-width / 2) 0 ($tooltip-arrow-width / 2) $tooltip-arrow-height;
+ border-left-color: $tooltip-arrow-color;
+ }
+ }
+}
+
+.bs-tooltip-auto {
+ &[x-placement^="top"] {
+ @extend .bs-tooltip-top;
+ }
+ &[x-placement^="right"] {
+ @extend .bs-tooltip-right;
+ }
+ &[x-placement^="bottom"] {
+ @extend .bs-tooltip-bottom;
+ }
+ &[x-placement^="left"] {
+ @extend .bs-tooltip-left;
+ }
+}
+
+// Wrapper for the tooltip content
+.tooltip-inner {
+ max-width: $tooltip-max-width;
+ padding: $tooltip-padding-y $tooltip-padding-x;
+ color: $tooltip-color;
+ text-align: center;
+ background-color: $tooltip-bg;
+ @include border-radius($tooltip-border-radius);
+}
diff --git a/site/_scss/bootstrap-4.1.3/_transitions.scss b/site/_scss/bootstrap-4.1.3/_transitions.scss
new file mode 100755
index 000000000..c8d91e271
--- /dev/null
+++ b/site/_scss/bootstrap-4.1.3/_transitions.scss
@@ -0,0 +1,22 @@
+// stylelint-disable selector-no-qualifying-type
+
+.fade {
+ @include transition($transition-fade);
+
+ &:not(.show) {
+ opacity: 0;
+ }
+}
+
+.collapse {
+ &:not(.show) {
+ display: none;
+ }
+}
+
+.collapsing {
+ position: relative;
+ height: 0;
+ overflow: hidden;
+ @include transition($transition-collapse);
+}
diff --git a/site/_scss/bootstrap-4.1.3/_type.scss b/site/_scss/bootstrap-4.1.3/_type.scss
new file mode 100755
index 000000000..57d610f0c
--- /dev/null
+++ b/site/_scss/bootstrap-4.1.3/_type.scss
@@ -0,0 +1,125 @@
+// stylelint-disable declaration-no-important, selector-list-comma-newline-after
+
+//
+// Headings
+//
+
+h1, h2, h3, h4, h5, h6,
+.h1, .h2, .h3, .h4, .h5, .h6 {
+ margin-bottom: $headings-margin-bottom;
+ font-family: $headings-font-family;
+ font-weight: $headings-font-weight;
+ line-height: $headings-line-height;
+ color: $headings-color;
+}
+
+h1, .h1 { font-size: $h1-font-size; }
+h2, .h2 { font-size: $h2-font-size; }
+h3, .h3 { font-size: $h3-font-size; }
+h4, .h4 { font-size: $h4-font-size; }
+h5, .h5 { font-size: $h5-font-size; }
+h6, .h6 { font-size: $h6-font-size; }
+
+.lead {
+ font-size: $lead-font-size;
+ font-weight: $lead-font-weight;
+}
+
+// Type display classes
+.display-1 {
+ font-size: $display1-size;
+ font-weight: $display1-weight;
+ line-height: $display-line-height;
+}
+.display-2 {
+ font-size: $display2-size;
+ font-weight: $display2-weight;
+ line-height: $display-line-height;
+}
+.display-3 {
+ font-size: $display3-size;
+ font-weight: $display3-weight;
+ line-height: $display-line-height;
+}
+.display-4 {
+ font-size: $display4-size;
+ font-weight: $display4-weight;
+ line-height: $display-line-height;
+}
+
+
+//
+// Horizontal rules
+//
+
+hr {
+ margin-top: $hr-margin-y;
+ margin-bottom: $hr-margin-y;
+ border: 0;
+ border-top: $hr-border-width solid $hr-border-color;
+}
+
+
+//
+// Emphasis
+//
+
+small,
+.small {
+ font-size: $small-font-size;
+ font-weight: $font-weight-normal;
+}
+
+mark,
+.mark {
+ padding: $mark-padding;
+ background-color: $mark-bg;
+}
+
+
+//
+// Lists
+//
+
+.list-unstyled {
+ @include list-unstyled;
+}
+
+// Inline turns list items into inline-block
+.list-inline {
+ @include list-unstyled;
+}
+.list-inline-item {
+ display: inline-block;
+
+ &:not(:last-child) {
+ margin-right: $list-inline-padding;
+ }
+}
+
+
+//
+// Misc
+//
+
+// Builds on `abbr`
+.initialism {
+ font-size: 90%;
+ text-transform: uppercase;
+}
+
+// Blockquotes
+.blockquote {
+ margin-bottom: $spacer;
+ font-size: $blockquote-font-size;
+}
+
+.blockquote-footer {
+ display: block;
+ font-size: 80%; // back to default font-size
+ color: $blockquote-small-color;
+
+ &::before {
+ content: "\2014 \00A0"; // em dash, nbsp
+ }
+}
diff --git a/site/_scss/bootstrap-4.1.3/_utilities.scss b/site/_scss/bootstrap-4.1.3/_utilities.scss
new file mode 100755
index 000000000..6c7a7cdd3
--- /dev/null
+++ b/site/_scss/bootstrap-4.1.3/_utilities.scss
@@ -0,0 +1,15 @@
+@import "utilities/align";
+@import "utilities/background";
+@import "utilities/borders";
+@import "utilities/clearfix";
+@import "utilities/display";
+@import "utilities/embed";
+@import "utilities/flex";
+@import "utilities/float";
+@import "utilities/position";
+@import "utilities/screenreaders";
+@import "utilities/shadows";
+@import "utilities/sizing";
+@import "utilities/spacing";
+@import "utilities/text";
+@import "utilities/visibility";
diff --git a/site/_scss/bootstrap-4.1.3/_variables.scss b/site/_scss/bootstrap-4.1.3/_variables.scss
new file mode 100755
index 000000000..5cf118f03
--- /dev/null
+++ b/site/_scss/bootstrap-4.1.3/_variables.scss
@@ -0,0 +1,952 @@
+// Variables
+//
+// Variables should follow the `$component-state-property-size` formula for
+// consistent naming. Ex: $nav-link-disabled-color and $modal-content-box-shadow-xs.
+
+
+//
+// Color system
+//
+
+$white: #fff !default;
+$gray-100: #f8f9fa !default;
+$gray-200: #e9ecef !default;
+$gray-300: #dee2e6 !default;
+$gray-400: #ced4da !default;
+$gray-500: #adb5bd !default;
+$gray-600: #6c757d !default;
+$gray-700: #495057 !default;
+$gray-800: #343a40 !default;
+$gray-900: #212529 !default;
+$black: #000 !default;
+
+$grays: () !default;
+// stylelint-disable-next-line scss/dollar-variable-default
+$grays: map-merge(
+ (
+ "100": $gray-100,
+ "200": $gray-200,
+ "300": $gray-300,
+ "400": $gray-400,
+ "500": $gray-500,
+ "600": $gray-600,
+ "700": $gray-700,
+ "800": $gray-800,
+ "900": $gray-900
+ ),
+ $grays
+);
+
+
+$blue: #007bff !default;
+$indigo: #6610f2 !default;
+$purple: #6f42c1 !default;
+$pink: #e83e8c !default;
+$red: #dc3545 !default;
+$orange: #fd7e14 !default;
+$yellow: #ffc107 !default;
+$green: #28a745 !default;
+$teal: #20c997 !default;
+$cyan: #17a2b8 !default;
+
+$colors: () !default;
+// stylelint-disable-next-line scss/dollar-variable-default
+$colors: map-merge(
+ (
+ "blue": $blue,
+ "indigo": $indigo,
+ "purple": $purple,
+ "pink": $pink,
+ "red": $red,
+ "orange": $orange,
+ "yellow": $yellow,
+ "green": $green,
+ "teal": $teal,
+ "cyan": $cyan,
+ "white": $white,
+ "gray": $gray-600,
+ "gray-dark": $gray-800
+ ),
+ $colors
+);
+
+$primary: $blue !default;
+$secondary: $gray-600 !default;
+$success: $green !default;
+$info: $cyan !default;
+$warning: $yellow !default;
+$danger: $red !default;
+$light: $gray-100 !default;
+$dark: $gray-800 !default;
+
+$theme-colors: () !default;
+// stylelint-disable-next-line scss/dollar-variable-default
+$theme-colors: map-merge(
+ (
+ "primary": $primary,
+ "secondary": $secondary,
+ "success": $success,
+ "info": $info,
+ "warning": $warning,
+ "danger": $danger,
+ "light": $light,
+ "dark": $dark
+ ),
+ $theme-colors
+);
+
+// Set a specific jump point for requesting color jumps
+$theme-color-interval: 8% !default;
+
+// The yiq lightness value that determines when the lightness of color changes from "dark" to "light". Acceptable values are between 0 and 255.
+$yiq-contrasted-threshold: 150 !default;
+
+// Customize the light and dark text colors for use in our YIQ color contrast function.
+$yiq-text-dark: $gray-900 !default;
+$yiq-text-light: $white !default;
+
+// Options
+//
+// Quickly modify global styling by enabling or disabling optional features.
+
+$enable-caret: true !default;
+$enable-rounded: true !default;
+$enable-shadows: false !default;
+$enable-gradients: false !default;
+$enable-transitions: true !default;
+$enable-hover-media-query: false !default; // Deprecated, no longer affects any compiled CSS
+$enable-grid-classes: true !default;
+$enable-print-styles: true !default;
+
+
+// Spacing
+//
+// Control the default styling of most Bootstrap elements by modifying these
+// variables. Mostly focused on spacing.
+// You can add more entries to the $spacers map, should you need more variation.
+
+$spacer: 1rem !default;
+$spacers: () !default;
+// stylelint-disable-next-line scss/dollar-variable-default
+$spacers: map-merge(
+ (
+ 0: 0,
+ 1: ($spacer * .25),
+ 2: ($spacer * .5),
+ 3: $spacer,
+ 4: ($spacer * 1.5),
+ 5: ($spacer * 3)
+ ),
+ $spacers
+);
+
+// This variable affects the `.h-*` and `.w-*` classes.
+$sizes: () !default;
+// stylelint-disable-next-line scss/dollar-variable-default
+$sizes: map-merge(
+ (
+ 25: 25%,
+ 50: 50%,
+ 75: 75%,
+ 100: 100%,
+ auto: auto
+ ),
+ $sizes
+);
+
+// Body
+//
+// Settings for the `` element.
+
+$body-bg: $white !default;
+$body-color: $gray-900 !default;
+
+// Links
+//
+// Style anchor elements.
+
+$link-color: theme-color("primary") !default;
+$link-decoration: none !default;
+$link-hover-color: darken($link-color, 15%) !default;
+$link-hover-decoration: underline !default;
+
+// Paragraphs
+//
+// Style p element.
+
+$paragraph-margin-bottom: 1rem !default;
+
+
+// Grid breakpoints
+//
+// Define the minimum dimensions at which your layout will change,
+// adapting to different screen sizes, for use in media queries.
+
+$grid-breakpoints: (
+ xs: 0,
+ sm: 576px,
+ md: 768px,
+ lg: 992px,
+ xl: 1200px
+) !default;
+
+@include _assert-ascending($grid-breakpoints, "$grid-breakpoints");
+@include _assert-starts-at-zero($grid-breakpoints);
+
+
+// Grid containers
+//
+// Define the maximum width of `.container` for different screen sizes.
+
+$container-max-widths: (
+ sm: 540px,
+ md: 720px,
+ lg: 960px,
+ xl: 1140px
+) !default;
+
+@include _assert-ascending($container-max-widths, "$container-max-widths");
+
+
+// Grid columns
+//
+// Set the number of columns and specify the width of the gutters.
+
+$grid-columns: 12 !default;
+$grid-gutter-width: 30px !default;
+
+// Components
+//
+// Define common padding and border radius sizes and more.
+
+$line-height-lg: 1.5 !default;
+$line-height-sm: 1.5 !default;
+
+$border-width: 1px !default;
+$border-color: $gray-300 !default;
+
+$border-radius: .25rem !default;
+$border-radius-lg: .3rem !default;
+$border-radius-sm: .2rem !default;
+
+$box-shadow-sm: 0 .125rem .25rem rgba($black, .075) !default;
+$box-shadow: 0 .5rem 1rem rgba($black, .15) !default;
+$box-shadow-lg: 0 1rem 3rem rgba($black, .175) !default;
+
+$component-active-color: $white !default;
+$component-active-bg: theme-color("primary") !default;
+
+$caret-width: .3em !default;
+
+$transition-base: all .2s ease-in-out !default;
+$transition-fade: opacity .15s linear !default;
+$transition-collapse: height .35s ease !default;
+
+
+// Fonts
+//
+// Font, line-height, and color for body text, headings, and more.
+
+// stylelint-disable value-keyword-case
+$font-family-sans-serif: -apple-system, BlinkMacSystemFont, "Segoe UI", Roboto, "Helvetica Neue", Arial, sans-serif, "Apple Color Emoji", "Segoe UI Emoji", "Segoe UI Symbol", "Noto Color Emoji" !default;
+$font-family-monospace: SFMono-Regular, Menlo, Monaco, Consolas, "Liberation Mono", "Courier New", monospace !default;
+$font-family-base: $font-family-sans-serif !default;
+// stylelint-enable value-keyword-case
+
+$font-size-base: 1rem !default; // Assumes the browser default, typically `16px`
+$font-size-lg: ($font-size-base * 1.25) !default;
+$font-size-sm: ($font-size-base * .875) !default;
+
+$font-weight-light: 300 !default;
+$font-weight-normal: 400 !default;
+$font-weight-bold: 700 !default;
+
+$font-weight-base: $font-weight-normal !default;
+$line-height-base: 1.5 !default;
+
+$h1-font-size: $font-size-base * 2.5 !default;
+$h2-font-size: $font-size-base * 2 !default;
+$h3-font-size: $font-size-base * 1.75 !default;
+$h4-font-size: $font-size-base * 1.5 !default;
+$h5-font-size: $font-size-base * 1.25 !default;
+$h6-font-size: $font-size-base !default;
+
+$headings-margin-bottom: ($spacer / 2) !default;
+$headings-font-family: inherit !default;
+$headings-font-weight: 500 !default;
+$headings-line-height: 1.2 !default;
+$headings-color: inherit !default;
+
+$display1-size: 6rem !default;
+$display2-size: 5.5rem !default;
+$display3-size: 4.5rem !default;
+$display4-size: 3.5rem !default;
+
+$display1-weight: 300 !default;
+$display2-weight: 300 !default;
+$display3-weight: 300 !default;
+$display4-weight: 300 !default;
+$display-line-height: $headings-line-height !default;
+
+$lead-font-size: ($font-size-base * 1.25) !default;
+$lead-font-weight: 300 !default;
+
+$small-font-size: 80% !default;
+
+$text-muted: $gray-600 !default;
+
+$blockquote-small-color: $gray-600 !default;
+$blockquote-font-size: ($font-size-base * 1.25) !default;
+
+$hr-border-color: rgba($black, .1) !default;
+$hr-border-width: $border-width !default;
+
+$mark-padding: .2em !default;
+
+$dt-font-weight: $font-weight-bold !default;
+
+$kbd-box-shadow: inset 0 -.1rem 0 rgba($black, .25) !default;
+$nested-kbd-font-weight: $font-weight-bold !default;
+
+$list-inline-padding: .5rem !default;
+
+$mark-bg: #fcf8e3 !default;
+
+$hr-margin-y: $spacer !default;
+
+
+// Tables
+//
+// Customizes the `.table` component with basic values, each used across all table variations.
+
+$table-cell-padding: .75rem !default;
+$table-cell-padding-sm: .3rem !default;
+
+$table-bg: transparent !default;
+$table-accent-bg: rgba($black, .05) !default;
+$table-hover-bg: rgba($black, .075) !default;
+$table-active-bg: $table-hover-bg !default;
+
+$table-border-width: $border-width !default;
+$table-border-color: $gray-300 !default;
+
+$table-head-bg: $gray-200 !default;
+$table-head-color: $gray-700 !default;
+
+$table-dark-bg: $gray-900 !default;
+$table-dark-accent-bg: rgba($white, .05) !default;
+$table-dark-hover-bg: rgba($white, .075) !default;
+$table-dark-border-color: lighten($gray-900, 7.5%) !default;
+$table-dark-color: $body-bg !default;
+
+$table-striped-order: odd !default;
+
+$table-caption-color: $text-muted !default;
+
+// Buttons + Forms
+//
+// Shared variables that are reassigned to `$input-` and `$btn-` specific variables.
+
+$input-btn-padding-y: .375rem !default;
+$input-btn-padding-x: .75rem !default;
+$input-btn-line-height: $line-height-base !default;
+
+$input-btn-focus-width: .2rem !default;
+$input-btn-focus-color: rgba($component-active-bg, .25) !default;
+$input-btn-focus-box-shadow: 0 0 0 $input-btn-focus-width $input-btn-focus-color !default;
+
+$input-btn-padding-y-sm: .25rem !default;
+$input-btn-padding-x-sm: .5rem !default;
+$input-btn-line-height-sm: $line-height-sm !default;
+
+$input-btn-padding-y-lg: .5rem !default;
+$input-btn-padding-x-lg: 1rem !default;
+$input-btn-line-height-lg: $line-height-lg !default;
+
+$input-btn-border-width: $border-width !default;
+
+
+// Buttons
+//
+// For each of Bootstrap's buttons, define text, background, and border color.
+
+$btn-padding-y: $input-btn-padding-y !default;
+$btn-padding-x: $input-btn-padding-x !default;
+$btn-line-height: $input-btn-line-height !default;
+
+$btn-padding-y-sm: $input-btn-padding-y-sm !default;
+$btn-padding-x-sm: $input-btn-padding-x-sm !default;
+$btn-line-height-sm: $input-btn-line-height-sm !default;
+
+$btn-padding-y-lg: $input-btn-padding-y-lg !default;
+$btn-padding-x-lg: $input-btn-padding-x-lg !default;
+$btn-line-height-lg: $input-btn-line-height-lg !default;
+
+$btn-border-width: $input-btn-border-width !default;
+
+$btn-font-weight: $font-weight-normal !default;
+$btn-box-shadow: inset 0 1px 0 rgba($white, .15), 0 1px 1px rgba($black, .075) !default;
+$btn-focus-width: $input-btn-focus-width !default;
+$btn-focus-box-shadow: $input-btn-focus-box-shadow !default;
+$btn-disabled-opacity: .65 !default;
+$btn-active-box-shadow: inset 0 3px 5px rgba($black, .125) !default;
+
+$btn-link-disabled-color: $gray-600 !default;
+
+$btn-block-spacing-y: .5rem !default;
+
+// Allows for customizing button radius independently from global border radius
+$btn-border-radius: $border-radius !default;
+$btn-border-radius-lg: $border-radius-lg !default;
+$btn-border-radius-sm: $border-radius-sm !default;
+
+$btn-transition: color .15s ease-in-out, background-color .15s ease-in-out, border-color .15s ease-in-out, box-shadow .15s ease-in-out !default;
+
+
+// Forms
+
+$label-margin-bottom: .5rem !default;
+
+$input-padding-y: $input-btn-padding-y !default;
+$input-padding-x: $input-btn-padding-x !default;
+$input-line-height: $input-btn-line-height !default;
+
+$input-padding-y-sm: $input-btn-padding-y-sm !default;
+$input-padding-x-sm: $input-btn-padding-x-sm !default;
+$input-line-height-sm: $input-btn-line-height-sm !default;
+
+$input-padding-y-lg: $input-btn-padding-y-lg !default;
+$input-padding-x-lg: $input-btn-padding-x-lg !default;
+$input-line-height-lg: $input-btn-line-height-lg !default;
+
+$input-bg: $white !default;
+$input-disabled-bg: $gray-200 !default;
+
+$input-color: $gray-700 !default;
+$input-border-color: $gray-400 !default;
+$input-border-width: $input-btn-border-width !default;
+$input-box-shadow: inset 0 1px 1px rgba($black, .075) !default;
+
+$input-border-radius: $border-radius !default;
+$input-border-radius-lg: $border-radius-lg !default;
+$input-border-radius-sm: $border-radius-sm !default;
+
+$input-focus-bg: $input-bg !default;
+$input-focus-border-color: lighten($component-active-bg, 25%) !default;
+$input-focus-color: $input-color !default;
+$input-focus-width: $input-btn-focus-width !default;
+$input-focus-box-shadow: $input-btn-focus-box-shadow !default;
+
+$input-placeholder-color: $gray-600 !default;
+$input-plaintext-color: $body-color !default;
+
+$input-height-border: $input-border-width * 2 !default;
+
+$input-height-inner: ($font-size-base * $input-btn-line-height) + ($input-btn-padding-y * 2) !default;
+$input-height: calc(#{$input-height-inner} + #{$input-height-border}) !default;
+
+$input-height-inner-sm: ($font-size-sm * $input-btn-line-height-sm) + ($input-btn-padding-y-sm * 2) !default;
+$input-height-sm: calc(#{$input-height-inner-sm} + #{$input-height-border}) !default;
+
+$input-height-inner-lg: ($font-size-lg * $input-btn-line-height-lg) + ($input-btn-padding-y-lg * 2) !default;
+$input-height-lg: calc(#{$input-height-inner-lg} + #{$input-height-border}) !default;
+
+$input-transition: border-color .15s ease-in-out, box-shadow .15s ease-in-out !default;
+
+$form-text-margin-top: .25rem !default;
+
+$form-check-input-gutter: 1.25rem !default;
+$form-check-input-margin-y: .3rem !default;
+$form-check-input-margin-x: .25rem !default;
+
+$form-check-inline-margin-x: .75rem !default;
+$form-check-inline-input-margin-x: .3125rem !default;
+
+$form-group-margin-bottom: 1rem !default;
+
+$input-group-addon-color: $input-color !default;
+$input-group-addon-bg: $gray-200 !default;
+$input-group-addon-border-color: $input-border-color !default;
+
+$custom-forms-transition: background-color .15s ease-in-out, border-color .15s ease-in-out, box-shadow .15s ease-in-out !default;
+
+$custom-control-gutter: 1.5rem !default;
+$custom-control-spacer-x: 1rem !default;
+
+$custom-control-indicator-size: 1rem !default;
+$custom-control-indicator-bg: $gray-300 !default;
+$custom-control-indicator-bg-size: 50% 50% !default;
+$custom-control-indicator-box-shadow: inset 0 .25rem .25rem rgba($black, .1) !default;
+
+$custom-control-indicator-disabled-bg: $gray-200 !default;
+$custom-control-label-disabled-color: $gray-600 !default;
+
+$custom-control-indicator-checked-color: $component-active-color !default;
+$custom-control-indicator-checked-bg: $component-active-bg !default;
+$custom-control-indicator-checked-disabled-bg: rgba(theme-color("primary"), .5) !default;
+$custom-control-indicator-checked-box-shadow: none !default;
+
+$custom-control-indicator-focus-box-shadow: 0 0 0 1px $body-bg, $input-btn-focus-box-shadow !default;
+
+$custom-control-indicator-active-color: $component-active-color !default;
+$custom-control-indicator-active-bg: lighten($component-active-bg, 35%) !default;
+$custom-control-indicator-active-box-shadow: none !default;
+
+$custom-checkbox-indicator-border-radius: $border-radius !default;
+$custom-checkbox-indicator-icon-checked: str-replace(url("data:image/svg+xml;charset=utf8,%3Csvg xmlns='http://www.w3.org/2000/svg' viewBox='0 0 8 8'%3E%3Cpath fill='#{$custom-control-indicator-checked-color}' d='M6.564.75l-3.59 3.612-1.538-1.55L0 4.26 2.974 7.25 8 2.193z'/%3E%3C/svg%3E"), "#", "%23") !default;
+
+$custom-checkbox-indicator-indeterminate-bg: $component-active-bg !default;
+$custom-checkbox-indicator-indeterminate-color: $custom-control-indicator-checked-color !default;
+$custom-checkbox-indicator-icon-indeterminate: str-replace(url("data:image/svg+xml;charset=utf8,%3Csvg xmlns='http://www.w3.org/2000/svg' viewBox='0 0 4 4'%3E%3Cpath stroke='#{$custom-checkbox-indicator-indeterminate-color}' d='M0 2h4'/%3E%3C/svg%3E"), "#", "%23") !default;
+$custom-checkbox-indicator-indeterminate-box-shadow: none !default;
+
+$custom-radio-indicator-border-radius: 50% !default;
+$custom-radio-indicator-icon-checked: str-replace(url("data:image/svg+xml;charset=utf8,%3Csvg xmlns='http://www.w3.org/2000/svg' viewBox='-4 -4 8 8'%3E%3Ccircle r='3' fill='#{$custom-control-indicator-checked-color}'/%3E%3C/svg%3E"), "#", "%23") !default;
+
+$custom-select-padding-y: .375rem !default;
+$custom-select-padding-x: .75rem !default;
+$custom-select-height: $input-height !default;
+$custom-select-indicator-padding: 1rem !default; // Extra padding to account for the presence of the background-image based indicator
+$custom-select-line-height: $input-btn-line-height !default;
+$custom-select-color: $input-color !default;
+$custom-select-disabled-color: $gray-600 !default;
+$custom-select-bg: $input-bg !default;
+$custom-select-disabled-bg: $gray-200 !default;
+$custom-select-bg-size: 8px 10px !default; // In pixels because image dimensions
+$custom-select-indicator-color: $gray-800 !default;
+$custom-select-indicator: str-replace(url("data:image/svg+xml;charset=utf8,%3Csvg xmlns='http://www.w3.org/2000/svg' viewBox='0 0 4 5'%3E%3Cpath fill='#{$custom-select-indicator-color}' d='M2 0L0 2h4zm0 5L0 3h4z'/%3E%3C/svg%3E"), "#", "%23") !default;
+$custom-select-border-width: $input-btn-border-width !default;
+$custom-select-border-color: $input-border-color !default;
+$custom-select-border-radius: $border-radius !default;
+$custom-select-box-shadow: inset 0 1px 2px rgba($black, .075) !default;
+
+$custom-select-focus-border-color: $input-focus-border-color !default;
+$custom-select-focus-width: $input-btn-focus-width !default;
+$custom-select-focus-box-shadow: 0 0 0 $custom-select-focus-width rgba($custom-select-focus-border-color, .5) !default;
+
+$custom-select-font-size-sm: 75% !default;
+$custom-select-height-sm: $input-height-sm !default;
+
+$custom-select-font-size-lg: 125% !default;
+$custom-select-height-lg: $input-height-lg !default;
+
+$custom-range-track-width: 100% !default;
+$custom-range-track-height: .5rem !default;
+$custom-range-track-cursor: pointer !default;
+$custom-range-track-bg: $gray-300 !default;
+$custom-range-track-border-radius: 1rem !default;
+$custom-range-track-box-shadow: inset 0 .25rem .25rem rgba($black, .1) !default;
+
+$custom-range-thumb-width: 1rem !default;
+$custom-range-thumb-height: $custom-range-thumb-width !default;
+$custom-range-thumb-bg: $component-active-bg !default;
+$custom-range-thumb-border: 0 !default;
+$custom-range-thumb-border-radius: 1rem !default;
+$custom-range-thumb-box-shadow: 0 .1rem .25rem rgba($black, .1) !default;
+$custom-range-thumb-focus-box-shadow: 0 0 0 1px $body-bg, $input-btn-focus-box-shadow !default;
+$custom-range-thumb-focus-box-shadow-width: $input-btn-focus-width !default; // For focus box shadow issue in IE/Edge
+$custom-range-thumb-active-bg: lighten($component-active-bg, 35%) !default;
+
+$custom-file-height: $input-height !default;
+$custom-file-height-inner: $input-height-inner !default;
+$custom-file-focus-border-color: $input-focus-border-color !default;
+$custom-file-focus-box-shadow: $input-btn-focus-box-shadow !default;
+$custom-file-disabled-bg: $input-disabled-bg !default;
+
+$custom-file-padding-y: $input-btn-padding-y !default;
+$custom-file-padding-x: $input-btn-padding-x !default;
+$custom-file-line-height: $input-btn-line-height !default;
+$custom-file-color: $input-color !default;
+$custom-file-bg: $input-bg !default;
+$custom-file-border-width: $input-btn-border-width !default;
+$custom-file-border-color: $input-border-color !default;
+$custom-file-border-radius: $input-border-radius !default;
+$custom-file-box-shadow: $input-box-shadow !default;
+$custom-file-button-color: $custom-file-color !default;
+$custom-file-button-bg: $input-group-addon-bg !default;
+$custom-file-text: (
+ en: "Browse"
+) !default;
+
+
+// Form validation
+$form-feedback-margin-top: $form-text-margin-top !default;
+$form-feedback-font-size: $small-font-size !default;
+$form-feedback-valid-color: theme-color("success") !default;
+$form-feedback-invalid-color: theme-color("danger") !default;
+
+
+// Dropdowns
+//
+// Dropdown menu container and contents.
+
+$dropdown-min-width: 10rem !default;
+$dropdown-padding-y: .5rem !default;
+$dropdown-spacer: .125rem !default;
+$dropdown-bg: $white !default;
+$dropdown-border-color: rgba($black, .15) !default;
+$dropdown-border-radius: $border-radius !default;
+$dropdown-border-width: $border-width !default;
+$dropdown-divider-bg: $gray-200 !default;
+$dropdown-box-shadow: 0 .5rem 1rem rgba($black, .175) !default;
+
+$dropdown-link-color: $gray-900 !default;
+$dropdown-link-hover-color: darken($gray-900, 5%) !default;
+$dropdown-link-hover-bg: $gray-100 !default;
+
+$dropdown-link-active-color: $component-active-color !default;
+$dropdown-link-active-bg: $component-active-bg !default;
+
+$dropdown-link-disabled-color: $gray-600 !default;
+
+$dropdown-item-padding-y: .25rem !default;
+$dropdown-item-padding-x: 1.5rem !default;
+
+$dropdown-header-color: $gray-600 !default;
+
+
+// Z-index master list
+//
+// Warning: Avoid customizing these values. They're used for a bird's eye view
+// of components dependent on the z-axis and are designed to all work together.
+
+$zindex-dropdown: 1000 !default;
+$zindex-sticky: 1020 !default;
+$zindex-fixed: 1030 !default;
+$zindex-modal-backdrop: 1040 !default;
+$zindex-modal: 1050 !default;
+$zindex-popover: 1060 !default;
+$zindex-tooltip: 1070 !default;
+
+// Navs
+
+$nav-link-padding-y: .5rem !default;
+$nav-link-padding-x: 1rem !default;
+$nav-link-disabled-color: $gray-600 !default;
+
+$nav-tabs-border-color: $gray-300 !default;
+$nav-tabs-border-width: $border-width !default;
+$nav-tabs-border-radius: $border-radius !default;
+$nav-tabs-link-hover-border-color: $gray-200 $gray-200 $nav-tabs-border-color !default;
+$nav-tabs-link-active-color: $gray-700 !default;
+$nav-tabs-link-active-bg: $body-bg !default;
+$nav-tabs-link-active-border-color: $gray-300 $gray-300 $nav-tabs-link-active-bg !default;
+
+$nav-pills-border-radius: $border-radius !default;
+$nav-pills-link-active-color: $component-active-color !default;
+$nav-pills-link-active-bg: $component-active-bg !default;
+
+$nav-divider-color: $gray-200 !default;
+$nav-divider-margin-y: ($spacer / 2) !default;
+
+// Navbar
+
+$navbar-padding-y: ($spacer / 2) !default;
+$navbar-padding-x: $spacer !default;
+
+$navbar-nav-link-padding-x: .5rem !default;
+
+$navbar-brand-font-size: $font-size-lg !default;
+// Compute the navbar-brand padding-y so the navbar-brand will have the same height as navbar-text and nav-link
+$nav-link-height: ($font-size-base * $line-height-base + $nav-link-padding-y * 2) !default;
+$navbar-brand-height: $navbar-brand-font-size * $line-height-base !default;
+$navbar-brand-padding-y: ($nav-link-height - $navbar-brand-height) / 2 !default;
+
+$navbar-toggler-padding-y: .25rem !default;
+$navbar-toggler-padding-x: .75rem !default;
+$navbar-toggler-font-size: $font-size-lg !default;
+$navbar-toggler-border-radius: $btn-border-radius !default;
+
+$navbar-dark-color: rgba($white, .5) !default;
+$navbar-dark-hover-color: rgba($white, .75) !default;
+$navbar-dark-active-color: $white !default;
+$navbar-dark-disabled-color: rgba($white, .25) !default;
+$navbar-dark-toggler-icon-bg: str-replace(url("data:image/svg+xml;charset=utf8,%3Csvg viewBox='0 0 30 30' xmlns='http://www.w3.org/2000/svg'%3E%3Cpath stroke='#{$navbar-dark-color}' stroke-width='2' stroke-linecap='round' stroke-miterlimit='10' d='M4 7h22M4 15h22M4 23h22'/%3E%3C/svg%3E"), "#", "%23") !default;
+$navbar-dark-toggler-border-color: rgba($white, .1) !default;
+
+$navbar-light-color: rgba($black, .5) !default;
+$navbar-light-hover-color: rgba($black, .7) !default;
+$navbar-light-active-color: rgba($black, .9) !default;
+$navbar-light-disabled-color: rgba($black, .3) !default;
+$navbar-light-toggler-icon-bg: str-replace(url("data:image/svg+xml;charset=utf8,%3Csvg viewBox='0 0 30 30' xmlns='http://www.w3.org/2000/svg'%3E%3Cpath stroke='#{$navbar-light-color}' stroke-width='2' stroke-linecap='round' stroke-miterlimit='10' d='M4 7h22M4 15h22M4 23h22'/%3E%3C/svg%3E"), "#", "%23") !default;
+$navbar-light-toggler-border-color: rgba($black, .1) !default;
+
+// Pagination
+
+$pagination-padding-y: .5rem !default;
+$pagination-padding-x: .75rem !default;
+$pagination-padding-y-sm: .25rem !default;
+$pagination-padding-x-sm: .5rem !default;
+$pagination-padding-y-lg: .75rem !default;
+$pagination-padding-x-lg: 1.5rem !default;
+$pagination-line-height: 1.25 !default;
+
+$pagination-color: $link-color !default;
+$pagination-bg: $white !default;
+$pagination-border-width: $border-width !default;
+$pagination-border-color: $gray-300 !default;
+
+$pagination-focus-box-shadow: $input-btn-focus-box-shadow !default;
+$pagination-focus-outline: 0 !default;
+
+$pagination-hover-color: $link-hover-color !default;
+$pagination-hover-bg: $gray-200 !default;
+$pagination-hover-border-color: $gray-300 !default;
+
+$pagination-active-color: $component-active-color !default;
+$pagination-active-bg: $component-active-bg !default;
+$pagination-active-border-color: $pagination-active-bg !default;
+
+$pagination-disabled-color: $gray-600 !default;
+$pagination-disabled-bg: $white !default;
+$pagination-disabled-border-color: $gray-300 !default;
+
+
+// Jumbotron
+
+$jumbotron-padding: 2rem !default;
+$jumbotron-bg: $gray-200 !default;
+
+
+// Cards
+
+$card-spacer-y: .75rem !default;
+$card-spacer-x: 1.25rem !default;
+$card-border-width: $border-width !default;
+$card-border-radius: $border-radius !default;
+$card-border-color: rgba($black, .125) !default;
+$card-inner-border-radius: calc(#{$card-border-radius} - #{$card-border-width}) !default;
+$card-cap-bg: rgba($black, .03) !default;
+$card-bg: $white !default;
+
+$card-img-overlay-padding: 1.25rem !default;
+
+$card-group-margin: ($grid-gutter-width / 2) !default;
+$card-deck-margin: $card-group-margin !default;
+
+$card-columns-count: 3 !default;
+$card-columns-gap: 1.25rem !default;
+$card-columns-margin: $card-spacer-y !default;
+
+
+// Tooltips
+
+$tooltip-font-size: $font-size-sm !default;
+$tooltip-max-width: 200px !default;
+$tooltip-color: $white !default;
+$tooltip-bg: $black !default;
+$tooltip-border-radius: $border-radius !default;
+$tooltip-opacity: .9 !default;
+$tooltip-padding-y: .25rem !default;
+$tooltip-padding-x: .5rem !default;
+$tooltip-margin: 0 !default;
+
+$tooltip-arrow-width: .8rem !default;
+$tooltip-arrow-height: .4rem !default;
+$tooltip-arrow-color: $tooltip-bg !default;
+
+
+// Popovers
+
+$popover-font-size: $font-size-sm !default;
+$popover-bg: $white !default;
+$popover-max-width: 276px !default;
+$popover-border-width: $border-width !default;
+$popover-border-color: rgba($black, .2) !default;
+$popover-border-radius: $border-radius-lg !default;
+$popover-box-shadow: 0 .25rem .5rem rgba($black, .2) !default;
+
+$popover-header-bg: darken($popover-bg, 3%) !default;
+$popover-header-color: $headings-color !default;
+$popover-header-padding-y: .5rem !default;
+$popover-header-padding-x: .75rem !default;
+
+$popover-body-color: $body-color !default;
+$popover-body-padding-y: $popover-header-padding-y !default;
+$popover-body-padding-x: $popover-header-padding-x !default;
+
+$popover-arrow-width: 1rem !default;
+$popover-arrow-height: .5rem !default;
+$popover-arrow-color: $popover-bg !default;
+
+$popover-arrow-outer-color: fade-in($popover-border-color, .05) !default;
+
+
+// Badges
+
+$badge-font-size: 75% !default;
+$badge-font-weight: $font-weight-bold !default;
+$badge-padding-y: .25em !default;
+$badge-padding-x: .4em !default;
+$badge-border-radius: $border-radius !default;
+
+$badge-pill-padding-x: .6em !default;
+// Use a higher than normal value to ensure completely rounded edges when
+// customizing padding or font-size on labels.
+$badge-pill-border-radius: 10rem !default;
+
+
+// Modals
+
+// Padding applied to the modal body
+$modal-inner-padding: 1rem !default;
+
+$modal-dialog-margin: .5rem !default;
+$modal-dialog-margin-y-sm-up: 1.75rem !default;
+
+$modal-title-line-height: $line-height-base !default;
+
+$modal-content-bg: $white !default;
+$modal-content-border-color: rgba($black, .2) !default;
+$modal-content-border-width: $border-width !default;
+$modal-content-border-radius: $border-radius-lg !default;
+$modal-content-box-shadow-xs: 0 .25rem .5rem rgba($black, .5) !default;
+$modal-content-box-shadow-sm-up: 0 .5rem 1rem rgba($black, .5) !default;
+
+$modal-backdrop-bg: $black !default;
+$modal-backdrop-opacity: .5 !default;
+$modal-header-border-color: $gray-200 !default;
+$modal-footer-border-color: $modal-header-border-color !default;
+$modal-header-border-width: $modal-content-border-width !default;
+$modal-footer-border-width: $modal-header-border-width !default;
+$modal-header-padding: 1rem !default;
+
+$modal-lg: 800px !default;
+$modal-md: 500px !default;
+$modal-sm: 300px !default;
+
+$modal-transition: transform .3s ease-out !default;
+
+
+// Alerts
+//
+// Define alert colors, border radius, and padding.
+
+$alert-padding-y: .75rem !default;
+$alert-padding-x: 1.25rem !default;
+$alert-margin-bottom: 1rem !default;
+$alert-border-radius: $border-radius !default;
+$alert-link-font-weight: $font-weight-bold !default;
+$alert-border-width: $border-width !default;
+
+$alert-bg-level: -10 !default;
+$alert-border-level: -9 !default;
+$alert-color-level: 6 !default;
+
+
+// Progress bars
+
+$progress-height: 1rem !default;
+$progress-font-size: ($font-size-base * .75) !default;
+$progress-bg: $gray-200 !default;
+$progress-border-radius: $border-radius !default;
+$progress-box-shadow: inset 0 .1rem .1rem rgba($black, .1) !default;
+$progress-bar-color: $white !default;
+$progress-bar-bg: theme-color("primary") !default;
+$progress-bar-animation-timing: 1s linear infinite !default;
+$progress-bar-transition: width .6s ease !default;
+
+// List group
+
+$list-group-bg: $white !default;
+$list-group-border-color: rgba($black, .125) !default;
+$list-group-border-width: $border-width !default;
+$list-group-border-radius: $border-radius !default;
+
+$list-group-item-padding-y: .75rem !default;
+$list-group-item-padding-x: 1.25rem !default;
+
+$list-group-hover-bg: $gray-100 !default;
+$list-group-active-color: $component-active-color !default;
+$list-group-active-bg: $component-active-bg !default;
+$list-group-active-border-color: $list-group-active-bg !default;
+
+$list-group-disabled-color: $gray-600 !default;
+$list-group-disabled-bg: $list-group-bg !default;
+
+$list-group-action-color: $gray-700 !default;
+$list-group-action-hover-color: $list-group-action-color !default;
+
+$list-group-action-active-color: $body-color !default;
+$list-group-action-active-bg: $gray-200 !default;
+
+
+// Image thumbnails
+
+$thumbnail-padding: .25rem !default;
+$thumbnail-bg: $body-bg !default;
+$thumbnail-border-width: $border-width !default;
+$thumbnail-border-color: $gray-300 !default;
+$thumbnail-border-radius: $border-radius !default;
+$thumbnail-box-shadow: 0 1px 2px rgba($black, .075) !default;
+
+
+// Figures
+
+$figure-caption-font-size: 90% !default;
+$figure-caption-color: $gray-600 !default;
+
+
+// Breadcrumbs
+
+$breadcrumb-padding-y: .75rem !default;
+$breadcrumb-padding-x: 1rem !default;
+$breadcrumb-item-padding: .5rem !default;
+
+$breadcrumb-margin-bottom: 1rem !default;
+
+$breadcrumb-bg: $gray-200 !default;
+$breadcrumb-divider-color: $gray-600 !default;
+$breadcrumb-active-color: $gray-600 !default;
+$breadcrumb-divider: quote("/") !default;
+
+$breadcrumb-border-radius: $border-radius !default;
+
+
+// Carousel
+
+$carousel-control-color: $white !default;
+$carousel-control-width: 15% !default;
+$carousel-control-opacity: .5 !default;
+
+$carousel-indicator-width: 30px !default;
+$carousel-indicator-height: 3px !default;
+$carousel-indicator-spacer: 3px !default;
+$carousel-indicator-active-bg: $white !default;
+
+$carousel-caption-width: 70% !default;
+$carousel-caption-color: $white !default;
+
+$carousel-control-icon-width: 20px !default;
+
+$carousel-control-prev-icon-bg: str-replace(url("data:image/svg+xml;charset=utf8,%3Csvg xmlns='http://www.w3.org/2000/svg' fill='#{$carousel-control-color}' viewBox='0 0 8 8'%3E%3Cpath d='M5.25 0l-4 4 4 4 1.5-1.5-2.5-2.5 2.5-2.5-1.5-1.5z'/%3E%3C/svg%3E"), "#", "%23") !default;
+$carousel-control-next-icon-bg: str-replace(url("data:image/svg+xml;charset=utf8,%3Csvg xmlns='http://www.w3.org/2000/svg' fill='#{$carousel-control-color}' viewBox='0 0 8 8'%3E%3Cpath d='M2.75 0l-1.5 1.5 2.5 2.5-2.5 2.5 1.5 1.5 4-4-4-4z'/%3E%3C/svg%3E"), "#", "%23") !default;
+
+$carousel-transition: transform .6s ease !default; // Define transform transition first if using multiple transitions (e.g., `transform 2s ease, opacity .5s ease-out`)
+
+
+// Close
+
+$close-font-size: $font-size-base * 1.5 !default;
+$close-font-weight: $font-weight-bold !default;
+$close-color: $black !default;
+$close-text-shadow: 0 1px 0 $white !default;
+
+// Code
+
+$code-font-size: 87.5% !default;
+$code-color: $pink !default;
+
+$kbd-padding-y: .2rem !default;
+$kbd-padding-x: .4rem !default;
+$kbd-font-size: $code-font-size !default;
+$kbd-color: $white !default;
+$kbd-bg: $gray-900 !default;
+
+$pre-color: $gray-900 !default;
+$pre-scrollable-max-height: 340px !default;
+
+
+// Printing
+$print-page-size: a3 !default;
+$print-body-min-width: map-get($grid-breakpoints, "lg") !default;
diff --git a/site/_scss/bootstrap-4.1.3/bootstrap-grid.scss b/site/_scss/bootstrap-4.1.3/bootstrap-grid.scss
new file mode 100755
index 000000000..509171d4d
--- /dev/null
+++ b/site/_scss/bootstrap-4.1.3/bootstrap-grid.scss
@@ -0,0 +1,32 @@
+/*!
+ * Bootstrap Grid v4.1.3 (https://getbootstrap.com/)
+ * Copyright 2011-2018 The Bootstrap Authors
+ * Copyright 2011-2018 Twitter, Inc.
+ * Licensed under MIT (https://github.com/twbs/bootstrap/blob/master/LICENSE)
+ */
+
+@at-root {
+ @-ms-viewport { width: device-width; } // stylelint-disable-line at-rule-no-vendor-prefix
+}
+
+html {
+ box-sizing: border-box;
+ -ms-overflow-style: scrollbar;
+}
+
+*,
+*::before,
+*::after {
+ box-sizing: inherit;
+}
+
+@import "functions";
+@import "variables";
+
+@import "mixins/breakpoints";
+@import "mixins/grid-framework";
+@import "mixins/grid";
+
+@import "grid";
+@import "utilities/display";
+@import "utilities/flex";
diff --git a/site/_scss/bootstrap-4.1.3/bootstrap-reboot.scss b/site/_scss/bootstrap-4.1.3/bootstrap-reboot.scss
new file mode 100755
index 000000000..75baeb713
--- /dev/null
+++ b/site/_scss/bootstrap-4.1.3/bootstrap-reboot.scss
@@ -0,0 +1,12 @@
+/*!
+ * Bootstrap Reboot v4.1.3 (https://getbootstrap.com/)
+ * Copyright 2011-2018 The Bootstrap Authors
+ * Copyright 2011-2018 Twitter, Inc.
+ * Licensed under MIT (https://github.com/twbs/bootstrap/blob/master/LICENSE)
+ * Forked from Normalize.css, licensed MIT (https://github.com/necolas/normalize.css/blob/master/LICENSE.md)
+ */
+
+@import "functions";
+@import "variables";
+@import "mixins";
+@import "reboot";
diff --git a/site/_scss/bootstrap-4.1.3/bootstrap.scss b/site/_scss/bootstrap-4.1.3/bootstrap.scss
new file mode 100755
index 000000000..e3f76546b
--- /dev/null
+++ b/site/_scss/bootstrap-4.1.3/bootstrap.scss
@@ -0,0 +1,42 @@
+/*!
+ * Bootstrap v4.1.3 (https://getbootstrap.com/)
+ * Copyright 2011-2018 The Bootstrap Authors
+ * Copyright 2011-2018 Twitter, Inc.
+ * Licensed under MIT (https://github.com/twbs/bootstrap/blob/master/LICENSE)
+ */
+
+@import "functions";
+@import "variables";
+@import "mixins";
+@import "root";
+@import "reboot";
+@import "type";
+@import "images";
+@import "code";
+@import "grid";
+@import "tables";
+@import "forms";
+@import "buttons";
+@import "transitions";
+@import "dropdown";
+@import "button-group";
+@import "input-group";
+@import "custom-forms";
+@import "nav";
+@import "navbar";
+@import "card";
+@import "breadcrumb";
+@import "pagination";
+@import "badge";
+@import "jumbotron";
+@import "alert";
+@import "progress";
+@import "media";
+@import "list-group";
+@import "close";
+@import "modal";
+@import "tooltip";
+@import "popover";
+@import "carousel";
+@import "utilities";
+@import "print";
diff --git a/site/_scss/bootstrap-4.1.3/mixins/_alert.scss b/site/_scss/bootstrap-4.1.3/mixins/_alert.scss
new file mode 100755
index 000000000..db5a7eb45
--- /dev/null
+++ b/site/_scss/bootstrap-4.1.3/mixins/_alert.scss
@@ -0,0 +1,13 @@
+@mixin alert-variant($background, $border, $color) {
+ color: $color;
+ @include gradient-bg($background);
+ border-color: $border;
+
+ hr {
+ border-top-color: darken($border, 5%);
+ }
+
+ .alert-link {
+ color: darken($color, 10%);
+ }
+}
diff --git a/site/_scss/bootstrap-4.1.3/mixins/_background-variant.scss b/site/_scss/bootstrap-4.1.3/mixins/_background-variant.scss
new file mode 100755
index 000000000..494439d2b
--- /dev/null
+++ b/site/_scss/bootstrap-4.1.3/mixins/_background-variant.scss
@@ -0,0 +1,21 @@
+// stylelint-disable declaration-no-important
+
+// Contextual backgrounds
+
+@mixin bg-variant($parent, $color) {
+ #{$parent} {
+ background-color: $color !important;
+ }
+ a#{$parent},
+ button#{$parent} {
+ @include hover-focus {
+ background-color: darken($color, 10%) !important;
+ }
+ }
+}
+
+@mixin bg-gradient-variant($parent, $color) {
+ #{$parent} {
+ background: $color linear-gradient(180deg, mix($body-bg, $color, 15%), $color) repeat-x !important;
+ }
+}
diff --git a/site/_scss/bootstrap-4.1.3/mixins/_badge.scss b/site/_scss/bootstrap-4.1.3/mixins/_badge.scss
new file mode 100755
index 000000000..eeca0b40d
--- /dev/null
+++ b/site/_scss/bootstrap-4.1.3/mixins/_badge.scss
@@ -0,0 +1,12 @@
+@mixin badge-variant($bg) {
+ color: color-yiq($bg);
+ background-color: $bg;
+
+ &[href] {
+ @include hover-focus {
+ color: color-yiq($bg);
+ text-decoration: none;
+ background-color: darken($bg, 10%);
+ }
+ }
+}
diff --git a/site/_scss/bootstrap-4.1.3/mixins/_border-radius.scss b/site/_scss/bootstrap-4.1.3/mixins/_border-radius.scss
new file mode 100755
index 000000000..2024febcf
--- /dev/null
+++ b/site/_scss/bootstrap-4.1.3/mixins/_border-radius.scss
@@ -0,0 +1,35 @@
+// Single side border-radius
+
+@mixin border-radius($radius: $border-radius) {
+ @if $enable-rounded {
+ border-radius: $radius;
+ }
+}
+
+@mixin border-top-radius($radius) {
+ @if $enable-rounded {
+ border-top-left-radius: $radius;
+ border-top-right-radius: $radius;
+ }
+}
+
+@mixin border-right-radius($radius) {
+ @if $enable-rounded {
+ border-top-right-radius: $radius;
+ border-bottom-right-radius: $radius;
+ }
+}
+
+@mixin border-bottom-radius($radius) {
+ @if $enable-rounded {
+ border-bottom-right-radius: $radius;
+ border-bottom-left-radius: $radius;
+ }
+}
+
+@mixin border-left-radius($radius) {
+ @if $enable-rounded {
+ border-top-left-radius: $radius;
+ border-bottom-left-radius: $radius;
+ }
+}
diff --git a/site/_scss/bootstrap-4.1.3/mixins/_box-shadow.scss b/site/_scss/bootstrap-4.1.3/mixins/_box-shadow.scss
new file mode 100755
index 000000000..b2410e53a
--- /dev/null
+++ b/site/_scss/bootstrap-4.1.3/mixins/_box-shadow.scss
@@ -0,0 +1,5 @@
+@mixin box-shadow($shadow...) {
+ @if $enable-shadows {
+ box-shadow: $shadow;
+ }
+}
diff --git a/site/_scss/bootstrap-4.1.3/mixins/_breakpoints.scss b/site/_scss/bootstrap-4.1.3/mixins/_breakpoints.scss
new file mode 100755
index 000000000..59f25a27e
--- /dev/null
+++ b/site/_scss/bootstrap-4.1.3/mixins/_breakpoints.scss
@@ -0,0 +1,123 @@
+// Breakpoint viewport sizes and media queries.
+//
+// Breakpoints are defined as a map of (name: minimum width), order from small to large:
+//
+// (xs: 0, sm: 576px, md: 768px, lg: 992px, xl: 1200px)
+//
+// The map defined in the `$grid-breakpoints` global variable is used as the `$breakpoints` argument by default.
+
+// Name of the next breakpoint, or null for the last breakpoint.
+//
+// >> breakpoint-next(sm)
+// md
+// >> breakpoint-next(sm, (xs: 0, sm: 576px, md: 768px, lg: 992px, xl: 1200px))
+// md
+// >> breakpoint-next(sm, $breakpoint-names: (xs sm md lg xl))
+// md
+@function breakpoint-next($name, $breakpoints: $grid-breakpoints, $breakpoint-names: map-keys($breakpoints)) {
+ $n: index($breakpoint-names, $name);
+ @return if($n < length($breakpoint-names), nth($breakpoint-names, $n + 1), null);
+}
+
+// Minimum breakpoint width. Null for the smallest (first) breakpoint.
+//
+// >> breakpoint-min(sm, (xs: 0, sm: 576px, md: 768px, lg: 992px, xl: 1200px))
+// 576px
+@function breakpoint-min($name, $breakpoints: $grid-breakpoints) {
+ $min: map-get($breakpoints, $name);
+ @return if($min != 0, $min, null);
+}
+
+// Maximum breakpoint width. Null for the largest (last) breakpoint.
+// The maximum value is calculated as the minimum of the next one less 0.02px
+// to work around the limitations of `min-` and `max-` prefixes and viewports with fractional widths.
+// See https://www.w3.org/TR/mediaqueries-4/#mq-min-max
+// Uses 0.02px rather than 0.01px to work around a current rounding bug in Safari.
+// See https://bugs.webkit.org/show_bug.cgi?id=178261
+//
+// >> breakpoint-max(sm, (xs: 0, sm: 576px, md: 768px, lg: 992px, xl: 1200px))
+// 767.98px
+@function breakpoint-max($name, $breakpoints: $grid-breakpoints) {
+ $next: breakpoint-next($name, $breakpoints);
+ @return if($next, breakpoint-min($next, $breakpoints) - .02px, null);
+}
+
+// Returns a blank string if smallest breakpoint, otherwise returns the name with a dash in front.
+// Useful for making responsive utilities.
+//
+// >> breakpoint-infix(xs, (xs: 0, sm: 576px, md: 768px, lg: 992px, xl: 1200px))
+// "" (Returns a blank string)
+// >> breakpoint-infix(sm, (xs: 0, sm: 576px, md: 768px, lg: 992px, xl: 1200px))
+// "-sm"
+@function breakpoint-infix($name, $breakpoints: $grid-breakpoints) {
+ @return if(breakpoint-min($name, $breakpoints) == null, "", "-#{$name}");
+}
+
+// Media of at least the minimum breakpoint width. No query for the smallest breakpoint.
+// Makes the @content apply to the given breakpoint and wider.
+@mixin media-breakpoint-up($name, $breakpoints: $grid-breakpoints) {
+ $min: breakpoint-min($name, $breakpoints);
+ @if $min {
+ @media (min-width: $min) {
+ @content;
+ }
+ } @else {
+ @content;
+ }
+}
+
+// Media of at most the maximum breakpoint width. No query for the largest breakpoint.
+// Makes the @content apply to the given breakpoint and narrower.
+@mixin media-breakpoint-down($name, $breakpoints: $grid-breakpoints) {
+ $max: breakpoint-max($name, $breakpoints);
+ @if $max {
+ @media (max-width: $max) {
+ @content;
+ }
+ } @else {
+ @content;
+ }
+}
+
+// Media that spans multiple breakpoint widths.
+// Makes the @content apply between the min and max breakpoints
+@mixin media-breakpoint-between($lower, $upper, $breakpoints: $grid-breakpoints) {
+ $min: breakpoint-min($lower, $breakpoints);
+ $max: breakpoint-max($upper, $breakpoints);
+
+ @if $min != null and $max != null {
+ @media (min-width: $min) and (max-width: $max) {
+ @content;
+ }
+ } @else if $max == null {
+ @include media-breakpoint-up($lower, $breakpoints) {
+ @content;
+ }
+ } @else if $min == null {
+ @include media-breakpoint-down($upper, $breakpoints) {
+ @content;
+ }
+ }
+}
+
+// Media between the breakpoint's minimum and maximum widths.
+// No minimum for the smallest breakpoint, and no maximum for the largest one.
+// Makes the @content apply only to the given breakpoint, not viewports any wider or narrower.
+@mixin media-breakpoint-only($name, $breakpoints: $grid-breakpoints) {
+ $min: breakpoint-min($name, $breakpoints);
+ $max: breakpoint-max($name, $breakpoints);
+
+ @if $min != null and $max != null {
+ @media (min-width: $min) and (max-width: $max) {
+ @content;
+ }
+ } @else if $max == null {
+ @include media-breakpoint-up($name, $breakpoints) {
+ @content;
+ }
+ } @else if $min == null {
+ @include media-breakpoint-down($name, $breakpoints) {
+ @content;
+ }
+ }
+}
diff --git a/site/_scss/bootstrap-4.1.3/mixins/_buttons.scss b/site/_scss/bootstrap-4.1.3/mixins/_buttons.scss
new file mode 100755
index 000000000..06ad6772f
--- /dev/null
+++ b/site/_scss/bootstrap-4.1.3/mixins/_buttons.scss
@@ -0,0 +1,109 @@
+// Button variants
+//
+// Easily pump out default styles, as well as :hover, :focus, :active,
+// and disabled options for all buttons
+
+@mixin button-variant($background, $border, $hover-background: darken($background, 7.5%), $hover-border: darken($border, 10%), $active-background: darken($background, 10%), $active-border: darken($border, 12.5%)) {
+ color: color-yiq($background);
+ @include gradient-bg($background);
+ border-color: $border;
+ @include box-shadow($btn-box-shadow);
+
+ @include hover {
+ color: color-yiq($hover-background);
+ @include gradient-bg($hover-background);
+ border-color: $hover-border;
+ }
+
+ &:focus,
+ &.focus {
+ // Avoid using mixin so we can pass custom focus shadow properly
+ @if $enable-shadows {
+ box-shadow: $btn-box-shadow, 0 0 0 $btn-focus-width rgba($border, .5);
+ } @else {
+ box-shadow: 0 0 0 $btn-focus-width rgba($border, .5);
+ }
+ }
+
+ // Disabled comes first so active can properly restyle
+ &.disabled,
+ &:disabled {
+ color: color-yiq($background);
+ background-color: $background;
+ border-color: $border;
+ }
+
+ &:not(:disabled):not(.disabled):active,
+ &:not(:disabled):not(.disabled).active,
+ .show > &.dropdown-toggle {
+ color: color-yiq($active-background);
+ background-color: $active-background;
+ @if $enable-gradients {
+ background-image: none; // Remove the gradient for the pressed/active state
+ }
+ border-color: $active-border;
+
+ &:focus {
+ // Avoid using mixin so we can pass custom focus shadow properly
+ @if $enable-shadows {
+ box-shadow: $btn-active-box-shadow, 0 0 0 $btn-focus-width rgba($border, .5);
+ } @else {
+ box-shadow: 0 0 0 $btn-focus-width rgba($border, .5);
+ }
+ }
+ }
+}
+
+@mixin button-outline-variant($color, $color-hover: color-yiq($color), $active-background: $color, $active-border: $color) {
+ color: $color;
+ background-color: transparent;
+ background-image: none;
+ border-color: $color;
+
+ &:hover {
+ color: $color-hover;
+ background-color: $active-background;
+ border-color: $active-border;
+ }
+
+ &:focus,
+ &.focus {
+ box-shadow: 0 0 0 $btn-focus-width rgba($color, .5);
+ }
+
+ &.disabled,
+ &:disabled {
+ color: $color;
+ background-color: transparent;
+ }
+
+ &:not(:disabled):not(.disabled):active,
+ &:not(:disabled):not(.disabled).active,
+ .show > &.dropdown-toggle {
+ color: color-yiq($active-background);
+ background-color: $active-background;
+ border-color: $active-border;
+
+ &:focus {
+ // Avoid using mixin so we can pass custom focus shadow properly
+ @if $enable-shadows and $btn-active-box-shadow != none {
+ box-shadow: $btn-active-box-shadow, 0 0 0 $btn-focus-width rgba($color, .5);
+ } @else {
+ box-shadow: 0 0 0 $btn-focus-width rgba($color, .5);
+ }
+ }
+ }
+}
+
+// Button sizes
+@mixin button-size($padding-y, $padding-x, $font-size, $line-height, $border-radius) {
+ padding: $padding-y $padding-x;
+ font-size: $font-size;
+ line-height: $line-height;
+ // Manually declare to provide an override to the browser default
+ @if $enable-rounded {
+ border-radius: $border-radius;
+ } @else {
+ border-radius: 0;
+ }
+}
diff --git a/site/_scss/bootstrap-4.1.3/mixins/_caret.scss b/site/_scss/bootstrap-4.1.3/mixins/_caret.scss
new file mode 100755
index 000000000..82aea4210
--- /dev/null
+++ b/site/_scss/bootstrap-4.1.3/mixins/_caret.scss
@@ -0,0 +1,66 @@
+@mixin caret-down {
+ border-top: $caret-width solid;
+ border-right: $caret-width solid transparent;
+ border-bottom: 0;
+ border-left: $caret-width solid transparent;
+}
+
+@mixin caret-up {
+ border-top: 0;
+ border-right: $caret-width solid transparent;
+ border-bottom: $caret-width solid;
+ border-left: $caret-width solid transparent;
+}
+
+@mixin caret-right {
+ border-top: $caret-width solid transparent;
+ border-right: 0;
+ border-bottom: $caret-width solid transparent;
+ border-left: $caret-width solid;
+}
+
+@mixin caret-left {
+ border-top: $caret-width solid transparent;
+ border-right: $caret-width solid;
+ border-bottom: $caret-width solid transparent;
+}
+
+@mixin caret($direction: down) {
+ @if $enable-caret {
+ &::after {
+ display: inline-block;
+ width: 0;
+ height: 0;
+ margin-left: $caret-width * .85;
+ vertical-align: $caret-width * .85;
+ content: "";
+ @if $direction == down {
+ @include caret-down;
+ } @else if $direction == up {
+ @include caret-up;
+ } @else if $direction == right {
+ @include caret-right;
+ }
+ }
+
+ @if $direction == left {
+ &::after {
+ display: none;
+ }
+
+ &::before {
+ display: inline-block;
+ width: 0;
+ height: 0;
+ margin-right: $caret-width * .85;
+ vertical-align: $caret-width * .85;
+ content: "";
+ @include caret-left;
+ }
+ }
+
+ &:empty::after {
+ margin-left: 0;
+ }
+ }
+}
diff --git a/site/_scss/bootstrap-4.1.3/mixins/_clearfix.scss b/site/_scss/bootstrap-4.1.3/mixins/_clearfix.scss
new file mode 100755
index 000000000..11a977b73
--- /dev/null
+++ b/site/_scss/bootstrap-4.1.3/mixins/_clearfix.scss
@@ -0,0 +1,7 @@
+@mixin clearfix() {
+ &::after {
+ display: block;
+ clear: both;
+ content: "";
+ }
+}
diff --git a/site/_scss/bootstrap-4.1.3/mixins/_float.scss b/site/_scss/bootstrap-4.1.3/mixins/_float.scss
new file mode 100755
index 000000000..48fa8b6d5
--- /dev/null
+++ b/site/_scss/bootstrap-4.1.3/mixins/_float.scss
@@ -0,0 +1,11 @@
+// stylelint-disable declaration-no-important
+
+@mixin float-left {
+ float: left !important;
+}
+@mixin float-right {
+ float: right !important;
+}
+@mixin float-none {
+ float: none !important;
+}
diff --git a/site/_scss/bootstrap-4.1.3/mixins/_forms.scss b/site/_scss/bootstrap-4.1.3/mixins/_forms.scss
new file mode 100755
index 000000000..3a6187869
--- /dev/null
+++ b/site/_scss/bootstrap-4.1.3/mixins/_forms.scss
@@ -0,0 +1,147 @@
+// Form control focus state
+//
+// Generate a customized focus state and for any input with the specified color,
+// which defaults to the `$input-focus-border-color` variable.
+//
+// We highly encourage you to not customize the default value, but instead use
+// this to tweak colors on an as-needed basis. This aesthetic change is based on
+// WebKit's default styles, but applicable to a wider range of browsers. Its
+// usability and accessibility should be taken into account with any change.
+//
+// Example usage: change the default blue border and shadow to white for better
+// contrast against a dark gray background.
+@mixin form-control-focus() {
+ &:focus {
+ color: $input-focus-color;
+ background-color: $input-focus-bg;
+ border-color: $input-focus-border-color;
+ outline: 0;
+ // Avoid using mixin so we can pass custom focus shadow properly
+ @if $enable-shadows {
+ box-shadow: $input-box-shadow, $input-focus-box-shadow;
+ } @else {
+ box-shadow: $input-focus-box-shadow;
+ }
+ }
+}
+
+
+@mixin form-validation-state($state, $color) {
+ .#{$state}-feedback {
+ display: none;
+ width: 100%;
+ margin-top: $form-feedback-margin-top;
+ font-size: $form-feedback-font-size;
+ color: $color;
+ }
+
+ .#{$state}-tooltip {
+ position: absolute;
+ top: 100%;
+ z-index: 5;
+ display: none;
+ max-width: 100%; // Contain to parent when possible
+ padding: $tooltip-padding-y $tooltip-padding-x;
+ margin-top: .1rem;
+ font-size: $tooltip-font-size;
+ line-height: $line-height-base;
+ color: color-yiq($color);
+ background-color: rgba($color, $tooltip-opacity);
+ @include border-radius($tooltip-border-radius);
+ }
+
+ .form-control,
+ .custom-select {
+ .was-validated &:#{$state},
+ &.is-#{$state} {
+ border-color: $color;
+
+ &:focus {
+ border-color: $color;
+ box-shadow: 0 0 0 $input-focus-width rgba($color, .25);
+ }
+
+ ~ .#{$state}-feedback,
+ ~ .#{$state}-tooltip {
+ display: block;
+ }
+ }
+ }
+
+ .form-control-file {
+ .was-validated &:#{$state},
+ &.is-#{$state} {
+ ~ .#{$state}-feedback,
+ ~ .#{$state}-tooltip {
+ display: block;
+ }
+ }
+ }
+
+ .form-check-input {
+ .was-validated &:#{$state},
+ &.is-#{$state} {
+ ~ .form-check-label {
+ color: $color;
+ }
+
+ ~ .#{$state}-feedback,
+ ~ .#{$state}-tooltip {
+ display: block;
+ }
+ }
+ }
+
+ .custom-control-input {
+ .was-validated &:#{$state},
+ &.is-#{$state} {
+ ~ .custom-control-label {
+ color: $color;
+
+ &::before {
+ background-color: lighten($color, 25%);
+ }
+ }
+
+ ~ .#{$state}-feedback,
+ ~ .#{$state}-tooltip {
+ display: block;
+ }
+
+ &:checked {
+ ~ .custom-control-label::before {
+ @include gradient-bg(lighten($color, 10%));
+ }
+ }
+
+ &:focus {
+ ~ .custom-control-label::before {
+ box-shadow: 0 0 0 1px $body-bg, 0 0 0 $input-focus-width rgba($color, .25);
+ }
+ }
+ }
+ }
+
+ // custom file
+ .custom-file-input {
+ .was-validated &:#{$state},
+ &.is-#{$state} {
+ ~ .custom-file-label {
+ border-color: $color;
+
+ &::after { border-color: inherit; }
+ }
+
+ ~ .#{$state}-feedback,
+ ~ .#{$state}-tooltip {
+ display: block;
+ }
+
+ &:focus {
+ ~ .custom-file-label {
+ box-shadow: 0 0 0 $input-focus-width rgba($color, .25);
+ }
+ }
+ }
+ }
+}
diff --git a/site/_scss/bootstrap-4.1.3/mixins/_gradients.scss b/site/_scss/bootstrap-4.1.3/mixins/_gradients.scss
new file mode 100755
index 000000000..88c4d64b7
--- /dev/null
+++ b/site/_scss/bootstrap-4.1.3/mixins/_gradients.scss
@@ -0,0 +1,45 @@
+// Gradients
+
+@mixin gradient-bg($color) {
+ @if $enable-gradients {
+ background: $color linear-gradient(180deg, mix($body-bg, $color, 15%), $color) repeat-x;
+ } @else {
+ background-color: $color;
+ }
+}
+
+// Horizontal gradient, from left to right
+//
+// Creates two color stops, start and end, by specifying a color and position for each color stop.
+@mixin gradient-x($start-color: $gray-700, $end-color: $gray-800, $start-percent: 0%, $end-percent: 100%) {
+ background-image: linear-gradient(to right, $start-color $start-percent, $end-color $end-percent);
+ background-repeat: repeat-x;
+}
+
+// Vertical gradient, from top to bottom
+//
+// Creates two color stops, start and end, by specifying a color and position for each color stop.
+@mixin gradient-y($start-color: $gray-700, $end-color: $gray-800, $start-percent: 0%, $end-percent: 100%) {
+ background-image: linear-gradient(to bottom, $start-color $start-percent, $end-color $end-percent);
+ background-repeat: repeat-x;
+}
+
+@mixin gradient-directional($start-color: $gray-700, $end-color: $gray-800, $deg: 45deg) {
+ background-image: linear-gradient($deg, $start-color, $end-color);
+ background-repeat: repeat-x;
+}
+@mixin gradient-x-three-colors($start-color: $blue, $mid-color: $purple, $color-stop: 50%, $end-color: $red) {
+ background-image: linear-gradient(to right, $start-color, $mid-color $color-stop, $end-color);
+ background-repeat: no-repeat;
+}
+@mixin gradient-y-three-colors($start-color: $blue, $mid-color: $purple, $color-stop: 50%, $end-color: $red) {
+ background-image: linear-gradient($start-color, $mid-color $color-stop, $end-color);
+ background-repeat: no-repeat;
+}
+@mixin gradient-radial($inner-color: $gray-700, $outer-color: $gray-800) {
+ background-image: radial-gradient(circle, $inner-color, $outer-color);
+ background-repeat: no-repeat;
+}
+@mixin gradient-striped($color: rgba($white, .15), $angle: 45deg) {
+ background-image: linear-gradient($angle, $color 25%, transparent 25%, transparent 50%, $color 50%, $color 75%, transparent 75%, transparent);
+}
diff --git a/site/_scss/bootstrap-4.1.3/mixins/_grid-framework.scss b/site/_scss/bootstrap-4.1.3/mixins/_grid-framework.scss
new file mode 100755
index 000000000..7b37f868f
--- /dev/null
+++ b/site/_scss/bootstrap-4.1.3/mixins/_grid-framework.scss
@@ -0,0 +1,67 @@
+// Framework grid generation
+//
+// Used only by Bootstrap to generate the correct number of grid classes given
+// any value of `$grid-columns`.
+
+@mixin make-grid-columns($columns: $grid-columns, $gutter: $grid-gutter-width, $breakpoints: $grid-breakpoints) {
+ // Common properties for all breakpoints
+ %grid-column {
+ position: relative;
+ width: 100%;
+ min-height: 1px; // Prevent columns from collapsing when empty
+ padding-right: ($gutter / 2);
+ padding-left: ($gutter / 2);
+ }
+
+ @each $breakpoint in map-keys($breakpoints) {
+ $infix: breakpoint-infix($breakpoint, $breakpoints);
+
+ // Allow columns to stretch full width below their breakpoints
+ @for $i from 1 through $columns {
+ .col#{$infix}-#{$i} {
+ @extend %grid-column;
+ }
+ }
+ .col#{$infix},
+ .col#{$infix}-auto {
+ @extend %grid-column;
+ }
+
+ @include media-breakpoint-up($breakpoint, $breakpoints) {
+ // Provide basic `.col-{bp}` classes for equal-width flexbox columns
+ .col#{$infix} {
+ flex-basis: 0;
+ flex-grow: 1;
+ max-width: 100%;
+ }
+ .col#{$infix}-auto {
+ flex: 0 0 auto;
+ width: auto;
+ max-width: none; // Reset earlier grid tiers
+ }
+
+ @for $i from 1 through $columns {
+ .col#{$infix}-#{$i} {
+ @include make-col($i, $columns);
+ }
+ }
+
+ .order#{$infix}-first { order: -1; }
+
+ .order#{$infix}-last { order: $columns + 1; }
+
+ @for $i from 0 through $columns {
+ .order#{$infix}-#{$i} { order: $i; }
+ }
+
+ // `$columns - 1` because offsetting by the width of an entire row isn't possible
+ @for $i from 0 through ($columns - 1) {
+ @if not ($infix == "" and $i == 0) { // Avoid emitting useless .offset-0
+ .offset#{$infix}-#{$i} {
+ @include make-col-offset($i, $columns);
+ }
+ }
+ }
+ }
+ }
+}
diff --git a/site/_scss/bootstrap-4.1.3/mixins/_grid.scss b/site/_scss/bootstrap-4.1.3/mixins/_grid.scss
new file mode 100755
index 000000000..b75ebcbca
--- /dev/null
+++ b/site/_scss/bootstrap-4.1.3/mixins/_grid.scss
@@ -0,0 +1,52 @@
+/// Grid system
+//
+// Generate semantic grid columns with these mixins.
+
+@mixin make-container() {
+ width: 100%;
+ padding-right: ($grid-gutter-width / 2);
+ padding-left: ($grid-gutter-width / 2);
+ margin-right: auto;
+ margin-left: auto;
+}
+
+
+// For each breakpoint, define the maximum width of the container in a media query
+@mixin make-container-max-widths($max-widths: $container-max-widths, $breakpoints: $grid-breakpoints) {
+ @each $breakpoint, $container-max-width in $max-widths {
+ @include media-breakpoint-up($breakpoint, $breakpoints) {
+ max-width: $container-max-width;
+ }
+ }
+}
+
+@mixin make-row() {
+ display: flex;
+ flex-wrap: wrap;
+ margin-right: ($grid-gutter-width / -2);
+ margin-left: ($grid-gutter-width / -2);
+}
+
+@mixin make-col-ready() {
+ position: relative;
+ // Prevent columns from becoming too narrow when at smaller grid tiers by
+ // always setting `width: 100%;`. This works because we use `flex` values
+ // later on to override this initial width.
+ width: 100%;
+ min-height: 1px; // Prevent collapsing
+ padding-right: ($grid-gutter-width / 2);
+ padding-left: ($grid-gutter-width / 2);
+}
+
+@mixin make-col($size, $columns: $grid-columns) {
+ flex: 0 0 percentage($size / $columns);
+ // Add a `max-width` to ensure content within each column does not blow out
+ // the width of the column. Applies to IE10+ and Firefox. Chrome and Safari
+ // do not appear to require this.
+ max-width: percentage($size / $columns);
+}
+
+@mixin make-col-offset($size, $columns: $grid-columns) {
+ $num: $size / $columns;
+ margin-left: if($num == 0, 0, percentage($num));
+}
diff --git a/site/_scss/bootstrap-4.1.3/mixins/_hover.scss b/site/_scss/bootstrap-4.1.3/mixins/_hover.scss
new file mode 100755
index 000000000..192f847e1
--- /dev/null
+++ b/site/_scss/bootstrap-4.1.3/mixins/_hover.scss
@@ -0,0 +1,37 @@
+// Hover mixin and `$enable-hover-media-query` are deprecated.
+//
+// Originally added during our alphas and maintained during betas, this mixin was
+// designed to prevent `:hover` stickiness on iOS-an issue where hover styles
+// would persist after initial touch.
+//
+// For backward compatibility, we've kept these mixins and updated them to
+// always return their regular pseudo-classes instead of a shimmed media query.
+//
+// Issue: https://github.com/twbs/bootstrap/issues/25195
+
+@mixin hover {
+ &:hover { @content; }
+}
+
+@mixin hover-focus {
+ &:hover,
+ &:focus {
+ @content;
+ }
+}
+
+@mixin plain-hover-focus {
+ &,
+ &:hover,
+ &:focus {
+ @content;
+ }
+}
+
+@mixin hover-focus-active {
+ &:hover,
+ &:focus,
+ &:active {
+ @content;
+ }
+}
diff --git a/site/_scss/bootstrap-4.1.3/mixins/_image.scss b/site/_scss/bootstrap-4.1.3/mixins/_image.scss
new file mode 100755
index 000000000..0544f0d2a
--- /dev/null
+++ b/site/_scss/bootstrap-4.1.3/mixins/_image.scss
@@ -0,0 +1,36 @@
+// Image Mixins
+// - Responsive image
+// - Retina image
+
+
+// Responsive image
+//
+// Keep images from scaling beyond the width of their parents.
+
+@mixin img-fluid {
+ // Part 1: Set a maximum relative to the parent
+ max-width: 100%;
+ // Part 2: Override the height to auto, otherwise images will be stretched
+ // when setting a width and height attribute on the img element.
+ height: auto;
+}
+
+
+// Retina image
+//
+// Short retina mixin for setting background-image and -size.
+
+// stylelint-disable indentation, media-query-list-comma-newline-after
+@mixin img-retina($file-1x, $file-2x, $width-1x, $height-1x) {
+ background-image: url($file-1x);
+
+ // Autoprefixer takes care of adding -webkit-min-device-pixel-ratio and -o-min-device-pixel-ratio,
+ // but doesn't convert dppx=>dpi.
+ // There's no such thing as unprefixed min-device-pixel-ratio since it's nonstandard.
+ // Compatibility info: https://caniuse.com/#feat=css-media-resolution
+ @media only screen and (min-resolution: 192dpi), // IE9-11 don't support dppx
+ only screen and (min-resolution: 2dppx) { // Standardized
+ background-image: url($file-2x);
+ background-size: $width-1x $height-1x;
+ }
+}
diff --git a/site/_scss/bootstrap-4.1.3/mixins/_list-group.scss b/site/_scss/bootstrap-4.1.3/mixins/_list-group.scss
new file mode 100755
index 000000000..cd47a4e9f
--- /dev/null
+++ b/site/_scss/bootstrap-4.1.3/mixins/_list-group.scss
@@ -0,0 +1,21 @@
+// List Groups
+
+@mixin list-group-item-variant($state, $background, $color) {
+ .list-group-item-#{$state} {
+ color: $color;
+ background-color: $background;
+
+ &.list-group-item-action {
+ @include hover-focus {
+ color: $color;
+ background-color: darken($background, 5%);
+ }
+
+ &.active {
+ color: $white;
+ background-color: $color;
+ border-color: $color;
+ }
+ }
+ }
+}
diff --git a/site/_scss/bootstrap-4.1.3/mixins/_lists.scss b/site/_scss/bootstrap-4.1.3/mixins/_lists.scss
new file mode 100755
index 000000000..251856266
--- /dev/null
+++ b/site/_scss/bootstrap-4.1.3/mixins/_lists.scss
@@ -0,0 +1,7 @@
+// Lists
+
+// Unstyled keeps list items block level, just removes default browser padding and list-style
+@mixin list-unstyled {
+ padding-left: 0;
+ list-style: none;
+}
diff --git a/site/_scss/bootstrap-4.1.3/mixins/_nav-divider.scss b/site/_scss/bootstrap-4.1.3/mixins/_nav-divider.scss
new file mode 100755
index 000000000..4fb37b622
--- /dev/null
+++ b/site/_scss/bootstrap-4.1.3/mixins/_nav-divider.scss
@@ -0,0 +1,10 @@
+// Horizontal dividers
+//
+// Dividers (basically an hr) within dropdowns and nav lists
+
+@mixin nav-divider($color: $nav-divider-color, $margin-y: $nav-divider-margin-y) {
+ height: 0;
+ margin: $margin-y 0;
+ overflow: hidden;
+ border-top: 1px solid $color;
+}
diff --git a/site/_scss/bootstrap-4.1.3/mixins/_pagination.scss b/site/_scss/bootstrap-4.1.3/mixins/_pagination.scss
new file mode 100755
index 000000000..ff36eb6b4
--- /dev/null
+++ b/site/_scss/bootstrap-4.1.3/mixins/_pagination.scss
@@ -0,0 +1,22 @@
+// Pagination
+
+@mixin pagination-size($padding-y, $padding-x, $font-size, $line-height, $border-radius) {
+ .page-link {
+ padding: $padding-y $padding-x;
+ font-size: $font-size;
+ line-height: $line-height;
+ }
+
+ .page-item {
+ &:first-child {
+ .page-link {
+ @include border-left-radius($border-radius);
+ }
+ }
+ &:last-child {
+ .page-link {
+ @include border-right-radius($border-radius);
+ }
+ }
+ }
+}
diff --git a/site/_scss/bootstrap-4.1.3/mixins/_reset-text.scss b/site/_scss/bootstrap-4.1.3/mixins/_reset-text.scss
new file mode 100755
index 000000000..71edb0061
--- /dev/null
+++ b/site/_scss/bootstrap-4.1.3/mixins/_reset-text.scss
@@ -0,0 +1,17 @@
+@mixin reset-text {
+ font-family: $font-family-base;
+ // We deliberately do NOT reset font-size or word-wrap.
+ font-style: normal;
+ font-weight: $font-weight-normal;
+ line-height: $line-height-base;
+ text-align: left; // Fallback for where `start` is not supported
+ text-align: start; // stylelint-disable-line declaration-block-no-duplicate-properties
+ text-decoration: none;
+ text-shadow: none;
+ text-transform: none;
+ letter-spacing: normal;
+ word-break: normal;
+ word-spacing: normal;
+ white-space: normal;
+ line-break: auto;
+}
diff --git a/site/_scss/bootstrap-4.1.3/mixins/_resize.scss b/site/_scss/bootstrap-4.1.3/mixins/_resize.scss
new file mode 100755
index 000000000..66f233a63
--- /dev/null
+++ b/site/_scss/bootstrap-4.1.3/mixins/_resize.scss
@@ -0,0 +1,6 @@
+// Resize anything
+
+@mixin resizable($direction) {
+ overflow: auto; // Per CSS3 UI, `resize` only applies when `overflow` isn't `visible`
+ resize: $direction; // Options: horizontal, vertical, both
+}
diff --git a/site/_scss/bootstrap-4.1.3/mixins/_screen-reader.scss b/site/_scss/bootstrap-4.1.3/mixins/_screen-reader.scss
new file mode 100755
index 000000000..812591bc5
--- /dev/null
+++ b/site/_scss/bootstrap-4.1.3/mixins/_screen-reader.scss
@@ -0,0 +1,33 @@
+// Only display content to screen readers
+//
+// See: https://a11yproject.com/posts/how-to-hide-content/
+// See: https://hugogiraudel.com/2016/10/13/css-hide-and-seek/
+
+@mixin sr-only {
+ position: absolute;
+ width: 1px;
+ height: 1px;
+ padding: 0;
+ overflow: hidden;
+ clip: rect(0, 0, 0, 0);
+ white-space: nowrap;
+ border: 0;
+}
+
+// Use in conjunction with .sr-only to only display content when it's focused.
+//
+// Useful for "Skip to main content" links; see https://www.w3.org/TR/2013/NOTE-WCAG20-TECHS-20130905/G1
+//
+// Credit: HTML5 Boilerplate
+
+@mixin sr-only-focusable {
+ &:active,
+ &:focus {
+ position: static;
+ width: auto;
+ height: auto;
+ overflow: visible;
+ clip: auto;
+ white-space: normal;
+ }
+}
diff --git a/site/_scss/bootstrap-4.1.3/mixins/_size.scss b/site/_scss/bootstrap-4.1.3/mixins/_size.scss
new file mode 100755
index 000000000..b9dd48e8d
--- /dev/null
+++ b/site/_scss/bootstrap-4.1.3/mixins/_size.scss
@@ -0,0 +1,6 @@
+// Sizing shortcuts
+
+@mixin size($width, $height: $width) {
+ width: $width;
+ height: $height;
+}
diff --git a/site/_scss/bootstrap-4.1.3/mixins/_table-row.scss b/site/_scss/bootstrap-4.1.3/mixins/_table-row.scss
new file mode 100755
index 000000000..84f1d305a
--- /dev/null
+++ b/site/_scss/bootstrap-4.1.3/mixins/_table-row.scss
@@ -0,0 +1,30 @@
+// Tables
+
+@mixin table-row-variant($state, $background) {
+ // Exact selectors below required to override `.table-striped` and prevent
+ // inheritance to nested tables.
+ .table-#{$state} {
+ &,
+ > th,
+ > td {
+ background-color: $background;
+ }
+ }
+
+ // Hover states for `.table-hover`
+ // Note: this is not available for cells or rows within `thead` or `tfoot`.
+ .table-hover {
+ $hover-background: darken($background, 5%);
+
+ .table-#{$state} {
+ @include hover {
+ background-color: $hover-background;
+
+ > td,
+ > th {
+ background-color: $hover-background;
+ }
+ }
+ }
+ }
+}
diff --git a/site/_scss/bootstrap-4.1.3/mixins/_text-emphasis.scss b/site/_scss/bootstrap-4.1.3/mixins/_text-emphasis.scss
new file mode 100755
index 000000000..58db3e0fc
--- /dev/null
+++ b/site/_scss/bootstrap-4.1.3/mixins/_text-emphasis.scss
@@ -0,0 +1,14 @@
+// stylelint-disable declaration-no-important
+
+// Typography
+
+@mixin text-emphasis-variant($parent, $color) {
+ #{$parent} {
+ color: $color !important;
+ }
+ a#{$parent} {
+ @include hover-focus {
+ color: darken($color, 10%) !important;
+ }
+ }
+}
diff --git a/site/_scss/bootstrap-4.1.3/mixins/_text-hide.scss b/site/_scss/bootstrap-4.1.3/mixins/_text-hide.scss
new file mode 100755
index 000000000..9ffab169f
--- /dev/null
+++ b/site/_scss/bootstrap-4.1.3/mixins/_text-hide.scss
@@ -0,0 +1,13 @@
+// CSS image replacement
+@mixin text-hide($ignore-warning: false) {
+ // stylelint-disable-next-line font-family-no-missing-generic-family-keyword
+ font: 0/0 a;
+ color: transparent;
+ text-shadow: none;
+ background-color: transparent;
+ border: 0;
+
+ @if ($ignore-warning != true) {
+ @warn "The `text-hide()` mixin has been deprecated as of v4.1.0. It will be removed entirely in v5.";
+ }
+}
diff --git a/site/_scss/bootstrap-4.1.3/mixins/_text-truncate.scss b/site/_scss/bootstrap-4.1.3/mixins/_text-truncate.scss
new file mode 100755
index 000000000..3504bb1aa
--- /dev/null
+++ b/site/_scss/bootstrap-4.1.3/mixins/_text-truncate.scss
@@ -0,0 +1,8 @@
+// Text truncate
+// Requires inline-block or block for proper styling
+
+@mixin text-truncate() {
+ overflow: hidden;
+ text-overflow: ellipsis;
+ white-space: nowrap;
+}
diff --git a/site/_scss/bootstrap-4.1.3/mixins/_transition.scss b/site/_scss/bootstrap-4.1.3/mixins/_transition.scss
new file mode 100755
index 000000000..f85382134
--- /dev/null
+++ b/site/_scss/bootstrap-4.1.3/mixins/_transition.scss
@@ -0,0 +1,13 @@
+@mixin transition($transition...) {
+ @if $enable-transitions {
+ @if length($transition) == 0 {
+ transition: $transition-base;
+ } @else {
+ transition: $transition;
+ }
+ }
+
+ @media screen and (prefers-reduced-motion: reduce) {
+ transition: none;
+ }
+}
diff --git a/site/_scss/bootstrap-4.1.3/mixins/_visibility.scss b/site/_scss/bootstrap-4.1.3/mixins/_visibility.scss
new file mode 100755
index 000000000..fe523d0ee
--- /dev/null
+++ b/site/_scss/bootstrap-4.1.3/mixins/_visibility.scss
@@ -0,0 +1,7 @@
+// stylelint-disable declaration-no-important
+
+// Visibility
+
+@mixin invisible($visibility) {
+ visibility: $visibility !important;
+}
diff --git a/site/_scss/bootstrap-4.1.3/utilities/_align.scss b/site/_scss/bootstrap-4.1.3/utilities/_align.scss
new file mode 100755
index 000000000..8b7df9f76
--- /dev/null
+++ b/site/_scss/bootstrap-4.1.3/utilities/_align.scss
@@ -0,0 +1,8 @@
+// stylelint-disable declaration-no-important
+
+.align-baseline { vertical-align: baseline !important; } // Browser default
+.align-top { vertical-align: top !important; }
+.align-middle { vertical-align: middle !important; }
+.align-bottom { vertical-align: bottom !important; }
+.align-text-bottom { vertical-align: text-bottom !important; }
+.align-text-top { vertical-align: text-top !important; }
diff --git a/site/_scss/bootstrap-4.1.3/utilities/_background.scss b/site/_scss/bootstrap-4.1.3/utilities/_background.scss
new file mode 100755
index 000000000..1f18b2f3f
--- /dev/null
+++ b/site/_scss/bootstrap-4.1.3/utilities/_background.scss
@@ -0,0 +1,19 @@
+// stylelint-disable declaration-no-important
+
+@each $color, $value in $theme-colors {
+ @include bg-variant(".bg-#{$color}", $value);
+}
+
+@if $enable-gradients {
+ @each $color, $value in $theme-colors {
+ @include bg-gradient-variant(".bg-gradient-#{$color}", $value);
+ }
+}
+
+.bg-white {
+ background-color: $white !important;
+}
+
+.bg-transparent {
+ background-color: transparent !important;
+}
diff --git a/site/_scss/bootstrap-4.1.3/utilities/_borders.scss b/site/_scss/bootstrap-4.1.3/utilities/_borders.scss
new file mode 100755
index 000000000..b8832ef72
--- /dev/null
+++ b/site/_scss/bootstrap-4.1.3/utilities/_borders.scss
@@ -0,0 +1,59 @@
+// stylelint-disable declaration-no-important
+
+//
+// Border
+//
+
+.border { border: $border-width solid $border-color !important; }
+.border-top { border-top: $border-width solid $border-color !important; }
+.border-right { border-right: $border-width solid $border-color !important; }
+.border-bottom { border-bottom: $border-width solid $border-color !important; }
+.border-left { border-left: $border-width solid $border-color !important; }
+
+.border-0 { border: 0 !important; }
+.border-top-0 { border-top: 0 !important; }
+.border-right-0 { border-right: 0 !important; }
+.border-bottom-0 { border-bottom: 0 !important; }
+.border-left-0 { border-left: 0 !important; }
+
+@each $color, $value in $theme-colors {
+ .border-#{$color} {
+ border-color: $value !important;
+ }
+}
+
+.border-white {
+ border-color: $white !important;
+}
+
+//
+// Border-radius
+//
+
+.rounded {
+ border-radius: $border-radius !important;
+}
+.rounded-top {
+ border-top-left-radius: $border-radius !important;
+ border-top-right-radius: $border-radius !important;
+}
+.rounded-right {
+ border-top-right-radius: $border-radius !important;
+ border-bottom-right-radius: $border-radius !important;
+}
+.rounded-bottom {
+ border-bottom-right-radius: $border-radius !important;
+ border-bottom-left-radius: $border-radius !important;
+}
+.rounded-left {
+ border-top-left-radius: $border-radius !important;
+ border-bottom-left-radius: $border-radius !important;
+}
+
+.rounded-circle {
+ border-radius: 50% !important;
+}
+
+.rounded-0 {
+ border-radius: 0 !important;
+}
diff --git a/site/_scss/bootstrap-4.1.3/utilities/_clearfix.scss b/site/_scss/bootstrap-4.1.3/utilities/_clearfix.scss
new file mode 100755
index 000000000..e92522a94
--- /dev/null
+++ b/site/_scss/bootstrap-4.1.3/utilities/_clearfix.scss
@@ -0,0 +1,3 @@
+.clearfix {
+ @include clearfix();
+}
diff --git a/site/_scss/bootstrap-4.1.3/utilities/_display.scss b/site/_scss/bootstrap-4.1.3/utilities/_display.scss
new file mode 100755
index 000000000..20aeeb5f3
--- /dev/null
+++ b/site/_scss/bootstrap-4.1.3/utilities/_display.scss
@@ -0,0 +1,38 @@
+// stylelint-disable declaration-no-important
+
+//
+// Utilities for common `display` values
+//
+
+@each $breakpoint in map-keys($grid-breakpoints) {
+ @include media-breakpoint-up($breakpoint) {
+ $infix: breakpoint-infix($breakpoint, $grid-breakpoints);
+
+ .d#{$infix}-none { display: none !important; }
+ .d#{$infix}-inline { display: inline !important; }
+ .d#{$infix}-inline-block { display: inline-block !important; }
+ .d#{$infix}-block { display: block !important; }
+ .d#{$infix}-table { display: table !important; }
+ .d#{$infix}-table-row { display: table-row !important; }
+ .d#{$infix}-table-cell { display: table-cell !important; }
+ .d#{$infix}-flex { display: flex !important; }
+ .d#{$infix}-inline-flex { display: inline-flex !important; }
+ }
+}
+
+
+//
+// Utilities for toggling `display` in print
+//
+
+@media print {
+ .d-print-none { display: none !important; }
+ .d-print-inline { display: inline !important; }
+ .d-print-inline-block { display: inline-block !important; }
+ .d-print-block { display: block !important; }
+ .d-print-table { display: table !important; }
+ .d-print-table-row { display: table-row !important; }
+ .d-print-table-cell { display: table-cell !important; }
+ .d-print-flex { display: flex !important; }
+ .d-print-inline-flex { display: inline-flex !important; }
+}
diff --git a/site/_scss/bootstrap-4.1.3/utilities/_embed.scss b/site/_scss/bootstrap-4.1.3/utilities/_embed.scss
new file mode 100755
index 000000000..d3362b6fd
--- /dev/null
+++ b/site/_scss/bootstrap-4.1.3/utilities/_embed.scss
@@ -0,0 +1,52 @@
+// Credit: Nicolas Gallagher and SUIT CSS.
+
+.embed-responsive {
+ position: relative;
+ display: block;
+ width: 100%;
+ padding: 0;
+ overflow: hidden;
+
+ &::before {
+ display: block;
+ content: "";
+ }
+
+ .embed-responsive-item,
+ iframe,
+ embed,
+ object,
+ video {
+ position: absolute;
+ top: 0;
+ bottom: 0;
+ left: 0;
+ width: 100%;
+ height: 100%;
+ border: 0;
+ }
+}
+
+.embed-responsive-21by9 {
+ &::before {
+ padding-top: percentage(9 / 21);
+ }
+}
+
+.embed-responsive-16by9 {
+ &::before {
+ padding-top: percentage(9 / 16);
+ }
+}
+
+.embed-responsive-4by3 {
+ &::before {
+ padding-top: percentage(3 / 4);
+ }
+}
+
+.embed-responsive-1by1 {
+ &::before {
+ padding-top: percentage(1 / 1);
+ }
+}
diff --git a/site/_scss/bootstrap-4.1.3/utilities/_flex.scss b/site/_scss/bootstrap-4.1.3/utilities/_flex.scss
new file mode 100755
index 000000000..3d4266e0d
--- /dev/null
+++ b/site/_scss/bootstrap-4.1.3/utilities/_flex.scss
@@ -0,0 +1,51 @@
+// stylelint-disable declaration-no-important
+
+// Flex variation
+//
+// Custom styles for additional flex alignment options.
+
+@each $breakpoint in map-keys($grid-breakpoints) {
+ @include media-breakpoint-up($breakpoint) {
+ $infix: breakpoint-infix($breakpoint, $grid-breakpoints);
+
+ .flex#{$infix}-row { flex-direction: row !important; }
+ .flex#{$infix}-column { flex-direction: column !important; }
+ .flex#{$infix}-row-reverse { flex-direction: row-reverse !important; }
+ .flex#{$infix}-column-reverse { flex-direction: column-reverse !important; }
+
+ .flex#{$infix}-wrap { flex-wrap: wrap !important; }
+ .flex#{$infix}-nowrap { flex-wrap: nowrap !important; }
+ .flex#{$infix}-wrap-reverse { flex-wrap: wrap-reverse !important; }
+ .flex#{$infix}-fill { flex: 1 1 auto !important; }
+ .flex#{$infix}-grow-0 { flex-grow: 0 !important; }
+ .flex#{$infix}-grow-1 { flex-grow: 1 !important; }
+ .flex#{$infix}-shrink-0 { flex-shrink: 0 !important; }
+ .flex#{$infix}-shrink-1 { flex-shrink: 1 !important; }
+
+ .justify-content#{$infix}-start { justify-content: flex-start !important; }
+ .justify-content#{$infix}-end { justify-content: flex-end !important; }
+ .justify-content#{$infix}-center { justify-content: center !important; }
+ .justify-content#{$infix}-between { justify-content: space-between !important; }
+ .justify-content#{$infix}-around { justify-content: space-around !important; }
+
+ .align-items#{$infix}-start { align-items: flex-start !important; }
+ .align-items#{$infix}-end { align-items: flex-end !important; }
+ .align-items#{$infix}-center { align-items: center !important; }
+ .align-items#{$infix}-baseline { align-items: baseline !important; }
+ .align-items#{$infix}-stretch { align-items: stretch !important; }
+
+ .align-content#{$infix}-start { align-content: flex-start !important; }
+ .align-content#{$infix}-end { align-content: flex-end !important; }
+ .align-content#{$infix}-center { align-content: center !important; }
+ .align-content#{$infix}-between { align-content: space-between !important; }
+ .align-content#{$infix}-around { align-content: space-around !important; }
+ .align-content#{$infix}-stretch { align-content: stretch !important; }
+
+ .align-self#{$infix}-auto { align-self: auto !important; }
+ .align-self#{$infix}-start { align-self: flex-start !important; }
+ .align-self#{$infix}-end { align-self: flex-end !important; }
+ .align-self#{$infix}-center { align-self: center !important; }
+ .align-self#{$infix}-baseline { align-self: baseline !important; }
+ .align-self#{$infix}-stretch { align-self: stretch !important; }
+ }
+}
diff --git a/site/_scss/bootstrap-4.1.3/utilities/_float.scss b/site/_scss/bootstrap-4.1.3/utilities/_float.scss
new file mode 100755
index 000000000..01655e9a5
--- /dev/null
+++ b/site/_scss/bootstrap-4.1.3/utilities/_float.scss
@@ -0,0 +1,9 @@
+@each $breakpoint in map-keys($grid-breakpoints) {
+ @include media-breakpoint-up($breakpoint) {
+ $infix: breakpoint-infix($breakpoint, $grid-breakpoints);
+
+ .float#{$infix}-left { @include float-left; }
+ .float#{$infix}-right { @include float-right; }
+ .float#{$infix}-none { @include float-none; }
+ }
+}
diff --git a/site/_scss/bootstrap-4.1.3/utilities/_position.scss b/site/_scss/bootstrap-4.1.3/utilities/_position.scss
new file mode 100755
index 000000000..9ecdeeb9b
--- /dev/null
+++ b/site/_scss/bootstrap-4.1.3/utilities/_position.scss
@@ -0,0 +1,37 @@
+// stylelint-disable declaration-no-important
+
+// Common values
+
+// Sass list not in variables since it's not intended for customization.
+// stylelint-disable-next-line scss/dollar-variable-default
+$positions: static, relative, absolute, fixed, sticky;
+
+@each $position in $positions {
+ .position-#{$position} { position: $position !important; }
+}
+
+// Shorthand
+
+.fixed-top {
+ position: fixed;
+ top: 0;
+ right: 0;
+ left: 0;
+ z-index: $zindex-fixed;
+}
+
+.fixed-bottom {
+ position: fixed;
+ right: 0;
+ bottom: 0;
+ left: 0;
+ z-index: $zindex-fixed;
+}
+
+.sticky-top {
+ @supports (position: sticky) {
+ position: sticky;
+ top: 0;
+ z-index: $zindex-sticky;
+ }
+}
diff --git a/site/_scss/bootstrap-4.1.3/utilities/_screenreaders.scss b/site/_scss/bootstrap-4.1.3/utilities/_screenreaders.scss
new file mode 100755
index 000000000..9f26fde03
--- /dev/null
+++ b/site/_scss/bootstrap-4.1.3/utilities/_screenreaders.scss
@@ -0,0 +1,11 @@
+//
+// Screenreaders
+//
+
+.sr-only {
+ @include sr-only();
+}
+
+.sr-only-focusable {
+ @include sr-only-focusable();
+}
diff --git a/site/_scss/bootstrap-4.1.3/utilities/_shadows.scss b/site/_scss/bootstrap-4.1.3/utilities/_shadows.scss
new file mode 100755
index 000000000..f5d03fcd5
--- /dev/null
+++ b/site/_scss/bootstrap-4.1.3/utilities/_shadows.scss
@@ -0,0 +1,6 @@
+// stylelint-disable declaration-no-important
+
+.shadow-sm { box-shadow: $box-shadow-sm !important; }
+.shadow { box-shadow: $box-shadow !important; }
+.shadow-lg { box-shadow: $box-shadow-lg !important; }
+.shadow-none { box-shadow: none !important; }
diff --git a/site/_scss/bootstrap-4.1.3/utilities/_sizing.scss b/site/_scss/bootstrap-4.1.3/utilities/_sizing.scss
new file mode 100755
index 000000000..e95a4db36
--- /dev/null
+++ b/site/_scss/bootstrap-4.1.3/utilities/_sizing.scss
@@ -0,0 +1,12 @@
+// stylelint-disable declaration-no-important
+
+// Width and height
+
+@each $prop, $abbrev in (width: w, height: h) {
+ @each $size, $length in $sizes {
+ .#{$abbrev}-#{$size} { #{$prop}: $length !important; }
+ }
+}
+
+.mw-100 { max-width: 100% !important; }
+.mh-100 { max-height: 100% !important; }
diff --git a/site/_scss/bootstrap-4.1.3/utilities/_spacing.scss b/site/_scss/bootstrap-4.1.3/utilities/_spacing.scss
new file mode 100755
index 000000000..b2e2354b1
--- /dev/null
+++ b/site/_scss/bootstrap-4.1.3/utilities/_spacing.scss
@@ -0,0 +1,51 @@
+// stylelint-disable declaration-no-important
+
+// Margin and Padding
+
+@each $breakpoint in map-keys($grid-breakpoints) {
+ @include media-breakpoint-up($breakpoint) {
+ $infix: breakpoint-infix($breakpoint, $grid-breakpoints);
+
+ @each $prop, $abbrev in (margin: m, padding: p) {
+ @each $size, $length in $spacers {
+
+ .#{$abbrev}#{$infix}-#{$size} { #{$prop}: $length !important; }
+ .#{$abbrev}t#{$infix}-#{$size},
+ .#{$abbrev}y#{$infix}-#{$size} {
+ #{$prop}-top: $length !important;
+ }
+ .#{$abbrev}r#{$infix}-#{$size},
+ .#{$abbrev}x#{$infix}-#{$size} {
+ #{$prop}-right: $length !important;
+ }
+ .#{$abbrev}b#{$infix}-#{$size},
+ .#{$abbrev}y#{$infix}-#{$size} {
+ #{$prop}-bottom: $length !important;
+ }
+ .#{$abbrev}l#{$infix}-#{$size},
+ .#{$abbrev}x#{$infix}-#{$size} {
+ #{$prop}-left: $length !important;
+ }
+ }
+ }
+
+ // Some special margin utils
+ .m#{$infix}-auto { margin: auto !important; }
+ .mt#{$infix}-auto,
+ .my#{$infix}-auto {
+ margin-top: auto !important;
+ }
+ .mr#{$infix}-auto,
+ .mx#{$infix}-auto {
+ margin-right: auto !important;
+ }
+ .mb#{$infix}-auto,
+ .my#{$infix}-auto {
+ margin-bottom: auto !important;
+ }
+ .ml#{$infix}-auto,
+ .mx#{$infix}-auto {
+ margin-left: auto !important;
+ }
+ }
+}
diff --git a/site/_scss/bootstrap-4.1.3/utilities/_text.scss b/site/_scss/bootstrap-4.1.3/utilities/_text.scss
new file mode 100755
index 000000000..9d96c4656
--- /dev/null
+++ b/site/_scss/bootstrap-4.1.3/utilities/_text.scss
@@ -0,0 +1,58 @@
+// stylelint-disable declaration-no-important
+
+//
+// Text
+//
+
+.text-monospace { font-family: $font-family-monospace; }
+
+// Alignment
+
+.text-justify { text-align: justify !important; }
+.text-nowrap { white-space: nowrap !important; }
+.text-truncate { @include text-truncate; }
+
+// Responsive alignment
+
+@each $breakpoint in map-keys($grid-breakpoints) {
+ @include media-breakpoint-up($breakpoint) {
+ $infix: breakpoint-infix($breakpoint, $grid-breakpoints);
+
+ .text#{$infix}-left { text-align: left !important; }
+ .text#{$infix}-right { text-align: right !important; }
+ .text#{$infix}-center { text-align: center !important; }
+ }
+}
+
+// Transformation
+
+.text-lowercase { text-transform: lowercase !important; }
+.text-uppercase { text-transform: uppercase !important; }
+.text-capitalize { text-transform: capitalize !important; }
+
+// Weight and italics
+
+.font-weight-light { font-weight: $font-weight-light !important; }
+.font-weight-normal { font-weight: $font-weight-normal !important; }
+.font-weight-bold { font-weight: $font-weight-bold !important; }
+.font-italic { font-style: italic !important; }
+
+// Contextual colors
+
+.text-white { color: $white !important; }
+
+@each $color, $value in $theme-colors {
+ @include text-emphasis-variant(".text-#{$color}", $value);
+}
+
+.text-body { color: $body-color !important; }
+.text-muted { color: $text-muted !important; }
+
+.text-black-50 { color: rgba($black, .5) !important; }
+.text-white-50 { color: rgba($white, .5) !important; }
+
+// Misc
+
+.text-hide {
+ @include text-hide($ignore-warning: true);
+}
diff --git a/site/_scss/bootstrap-4.1.3/utilities/_visibility.scss b/site/_scss/bootstrap-4.1.3/utilities/_visibility.scss
new file mode 100755
index 000000000..823406dc3
--- /dev/null
+++ b/site/_scss/bootstrap-4.1.3/utilities/_visibility.scss
@@ -0,0 +1,11 @@
+//
+// Visibility utilities
+//
+
+.visible {
+ @include invisible(visible);
+}
+
+.invisible {
+ @include invisible(hidden);
+}
diff --git a/site/_scss/site/common/_core.scss b/site/_scss/site/common/_core.scss
new file mode 100644
index 000000000..c7c04d018
--- /dev/null
+++ b/site/_scss/site/common/_core.scss
@@ -0,0 +1,13 @@
+body {
+ -webkit-font-smoothing: antialiased;
+}
+
+
+a {
+ &.dark {
+ color: $body-color !important;
+ }
+ &.light {
+ color: $white !important;
+ }
+}
\ No newline at end of file
diff --git a/site/_scss/site/common/_fonts.scss b/site/_scss/site/common/_fonts.scss
new file mode 100644
index 000000000..db9bc821a
--- /dev/null
+++ b/site/_scss/site/common/_fonts.scss
@@ -0,0 +1,45 @@
+// Metropolis
+
+@font-face {
+ font-family: "Metropolis";
+ src: local("Metropolis Regular"), local("Metropolis-Regular"),
+ url("#{$path-fonts}/Metropolis/Metropolis-Regular.woff") format("woff");
+ font-weight: $font-weight-normal;
+}
+
+@font-face {
+ font-family: "Metropolis";
+ src: local("Metropolis Light"), local("Metropolis-Light"),
+ url("#{$path-fonts}/Metropolis/Metropolis-Light.woff") format("woff");
+ font-weight: $font-weight-light;
+}
+
+@font-face {
+ font-family: "Metropolis";
+ src: local("Metropolis Medium"), local("Metropolis-Medium"),
+ url("#{$path-fonts}/Metropolis/Metropolis-Medium.woff") format("woff");
+ font-weight: $font-weight-medium;
+}
+
+@font-face {
+ font-family: "Metropolis";
+ src: local("Metropolis SemiBold"), local("Metropolis-SemiBold"),
+ url("#{$path-fonts}/Metropolis/Metropolis-SemiBold.woff") format("woff");
+ font-weight: $font-weight-semibold;
+}
+
+@font-face {
+ font-family: "Metropolis";
+ src: local("Metropolis Bold"), local("Metropolis-Bold"),
+ url("#{$path-fonts}/Metropolis/Metropolis-Bold.woff") format("woff");
+ font-weight: $font-weight-bold;
+}
+
+// IcoMoon
+
+@font-face {
+ font-family: "IcoMoon-Free";
+ src: url("#{$path-fonts}/IcoMoon/IcoMoon-Free.ttf") format("truetype");
+ font-weight: normal;
+ font-style: normal;
+}
diff --git a/site/_scss/site/common/_type.scss b/site/_scss/site/common/_type.scss
new file mode 100644
index 000000000..9c4fd494a
--- /dev/null
+++ b/site/_scss/site/common/_type.scss
@@ -0,0 +1,38 @@
+
+h1,
+h2,
+h3,
+h4,
+h5,
+h6 {
+ font-weight: $font-weight-medium;
+}
+
+h1,
+h5,
+h6 {
+ font-weight: $font-weight-semibold;
+}
+
+h1 {
+ font-size: 2.875rem;
+ color: $body-color-darkest;
+
+ @include media-breakpoint-down(sm) {
+ font-size: 1.625rem;
+ }
+}
+
+h2 {
+ color: $body-color-darkest;
+ margin-bottom: 2rem;
+}
+
+h5 {
+ font-size: 1.375rem;
+ margin-bottom: 1.25rem;
+}
+
+strong {
+ font-weight: $font-weight-semibold;
+}
\ No newline at end of file
diff --git a/site/_scss/site/layouts/_container.scss b/site/_scss/site/layouts/_container.scss
new file mode 100644
index 000000000..cb0f9c42f
--- /dev/null
+++ b/site/_scss/site/layouts/_container.scss
@@ -0,0 +1,9 @@
+.site-outer-container {
+ max-width: $container-max-width;
+ padding-left: 0;
+ padding-right: 0;
+}
+
+.site-container {
+ background: $container-background;
+}
diff --git a/site/_scss/site/objects/_alternating-cards.scss b/site/_scss/site/objects/_alternating-cards.scss
new file mode 100644
index 000000000..0d8968d64
--- /dev/null
+++ b/site/_scss/site/objects/_alternating-cards.scss
@@ -0,0 +1,28 @@
+.alternating-cards {
+ .row {
+ border: 1px solid $border-color;
+ margin-bottom: 30px;
+ }
+ .icon {
+ min-height: 220px;
+ background: red; // default
+ text-align: center;
+ position: relative;
+ img {
+ position: absolute;
+ top: 50%;
+ left: 50%;
+ transform: translate(-50%, -50%);
+ }
+ }
+ .card-body {
+ padding: 40px 130px 32px 30px;
+ .card-title {
+ font-weight: $font-weight-medium;
+ }
+ p {
+ font-weight: $font-weight-light;
+ font-size: 0.875rem;
+ }
+ }
+}
\ No newline at end of file
diff --git a/site/_scss/site/objects/_button.scss b/site/_scss/site/objects/_button.scss
new file mode 100644
index 000000000..65d057c44
--- /dev/null
+++ b/site/_scss/site/objects/_button.scss
@@ -0,0 +1,59 @@
+.btn {
+ padding: {
+ top: 13px;
+ bottom: 9px;
+ }
+ font-size: 0.75rem;
+ border-radius: 5px;
+ text-transform: uppercase;
+ font-weight: $font-weight-bold;
+ &.btn-no-border {
+ border-width: 0 !important;
+ }
+ &:hover {
+ text-decoration: underlin;
+ }
+}
+
+.btn-sm {
+ padding: 12px 52px;
+}
+
+.btn-primary {
+ color: $button-primary-foreground;
+ background-color: $button-primary-background;
+ border-color: $button-primary-foreground;
+ &:hover {
+ color: $button-primary-background;
+ background-color: $button-primary-background-hover;
+ border-color: $button-primary-border-hover;
+ text-decoration: underline;
+ }
+}
+
+.btn-secondary {
+ color: $button-secondary-foreground;
+ background-color: $button-secondary-background;
+ border-color: $button-secondary-border;
+ &:hover {
+ color: $button-secondary-background;
+ background-color: $button-secondary-background-hover;
+ border-color: $button-secondary-border-hover;
+ text-decoration: underline;
+ }
+}
+
+.btn-outline-primary {
+ color: $button-primary-foreground;
+ background-color: transparent;
+ border-color: $button-primary-foreground;
+ &:hover {
+ color: $white;
+ background: $button-primary-foreground;
+ }
+}
+.btn-outline-light {
+ &:hover {
+ color: $button-primary-foreground;
+ }
+}
\ No newline at end of file
diff --git a/site/_scss/site/objects/_card.scss b/site/_scss/site/objects/_card.scss
new file mode 100644
index 000000000..355a96190
--- /dev/null
+++ b/site/_scss/site/objects/_card.scss
@@ -0,0 +1,56 @@
+.card {
+ border-radius: 0;
+ .card-body {
+ text-align: center;
+ padding: 2rem 1.25rem;
+ }
+
+ &.card-dark {
+ color: $card-dark-foreground;
+ background-color: $card-dark-background;
+ a {
+ color: $card-dark-link;
+ &:hover {
+ color: $card-dark-link-hover;
+ }
+ }
+ }
+
+ &.card-light {
+ a {
+ color: $card-light-link;
+ font-weight: $font-weight-medium
+ }
+ color: #777777;
+ background-color: $card-light-background;
+ p {
+ font-size: .875rem;
+ }
+ }
+ // specific blog card styles
+ &.blog-card {
+ .card-body {
+ padding: 0;
+ }
+ article.post {
+ padding: 2rem 1.25rem;
+ }
+ }
+}
+
+// landing page promo cards
+.promo-cards {
+ figure {
+ text-align: center;
+ height: 90px;
+ img {
+ width: auto;
+ max-height: 90px;
+ }
+ }
+ h5 {
+ margin-left: auto;
+ margin-right: auto;
+ width: 90%;
+ }
+}
\ No newline at end of file
diff --git a/site/_scss/site/objects/_footer.scss b/site/_scss/site/objects/_footer.scss
new file mode 100644
index 000000000..ba5be8d6a
--- /dev/null
+++ b/site/_scss/site/objects/_footer.scss
@@ -0,0 +1,44 @@
+.site-footer {
+ padding: 24px 0 34px 0;
+ .social-links {
+ color: $footer-foreground;
+ list-style: none;
+ padding: 0;
+ margin: 0;
+ a {
+ font-size: 0.75rem;
+ color: $footer-link-color;
+ &:hover {
+ color: $footer-link-color;
+ text-decoration: underline;
+ }
+ }
+ li {
+ display: inline-block;
+ padding: 5px;
+ &:hover {
+ color: $footer-link-color;
+ a {
+ text-decoration: underline;
+ }
+ }
+ }
+ }
+ .copyright {
+ font-size: 0.75rem;
+ font-weight: $font-weight-light;
+ color: $footer-copyright;
+ }
+ .logo {
+ max-width: 146px;
+ height: auto;
+ margin-left: 30px;
+ }
+ .vm-logo {
+ font-size: .75rem;
+ img {
+ max-width: 75px;
+ margin-left: 30px;
+ }
+ }
+}
\ No newline at end of file
diff --git a/site/_scss/site/objects/_header.scss b/site/_scss/site/objects/_header.scss
new file mode 100644
index 000000000..8d58f2823
--- /dev/null
+++ b/site/_scss/site/objects/_header.scss
@@ -0,0 +1,108 @@
+.site-header {
+ background: $header-background;
+
+ .site-header-content {
+ position: relative;
+ display: flex;
+ margin: 0 auto;
+ padding: 17px 0 18px 0;
+ max-width: $section-content-max-width;
+ @include media-breakpoint-down(lg) {
+ padding: {
+ left: $grid-gutter-width / 2 + $section-padding-x;
+ right: $grid-gutter-width / 2 + $section-padding-x;
+ }
+ }
+ }
+
+ .logo {
+ height: 45px;
+ width: auto;
+ }
+
+ .nav-mobile-link {
+ display: none;
+ position: absolute;
+ top: 50%;
+ right: 30px;
+ margin-top: -6px;
+
+ a {
+ display: block;
+ width: 23px;
+ height: 12px;
+ border-top: 4px solid $header-foreground;
+ border-bottom: 4px solid $header-foreground;
+ &.selected {
+ border-color: $header-foreground-selected;
+ }
+ }
+
+ @include media-breakpoint-down(sm) {
+ display: block;
+ }
+ }
+
+ .nav-menu {
+ flex: 1;
+ display: flex;
+ align-items: center;
+ justify-content: flex-end;
+ list-style: none;
+ margin: 0;
+ margin-left: 50px;
+ padding: 0;
+
+ @include media-breakpoint-down(sm) {
+ display: none;
+ position: absolute;
+ top: 100%;
+ left: 0;
+ right: 0;
+ margin: 0;
+ padding: 30px;
+ min-height: 250px;
+ background: $header-background;
+ box-shadow: 3px 2px 4px 2px rgba(0,0,0,0.25);
+
+ &.on {
+ display: block;
+ }
+
+ li {
+ font-size: 1.5rem;
+ }
+ }
+
+ li {
+ margin-right: 35px;
+ a {
+ font-weight: $font-weight-light;
+ font-size: .875rem;
+ }
+ &:last-child {
+ margin-right: 0;
+ }
+
+ &.selected {
+ a {
+ color: $header-foreground-selected;
+ font-weight: $font-weight-semibold;
+ &:hover {
+ color: $header-foreground-selected;
+ text-decoration: none;
+ }
+ }
+ }
+
+ a {
+ color: $header-foreground;
+
+ &:hover {
+ color: $header-foreground;
+ text-decoration: underline;
+ }
+ }
+ }
+ }
+}
\ No newline at end of file
diff --git a/site/_scss/site/objects/_home-hero.scss b/site/_scss/site/objects/_home-hero.scss
new file mode 100644
index 000000000..67e676349
--- /dev/null
+++ b/site/_scss/site/objects/_home-hero.scss
@@ -0,0 +1,55 @@
+.home-hero {
+ background-repeat: no-repeat;
+ background-position: top center;
+ @include media-breakpoint-down(sm) {
+ background-image: none !important;
+ }
+ @include media-breakpoint-up(md) {
+ min-height: 500px;
+ }
+ color: $white;
+ h1,
+ h2,
+ h3 {
+ color: $white;
+ font-weight: $font-weight-light;
+ }
+ .section-content {
+ margin-top: 15px;
+ .hero-content,
+ .hero-cta {
+ @include media-breakpoint-up(md) {
+ @include make-col-ready();
+ @include make-col(8);
+ }
+ }
+ }
+
+ .hero-cta {
+ display: block;
+ margin-bottom: 70px;
+ @include media-breakpoint-up(md) {
+ display: flex;
+ flex-direction: row;
+ justify-content: left;
+ }
+ .btn {
+ @include media-breakpoint-up(md) {
+ min-width: 250px;
+ }
+ padding: {
+ top: 16px;
+ bottom: 16px;
+ }
+ margin: 0 32px 0 0;
+ }
+ }
+
+ .section-card {
+ margin-top: 68px;
+ .section-content {
+ background-color: transparent;
+ padding: 0;
+ }
+ }
+}
diff --git a/site/_scss/site/objects/_post.scss b/site/_scss/site/objects/_post.scss
new file mode 100644
index 000000000..d8cacb82d
--- /dev/null
+++ b/site/_scss/site/objects/_post.scss
@@ -0,0 +1,131 @@
+.post-thumbnail {
+ width: 100%;
+ margin: 0 auto 1.875rem auto;
+ height: 137px;
+ position: relative;
+ img {
+ width: auto;
+ height: auto;
+ max-width: 100%;
+ max-height: 100%;
+ position: absolute;
+ top: 50%;
+ left: 50%;
+ transform: translate(-50%, -50%);
+ }
+}
+
+.post-single-hero {
+ background-color: map-get($field-backgrounds, 'med-blue'); // default
+ padding-bottom: 105px;
+ h1,
+ h2,
+ h3 {
+ color: $white;
+ font-weight: $font-weight-light;
+ text-align: center;
+ }
+}
+
+.post-single-body {
+ margin-top: -105px;
+}
+
+.post-single-meta {
+ display: flex;
+ align-items: center;
+ color: $post-meta-foreground;
+ margin-bottom: 3rem;
+
+ @include media-breakpoint-down(sm) {
+ // flex-direction: column;
+ display: block;
+ }
+}
+
+.post-single-meta-author {
+ display: flex;
+ align-items: center;
+ flex: 1;
+ margin-right: 1rem;
+
+ @include media-breakpoint-down(sm) {
+ justify-content: center;
+ margin-right: 0;
+ margin-bottom: 1rem;
+ }
+}
+
+.post-single-meta-author-avatar {
+ border-radius: 50%;
+ width: 64px;
+ height: 64px;
+ margin-right: 1rem;
+ overflow: hidden;
+
+ img {
+ width: 100%;
+ height: auto;
+ }
+}
+
+.post-single-meta-author-name {
+ flex: 1;
+ font-weight: $font-weight-semibold;
+
+ @include media-breakpoint-down(sm) {
+ flex: none;
+ }
+}
+
+.post-single-meta-date {
+ text-align: right;
+
+ @include media-breakpoint-down(sm) {
+ text-align: center;
+ }
+}
+
+.post-single-image {
+ margin: 0 auto 3rem auto;
+ max-width: 700px;
+
+ img {
+ height: auto;
+ width: 100%;
+ }
+
+ @include media-breakpoint-down(sm) {
+ margin-left: -30px;
+ margin-right: -30px;
+ }
+}
+
+.post-single-content {
+ max-width: 700px;
+ margin: 0 auto 3rem auto;
+
+ h2,
+ h3,
+ p {
+ margin-bottom: 1.875rem;
+ }
+
+ h2 {
+ font-size: $font-size-base;
+ font-weight: $font-weight-semibold;
+ }
+
+ h3 {
+ font-size: $font-size-base;
+ font-weight: $font-weight-medium;
+ }
+
+ p:last-child {
+ margin-bottom: 0;
+ }
+
+ img {
+ max-width: 100%;
+ }
+}
\ No newline at end of file
diff --git a/site/_scss/site/objects/_section.scss b/site/_scss/site/objects/_section.scss
new file mode 100644
index 000000000..0e6006b2a
--- /dev/null
+++ b/site/_scss/site/objects/_section.scss
@@ -0,0 +1,51 @@
+.section {
+ padding: $section-padding-y $section-padding-x;
+ &.section-blue {
+ color: $section-blue-foreground;
+ background: $section-blue-background;
+ }
+
+ &.section-grey {
+ color: $body-color-darkest;
+ background: $section-grey-background;
+ }
+
+ &.section-card {
+ padding-top: 0;
+ padding-left: 0;
+ padding-right: 0;
+ &.section-card-offset-top {
+ .row {
+ margin-top: -120px;
+ }
+ .section-content {
+ @include media-breakpoint-up(lg) {
+ padding: {
+ left: 0;
+ right: 0;
+ }
+ }
+ }
+ }
+ .section-content {
+ max-width: $section-content-max-width;
+ background: $white;
+ border-radius: 0;
+ padding: 45px 30px;
+ min-height: 115px;
+ @include media-breakpoint-down(sm) {
+ border-radius: 0;
+ }
+ }
+ }
+
+ .section-content {
+ max-width: $section-content-max-width;
+ margin: 0 auto;
+
+ &.section-content-thin {
+ padding-left: 50px;
+ padding-right: 50px;
+ }
+ }
+}
\ No newline at end of file
diff --git a/site/_scss/site/objects/_thumbnail-grid.scss b/site/_scss/site/objects/_thumbnail-grid.scss
new file mode 100644
index 000000000..cb463e4e0
--- /dev/null
+++ b/site/_scss/site/objects/_thumbnail-grid.scss
@@ -0,0 +1,27 @@
+.thumbnail-grid {
+ color: $white;
+ h6 {
+ font-size: 1rem;
+ margin-bottom: 0;
+ a {
+ color: $white;
+ }
+ }
+ p {
+ font-size: .875rem;
+ }
+ .thumbnail-item {
+ margin-bottom: 2.5rem;
+ img {
+ width: 80px;
+ height: 80px;
+ @include media-breakpoint-up(md) {
+ width: 120px;
+ height: 120px;
+ }
+ }
+ }
+ .media-body {
+ margin-left: 20px;
+ }
+}
\ No newline at end of file
diff --git a/site/_scss/site/settings/_variables.scss b/site/_scss/site/settings/_variables.scss
new file mode 100644
index 000000000..46204f3d1
--- /dev/null
+++ b/site/_scss/site/settings/_variables.scss
@@ -0,0 +1,121 @@
+// File Paths
+$path-fonts: "fonts";
+$path-images: "img";
+
+// Colors
+
+$black: #000;
+$white: #fff;
+$light: $white;
+
+// Bootstrap overrides
+
+$body-bg: #bbb;
+$body-color: #3F3E3E;
+$box-shadow-sm: 0px 2px 4px 0px rgba(0,0,0,0.5);
+$border-color: #E8E8E8;
+
+$card-border-width: 1px;
+$card-border-color: $border-color;
+
+$font-family-base: "Metropolis", Helvetica, Arial, sans-serif;
+$font-size-base: 1.125rem; // 18px
+
+$link-color: #0096D9;
+$link-decoration: none;
+$link-hover-color: $link-color;
+$link-hover-decoration: underline;
+
+$font-weight-light: 300;
+$font-weight-normal: 400;
+$font-weight-medium: 500;
+$font-weight-semibold: 600;
+$font-weight-bold: 700;
+
+// Custom
+
+$body-color-darker: #333;
+$body-color-darkest: #111;
+
+// Container
+
+$container-background: $white;
+$container-max-width: 1440px;
+
+// Header
+
+$header-background: $white;
+$header-foreground: #777;
+$header-foreground-selected: #777777;
+
+// Footer
+$footer-foreground: #E8E8E8;
+$footer-link-color: #777777;
+$footer-copyright: #777777;
+
+// Sections
+
+$section-content-max-width: 996px;
+$section-grey-background: #f2f2f2;
+
+$section-blue-background: #0165AB;
+$section-blue-foreground: $white;
+
+// Cards
+
+$card-dark-background: #0165AB;
+$card-dark-foreground: $white;
+$card-dark-link: $white;
+$card-dark-link-hover: $white;
+
+$card-light-background: $white;
+$card-light-link: $link-color;
+
+// alternating cards
+$field-backgrounds: (
+ 'light-blue': #00C1D5,
+ 'med-blue': #0091DA,
+ 'dark-blue': #1D428A,
+ 'darkest-blue': #002538,
+ 'green': #78BE20
+);
+
+@each $name, $hex in $field-backgrounds {
+ .section-background-#{$name} {
+ background-color: #{$hex} !important;
+ color: $white !important;
+ h1,
+ h2,
+ p {
+ color: $white !important;
+ }
+ }
+ .bg-color-#{$name} {
+ background-color: #{$hex} !important;
+ }
+}
+
+
+
+// Buttons
+
+$button-primary-background: $white;
+$button-primary-background-hover: #0091DA;
+$button-primary-foreground: #0091DA;
+$button-primary-border: $button-primary-background;
+$button-primary-border-hover: $button-primary-background;
+
+$button-secondary-background: #0091DA;
+$button-secondary-background-hover: $white;
+$button-secondary-foreground: $white;
+$button-secondary-border: $white;
+$button-secondary-border-hover: #0091DA;
+
+// Posts
+$post-hero-gradient-start: #fafafa;
+$post-hero-gradient-end: #ddd;
+$post-meta-foreground: $body-color-darker;
+
+// section
+$section-padding-x: 30px;
+$section-padding-y: 40px;
diff --git a/site/_scss/site/utilities/_image.scss b/site/_scss/site/utilities/_image.scss
new file mode 100644
index 000000000..44787da8c
--- /dev/null
+++ b/site/_scss/site/utilities/_image.scss
@@ -0,0 +1,3 @@
+.thumbnail img {
+ width: 100%;
+}
diff --git a/site/_scss/site/utilities/_type.scss b/site/_scss/site/utilities/_type.scss
new file mode 100644
index 000000000..374900f13
--- /dev/null
+++ b/site/_scss/site/utilities/_type.scss
@@ -0,0 +1,44 @@
+// Weights
+
+.font-weight-light {
+ font-weight: $font-weight-light !important;
+}
+
+.font-weight-normal {
+ font-weight: $font-weight-normal !important;
+}
+
+.font-weight-medium {
+ font-weight: $font-weight-medium !important;
+}
+
+.font-weight-semibold {
+ font-weight: $font-weight-semibold !important;
+}
+
+.font-weight-bold {
+ font-weight: $font-weight-bold !important;
+}
+
+// Colors
+
+.font-color-darker {
+ color: $body-color-darker !important;
+}
+
+.font-color-darkest {
+ color: $body-color-darkest !important;
+}
+
+// Misc
+
+p {
+ &.lead-in {
+ color: $body-color-darker;
+ font-size: 1.375rem;
+
+ @include media-breakpoint-down(sm) {
+ font-size: 1.125rem;
+ }
+ }
+}
diff --git a/site/blog.html b/site/blog.html
new file mode 100644
index 000000000..594677cc1
--- /dev/null
+++ b/site/blog.html
@@ -0,0 +1,19 @@
+---
+layout: default
+title: Blog
+id: blog
+---
+
+
+
+
+ {% include blog-posts.html %}
+
+
+
\ No newline at end of file
diff --git a/site/community.md b/site/community.md
new file mode 100644
index 000000000..21a4fd412
--- /dev/null
+++ b/site/community.md
@@ -0,0 +1,18 @@
+---
+layout: page
+title: Community
+id: community
+---
+## Do you want to help build Velero?
+
+If you’re a newcomer, check out the “[Good first issue](https://github.com/heptio/velero/issues?q=is%3Aopen+is%3Aissue+label%3A%22Good+first+issue%22)” and “[Help wanted](https://github.com/heptio/velero/issues?utf8=%E2%9C%93&q=is%3Aopen+is%3Aissue+label%3A%22Help+wanted%22+)” labels in the Velero repository.
+
+* Follow us on Twitter at [@projectvelero](https://groups.google.com/forum/#!forum/projectvelero)
+
+* Join our Kubernetes Slack channel and talk to over 800 other community members: [#velero](https://groups.google.com/forum/#!forum/projectvelero)
+
+* Join our [Google Group](https://groups.google.com/forum/#!forum/projectvelero) to get updates on the project and invites to community meetings.
+
+* Join the Velero community meetings every 1st and 3rd Tuesday:
+
+* See previous community meetings on our [YouTube Channel](https://www.youtube.com/playlist?list=PL7bmigfV0EqQRysvqvqOtRNk4L5S7uqwM)
\ No newline at end of file
diff --git a/site/css/fonts/IcoMoon/IcoMoon-Free.ttf b/site/css/fonts/IcoMoon/IcoMoon-Free.ttf
new file mode 100755
index 000000000..56919449d
Binary files /dev/null and b/site/css/fonts/IcoMoon/IcoMoon-Free.ttf differ
diff --git a/site/css/fonts/Metropolis/Metropolis-Bold.woff b/site/css/fonts/Metropolis/Metropolis-Bold.woff
new file mode 100755
index 000000000..b9eb25136
Binary files /dev/null and b/site/css/fonts/Metropolis/Metropolis-Bold.woff differ
diff --git a/site/css/fonts/Metropolis/Metropolis-BoldItalic.woff b/site/css/fonts/Metropolis/Metropolis-BoldItalic.woff
new file mode 100755
index 000000000..3d0d67d86
Binary files /dev/null and b/site/css/fonts/Metropolis/Metropolis-BoldItalic.woff differ
diff --git a/site/css/fonts/Metropolis/Metropolis-Light.woff b/site/css/fonts/Metropolis/Metropolis-Light.woff
new file mode 100755
index 000000000..7bdd5d9ff
Binary files /dev/null and b/site/css/fonts/Metropolis/Metropolis-Light.woff differ
diff --git a/site/css/fonts/Metropolis/Metropolis-LightItalic.woff b/site/css/fonts/Metropolis/Metropolis-LightItalic.woff
new file mode 100755
index 000000000..9dbe57082
Binary files /dev/null and b/site/css/fonts/Metropolis/Metropolis-LightItalic.woff differ
diff --git a/site/css/fonts/Metropolis/Metropolis-Medium.woff b/site/css/fonts/Metropolis/Metropolis-Medium.woff
new file mode 100755
index 000000000..90cb752a5
Binary files /dev/null and b/site/css/fonts/Metropolis/Metropolis-Medium.woff differ
diff --git a/site/css/fonts/Metropolis/Metropolis-MediumItalic.woff b/site/css/fonts/Metropolis/Metropolis-MediumItalic.woff
new file mode 100755
index 000000000..34335d647
Binary files /dev/null and b/site/css/fonts/Metropolis/Metropolis-MediumItalic.woff differ
diff --git a/site/css/fonts/Metropolis/Metropolis-Regular.woff b/site/css/fonts/Metropolis/Metropolis-Regular.woff
new file mode 100755
index 000000000..312202cf1
Binary files /dev/null and b/site/css/fonts/Metropolis/Metropolis-Regular.woff differ
diff --git a/site/css/fonts/Metropolis/Metropolis-RegularItalic.woff b/site/css/fonts/Metropolis/Metropolis-RegularItalic.woff
new file mode 100755
index 000000000..63846f94e
Binary files /dev/null and b/site/css/fonts/Metropolis/Metropolis-RegularItalic.woff differ
diff --git a/site/css/fonts/Metropolis/Metropolis-SemiBold.woff b/site/css/fonts/Metropolis/Metropolis-SemiBold.woff
new file mode 100755
index 000000000..c41071185
Binary files /dev/null and b/site/css/fonts/Metropolis/Metropolis-SemiBold.woff differ
diff --git a/site/css/fonts/Metropolis/Metropolis-SemiBoldItalic.woff b/site/css/fonts/Metropolis/Metropolis-SemiBoldItalic.woff
new file mode 100755
index 000000000..522f97da2
Binary files /dev/null and b/site/css/fonts/Metropolis/Metropolis-SemiBoldItalic.woff differ
diff --git a/site/css/fonts/Metropolis/Open Font License.md b/site/css/fonts/Metropolis/Open Font License.md
new file mode 100755
index 000000000..9f52ca56e
--- /dev/null
+++ b/site/css/fonts/Metropolis/Open Font License.md
@@ -0,0 +1,105 @@
+ Copyright (c) 2015, Chris Simpson , with Reserved Font Name: "Metropolis".
+
+ This Font Software is licensed under the SIL Open Font License, Version 1.1.
+ This license is copied below, and is also available with a FAQ at:
+ http://scripts.sil.org/OFL
+
+ Version 2.0 - 18 March 2012
+
+
+SIL Open Font License
+====================================================
+
+
+Preamble
+----------
+
+The goals of the Open Font License (OFL) are to stimulate worldwide
+development of collaborative font projects, to support the font creation
+efforts of academic and linguistic communities, and to provide a free and
+open framework in which fonts may be shared and improved in partnership
+with others.
+
+The OFL allows the licensed fonts to be used, studied, modified and
+redistributed freely as long as they are not sold by themselves. The
+fonts, including any derivative works, can be bundled, embedded,
+redistributed and/or sold with any software provided that any reserved
+names are not used by derivative works. The fonts and derivatives,
+however, cannot be released under any other type of license. The
+requirement for fonts to remain under this license does not apply
+to any document created using the fonts or their derivatives.
+
+Definitions
+-------------
+
+`"Font Software"` refers to the set of files released by the Copyright
+Holder(s) under this license and clearly marked as such. This may
+include source files, build scripts and documentation.
+
+`"Reserved Font Name"` refers to any names specified as such after the
+copyright statement(s).
+
+`"Original Version"` refers to the collection of Font Software components as
+distributed by the Copyright Holder(s).
+
+`"Modified Version"` refers to any derivative made by adding to, deleting,
+or substituting -- in part or in whole -- any of the components of the
+Original Version, by changing formats or by porting the Font Software to a
+new environment.
+
+`"Author"` refers to any designer, engineer, programmer, technical
+writer or other person who contributed to the Font Software.
+
+Permission & Conditions
+------------------------
+
+Permission is hereby granted, free of charge, to any person obtaining
+a copy of the Font Software, to use, study, copy, merge, embed, modify,
+redistribute, and sell modified and unmodified copies of the Font
+Software, subject to the following conditions:
+
+1. Neither the Font Software nor any of its individual components,
+in Original or Modified Versions, may be sold by itself.
+
+2. Original or Modified Versions of the Font Software may be bundled,
+redistributed and/or sold with any software, provided that each copy
+contains the above copyright notice and this license. These can be
+included either as stand-alone text files, human-readable headers or
+in the appropriate machine-readable metadata fields within text or
+binary files as long as those fields can be easily viewed by the user.
+
+3. No Modified Version of the Font Software may use the Reserved Font
+Name(s) unless explicit written permission is granted by the corresponding
+Copyright Holder. This restriction only applies to the primary font name as
+presented to the users.
+
+4. The name(s) of the Copyright Holder(s) or the Author(s) of the Font
+Software shall not be used to promote, endorse or advertise any
+Modified Version, except to acknowledge the contribution(s) of the
+Copyright Holder(s) and the Author(s) or with their explicit written
+permission.
+
+5. The Font Software, modified or unmodified, in part or in whole,
+must be distributed entirely under this license, and must not be
+distributed under any other license. The requirement for fonts to
+remain under this license does not apply to any document created
+using the Font Software.
+
+Termination
+-----------
+
+This license becomes null and void if any of the above conditions are
+not met.
+
+
+ DISCLAIMER
+
+ THE FONT SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND,
+ EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTIES OF
+ MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT
+ OF COPYRIGHT, PATENT, TRADEMARK, OR OTHER RIGHT. IN NO EVENT SHALL THE
+ COPYRIGHT HOLDER BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY,
+ INCLUDING ANY GENERAL, SPECIAL, INDIRECT, INCIDENTAL, OR CONSEQUENTIAL
+ DAMAGES, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING
+ FROM, OUT OF THE USE OR INABILITY TO USE THE FONT SOFTWARE OR FROM
+ OTHER DEALINGS IN THE FONT SOFTWARE.
diff --git a/site/css/fonts/Metropolis/README.md b/site/css/fonts/Metropolis/README.md
new file mode 100755
index 000000000..e6b973aba
--- /dev/null
+++ b/site/css/fonts/Metropolis/README.md
@@ -0,0 +1,24 @@
+
+
+# The Metropolis Typeface
+
+The Vision
+---
+To create a modern, geometric typeface. Open sourced, and openly available. Influenced by other popular geometric, minimalist sans-serif typefaces of the new millenium. Designed for optimal readability at small point sizes while beautiful at large point sizes.
+
+December 2017 update
+---
+Currently working on greatly improving spacing and kerning of the base typeface. Once this is done, work on other variations (e.g. rounded or slab) can begin in earnest.
+
+The License
+---
+Licensed under Open Font License (OFL). Available to anyone and everyone. Contributions welcome.
+
+Contact
+---
+Contact me via chris.m.simpson@icloud.com or http://twitter.com/ChrisMSimpson for any questions, requests or improvements (or just submit a pull request).
+
+Support
+---
+You can now support work on Metropolis via Patreon at https://www.patreon.com/metropolis.
+
diff --git a/site/css/styles.scss b/site/css/styles.scss
new file mode 100644
index 000000000..0977fd727
--- /dev/null
+++ b/site/css/styles.scss
@@ -0,0 +1,3 @@
+---
+---
+@import '../_scss/styles';
diff --git a/site/docs/master/README.md b/site/docs/master/README.md
new file mode 100644
index 000000000..a65168e75
--- /dev/null
+++ b/site/docs/master/README.md
@@ -0,0 +1,81 @@
+![100]
+
+[![Build Status][1]][2]
+
+## Overview
+
+Velero (formerly Heptio Ark) gives you tools to back up and restore your Kubernetes cluster resources and persistent volumes. Velero lets you:
+
+* Take backups of your cluster and restore in case of loss.
+* Copy cluster resources to other clusters.
+* Replicate your production environment for development and testing environments.
+
+Velero consists of:
+
+* A server that runs on your cluster
+* A command-line client that runs locally
+
+You can run Velero in clusters on a cloud provider or on-premises. For detailed information, see [Compatible Storage Providers][99].
+
+## Installation
+
+We strongly recommend that you use an [official release][6] of Velero. The tarballs for each release contain the
+command-line client **and** version-specific sample YAML files for deploying Velero to your cluster.
+Follow the instructions under the **Install** section of [our documentation][29] to get started.
+
+_The code and sample YAML files in the master branch of the Velero repository are under active development and are not guaranteed to be stable. Use them at your own risk!_
+
+## More information
+
+[The documentation][29] provides a getting started guide, plus information about building from source, architecture, extending Velero, and more.
+
+Please use the version selector at the top of the site to ensure you are using the appropriate documentation for your version of Velero.
+
+## Troubleshooting
+
+If you encounter issues, review the [troubleshooting docs][30], [file an issue][4], or talk to us on the [#velero channel][25] on the Kubernetes Slack server.
+
+## Contributing
+
+Thanks for taking the time to join our community and start contributing!
+
+Feedback and discussion are available on [the mailing list][24].
+
+### Before you start
+
+* Please familiarize yourself with the [Code of Conduct][8] before contributing.
+* See [CONTRIBUTING.md][5] for instructions on the developer certificate of origin that we require.
+* Read how [we're using ZenHub][26] for project and roadmap planning
+
+### Pull requests
+
+* We welcome pull requests. Feel free to dig through the [issues][4] and jump in.
+
+## Changelog
+
+See [the list of releases][6] to find out about feature changes.
+
+[1]: https://travis-ci.org/heptio/velero.svg?branch=master
+[2]: https://travis-ci.org/heptio/velero
+
+[4]: https://github.com/heptio/velero/issues
+[5]: https://github.com/heptio/velero/blob/master/CONTRIBUTING.md
+[6]: https://github.com/heptio/velero/releases
+
+[8]: https://github.com/heptio/velero/blob/master/CODE_OF_CONDUCT.md
+[9]: https://kubernetes.io/docs/setup/
+[10]: https://kubernetes.io/docs/tasks/tools/install-kubectl/#install-with-homebrew-on-macos
+[11]: https://kubernetes.io/docs/tasks/tools/install-kubectl/#tabset-1
+[12]: https://github.com/kubernetes/kubernetes/blob/master/cluster/addons/dns/README.md
+[14]: https://github.com/kubernetes/kubernetes
+
+[24]: https://groups.google.com/forum/#!forum/projectvelero
+[25]: https://kubernetes.slack.com/messages/velero
+[26]: https://github.com/heptio/velero/blob/master/docs/zenhub.md
+
+
+[29]: https://heptio.github.io/velero/
+[30]: troubleshooting.md
+
+[99]: support-matrix.md
+[100]: img/velero.png
diff --git a/docs/about.md b/site/docs/master/about.md
similarity index 100%
rename from docs/about.md
rename to site/docs/master/about.md
diff --git a/docs/api-types/README.md b/site/docs/master/api-types/README.md
similarity index 100%
rename from docs/api-types/README.md
rename to site/docs/master/api-types/README.md
diff --git a/docs/api-types/backup.md b/site/docs/master/api-types/backup.md
similarity index 100%
rename from docs/api-types/backup.md
rename to site/docs/master/api-types/backup.md
diff --git a/docs/api-types/backupstoragelocation.md b/site/docs/master/api-types/backupstoragelocation.md
similarity index 100%
rename from docs/api-types/backupstoragelocation.md
rename to site/docs/master/api-types/backupstoragelocation.md
diff --git a/docs/api-types/volumesnapshotlocation.md b/site/docs/master/api-types/volumesnapshotlocation.md
similarity index 100%
rename from docs/api-types/volumesnapshotlocation.md
rename to site/docs/master/api-types/volumesnapshotlocation.md
diff --git a/docs/aws-config.md b/site/docs/master/aws-config.md
similarity index 100%
rename from docs/aws-config.md
rename to site/docs/master/aws-config.md
diff --git a/docs/azure-config.md b/site/docs/master/azure-config.md
similarity index 100%
rename from docs/azure-config.md
rename to site/docs/master/azure-config.md
diff --git a/docs/build-from-source.md b/site/docs/master/build-from-source.md
similarity index 100%
rename from docs/build-from-source.md
rename to site/docs/master/build-from-source.md
diff --git a/docs/debugging-install.md b/site/docs/master/debugging-install.md
similarity index 100%
rename from docs/debugging-install.md
rename to site/docs/master/debugging-install.md
diff --git a/docs/debugging-restores.md b/site/docs/master/debugging-restores.md
similarity index 100%
rename from docs/debugging-restores.md
rename to site/docs/master/debugging-restores.md
diff --git a/docs/disaster-case.md b/site/docs/master/disaster-case.md
similarity index 100%
rename from docs/disaster-case.md
rename to site/docs/master/disaster-case.md
diff --git a/docs/extend.md b/site/docs/master/extend.md
similarity index 100%
rename from docs/extend.md
rename to site/docs/master/extend.md
diff --git a/docs/faq.md b/site/docs/master/faq.md
similarity index 100%
rename from docs/faq.md
rename to site/docs/master/faq.md
diff --git a/docs/gcp-config.md b/site/docs/master/gcp-config.md
similarity index 100%
rename from docs/gcp-config.md
rename to site/docs/master/gcp-config.md
diff --git a/docs/get-started.md b/site/docs/master/get-started.md
similarity index 100%
rename from docs/get-started.md
rename to site/docs/master/get-started.md
diff --git a/docs/hooks.md b/site/docs/master/hooks.md
similarity index 100%
rename from docs/hooks.md
rename to site/docs/master/hooks.md
diff --git a/docs/ibm-config.md b/site/docs/master/ibm-config.md
similarity index 100%
rename from docs/ibm-config.md
rename to site/docs/master/ibm-config.md
diff --git a/docs/image-tagging.md b/site/docs/master/image-tagging.md
similarity index 100%
rename from docs/image-tagging.md
rename to site/docs/master/image-tagging.md
diff --git a/docs/img/README.md b/site/docs/master/img/README.md
similarity index 100%
rename from docs/img/README.md
rename to site/docs/master/img/README.md
diff --git a/docs/img/backup-process.png b/site/docs/master/img/backup-process.png
similarity index 100%
rename from docs/img/backup-process.png
rename to site/docs/master/img/backup-process.png
diff --git a/docs/img/velero.png b/site/docs/master/img/velero.png
similarity index 100%
rename from docs/img/velero.png
rename to site/docs/master/img/velero.png
diff --git a/docs/install-overview.md b/site/docs/master/install-overview.md
similarity index 100%
rename from docs/install-overview.md
rename to site/docs/master/install-overview.md
diff --git a/site/docs/master/issue-template-gen/main.go b/site/docs/master/issue-template-gen/main.go
new file mode 100644
index 000000000..5adc1b647
--- /dev/null
+++ b/site/docs/master/issue-template-gen/main.go
@@ -0,0 +1,45 @@
+/*
+Copyright 2018 the Velero contributors.
+
+Licensed under the Apache License, Version 2.0 (the "License");
+you may not use this file except in compliance with the License.
+You may obtain a copy of the License at
+
+ http://www.apache.org/licenses/LICENSE-2.0
+
+Unless required by applicable law or agreed to in writing, software
+distributed under the License is distributed on an "AS IS" BASIS,
+WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+See the License for the specific language governing permissions and
+limitations under the License.
+*/
+
+// This code renders the IssueTemplate string in pkg/cmd/cli/bug/bug.go to
+// .github/ISSUE_TEMPLATE/bug_report.md via the hack/update-generated-issue-template.sh script.
+
+package main
+
+import (
+ "log"
+ "os"
+ "text/template"
+
+ "github.com/heptio/velero/pkg/cmd/cli/bug"
+)
+
+func main() {
+ outTemplateFilename := os.Args[1]
+ outFile, err := os.OpenFile(outTemplateFilename, os.O_CREATE|os.O_TRUNC|os.O_WRONLY, 0644)
+ if err != nil {
+ log.Fatal(err)
+ }
+ defer outFile.Close()
+ tmpl, err := template.New("ghissue").Parse(bug.IssueTemplate)
+ if err != nil {
+ log.Fatal(err)
+ }
+ err = tmpl.Execute(outFile, bug.VeleroBugInfo{})
+ if err != nil {
+ log.Fatal(err)
+ }
+}
diff --git a/docs/locations.md b/site/docs/master/locations.md
similarity index 100%
rename from docs/locations.md
rename to site/docs/master/locations.md
diff --git a/docs/migrating-to-velero.md b/site/docs/master/migrating-to-velero.md
similarity index 100%
rename from docs/migrating-to-velero.md
rename to site/docs/master/migrating-to-velero.md
diff --git a/docs/migration-case.md b/site/docs/master/migration-case.md
similarity index 100%
rename from docs/migration-case.md
rename to site/docs/master/migration-case.md
diff --git a/docs/namespace.md b/site/docs/master/namespace.md
similarity index 100%
rename from docs/namespace.md
rename to site/docs/master/namespace.md
diff --git a/docs/output-file-format.md b/site/docs/master/output-file-format.md
similarity index 100%
rename from docs/output-file-format.md
rename to site/docs/master/output-file-format.md
diff --git a/docs/plugins.md b/site/docs/master/plugins.md
similarity index 100%
rename from docs/plugins.md
rename to site/docs/master/plugins.md
diff --git a/docs/rbac.md b/site/docs/master/rbac.md
similarity index 100%
rename from docs/rbac.md
rename to site/docs/master/rbac.md
diff --git a/docs/restic.md b/site/docs/master/restic.md
similarity index 100%
rename from docs/restic.md
rename to site/docs/master/restic.md
diff --git a/docs/support-matrix.md b/site/docs/master/support-matrix.md
similarity index 100%
rename from docs/support-matrix.md
rename to site/docs/master/support-matrix.md
diff --git a/docs/troubleshooting.md b/site/docs/master/troubleshooting.md
similarity index 100%
rename from docs/troubleshooting.md
rename to site/docs/master/troubleshooting.md
diff --git a/docs/upgrade-to-1.0.md b/site/docs/master/upgrade-to-1.0.md
similarity index 100%
rename from docs/upgrade-to-1.0.md
rename to site/docs/master/upgrade-to-1.0.md
diff --git a/docs/vendoring-dependencies.md b/site/docs/master/vendoring-dependencies.md
similarity index 100%
rename from docs/vendoring-dependencies.md
rename to site/docs/master/vendoring-dependencies.md
diff --git a/docs/zenhub.md b/site/docs/master/zenhub.md
similarity index 100%
rename from docs/zenhub.md
rename to site/docs/master/zenhub.md
diff --git a/site/docs/v0.10.0/README.md b/site/docs/v0.10.0/README.md
new file mode 100644
index 000000000..e1f68e8a5
--- /dev/null
+++ b/site/docs/v0.10.0/README.md
@@ -0,0 +1,78 @@
+# Heptio Ark
+
+**Maintainers:** [Heptio][0]
+
+[![Build Status][1]][2]
+
+## Overview
+
+Ark gives you tools to back up and restore your Kubernetes cluster resources and persistent volumes. Ark lets you:
+
+* Take backups of your cluster and restore in case of loss.
+* Copy cluster resources to other clusters.
+* Replicate your production environment for development and testing environments.
+
+Ark consists of:
+
+* A server that runs on your cluster
+* A command-line client that runs locally
+
+You can run Ark in clusters on a cloud provider or on-premises. For detailed information, see [Compatible Storage Providers][99].
+
+## Breaking changes
+
+Ark version 0.10.0 introduces a number of breaking changes. Before you upgrade to version 0.10.0, make sure to read [the documentation on upgrading](upgrading-to-v0.10.md).
+
+## More information
+
+[The documentation][29] provides a getting started guide, plus information about building from source, architecture, extending Ark, and more.
+
+## Troubleshooting
+
+If you encounter issues, review the [troubleshooting docs][30], [file an issue][4], or talk to us on the [#ark-dr channel][25] on the Kubernetes Slack server.
+
+## Contributing
+
+Thanks for taking the time to join our community and start contributing!
+
+Feedback and discussion are available on [the mailing list][24].
+
+### Before you start
+
+* Please familiarize yourself with the [Code of Conduct][8] before contributing.
+* See [CONTRIBUTING.md][5] for instructions on the developer certificate of origin that we require.
+* Read how [we're using ZenHub][26] for project and roadmap planning
+
+### Pull requests
+
+* We welcome pull requests. Feel free to dig through the [issues][4] and jump in.
+
+## Changelog
+
+See [the list of releases][6] to find out about feature changes.
+
+[0]: https://github.com/heptio
+[1]: https://travis-ci.org/heptio/ark.svg?branch=master
+[2]: https://travis-ci.org/heptio/ark
+
+[4]: https://github.com/heptio/ark/issues
+[5]: https://github.com/heptio/ark/blob/master/CONTRIBUTING.md
+[6]: https://github.com/heptio/ark/releases
+
+[8]: https://github.com/heptio/ark/blob/master/CODE_OF_CONDUCT.md
+[9]: https://kubernetes.io/docs/setup/
+[10]: https://kubernetes.io/docs/tasks/tools/install-kubectl/#install-with-homebrew-on-macos
+[11]: https://kubernetes.io/docs/tasks/tools/install-kubectl/#tabset-1
+[12]: https://github.com/kubernetes/kubernetes/blob/master/cluster/addons/dns/README.md
+[14]: https://github.com/kubernetes/kubernetes
+
+
+[24]: http://j.hept.io/ark-list
+[25]: https://kubernetes.slack.com/messages/ark-dr
+[26]: https://github.com/heptio/ark/blob/master/docs/zenhub.md
+
+
+[29]: https://heptio.github.io/velero/
+[30]: /troubleshooting.md
+
+[99]: /support-matrix.md
diff --git a/site/docs/v0.10.0/about.md b/site/docs/v0.10.0/about.md
new file mode 100644
index 000000000..6270ca8a5
--- /dev/null
+++ b/site/docs/v0.10.0/about.md
@@ -0,0 +1,73 @@
+# How Ark Works
+
+Each Ark operation -- on-demand backup, scheduled backup, restore -- is a custom resource, defined with a Kubernetes [Custom Resource Definition (CRD)][20] and stored in [etcd][22]. Ark also includes controllers that process the custom resources to perform backups, restores, and all related operations.
+
+You can back up or restore all objects in your cluster, or you can filter objects by type, namespace, and/or label.
+
+Ark is ideal for the disaster recovery use case, as well as for snapshotting your application state, prior to performing system operations on your cluster (e.g. upgrades).
+
+## On-demand backups
+
+The **backup** operation:
+
+1. Uploads a tarball of copied Kubernetes objects into cloud object storage.
+
+1. Calls the cloud provider API to make disk snapshots of persistent volumes, if specified.
+
+You can optionally specify hooks to be executed during the backup. For example, you might
+need to tell a database to flush its in-memory buffers to disk before taking a snapshot. [More about hooks][10].
+
+Note that cluster backups are not strictly atomic. If Kubernetes objects are being created or edited at the time of backup, they might not be included in the backup. The odds of capturing inconsistent information are low, but it is possible.
+
+## Scheduled backups
+
+The **schedule** operation allows you to back up your data at recurring intervals. The first backup is performed when the schedule is first created, and subsequent backups happen at the schedule's specified interval. These intervals are specified by a Cron expression.
+
+Scheduled backups are saved with the name `-`, where `` is formatted as *YYYYMMDDhhmmss*.
+
+## Restores
+
+The **restore** operation allows you to restore all of the objects and persistent volumes from a previously created backup. You can also restore only a filtered subset of objects and persistent volumes. Ark supports multiple namespace remapping--for example, in a single restore, objects in namespace "abc" can be recreated under namespace "def", and the objects in namespace "123" under "456".
+
+The default name of a restore is `-`, where `` is formatted as *YYYYMMDDhhmmss*. You can also specify a custom name. A restored object also includes a label with key `ark.heptio.com/restore-name` and value ``.
+
+You can also run the Ark server in restore-only mode, which disables backup, schedule, and garbage collection functionality during disaster recovery.
+
+## Backup workflow
+
+When you run `ark backup create test-backup`:
+
+1. The Ark client makes a call to the Kubernetes API server to create a `Backup` object.
+
+1. The `BackupController` notices the new `Backup` object and performs validation.
+
+1. The `BackupController` begins the backup process. It collects the data to back up by querying the API server for resources.
+
+1. The `BackupController` makes a call to the object storage service -- for example, AWS S3 -- to upload the backup file.
+
+By default, `ark backup create` makes disk snapshots of any persistent volumes. You can adjust the snapshots by specifying additional flags. Run `ark backup create --help` to see available flags. Snapshots can be disabled with the option `--snapshot-volumes=false`.
+
+![19]
+
+## Set a backup to expire
+
+When you create a backup, you can specify a TTL by adding the flag `--ttl `. If Ark sees that an existing backup resource is expired, it removes:
+
+* The backup resource
+* The backup file from cloud object storage
+* All PersistentVolume snapshots
+* All associated Restores
+
+## Object storage sync
+
+Heptio Ark treats object storage as the source of truth. It continuously checks to see that the correct backup resources are always present. If there is a properly formatted backup file in the storage bucket, but no corresponding backup resource in the Kubernetes API, Ark synchronizes the information from object storage to Kubernetes.
+
+This allows restore functionality to work in a cluster migration scenario, where the original backup objects do not exist in the new cluster.
+
+Likewise, if a backup object exists in Kubernetes but not in object storage, it will be deleted from Kubernetes since the backup tarball no longer exists.
+
+[10]: hooks.md
+[19]: /img/backup-process.png
+[20]: https://kubernetes.io/docs/concepts/api-extension/custom-resources/#customresourcedefinitions
+[21]: https://kubernetes.io/docs/concepts/api-extension/custom-resources/#custom-controllers
+[22]: https://github.com/coreos/etcd
diff --git a/site/docs/v0.10.0/api-types/README.md b/site/docs/v0.10.0/api-types/README.md
new file mode 100644
index 000000000..563892788
--- /dev/null
+++ b/site/docs/v0.10.0/api-types/README.md
@@ -0,0 +1,10 @@
+# Table of Contents
+
+## API types
+
+Here we list the API types that have some functionality that you can only configure via json/yaml vs the `ark` cli
+(hooks)
+
+* [Backup][1]
+
+[1]: backup.md
diff --git a/site/docs/v0.10.0/api-types/backup.md b/site/docs/v0.10.0/api-types/backup.md
new file mode 100644
index 000000000..40fe71c65
--- /dev/null
+++ b/site/docs/v0.10.0/api-types/backup.md
@@ -0,0 +1,144 @@
+# Backup API Type
+
+## Use
+
+The `Backup` API type is used as a request for the Ark Server to perform a backup. Once created, the
+Ark Server immediately starts the backup process.
+
+## API GroupVersion
+
+Backup belongs to the API group version `ark.heptio.com/v1`.
+
+## Definition
+
+Here is a sample `Backup` object with each of the fields documented:
+
+```yaml
+# Standard Kubernetes API Version declaration. Required.
+apiVersion: ark.heptio.com/v1
+# Standard Kubernetes Kind declaration. Required.
+kind: Backup
+# Standard Kubernetes metadata. Required.
+metadata:
+ # Backup name. May be any valid Kubernetes object name. Required.
+ name: a
+ # Backup namespace. Required. In version 0.7.0 and later, can be any string. Must be the namespace of the Ark server.
+ namespace: heptio-ark
+# Parameters about the backup. Required.
+spec:
+ # Array of namespaces to include in the backup. If unspecified, all namespaces are included.
+ # Optional.
+ includedNamespaces:
+ - '*'
+ # Array of namespaces to exclude from the backup. Optional.
+ excludedNamespaces:
+ - some-namespace
+ # Array of resources to include in the backup. Resources may be shortcuts (e.g. 'po' for 'pods')
+ # or fully-qualified. If unspecified, all resources are included. Optional.
+ includedResources:
+ - '*'
+ # Array of resources to exclude from the backup. Resources may be shortcuts (e.g. 'po' for 'pods')
+ # or fully-qualified. Optional.
+ excludedResources:
+ - storageclasses.storage.k8s.io
+ # Whether or not to include cluster-scoped resources. Valid values are true, false, and
+ # null/unset. If true, all cluster-scoped resources are included (subject to included/excluded
+ # resources and the label selector). If false, no cluster-scoped resources are included. If unset,
+ # all cluster-scoped resources are included if and only if all namespaces are included and there are
+ # no excluded namespaces. Otherwise, if there is at least one namespace specified in either
+ # includedNamespaces or excludedNamespaces, then the only cluster-scoped resources that are backed
+ # up are those associated with namespace-scoped resources included in the backup. For example, if a
+ # PersistentVolumeClaim is included in the backup, its associated PersistentVolume (which is
+ # cluster-scoped) would also be backed up.
+ includeClusterResources: null
+ # Individual objects must match this label selector to be included in the backup. Optional.
+ labelSelector:
+ matchLabels:
+ app: ark
+ component: server
+ # Whether or not to snapshot volumes. This only applies to PersistentVolumes for Azure, GCE, and
+ # AWS. Valid values are true, false, and null/unset. If unset, Ark performs snapshots as long as
+ # a persistent volume provider is configured for Ark.
+ snapshotVolumes: null
+ # Where to store the tarball and logs.
+ storageLocation: aws-primary
+ # The list of locations in which to store volume snapshots created for this backup.
+ volumeSnapshotLocations:
+ - aws-primary
+ - gcp-primary
+ # The amount of time before this backup is eligible for garbage collection.
+ ttl: 24h0m0s
+ # Actions to perform at different times during a backup. The only hook currently supported is
+ # executing a command in a container in a pod using the pod exec API. Optional.
+ hooks:
+ # Array of hooks that are applicable to specific resources. Optional.
+ resources:
+ -
+ # Name of the hook. Will be displayed in backup log.
+ name: my-hook
+ # Array of namespaces to which this hook applies. If unspecified, the hook applies to all
+ # namespaces. Optional.
+ includedNamespaces:
+ - '*'
+ # Array of namespaces to which this hook does not apply. Optional.
+ excludedNamespaces:
+ - some-namespace
+ # Array of resources to which this hook applies. The only resource supported at this time is
+ # pods.
+ includedResources:
+ - pods
+ # Array of resources to which this hook does not apply. Optional.
+ excludedResources: []
+ # This hook only applies to objects matching this label selector. Optional.
+ labelSelector:
+ matchLabels:
+ app: ark
+ component: server
+ # An array of hooks to run before executing custom actions. Currently only "exec" hooks are supported.
+ # DEPRECATED. Use pre instead.
+ hooks:
+ # Same content as pre below.
+ # An array of hooks to run before executing custom actions. Currently only "exec" hooks are supported.
+ pre:
+ -
+ # The type of hook. This must be "exec".
+ exec:
+ # The name of the container where the command will be executed. If unspecified, the
+ # first container in the pod will be used. Optional.
+ container: my-container
+ # The command to execute, specified as an array. Required.
+ command:
+ - /bin/uname
+ - -a
+ # How to handle an error executing the command. Valid values are Fail and Continue.
+ # Defaults to Fail. Optional.
+ onError: Fail
+ # How long to wait for the command to finish executing. Defaults to 30 seconds. Optional.
+ timeout: 10s
+ # An array of hooks to run after all custom actions and additional items have been
+ # processed. Currently only "exec" hooks are supported.
+ post:
+ # Same content as pre above.
+# Status about the Backup. Users should not set any data here.
+status:
+ # The date and time when the Backup is eligible for garbage collection.
+ expiration: null
+ # The current phase. Valid values are New, FailedValidation, InProgress, Completed, Failed.
+ phase: ""
+ # An array of any validation errors encountered.
+ validationErrors: null
+ # The version of this Backup. The only version currently supported is 1.
+ version: 1
+ # Information about PersistentVolumes needed during restores.
+ volumeBackups:
+ # Each key is the name of a PersistentVolume.
+ some-pv-name:
+ # The ID used by the cloud provider for the snapshot created for this Backup.
+ snapshotID: snap-1234
+ # The type of the volume in the cloud provider API.
+ type: io1
+ # The availability zone where the volume resides in the cloud provider.
+ availabilityZone: my-zone
+ # The amount of provisioned IOPS for the volume. Optional.
+ iops: 10000
+```
diff --git a/site/docs/v0.10.0/api-types/backupstoragelocation.md b/site/docs/v0.10.0/api-types/backupstoragelocation.md
new file mode 100644
index 000000000..15218a4c6
--- /dev/null
+++ b/site/docs/v0.10.0/api-types/backupstoragelocation.md
@@ -0,0 +1,71 @@
+# Ark Backup Storage Locations
+
+## Backup Storage Location
+
+Ark can store backups in a number of locations. These are represented in the cluster via the `BackupStorageLocation` CRD.
+
+Ark must have at least one `BackupStorageLocation`. By default, this is expected to be named `default`, however the name can be changed by specifying `--default-backup-storage-location` on `ark server`. Backups that do not explicitly specify a storage location will be saved to this `BackupStorageLocation`.
+
+> *NOTE*: `BackupStorageLocation` takes the place of the `Config.backupStorageProvider` key as of v0.10.0
+
+A sample YAML `BackupStorageLocation` looks like the following:
+
+```yaml
+apiVersion: ark.heptio.com/v1
+kind: BackupStorageLocation
+metadata:
+ name: default
+ namespace: heptio-ark
+spec:
+ provider: aws
+ objectStorage:
+ bucket: myBucket
+ config:
+ region: us-west-2
+```
+
+### Parameter Reference
+
+The configurable parameters are as follows:
+
+#### Main config parameters
+
+| Key | Type | Default | Meaning |
+| --- | --- | --- | --- |
+| `provider` | String (Ark natively supports `aws`, `gcp`, and `azure`. Other providers may be available via external plugins.)| Required Field | The name for whichever cloud provider will be used to actually store the backups. |
+| `objectStorage` | ObjectStorageLocation | Specification of the object storage for the given provider. |
+| `objectStorage/bucket` | String | Required Field | The storage bucket where backups are to be uploaded. |
+| `objectStorage/prefix` | String | Optional Field | The directory inside a storage bucket where backups are to be uploaded. |
+| `objectStorage/config` | map[string]string
(See the corresponding [AWS][0], [GCP][1], and [Azure][2]-specific configs or your provider's documentation.) | None (Optional) | Configuration keys/values to be passed to the cloud provider for backup storage. |
+
+#### AWS
+
+**(Or other S3-compatible storage)**
+
+##### objectStorage/config
+
+| Key | Type | Default | Meaning |
+| --- | --- | --- | --- |
+| `region` | string | Empty | *Example*: "us-east-1"
See [AWS documentation][3] for the full list.
Queried from the AWS S3 API if not provided. |
+| `s3ForcePathStyle` | bool | `false` | Set this to `true` if you are using a local storage service like Minio. |
+| `s3Url` | string | Required field for non-AWS-hosted storage| *Example*: http://minio:9000
You can specify the AWS S3 URL here for explicitness, but Ark can already generate it from `region`, and `bucket`. This field is primarily for local storage services like Minio.|
+| `publicUrl` | string | Empty | *Example*: https://minio.mycluster.com
If specified, use this instead of `s3Url` when generating download URLs (e.g., for logs). This field is primarily for local storage services like Minio.|
+| `kmsKeyId` | string | Empty | *Example*: "502b409c-4da1-419f-a16e-eif453b3i49f" or "alias/``"
Specify an [AWS KMS key][10] id or alias to enable encryption of the backups stored in S3. Only works with AWS S3 and may require explicitly granting key usage rights.|
+
+#### Azure
+
+##### objectStorage/config
+
+| Key | Type | Default | Meaning |
+| --- | --- | --- | --- |
+| `resourceGroup` | string | Required Field | Name of the resource group containing the storage account for this backup storage location. |
+| `storageAccount` | string | Required Field | Name of the storage account for this backup storage location. |
+
+#### GCP
+
+No parameters required.
+
+[0]: #aws
+[1]: #gcp
+[2]: #azure
+[3]: http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/using-regions-availability-zones.html#concepts-available-regions
diff --git a/site/docs/v0.10.0/api-types/volumesnapshotlocation.md b/site/docs/v0.10.0/api-types/volumesnapshotlocation.md
new file mode 100644
index 000000000..95744c4c6
--- /dev/null
+++ b/site/docs/v0.10.0/api-types/volumesnapshotlocation.md
@@ -0,0 +1,60 @@
+# Ark Volume Snapshot Location
+
+## Volume Snapshot Location
+
+A volume snapshot location is the location in which to store the volume snapshots created for a backup.
+
+Ark can be configured to take snapshots of volumes from multiple providers. Ark also allows you to configure multiple possible `VolumeSnapshotLocation` per provider, although you can only select one location per provider at backup time.
+
+Each VolumeSnapshotLocation describes a provider + location. These are represented in the cluster via the `VolumeSnapshotLocation` CRD. Ark must have at least one `VolumeSnapshotLocation` per cloud provider.
+
+A sample YAML `VolumeSnapshotLocation` looks like the following:
+
+```yaml
+apiVersion: ark.heptio.com/v1
+kind: VolumeSnapshotLocation
+metadata:
+ name: aws-default
+ namespace: heptio-ark
+spec:
+ provider: aws
+ config:
+ region: us-west-2
+```
+
+### Parameter Reference
+
+The configurable parameters are as follows:
+
+#### Main config parameters
+
+| Key | Type | Default | Meaning |
+| --- | --- | --- | --- |
+| `provider` | String (Ark natively supports `aws`, `gcp`, and `azure`. Other providers may be available via external plugins.)| Required Field | The name for whichever cloud provider will be used to actually store the volume. |
+| `config` | See the corresponding [AWS][0], [GCP][1], and [Azure][2]-specific configs or your provider's documentation.
+
+#### AWS
+
+##### config
+
+| Key | Type | Default | Meaning |
+| --- | --- | --- | --- |
+| `region` | string | Empty | *Example*: "us-east-1"
See [AWS documentation][3] for the full list.
Queried from the AWS S3 API if not provided. |
+
+#### Azure
+
+##### config
+
+| Key | Type | Default | Meaning |
+| --- | --- | --- | --- |
+| `apiTimeout` | metav1.Duration | 2m0s | How long to wait for an Azure API request to complete before timeout. |
+| `resourceGroup` | string | Optional | The name of the resource group where volume snapshots should be stored, if different from the cluster's resource group. |
+
+#### GCP
+
+No parameters required.
+
+[0]: #aws
+[1]: #gcp
+[2]: #azure
+[3]: http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/using-regions-availability-zones.html#concepts-available-regions
diff --git a/site/docs/v0.10.0/aws-config.md b/site/docs/v0.10.0/aws-config.md
new file mode 100644
index 000000000..57e006588
--- /dev/null
+++ b/site/docs/v0.10.0/aws-config.md
@@ -0,0 +1,311 @@
+# Run Ark on AWS
+
+To set up Ark on AWS, you:
+
+* Create your S3 bucket
+* Create an AWS IAM user for Ark
+* Configure the server
+* Create a Secret for your credentials
+
+If you do not have the `aws` CLI locally installed, follow the [user guide][5] to set it up.
+
+## Create S3 bucket
+
+Heptio Ark requires an object storage bucket to store backups in, preferrably unique to a single Kubernetes cluster (see the [FAQ][20] for more details). Create an S3 bucket, replacing placeholders appropriately:
+
+```bash
+aws s3api create-bucket \
+ --bucket \
+ --region \
+ --create-bucket-configuration LocationConstraint=
+```
+NOTE: us-east-1 does not support a `LocationConstraint`. If your region is `us-east-1`, omit the bucket configuration:
+
+```bash
+aws s3api create-bucket \
+ --bucket \
+ --region us-east-1
+```
+
+## Create IAM user
+
+For more information, see [the AWS documentation on IAM users][14].
+
+1. Create the IAM user:
+
+ ```bash
+ aws iam create-user --user-name heptio-ark
+ ```
+
+ > If you'll be using Ark to backup multiple clusters with multiple S3 buckets, it may be desirable to create a unique username per cluster rather than the default `heptio-ark`.
+
+2. Attach policies to give `heptio-ark` the necessary permissions:
+
+ ```bash
+ BUCKET=
+ cat > heptio-ark-policy.json <,
+ "AccessKeyId":
+ }
+ }
+ ```
+
+4. Create an Ark-specific credentials file (`credentials-ark`) in your local directory:
+
+ ```
+ [default]
+ aws_access_key_id=
+ aws_secret_access_key=
+ ```
+
+ where the access key id and secret are the values returned from the `create-access-key` request.
+
+## Credentials and configuration
+
+In the Ark directory (i.e. where you extracted the release tarball), run the following to first set up namespaces, RBAC, and other scaffolding. To run in a custom namespace, make sure that you have edited the YAML files to specify the namespace. See [Run in custom namespace][0].
+
+```bash
+kubectl apply -f config/common/00-prereqs.yaml
+```
+
+Create a Secret. In the directory of the credentials file you just created, run:
+
+```bash
+kubectl create secret generic cloud-credentials \
+ --namespace \
+ --from-file cloud=credentials-ark
+```
+
+Specify the following values in the example files:
+
+* In `config/aws/05-ark-backupstoragelocation.yaml`:
+
+ * Replace `` and `` (for S3 backup storage, region is optional and will be queried from the AWS S3 API if not provided). See the [BackupStorageLocation definition][21] for details.
+
+* In `config/aws/06-ark-volumesnapshotlocation.yaml`:
+
+ * Replace ``. See the [VolumeSnapshotLocation definition][6] for details.
+
+* (Optional, use only to specify multiple volume snapshot locations) In `config/aws/10-deployment.yaml` (or `config/aws/10-deployment-kube2iam.yaml`, as appropriate):
+
+ * Uncomment the `--default-volume-snapshot-locations` and replace provider locations with the values for your environment.
+
+* (Optional) If you run the nginx example, in file `config/nginx-app/with-pv.yaml`:
+
+ * Replace `` with `gp2`. This is AWS's default `StorageClass` name.
+
+* (Optional) If you have multiple clusters and you want to support migration of resources between them, in file `config/aws/10-deployment.yaml`:
+
+ * Uncomment the environment variable `AWS_CLUSTER_NAME` and replace `` with the current cluster's name. When restoring backup, it will make Ark (and cluster it's running on) claim ownership of AWS volumes created from snapshots taken on different cluster.
+ The best way to get the current cluster's name is to either check it with used deployment tool or to read it directly from the EC2 instances tags.
+
+ The following listing shows how to get the cluster's nodes EC2 Tags. First, get the nodes external IDs (EC2 IDs):
+
+ ```bash
+ kubectl get nodes -o jsonpath='{.items[*].spec.externalID}'
+ ```
+
+ Copy one of the returned IDs `` and use it with the `aws` CLI tool to search for one of the following:
+
+ * The `kubernetes.io/cluster/` tag of the value `owned`. The `` is then your cluster's name:
+
+ ```bash
+ aws ec2 describe-tags --filters "Name=resource-id,Values=" "Name=value,Values=owned"
+ ```
+
+ * If the first output returns nothing, then check for the legacy Tag `KubernetesCluster` of the value ``:
+
+ ```bash
+ aws ec2 describe-tags --filters "Name=resource-id,Values=" "Name=key,Values=KubernetesCluster"
+ ```
+
+## Start the server
+
+In the root of your Ark directory, run:
+
+ ```bash
+ kubectl apply -f config/aws/05-ark-backupstoragelocation.yaml
+ kubectl apply -f config/aws/06-ark-volumesnapshotlocation.yaml
+ kubectl apply -f config/aws/10-deployment.yaml
+ ```
+
+## ALTERNATIVE: Setup permissions using kube2iam
+
+[Kube2iam](https://github.com/jtblin/kube2iam) is a Kubernetes application that allows managing AWS IAM permissions for pod via annotations rather than operating on API keys.
+
+> This path assumes you have `kube2iam` already running in your Kubernetes cluster. If that is not the case, please install it first, following the docs here: [https://github.com/jtblin/kube2iam](https://github.com/jtblin/kube2iam)
+
+It can be set up for Ark by creating a role that will have required permissions, and later by adding the permissions annotation on the ark deployment to define which role it should use internally.
+
+1. Create a Trust Policy document to allow the role being used for EC2 management & assume kube2iam role:
+
+ ```bash
+ cat > heptio-ark-trust-policy.json <:role/"
+ },
+ "Action": "sts:AssumeRole"
+ }
+ ]
+ }
+ EOF
+ ```
+
+2. Create the IAM role:
+
+ ```bash
+ aws iam create-role --role-name heptio-ark --assume-role-policy-document file://./heptio-ark-trust-policy.json
+ ```
+
+3. Attach policies to give `heptio-ark` the necessary permissions:
+
+ ```bash
+ BUCKET=
+ cat > heptio-ark-policy.json <:role/
+ ...
+ ```
+
+5. Run Ark deployment using the file `config/aws/10-deployment-kube2iam.yaml`.
+
+[0]: namespace.md
+[5]: https://docs.aws.amazon.com/cli/latest/userguide/cli-chap-welcome.html
+[6]: api-types/volumesnapshotlocation.md#aws
+[14]: http://docs.aws.amazon.com/IAM/latest/UserGuide/introduction.html
+[20]: faq.md
+[21]: api-types/backupstoragelocation.md#aws
diff --git a/site/docs/v0.10.0/azure-config.md b/site/docs/v0.10.0/azure-config.md
new file mode 100644
index 000000000..d72ae48f6
--- /dev/null
+++ b/site/docs/v0.10.0/azure-config.md
@@ -0,0 +1,155 @@
+# Run Ark on Azure
+
+To configure Ark on Azure, you:
+
+* Create your Azure storage account and blob container
+* Create Azure service principal for Ark
+* Configure the server
+* Create a Secret for your credentials
+
+If you do not have the `az` Azure CLI 2.0 installed locally, follow the [install guide][18] to set it up.
+
+Run:
+
+```bash
+az login
+```
+
+## Kubernetes cluster prerequisites
+
+Ensure that the VMs for your agent pool allow Managed Disks. If I/O performance is critical,
+consider using Premium Managed Disks, which are SSD backed.
+
+## Create Azure storage account and blob container
+
+Heptio Ark requires a storage account and blob container in which to store backups.
+
+The storage account can be created in the same Resource Group as your Kubernetes cluster or
+separated into its own Resource Group. The example below shows the storage account created in a
+separate `Ark_Backups` Resource Group.
+
+The storage account needs to be created with a globally unique id since this is used for dns. In
+the sample script below, we're generating a random name using `uuidgen`, but you can come up with
+this name however you'd like, following the [Azure naming rules for storage accounts][19]. The
+storage account is created with encryption at rest capabilities (Microsoft managed keys) and is
+configured to only allow access via https.
+
+```bash
+# Create a resource group for the backups storage account. Change the location as needed.
+AZURE_BACKUP_RESOURCE_GROUP=Ark_Backups
+az group create -n $AZURE_BACKUP_RESOURCE_GROUP --location WestUS
+
+# Create the storage account
+AZURE_STORAGE_ACCOUNT_ID="ark$(uuidgen | cut -d '-' -f5 | tr '[A-Z]' '[a-z]')"
+az storage account create \
+ --name $AZURE_STORAGE_ACCOUNT_ID \
+ --resource-group $AZURE_BACKUP_RESOURCE_GROUP \
+ --sku Standard_GRS \
+ --encryption-services blob \
+ --https-only true \
+ --kind BlobStorage \
+ --access-tier Hot
+```
+
+Create the blob container named `ark`. Feel free to use a different name, preferably unique to a single Kubernetes cluster. See the [FAQ][20] for more details.
+
+```bash
+az storage container create -n ark --public-access off --account-name $AZURE_STORAGE_ACCOUNT_ID
+```
+
+## Get resource group for persistent volume snapshots
+
+1. Set the name of the Resource Group that contains your Kubernetes cluster's virtual machines/disks.
+
+ > **WARNING**: If you're using [AKS][22], `AZURE_RESOURCE_GROUP` must be set to the name of the auto-generated resource group that is created
+ when you provision your cluster in Azure, since this is the resource group that contains your cluster's virtual machines/disks.
+
+ ```bash
+ AZURE_RESOURCE_GROUP=
+ ```
+
+ If you are unsure of the Resource Group name, run the following command to get a list that you can select from. Then set the `AZURE_RESOURCE_GROUP` environment variable to the appropriate value.
+
+ ```bash
+ az group list --query '[].{ ResourceGroup: name, Location:location }'
+ ```
+
+ Get your cluster's Resource Group name from the `ResourceGroup` value in the response, and use it to set `$AZURE_RESOURCE_GROUP`.
+
+## Create service principal
+
+To integrate Ark with Azure, you must create an Ark-specific [service principal][17].
+
+1. Obtain your Azure Account Subscription ID and Tenant ID:
+
+ ```bash
+ AZURE_SUBSCRIPTION_ID=`az account list --query '[?isDefault].id' -o tsv`
+ AZURE_TENANT_ID=`az account list --query '[?isDefault].tenantId' -o tsv`
+ ```
+
+1. Create a service principal with `Contributor` role. This will have subscription-wide access, so protect this credential. You can specify a password or let the `az ad sp create-for-rbac` command create one for you.
+
+ > If you'll be using Ark to backup multiple clusters with multiple blob containers, it may be desirable to create a unique username per cluster rather than the default `heptio-ark`.
+
+ ```bash
+ # Create service principal and specify your own password
+ AZURE_CLIENT_SECRET=super_secret_and_high_entropy_password_replace_me_with_your_own
+ az ad sp create-for-rbac --name "heptio-ark" --role "Contributor" --password $AZURE_CLIENT_SECRET
+
+ # Or create service principal and let the CLI generate a password for you. Make sure to capture the password.
+ AZURE_CLIENT_SECRET=`az ad sp create-for-rbac --name "heptio-ark" --role "Contributor" --query 'password' -o tsv`
+
+ # After creating the service principal, obtain the client id
+ AZURE_CLIENT_ID=`az ad sp list --display-name "heptio-ark" --query '[0].appId' -o tsv`
+ ```
+
+## Credentials and configuration
+
+In the Ark directory (i.e. where you extracted the release tarball), run the following to first set up namespaces, RBAC, and other scaffolding. To run in a custom namespace, make sure that you have edited the YAML file to specify the namespace. See [Run in custom namespace][0].
+
+```bash
+kubectl apply -f config/common/00-prereqs.yaml
+```
+
+Now you need to create a Secret that contains all the environment variables you just set. The command looks like the following:
+
+```bash
+kubectl create secret generic cloud-credentials \
+ --namespace \
+ --from-literal AZURE_SUBSCRIPTION_ID=${AZURE_SUBSCRIPTION_ID} \
+ --from-literal AZURE_TENANT_ID=${AZURE_TENANT_ID} \
+ --from-literal AZURE_CLIENT_ID=${AZURE_CLIENT_ID} \
+ --from-literal AZURE_CLIENT_SECRET=${AZURE_CLIENT_SECRET} \
+ --from-literal AZURE_RESOURCE_GROUP=${AZURE_RESOURCE_GROUP}
+```
+
+Now that you have your Azure credentials stored in a Secret, you need to replace some placeholder values in the template files. Specifically, you need to change the following:
+
+* In file `config/azure/05-ark-backupstoragelocation.yaml`:
+
+ * Replace ``, ``, and ``. See the [BackupStorageLocation definition][21] for details.
+
+* In file `config/azure/06-ark-volumesnapshotlocation.yaml`:
+
+ * Replace ``. See the [VolumeSnapshotLocation definition][8] for details.
+
+* (Optional, use only if you need to specify multiple volume snapshot locations) In `config/azure/00-ark-deployment.yaml`:
+
+ * Uncomment the `--default-volume-snapshot-locations` and replace provider locations with the values for your environment.
+
+## Start the server
+
+In the root of your Ark directory, run:
+
+ ```bash
+ kubectl apply -f config/azure/
+ ```
+
+[0]: namespace.md
+[8]: api-types/volumesnapshotlocation.md#azure
+[17]: https://docs.microsoft.com/en-us/azure/active-directory/develop/active-directory-application-objects
+[18]: https://docs.microsoft.com/en-us/cli/azure/install-azure-cli
+[19]: https://docs.microsoft.com/en-us/azure/architecture/best-practices/naming-conventions#storage
+[20]: faq.md
+[21]: api-types/backupstoragelocation.md#azure
+[22]: https://azure.microsoft.com/en-us/services/kubernetes-service/
diff --git a/site/docs/v0.10.0/build-from-scratch.md b/site/docs/v0.10.0/build-from-scratch.md
new file mode 100644
index 000000000..b6fcab650
--- /dev/null
+++ b/site/docs/v0.10.0/build-from-scratch.md
@@ -0,0 +1,225 @@
+# Build from source
+
+* [Prerequisites][1]
+* [Download][2]
+* [Build][3]
+* [Test][12]
+* [Run][7]
+* [Vendoring dependencies][10]
+
+## Prerequisites
+
+* Access to a Kubernetes cluster, version 1.7 or later. Version 1.7.5 or later is required to run `ark backup delete`.
+* A DNS server on the cluster
+* `kubectl` installed
+* [Go][5] installed (minimum version 1.8)
+
+## Getting the source
+
+```bash
+mkdir $HOME/go
+export GOPATH=$HOME/go
+go get github.com/heptio/ark
+```
+
+Where `go` is your [import path][4] for Go.
+
+For Go development, it is recommended to add the Go import path (`$HOME/go` in this example) to your path.
+
+
+## Build
+
+You can build your Ark image locally on the machine where you run your cluster, or you can push it to a private registry. This section covers both workflows.
+
+Set the `$REGISTRY` environment variable (used in the `Makefile`) to push the Heptio Ark images to your own registry. This allows any node in your cluster to pull your locally built image.
+
+In the Ark root directory, to build your container with the tag `$REGISTRY/ark:$VERSION`, run:
+
+```
+make container
+```
+
+To push your image to a registry, use `make push`.
+
+### Update generated files
+
+The following files are automatically generated from the source code:
+
+* The clientset
+* Listers
+* Shared informers
+* Documentation
+* Protobuf/gRPC types
+
+Run `make update` to regenerate files if you make the following changes:
+
+* Add/edit/remove command line flags and/or their help text
+* Add/edit/remove commands or subcommands
+* Add new API types
+
+Run [generate-proto.sh][13] to regenerate files if you make the following changes:
+
+* Add/edit/remove protobuf message or service definitions. These changes require the [proto compiler][14].
+
+### Cross compiling
+
+By default, `make build` builds an `ark` binary for `linux-amd64`.
+To build for another platform, run `make build--`.
+For example, to build for the Mac, run `make build-darwin-amd64`.
+All binaries are placed in `_output/bin//`-- for example, `_output/bin/darwin/amd64/ark`.
+
+Ark's `Makefile` has a convenience target, `all-build`, that builds the following platforms:
+
+* linux-amd64
+* linux-arm
+* linux-arm64
+* darwin-amd64
+* windows-amd64
+
+## 3. Test
+
+To run unit tests, use `make test`. You can also run `make verify` to ensure that all generated
+files (clientset, listers, shared informers, docs) are up to date.
+
+## 4. Run
+
+### Prerequisites
+
+When running Heptio Ark, you will need to account for the following (all of which are handled in the [`/examples`][6] manifests):
+
+* Appropriate RBAC permissions in the cluster
+ * Read access for all data from the source cluster and namespaces
+ * Write access to the target cluster and namespaces
+* Cloud provider credentials
+ * Read/write access to volumes
+ * Read/write access to object storage for backup data
+* A [BackupStorageLocation][20] object definition for the Ark server
+* (Optional) A [VolumeSnapshotLocation][21] object definition for the Ark server, to take PV snapshots
+
+### Create a cluster
+
+To provision a cluster on AWS using Amazon’s official CloudFormation templates, here are two options:
+
+* EC2 [Quick Start for Kubernetes][17]
+
+* eksctl - [a CLI for Amazon EKS][18]
+
+### Option 1: Run your Ark server locally
+
+Running the Ark server locally can speed up iterative development. This eliminates the need to rebuild the Ark server
+image and redeploy it to the cluster with each change.
+
+#### 1. Set enviroment variables
+
+Set the appropriate environment variable for your cloud provider:
+
+AWS: [AWS_SHARED_CREDENTIALS_FILE][15]
+
+GCP: [GOOGLE_APPLICATION_CREDENTIALS][16]
+
+Azure:
+
+ 1. AZURE_CLIENT_ID
+
+ 2. AZURE_CLIENT_SECRET
+
+ 3. AZURE_SUBSCRIPTION_ID
+
+ 4. AZURE_TENANT_ID
+
+ 5. AZURE_STORAGE_ACCOUNT_ID
+
+ 6. AZURE_STORAGE_KEY
+
+ 7. AZURE_RESOURCE_GROUP
+
+#### 2. Create resources in a cluster
+
+You may create resources on a cluster using our [example configurations][19].
+
+##### Example
+
+Here is how to setup using an existing cluster in AWS: At the root of the Ark repo:
+
+- Edit `examples/aws/05-ark-backupstoragelocation.yaml` to point to your AWS S3 bucket and region. Note: you can run `aws s3api list-buckets` to get the name of all your buckets.
+
+- (Optional) Edit `examples/aws/06-ark-volumesnapshotlocation.yaml` to point to your AWS region.
+
+Then run the commands below.
+
+`00-prereqs.yaml` contains all our CustomResourceDefinitions (CRDs) that allow us to perform CRUD operations on backups, restores, schedules, etc. it also contains the `heptio-ark` namespace, the `ark` ServiceAccount, and a cluster role binding to grant the `ark` ServiceAccount the cluster-admin role:
+
+```bash
+kubectl apply -f examples/common/00-prereqs.yaml
+```
+
+`10-deployment.yaml` is a sample Ark config resource for AWS:
+
+```bash
+kubectl apply -f examples/aws/10-deployment.yaml
+```
+
+And `05-ark-backupstoragelocation.yaml` specifies the location of your backup storage, together with the optional `06-ark-volumesnapshotlocation.yaml`:
+
+```bash
+kubectl apply -f examples/aws/05-ark-backupstoragelocation.yaml
+```
+
+or
+
+```bash
+kubectl apply -f examples/aws/05-ark-backupstoragelocation.yaml examples/aws/06-ark-volumesnapshotlocation.yaml
+```
+
+### 3. Start the Ark server
+
+* Make sure `ark` is in your `PATH` or specify the full path.
+
+* Set variable for Ark as needed. The variables below can be exported as environment variables or passed as CLI cmd flags:
+ * `--kubeconfig`: set the path to the kubeconfig file the Ark server uses to talk to the Kubernetes apiserver
+ * `--namespace`: the set namespace where the Ark server should look for backups, schedules, restores
+ * `--log-level`: set the Ark server's log level
+ * `--plugin-dir`: set the directory where the Ark server looks for plugins
+ * `--metrics-address`: set the bind address and port where Prometheus metrics are exposed
+
+* Start the server: `ark server`
+
+### Option 2: Run your Ark server in a deployment
+
+1. Install Ark using a deployment:
+
+We have examples of deployments for different cloud providers in `examples//10-deployment.yaml`.
+
+2. Replace the deployment's default Ark image with the image that you built. Run:
+
+```
+kubectl --namespace=heptio-ark set image deployment/ark ark=$REGISTRY/ark:$VERSION
+```
+
+where `$REGISTRY` and `$VERSION` are the values that you built Ark with.
+
+## 5. Vendoring dependencies
+
+If you need to add or update the vendored dependencies, see [Vendoring dependencies][11].
+
+[0]: ../README.md
+[1]: #prerequisites
+[2]: #download
+[3]: #build
+[4]: https://blog.golang.org/organizing-go-code
+[5]: https://golang.org/doc/install
+[6]: https://github.com/heptio/ark/tree/master/examples
+[7]: #run
+[8]: config-definition.md
+[10]: #vendoring-dependencies
+[11]: vendoring-dependencies.md
+[12]: #test
+[13]: https://github.com/heptio/ark/blob/master/hack/generate-proto.sh
+[14]: https://grpc.io/docs/quickstart/go.html#install-protocol-buffers-v3
+[15]: https://docs.aws.amazon.com/cli/latest/topic/config-vars.html#the-shared-credentials-file
+[16]: https://cloud.google.com/docs/authentication/getting-started#setting_the_environment_variable
+[17]: https://aws.amazon.com/quickstart/architecture/heptio-kubernetes/
+[18]: https://eksctl.io/
+[19]: ../examples/README.md
+[20]: /api-types/backupstoragelocation.md
+[21]: /api-types/volumesnapshotlocation.md
diff --git a/site/docs/v0.10.0/debugging-install.md b/site/docs/v0.10.0/debugging-install.md
new file mode 100644
index 000000000..ac31e6d69
--- /dev/null
+++ b/site/docs/v0.10.0/debugging-install.md
@@ -0,0 +1,59 @@
+# Debugging Installation Issues
+
+## General
+
+### `invalid configuration: no configuration has been provided`
+This typically means that no `kubeconfig` file can be found for the Ark client to use. Ark looks for a kubeconfig in the
+following locations:
+* the path specified by the `--kubeconfig` flag, if any
+* the path specified by the `$KUBECONFIG` environment variable, if any
+* `~/.kube/config`
+
+### Backups or restores stuck in `New` phase
+This means that the Ark controllers are not processing the backups/restores, which usually happens because the Ark server is not running. Check the pod description and logs for errors:
+```
+kubectl -n heptio-ark describe pods
+kubectl -n heptio-ark logs deployment/ark
+```
+
+
+## AWS
+
+### `NoCredentialProviders: no valid providers in chain`
+This means that the secret containing the AWS IAM user credentials for Ark has not been created/mounted properly
+into the Ark server pod. Ensure the following:
+* The `cloud-credentials` secret exists in the Ark server's namespace
+* The `cloud-credentials` secret has a single key, `cloud`, whose value is the contents of the `credentials-ark` file
+* The `credentials-ark` file is formatted properly and has the correct values:
+
+ ```
+ [default]
+ aws_access_key_id=
+ aws_secret_access_key=
+ ```
+* The `cloud-credentials` secret is defined as a volume for the Ark deployment
+* The `cloud-credentials` secret is being mounted into the Ark server pod at `/credentials`
+
+
+## Azure
+
+### `Failed to refresh the Token` or `adal: Refresh request failed`
+This means that the secrets containing the Azure service principal credentials for Ark has not been created/mounted
+properly into the Ark server pod. Ensure the following:
+* The `cloud-credentials` secret exists in the Ark server's namespace
+* The `cloud-credentials` secret has all of the expected keys and each one has the correct value (see [setup instructions](0))
+* The `cloud-credentials` secret is defined as a volume for the Ark deployment
+* The `cloud-credentials` secret is being mounted into the Ark server pod at `/credentials`
+
+
+## GCE/GKE
+
+### `open credentials/cloud: no such file or directory`
+This means that the secret containing the GCE service account credentials for Ark has not been created/mounted properly
+into the Ark server pod. Ensure the following:
+* The `cloud-credentials` secret exists in the Ark server's namespace
+* The `cloud-credentials` secret has a single key, `cloud`, whose value is the contents of the `credentials-ark` file
+* The `cloud-credentials` secret is defined as a volume for the Ark deployment
+* The `cloud-credentials` secret is being mounted into the Ark server pod at `/credentials`
+
+[0]: azure-config#credentials-and-configuration
\ No newline at end of file
diff --git a/site/docs/v0.10.0/debugging-restores.md b/site/docs/v0.10.0/debugging-restores.md
new file mode 100644
index 000000000..bac4de501
--- /dev/null
+++ b/site/docs/v0.10.0/debugging-restores.md
@@ -0,0 +1,103 @@
+# Debugging Restores
+
+* [Example][0]
+* [Structure][1]
+
+## Example
+
+When Heptio Ark finishes a Restore, its status changes to "Completed" regardless of whether or not there are issues during the process. The number of warnings and errors are indicated in the output columns from `ark restore get`:
+
+```
+NAME BACKUP STATUS WARNINGS ERRORS CREATED SELECTOR
+backup-test-20170726180512 backup-test Completed 155 76 2017-07-26 11:41:14 -0400 EDT
+backup-test-20170726180513 backup-test Completed 121 14 2017-07-26 11:48:24 -0400 EDT
+backup-test-2-20170726180514 backup-test-2 Completed 0 0 2017-07-26 13:31:21 -0400 EDT
+backup-test-2-20170726180515 backup-test-2 Completed 0 1 2017-07-26 13:32:59 -0400 EDT
+```
+
+To delve into the warnings and errors into more detail, you can use `ark restore describe`:
+```
+ark restore describe backup-test-20170726180512
+```
+The output looks like this:
+```
+Name: backup-test-20170726180512
+Namespace: heptio-ark
+Labels:
+Annotations:
+
+Backup: backup-test
+
+Namespaces:
+ Included: *
+ Excluded:
+
+Resources:
+ Included: serviceaccounts
+ Excluded: nodes, events, events.events.k8s.io
+ Cluster-scoped: auto
+
+Namespace mappings:
+
+Label selector:
+
+Restore PVs: auto
+
+Phase: Completed
+
+Validation errors:
+
+Warnings:
+ Ark:
+ Cluster:
+ Namespaces:
+ heptio-ark: serviceaccounts "ark" already exists
+ serviceaccounts "default" already exists
+ kube-public: serviceaccounts "default" already exists
+ kube-system: serviceaccounts "attachdetach-controller" already exists
+ serviceaccounts "certificate-controller" already exists
+ serviceaccounts "cronjob-controller" already exists
+ serviceaccounts "daemon-set-controller" already exists
+ serviceaccounts "default" already exists
+ serviceaccounts "deployment-controller" already exists
+ serviceaccounts "disruption-controller" already exists
+ serviceaccounts "endpoint-controller" already exists
+ serviceaccounts "generic-garbage-collector" already exists
+ serviceaccounts "horizontal-pod-autoscaler" already exists
+ serviceaccounts "job-controller" already exists
+ serviceaccounts "kube-dns" already exists
+ serviceaccounts "namespace-controller" already exists
+ serviceaccounts "node-controller" already exists
+ serviceaccounts "persistent-volume-binder" already exists
+ serviceaccounts "pod-garbage-collector" already exists
+ serviceaccounts "replicaset-controller" already exists
+ serviceaccounts "replication-controller" already exists
+ serviceaccounts "resourcequota-controller" already exists
+ serviceaccounts "service-account-controller" already exists
+ serviceaccounts "service-controller" already exists
+ serviceaccounts "statefulset-controller" already exists
+ serviceaccounts "ttl-controller" already exists
+ default: serviceaccounts "default" already exists
+
+Errors:
+ Ark:
+ Cluster:
+ Namespaces:
+```
+
+## Structure
+
+Errors appear for incomplete or partial restores. Warnings appear for non-blocking issues (e.g. the
+restore looks "normal" and all resources referenced in the backup exist in some form, although some
+of them may have been pre-existing).
+
+Both errors and warnings are structured in the same way:
+
+* `Ark`: A list of system-related issues encountered by the Ark server (e.g. couldn't read directory).
+
+* `Cluster`: A list of issues related to the restore of cluster-scoped resources.
+
+* `Namespaces`: A map of namespaces to the list of issues related to the restore of their respective resources.
+
+[0]: #example
+[1]: #structure
diff --git a/site/docs/v0.10.0/disaster-case.md b/site/docs/v0.10.0/disaster-case.md
new file mode 100644
index 000000000..73d569fba
--- /dev/null
+++ b/site/docs/v0.10.0/disaster-case.md
@@ -0,0 +1,24 @@
+# Disaster recovery
+
+*Using Schedules and Restore-Only Mode*
+
+If you periodically back up your cluster's resources, you are able to return to a previous state in case of some unexpected mishap, such as a service outage. Doing so with Heptio Ark looks like the following:
+
+1. After you first run the Ark server on your cluster, set up a daily backup (replacing `` in the command as desired):
+
+ ```
+ ark schedule create --schedule "0 7 * * *"
+ ```
+ This creates a Backup object with the name `-`.
+
+1. A disaster happens and you need to recreate your resources.
+
+1. Update the Ark server deployment, adding the argument for the `server` command flag `restore-only` set to `true`. This prevents Backup objects from being created or deleted during your Restore process.
+
+1. Create a restore with your most recent Ark Backup:
+ ```
+ ark restore create --from-backup -
+ ```
+
+
+
diff --git a/site/docs/v0.10.0/extend.md b/site/docs/v0.10.0/extend.md
new file mode 100644
index 000000000..0a96b8e3e
--- /dev/null
+++ b/site/docs/v0.10.0/extend.md
@@ -0,0 +1,9 @@
+# Extend Ark
+
+Ark includes mechanisms for extending the core functionality to meet your individual backup/restore needs:
+
+* [Hooks][27] allow you to specify commands to be executed within running pods during a backup. This is useful if you need to run a workload-specific command prior to taking a backup (for example, to flush disk buffers or to freeze a database).
+* [Plugins][28] allow you to develop custom object/block storage back-ends or per-item backup/restore actions that can execute arbitrary logic, including modifying the items being backed up/restored. Plugins can be used by Ark without needing to be compiled into the core Ark binary.
+
+[27]: hooks.md
+[28]: plugins.md
diff --git a/site/docs/v0.10.0/faq.md b/site/docs/v0.10.0/faq.md
new file mode 100644
index 000000000..b25b4f439
--- /dev/null
+++ b/site/docs/v0.10.0/faq.md
@@ -0,0 +1,37 @@
+# FAQ
+
+## When is it appropriate to use Ark instead of etcd's built in backup/restore?
+
+Etcd's backup/restore tooling is good for recovering from data loss in a single etcd cluster. For
+example, it is a good idea to take a backup of etcd prior to upgrading etcd itself. For more
+sophisticated management of your Kubernetes cluster backups and restores, we feel that Ark is
+generally a better approach. It gives you the ability to throw away an unstable cluster and restore
+your Kubernetes resources and data into a new cluster, which you can't do easily just by backing up
+and restoring etcd.
+
+Examples of cases where Ark is useful:
+
+* you don't have access to etcd (e.g. you're running on GKE)
+* backing up both Kubernetes resources and persistent volume state
+* cluster migrations
+* backing up a subset of your Kubernetes resources
+* backing up Kubernetes resources that are stored across multiple etcd clusters (for example if you
+ run a custom apiserver)
+
+## Will Ark restore my Kubernetes resources exactly the way they were before?
+
+Yes, with some exceptions. For example, when Ark restores pods it deletes the `nodeName` from the
+pod so that it can be scheduled onto a new node. You can see some more examples of the differences
+in [pod_action.go](https://github.com/heptio/ark/blob/master/pkg/restore/pod_action.go)
+
+## I'm using Ark in multiple clusters. Should I use the same bucket to store all of my backups?
+
+We **strongly** recommend that you use a separate bucket per cluster to store backups. Sharing a bucket
+across multiple Ark instances can lead to numerous problems - failed backups, overwritten backups,
+inadvertently deleted backups, etc., all of which can be avoided by using a separate bucket per Ark
+instance.
+
+Related to this, if you need to restore a backup from cluster A into cluster B, please use restore-only
+mode in cluster B's Ark instance (via the `--restore-only` flag on the `ark server` command specified
+in your Ark deployment) while it's configured to use cluster A's bucket. This will ensure no
+new backups are created, and no existing backups are deleted or overwritten.
diff --git a/site/docs/v0.10.0/gcp-config.md b/site/docs/v0.10.0/gcp-config.md
new file mode 100644
index 000000000..7b0b13e92
--- /dev/null
+++ b/site/docs/v0.10.0/gcp-config.md
@@ -0,0 +1,142 @@
+# Run Ark on GCP
+
+You can run Kubernetes on Google Cloud Platform in either:
+
+* Kubernetes on Google Compute Engine virtual machines
+* Google Kubernetes Engine
+
+If you do not have the `gcloud` and `gsutil` CLIs locally installed, follow the [user guide][16] to set them up.
+
+## Create GCS bucket
+
+Heptio Ark requires an object storage bucket in which to store backups, preferably unique to a single Kubernetes cluster (see the [FAQ][20] for more details). Create a GCS bucket, replacing the placeholder with the name of your bucket:
+
+```bash
+BUCKET=
+
+gsutil mb gs://$BUCKET/
+```
+
+## Create service account
+
+To integrate Heptio Ark with GCP, create an Ark-specific [Service Account][15]:
+
+1. View your current config settings:
+
+ ```bash
+ gcloud config list
+ ```
+
+ Store the `project` value from the results in the environment variable `$PROJECT_ID`.
+
+ ```bash
+ PROJECT_ID=$(gcloud config get-value project)
+ ```
+
+2. Create a service account:
+
+ ```bash
+ gcloud iam service-accounts create heptio-ark \
+ --display-name "Heptio Ark service account"
+ ```
+
+ > If you'll be using Ark to backup multiple clusters with multiple GCS buckets, it may be desirable to create a unique username per cluster rather than the default `heptio-ark`.
+
+ Then list all accounts and find the `heptio-ark` account you just created:
+ ```bash
+ gcloud iam service-accounts list
+ ```
+
+ Set the `$SERVICE_ACCOUNT_EMAIL` variable to match its `email` value.
+
+ ```bash
+ SERVICE_ACCOUNT_EMAIL=$(gcloud iam service-accounts list \
+ --filter="displayName:Heptio Ark service account" \
+ --format 'value(email)')
+ ```
+
+3. Attach policies to give `heptio-ark` the necessary permissions to function:
+
+ ```bash
+
+ ROLE_PERMISSIONS=(
+ compute.disks.get
+ compute.disks.create
+ compute.disks.createSnapshot
+ compute.snapshots.get
+ compute.snapshots.create
+ compute.snapshots.useReadOnly
+ compute.snapshots.delete
+ )
+
+ gcloud iam roles create heptio_ark.server \
+ --project $PROJECT_ID \
+ --title "Heptio Ark Server" \
+ --permissions "$(IFS=","; echo "${ROLE_PERMISSIONS[*]}")"
+
+ gcloud projects add-iam-policy-binding $PROJECT_ID \
+ --member serviceAccount:$SERVICE_ACCOUNT_EMAIL \
+ --role projects/$PROJECT_ID/roles/heptio_ark.server
+
+ gsutil iam ch serviceAccount:$SERVICE_ACCOUNT_EMAIL:objectAdmin gs://${BUCKET}
+ ```
+
+4. Create a service account key, specifying an output file (`credentials-ark`) in your local directory:
+
+ ```bash
+ gcloud iam service-accounts keys create credentials-ark \
+ --iam-account $SERVICE_ACCOUNT_EMAIL
+ ```
+
+## Credentials and configuration
+
+If you run Google Kubernetes Engine (GKE), make sure that your current IAM user is a cluster-admin. This role is required to create RBAC objects.
+See [the GKE documentation][22] for more information.
+
+In the Ark directory (i.e. where you extracted the release tarball), run the following to first set up namespaces, RBAC, and other scaffolding. To run in a custom namespace, make sure that you have edited the YAML files to specify the namespace. See [Run in custom namespace][0].
+
+```bash
+kubectl apply -f config/common/00-prereqs.yaml
+```
+
+Create a Secret. In the directory of the credentials file you just created, run:
+
+```bash
+kubectl create secret generic cloud-credentials \
+ --namespace heptio-ark \
+ --from-file cloud=credentials-ark
+```
+
+**Note: If you use a custom namespace, replace `heptio-ark` with the name of the custom namespace**
+
+Specify the following values in the example files:
+
+* In file `config/gcp/05-ark-backupstoragelocation.yaml`:
+
+ * Replace ``. See the [BackupStorageLocation definition][7] for details.
+
+* (Optional) If you run the nginx example, in file `config/nginx-app/with-pv.yaml`:
+
+ * Replace `` with `standard`. This is GCP's default `StorageClass` name.
+
+* (Optional, use only if you need to specify multiple volume snapshot locations) In `config/gcp/10-deployment.yaml`:
+
+ * Uncomment the `--default-volume-snapshot-locations` and replace provider locations with the values for your environment.
+
+## Start the server
+
+In the root of your Ark directory, run:
+
+ ```bash
+ kubectl apply -f config/gcp/05-ark-backupstoragelocation.yaml
+ kubectl apply -f config/gcp/06-ark-volumesnapshotlocation.yaml
+ kubectl apply -f config/gcp/10-deployment.yaml
+ ```
+
+ [0]: namespace.md
+ [7]: api-types/backupstoragelocation.md#gcp
+ [15]: https://cloud.google.com/compute/docs/access/service-accounts
+ [16]: https://cloud.google.com/sdk/docs/
+ [20]: faq.md
+ [22]: https://cloud.google.com/kubernetes-engine/docs/how-to/role-based-access-control#prerequisites_for_using_role-based_access_control
+
diff --git a/site/docs/v0.10.0/get-started.md b/site/docs/v0.10.0/get-started.md
new file mode 100644
index 000000000..80da57e45
--- /dev/null
+++ b/site/docs/v0.10.0/get-started.md
@@ -0,0 +1,211 @@
+# Getting started
+
+The following example sets up the Ark server and client, then backs up and restores a sample application.
+
+For simplicity, the example uses Minio, an S3-compatible storage service that runs locally on your cluster.
+
+**NOTE** The example lets you explore basic Ark functionality. Configuring Minio for production is out of scope.
+
+See [Set up Ark on your platform][3] for how to configure Ark for a production environment.
+
+## Prerequisites
+
+* Access to a Kubernetes cluster, version 1.7 or later. Version 1.7.5 or later is required to run `ark backup delete`.
+* A DNS server on the cluster
+* `kubectl` installed
+
+### Download
+
+1. Download the [latest release's][26] tarball for your platform.
+
+1. Extract the tarball:
+ ```bash
+ tar -xzf .tar.gz -C /dir/to/extract/to
+ ```
+ We'll refer to the directory you extracted to as the "Ark directory" in subsequent steps.
+
+1. Move the `ark` binary from the Ark directory to somewhere in your PATH.
+
+## Set up server
+
+These instructions start the Ark server and a Minio instance that is accessible from within the cluster only. See the following section for information about configuring your cluster for outside access to Minio. Outside access is required to access logs and run `ark describe` commands.
+
+1. Start the server and the local storage service. In the Ark directory, run:
+
+ ```bash
+ kubectl apply -f config/common/00-prereqs.yaml
+ kubectl apply -f config/minio/
+ ```
+
+1. Deploy the example nginx application:
+
+ ```bash
+ kubectl apply -f config/nginx-app/base.yaml
+ ```
+
+1. Check to see that both the Ark and nginx deployments are successfully created:
+
+ ```
+ kubectl get deployments -l component=ark --namespace=heptio-ark
+ kubectl get deployments --namespace=nginx-example
+ ```
+
+## (Optional) Expose Minio outside your cluster
+
+When you run commands to get logs or describe a backup, the Ark server generates a pre-signed URL to download the requested items. To access these URLs from outside the cluster -- that is, from your Ark client -- you need to make Minio available outside the cluster. You can:
+
+- Change the Minio Service type from `ClusterIP` to `NodePort`.
+- Set up Ingress for your cluster, keeping Minio Service type `ClusterIP`.
+
+In Ark 0.10, you can also specify the value of a new `publicUrl` field for the pre-signed URL in your backup storage config.
+
+### Expose Minio with Service of type NodePort
+
+The Minio deployment by default specifies a Service of type `ClusterIP`. You can change this to `NodePort` to easily expose a cluster service externally if you can reach the node from your Ark client.
+
+You must also get the Minio URL, which you can then specify as the value of the new `publicUrl` field in your backup storage config.
+
+1. In `examples/minio/00-minio-deployment.yaml`, change the value of Service `spec.type` from `ClusterIP` to `NodePort`.
+
+1. Get the Minio URL:
+
+ - if you're running Minikube:
+
+ ```shell
+ minikube service minio --namespace=heptio-ark --url
+ ```
+
+ - in any other environment:
+
+ 1. Get the value of an external IP address or DNS name of any node in your cluster. You must be able to reach this address from the Ark client.
+
+ 1. Append the value of the NodePort to get a complete URL. You can get this value by running:
+
+ ```shell
+ kubectl -n heptio-ark get svc/minio -o jsonpath='{.spec.ports[0].nodePort}'
+ ```
+
+1. In `examples/minio/05-ark-backupstoragelocation.yaml`, uncomment the `publicUrl` line and provide this Minio URL as the value of the `publicUrl` field. You must include the `http://` or `https://` prefix.
+
+### Work with Ingress
+
+Configuring Ingress for your cluster is out of scope for the Ark documentation. If you have already set up Ingress, however, it makes sense to continue with it while you run the example Ark configuration with Minio.
+
+In this case:
+
+1. Keep the Service type as `ClusterIP`.
+
+1. In `examples/minio/05-ark-backupstoragelocation.yaml`, uncomment the `publicUrl` line and provide the URL and port of your Ingress as the value of the `publicUrl` field.
+
+## Back up
+
+1. Create a backup for any object that matches the `app=nginx` label selector:
+
+ ```
+ ark backup create nginx-backup --selector app=nginx
+ ```
+
+ Alternatively if you want to backup all objects *except* those matching the label `backup=ignore`:
+
+ ```
+ ark backup create nginx-backup --selector 'backup notin (ignore)'
+ ```
+
+1. (Optional) Create regularly scheduled backups based on a cron expression using the `app=nginx` label selector:
+
+ ```
+ ark schedule create nginx-daily --schedule="0 1 * * *" --selector app=nginx
+ ```
+
+ Alternatively, you can use some non-standard shorthand cron expressions:
+
+ ```
+ ark schedule create nginx-daily --schedule="@daily" --selector app=nginx
+ ```
+
+ See the [cron package's documentation][30] for more usage examples.
+
+1. Simulate a disaster:
+
+ ```
+ kubectl delete namespace nginx-example
+ ```
+
+1. To check that the nginx deployment and service are gone, run:
+
+ ```
+ kubectl get deployments --namespace=nginx-example
+ kubectl get services --namespace=nginx-example
+ kubectl get namespace/nginx-example
+ ```
+
+ You should get no results.
+
+ NOTE: You might need to wait for a few minutes for the namespace to be fully cleaned up.
+
+## Restore
+
+1. Run:
+
+ ```
+ ark restore create --from-backup nginx-backup
+ ```
+
+1. Run:
+
+ ```
+ ark restore get
+ ```
+
+ After the restore finishes, the output looks like the following:
+
+ ```
+ NAME BACKUP STATUS WARNINGS ERRORS CREATED SELECTOR
+ nginx-backup-20170727200524 nginx-backup Completed 0 0 2017-07-27 20:05:24 +0000 UTC
+ ```
+
+NOTE: The restore can take a few moments to finish. During this time, the `STATUS` column reads `InProgress`.
+
+After a successful restore, the `STATUS` column is `Completed`, and `WARNINGS` and `ERRORS` are 0. All objects in the `nginx-example` namespace should be just as they were before you deleted them.
+
+If there are errors or warnings, you can look at them in detail:
+
+```
+ark restore describe
+```
+
+For more information, see [the debugging information][18].
+
+## Clean up
+
+If you want to delete any backups you created, including data in object storage and persistent
+volume snapshots, you can run:
+
+```
+ark backup delete BACKUP_NAME
+```
+
+This asks the Ark server to delete all backup data associated with `BACKUP_NAME`. You need to do
+this for each backup you want to permanently delete. A future version of Ark will allow you to
+delete multiple backups by name or label selector.
+
+Once fully removed, the backup is no longer visible when you run:
+
+```
+ark backup get BACKUP_NAME
+```
+
+If you want to uninstall Ark but preserve the backup data in object storage and persistent volume
+snapshots, it is safe to remove the `heptio-ark` namespace and everything else created for this
+example:
+
+```
+kubectl delete -f config/common/
+kubectl delete -f config/minio/
+kubectl delete -f config/nginx-app/base.yaml
+```
+
+[3]: install-overview.md
+[18]: debugging-restores.md
+[26]: https://github.com/heptio/ark/releases
+[30]: https://godoc.org/github.com/robfig/cron
diff --git a/site/docs/v0.10.0/hooks.md b/site/docs/v0.10.0/hooks.md
new file mode 100644
index 000000000..5db78e643
--- /dev/null
+++ b/site/docs/v0.10.0/hooks.md
@@ -0,0 +1,83 @@
+# Hooks
+
+Heptio Ark currently supports executing commands in containers in pods during a backup.
+
+## Backup Hooks
+
+When performing a backup, you can specify one or more commands to execute in a container in a pod
+when that pod is being backed up.
+
+Ark versions prior to v0.7.0 only support hooks that execute prior to any custom action processing
+("pre" hooks).
+
+As of version v0.7.0, Ark also supports "post" hooks - these execute after all custom actions have
+completed, as well as after all the additional items specified by custom actions have been backed
+up.
+
+There are two ways to specify hooks: annotations on the pod itself, and in the Backup spec.
+
+### Specifying Hooks As Pod Annotations
+
+You can use the following annotations on a pod to make Ark execute a hook when backing up the pod:
+
+#### Pre hooks
+
+| Annotation Name | Description |
+| --- | --- |
+| `pre.hook.backup.ark.heptio.com/container` | The container where the command should be executed. Defaults to the first container in the pod. Optional. |
+| `pre.hook.backup.ark.heptio.com/command` | The command to execute. If you need multiple arguments, specify the command as a JSON array, such as `["/usr/bin/uname", "-a"]` |
+| `pre.hook.backup.ark.heptio.com/on-error` | What to do if the command returns a non-zero exit code. Defaults to Fail. Valid values are Fail and Continue. Optional. |
+| `pre.hook.backup.ark.heptio.com/timeout` | How long to wait for the command to execute. The hook is considered in error if the command exceeds the timeout. Defaults to 30s. Optional. |
+
+Ark v0.7.0+ continues to support the original (deprecated) way to specify pre hooks - without the
+`pre.` prefix in the annotation names (e.g. `hook.backup.ark.heptio.com/container`).
+
+#### Post hooks (v0.7.0+)
+
+| Annotation Name | Description |
+| --- | --- |
+| `post.hook.backup.ark.heptio.com/container` | The container where the command should be executed. Defaults to the first container in the pod. Optional. |
+| `post.hook.backup.ark.heptio.com/command` | The command to execute. If you need multiple arguments, specify the command as a JSON array, such as `["/usr/bin/uname", "-a"]` |
+| `post.hook.backup.ark.heptio.com/on-error` | What to do if the command returns a non-zero exit code. Defaults to Fail. Valid values are Fail and Continue. Optional. |
+| `post.hook.backup.ark.heptio.com/timeout` | How long to wait for the command to execute. The hook is considered in error if the command exceeds the timeout. Defaults to 30s. Optional. |
+
+### Specifying Hooks in the Backup Spec
+
+Please see the documentation on the [Backup API Type][1] for how to specify hooks in the Backup
+spec.
+
+## Hook Example with fsfreeze
+
+We are going to walk through using both pre and post hooks for freezing a file system. Freezing the
+file system is useful to ensure that all pending disk I/O operations have completed prior to taking a snapshot.
+
+We will be using [examples/nginx-app/with-pv.yaml][2] for this example. Follow the [steps for your provider][3] to
+setup this example.
+
+### Annotations
+
+The Ark [example/nginx-app/with-pv.yaml][2] serves as an example of adding the pre and post hook annotations directly
+to your declarative deployment. Below is an example of what updating an object in place might look like.
+
+```shell
+kubectl annotate pod -n nginx-example -l app=nginx \
+ pre.hook.backup.ark.heptio.com/command='["/sbin/fsfreeze", "--freeze", "/var/log/nginx"]' \
+ pre.hook.backup.ark.heptio.com/container=fsfreeze \
+ post.hook.backup.ark.heptio.com/command='["/sbin/fsfreeze", "--unfreeze", "/var/log/nginx"]' \
+ post.hook.backup.ark.heptio.com/container=fsfreeze
+```
+
+Now test the pre and post hooks by creating a backup. You can use the Ark logs to verify that the pre and post
+hooks are running and exiting without error.
+
+```shell
+ark backup create nginx-hook-test
+
+ark backup get nginx-hook-test
+ark backup logs nginx-hook-test | grep hookCommand
+```
+
+
+[1]: api-types/backup.md
+[2]: examples/nginx-app/with-pv.yaml
+[3]: cloud-common.md
diff --git a/site/docs/v0.10.0/ibm-config.md b/site/docs/v0.10.0/ibm-config.md
new file mode 100644
index 000000000..b25cc0f2c
--- /dev/null
+++ b/site/docs/v0.10.0/ibm-config.md
@@ -0,0 +1,80 @@
+# Use IBM Cloud Object Storage as Ark's storage destination.
+You can deploy Ark on IBM [Public][5] or [Private][4] clouds, or even on any other Kubernetes cluster, but anyway you can use IBM Cloud Object Store as a destination for Ark's backups.
+
+To set up IBM Cloud Object Storage (COS) as Ark's destination, you:
+
+* Create your COS instance
+* Create an S3 bucket
+* Define a service that can store data in the bucket
+* Configure and start the Ark server
+
+
+## Create COS instance
+If you don’t have a COS instance, you can create a new one, according to the detailed instructions in [Creating a new resource instance][1].
+
+## Create an S3 bucket
+Heptio Ark requires an object storage bucket to store backups in. See instructions in [Create some buckets to store your data][2].
+
+## Define a service that can store data in the bucket.
+The process of creating service credentials is described in [Service credentials][3].
+Several comments:
+
+1. The Ark service will write its backup into the bucket, so it requires the “Writer” access role.
+
+2. Ark uses an AWS S3 compatible API. Which means it authenticates using a signature created from a pair of access and secret keys — a set of HMAC credentials. You can create these HMAC credentials by specifying `{“HMAC”:true}` as an optional inline parameter. See step 3 in the [Service credentials][3] guide.
+
+3. After successfully creating a Service credential, you can view the JSON definition of the credential. Under the `cos_hmac_keys` entry there are `access_key_id` and `secret_access_key`. We will use them in the next step.
+
+4. Create an Ark-specific credentials file (`credentials-ark`) in your local directory:
+
+ ```
+ [default]
+ aws_access_key_id=
+ aws_secret_access_key=
+ ```
+
+ where the access key id and secret are the values that we got above.
+
+## Credentials and configuration
+
+In the Ark directory (i.e. where you extracted the release tarball), run the following to first set up namespaces, RBAC, and other scaffolding. To run in a custom namespace, make sure that you have edited the YAML files to specify the namespace. See [Run in custom namespace][0].
+
+```bash
+kubectl apply -f config/common/00-prereqs.yaml
+```
+
+Create a Secret. In the directory of the credentials file you just created, run:
+
+```bash
+kubectl create secret generic cloud-credentials \
+ --namespace \
+ --from-file cloud=credentials-ark
+```
+
+Specify the following values in the example files:
+
+* In `config/ibm/05-ark-backupstoragelocation.yaml`:
+
+ * Replace ``, `` and ``. See the [BackupStorageLocation definition][6] for details.
+
+* (Optional) If you run the nginx example, in file `config/nginx-app/with-pv.yaml`:
+
+ * Replace `` with your `StorageClass` name.
+
+## Start the Ark server
+
+In the root of your Ark directory, run:
+
+ ```bash
+ kubectl apply -f config/ibm/05-ark-backupstoragelocation.yaml
+ kubectl apply -f config/ibm/10-deployment.yaml
+ ```
+
+ [0]: namespace.md
+ [1]: https://console.bluemix.net/docs/services/cloud-object-storage/basics/order-storage.html#creating-a-new-resource-instance
+ [2]: https://console.bluemix.net/docs/services/cloud-object-storage/getting-started.html#create-buckets
+ [3]: https://console.bluemix.net/docs/services/cloud-object-storage/iam/service-credentials.html#service-credentials
+ [4]: https://www.ibm.com/support/knowledgecenter/SSBS6K_2.1.0/kc_welcome_containers.html
+ [5]: https://console.bluemix.net/docs/containers/container_index.html#container_index
+ [6]: api-types/backupstoragelocation.md#aws
+ [14]: http://docs.aws.amazon.com/IAM/latest/UserGuide/introduction.html
diff --git a/site/docs/v0.10.0/image-tagging.md b/site/docs/v0.10.0/image-tagging.md
new file mode 100644
index 000000000..33460d8c3
--- /dev/null
+++ b/site/docs/v0.10.0/image-tagging.md
@@ -0,0 +1,21 @@
+# Image tagging policy
+
+This document describes Ark's image tagging policy.
+
+## Released versions
+
+`gcr.io/heptio-images/ark:`
+
+Ark follows the [Semantic Versioning](http://semver.org/) standard for releases. Each tag in the `github.com/heptio/ark` repository has a matching image, e.g. `gcr.io/heptio-images/ark:v0.8.0`.
+
+### Latest
+
+`gcr.io/heptio-images/ark:latest`
+
+The `latest` tag follows the most recently released version of Ark.
+
+## Development
+
+`gcr.io/heptio-images/ark:master`
+
+The `master` tag follows the latest commit to land on the `master` branch.
\ No newline at end of file
diff --git a/site/docs/v0.10.0/img/README.md b/site/docs/v0.10.0/img/README.md
new file mode 100644
index 000000000..85c071c63
--- /dev/null
+++ b/site/docs/v0.10.0/img/README.md
@@ -0,0 +1 @@
+Some of these diagrams (for instance backup-process.png), have been created on [draw.io](https://www.draw.io), using the "Include a copy of my diagram" option. If you want to make changes to these diagrams, try importing them into draw.io, and you should have access to the original shapes/text that went into the originals.
diff --git a/site/docs/v0.10.0/img/backup-process.png b/site/docs/v0.10.0/img/backup-process.png
new file mode 100644
index 000000000..744b37abe
Binary files /dev/null and b/site/docs/v0.10.0/img/backup-process.png differ
diff --git a/site/docs/v0.10.0/install-overview.md b/site/docs/v0.10.0/install-overview.md
new file mode 100644
index 000000000..e13d0bb57
--- /dev/null
+++ b/site/docs/v0.10.0/install-overview.md
@@ -0,0 +1,109 @@
+# Set up Ark on your platform
+
+You can run Ark with a cloud provider or on-premises. For detailed information about the platforms that Ark supports, see [Compatible Storage Providers][99].
+
+In version 0.7.0 and later, you can run Ark in any namespace, which requires additional customization. See [Run in custom namespace][3].
+
+In version 0.9.0 and later, you can use Ark's integration with restic, which requires additional setup. See [restic instructions][20].
+
+## Customize configuration
+
+Whether you run Ark on a cloud provider or on-premises, if you have more than one volume snapshot location for a given volume provider, you can specify its default location for backups by setting a server flag in your Ark deployment YAML.
+
+For details, see the documentation topics for individual cloud providers.
+
+## Cloud provider
+
+The Ark repository includes a set of example YAML files that specify the settings for each supported cloud provider. For provider-specific instructions, see:
+
+* [Run Ark on AWS][0]
+* [Run Ark on GCP][1]
+* [Run Ark on Azure][2]
+* [Use IBM Cloud Object Store as Ark's storage destination][4]
+
+## On-premises
+
+You can run Ark in an on-premises cluster in different ways depending on your requirements.
+
+First, you must select an object storage backend that Ark can use to store backup data. [Compatible Storage Providers][99] contains information on various
+options that are supported or have been reported to work by users. [Minio][101] is an option if you want to keep your backup data on-premises and you are
+not using another storage platform that offers an S3-compatible object storage API.
+
+Second, if you need to back up persistent volume data, you must select a volume backup solution. [Volume Snapshot Providers][100] contains information on
+the supported options. For example, if you use [Portworx][102] for persistent storage, you can install their Ark plugin to get native Portworx snapshots as part
+of your Ark backups. If there is no native snapshot plugin available for your storage platform, you can use Ark's [restic integration][20], which provides a
+platform-agnostic backup solution for volume data.
+
+## Examples
+
+After you set up the Ark server, try these examples:
+
+### Basic example (without PersistentVolumes)
+
+1. Start the sample nginx app:
+
+ ```bash
+ kubectl apply -f config/nginx-app/base.yaml
+ ```
+
+1. Create a backup:
+
+ ```bash
+ ark backup create nginx-backup --include-namespaces nginx-example
+ ```
+
+1. Simulate a disaster:
+
+ ```bash
+ kubectl delete namespaces nginx-example
+ ```
+
+ Wait for the namespace to be deleted.
+
+1. Restore your lost resources:
+
+ ```bash
+ ark restore create --from-backup nginx-backup
+ ```
+
+### Snapshot example (with PersistentVolumes)
+
+> NOTE: For Azure, you must run Kubernetes version 1.7.2 or later to support PV snapshotting of managed disks.
+
+1. Start the sample nginx app:
+
+ ```bash
+ kubectl apply -f config/nginx-app/with-pv.yaml
+ ```
+
+1. Create a backup with PV snapshotting:
+
+ ```bash
+ ark backup create nginx-backup --include-namespaces nginx-example
+ ```
+
+1. Simulate a disaster:
+
+ ```bash
+ kubectl delete namespaces nginx-example
+ ```
+
+ Because the default [reclaim policy][19] for dynamically-provisioned PVs is "Delete", these commands should trigger your cloud provider to delete the disk that backs the PV. Deletion is asynchronous, so this may take some time. **Before continuing to the next step, check your cloud provider to confirm that the disk no longer exists.**
+
+1. Restore your lost resources:
+
+ ```bash
+ ark restore create --from-backup nginx-backup
+ ```
+
+[0]: aws-config.md
+[1]: gcp-config.md
+[2]: azure-config.md
+[3]: namespace.md
+[4]: ibm-config.md
+[19]: https://kubernetes.io/docs/concepts/storage/persistent-volumes/#reclaiming
+[20]: restic.md
+[99]: support-matrix.md
+[100]: support-matrix.md#volume-snapshot-providers
+[101]: https://www.minio.io
+[102]: https://portworx.com
diff --git a/site/docs/v0.10.0/issue-template-gen/main.go b/site/docs/v0.10.0/issue-template-gen/main.go
new file mode 100644
index 000000000..19ef0ab85
--- /dev/null
+++ b/site/docs/v0.10.0/issue-template-gen/main.go
@@ -0,0 +1,45 @@
+/*
+Copyright 2018 the Heptio Ark contributors.
+
+Licensed under the Apache License, Version 2.0 (the "License");
+you may not use this file except in compliance with the License.
+You may obtain a copy of the License at
+
+ http://www.apache.org/licenses/LICENSE-2.0
+
+Unless required by applicable law or agreed to in writing, software
+distributed under the License is distributed on an "AS IS" BASIS,
+WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+See the License for the specific language governing permissions and
+limitations under the License.
+*/
+
+// This code renders the IssueTemplate string in pkg/cmd/cli/bug/bug.go to
+// .github/ISSUE_TEMPLATE/bug_report.md via the hack/update-generated-issue-template.sh script.
+
+package main
+
+import (
+ "log"
+ "os"
+ "text/template"
+
+ "github.com/heptio/ark/pkg/cmd/cli/bug"
+)
+
+func main() {
+ outTemplateFilename := os.Args[1]
+ outFile, err := os.OpenFile(outTemplateFilename, os.O_CREATE|os.O_TRUNC|os.O_WRONLY, 0644)
+ if err != nil {
+ log.Fatal(err)
+ }
+ defer outFile.Close()
+ tmpl, err := template.New("ghissue").Parse(bug.IssueTemplate)
+ if err != nil {
+ log.Fatal(err)
+ }
+ err = tmpl.Execute(outFile, bug.ArkBugInfo{})
+ if err != nil {
+ log.Fatal(err)
+ }
+}
diff --git a/site/docs/v0.10.0/locations.md b/site/docs/v0.10.0/locations.md
new file mode 100644
index 000000000..9479828b2
--- /dev/null
+++ b/site/docs/v0.10.0/locations.md
@@ -0,0 +1,168 @@
+# Backup Storage Locations and Volume Snapshot Locations
+
+Ark v0.10 introduces a new way of configuring where Ark backups and their associated persistent volume snapshots are stored.
+
+## Motivations
+
+In Ark versions prior to v0.10, the configuration for where to store backups & volume snapshots is specified in a `Config` custom resource. The `backupStorageProvider` section captures the place where all Ark backups should be stored. This is defined by a **provider** (e.g. `aws`, `azure`, `gcp`, `minio`, etc.), a **bucket**, and possibly some additional provider-specific settings (e.g. `region`). Similarly, the `persistentVolumeProvider` section captures the place where all persistent volume snapshots taken as part of Ark backups should be stored, and is defined by a **provider** and additional provider-specific settings (e.g. `region`).
+
+There are a number of use cases that this basic design does not support, such as:
+
+- Take snapshots of more than one kind of persistent volume in a single Ark backup (e.g. in a cluster with both EBS volumes and Portworx volumes)
+- Have some Ark backups go to a bucket in an eastern USA region, and others go to a bucket in a western USA region
+- For volume providers that support it (e.g. Portworx), have some snapshots be stored locally on the cluster and have others be stored in the cloud
+
+Additionally, as we look ahead to backup replication, a major feature on our roadmap, we know that we'll need Ark to be able to support multiple possible storage locations.
+
+## Overview
+
+In Ark v0.10 we got rid of the `Config` custom resource, and replaced it with two new custom resources, `BackupStorageLocation` and `VolumeSnapshotLocation`. The new resources directly replace the legacy `backupStorageProvider` and `persistentVolumeProvider` sections of the `Config` resource, respectively.
+
+Now, the user can pre-define more than one possible `BackupStorageLocation` and more than one `VolumeSnapshotLocation`, and can select *at backup creation time* the location in which the backup and associated snapshots should be stored.
+
+A `BackupStorageLocation` is defined as a bucket, a prefix within that bucket under which all Ark data should be stored, and a set of additional provider-specific fields (e.g. AWS region, Azure storage account, etc.) The [API documentation][1] captures the configurable parameters for each in-tree provider.
+
+A `VolumeSnapshotLocation` is defined entirely by provider-specific fields (e.g. AWS region, Azure resource group, Portworx snapshot type, etc.) The [API documentation][2] captures the configurable parameters for each in-tree provider.
+
+Additionally, since multiple `VolumeSnapshotLocations` can be created, the user can now configure locations for more than one volume provider, and if the cluster has volumes from multiple providers (e.g. AWS EBS and Portworx), all of them can be snapshotted in a single Ark backup.
+
+## Limitations / Caveats
+
+- Volume snapshots are still limited by where your provider allows you to create snapshots. For example, AWS and Azure do not allow you to create a volume snapshot in a different region than where the volume is. If you try to take an Ark backup using a volume snapshot location with a different region than where your cluster's volumes are, the backup will fail.
+
+- Each Ark backup has one `BackupStorageLocation`, and one `VolumeSnapshotLocation` per volume provider. It is not possible (yet) to send a single Ark backup to multiple backup storage locations simultaneously, or a single volume snapshot to multiple locations simultaneously. However, you can always set up multiple scheduled backups that differ only in the storage locations used if redundancy of backups across locations is important.
+
+- Cross-provider snapshots are not supported. If you have a cluster with more than one type of volume (e.g. EBS and Portworx), but you only have a `VolumeSnapshotLocation` configured for EBS, then Ark will **only** snapshot the EBS volumes.
+
+- Restic data is now stored under a prefix/subdirectory of the main Ark bucket, and will go into the bucket corresponding to the `BackupStorageLocation` selected by the user at backup creation time.
+
+## Examples
+
+Let's look at some examples of how we can use this new mechanism to address each of our previously unsupported use cases:
+
+#### Take snapshots of more than one kind of persistent volume in a single Ark backup (e.g. in a cluster with both EBS volumes and Portworx volumes)
+
+During server configuration:
+
+```shell
+ark snapshot-location create ebs-us-east-1 \
+ --provider aws \
+ --config region=us-east-1
+
+ark snapshot-location create portworx-cloud \
+ --provider portworx \
+ --config type=cloud
+```
+
+During backup creation:
+
+```shell
+ark backup create full-cluster-backup \
+ --volume-snapshot-locations ebs-us-east-1,portworx-cloud
+```
+
+Alternately, since in this example there's only one possible volume snapshot location configured for each of our two providers (`ebs-us-east-1` for `aws`, and `portworx-cloud` for `portworx`), Ark doesn't require them to be explicitly specified when creating the backup:
+
+```shell
+ark backup create full-cluster-backup
+```
+
+#### Have some Ark backups go to a bucket in an eastern USA region, and others go to a bucket in a western USA region
+
+During server configuration:
+
+```shell
+ark backup-location create default \
+ --provider aws \
+ --bucket ark-backups \
+ --config region=us-east-1
+
+ark backup-location create s3-alt-region \
+ --provider aws \
+ --bucket ark-backups-alt \
+ --config region=us-west-1
+```
+
+During backup creation:
+```shell
+# The Ark server will automatically store backups in the backup storage location named "default" if
+# one is not specified when creating the backup. You can alter which backup storage location is used
+# by default by setting the --default-backup-storage-location flag on the `ark server` command (run
+# by the Ark deployment) to the name of a different backup storage location.
+ark backup create full-cluster-backup
+```
+Or:
+```shell
+ark backup create full-cluster-alternate-location-backup \
+ --storage-location s3-alt-region
+```
+
+#### For volume providers that support it (e.g. Portworx), have some snapshots be stored locally on the cluster and have others be stored in the cloud
+
+During server configuration:
+
+```shell
+ark snapshot-location create portworx-local \
+ --provider portworx \
+ --config type=local
+
+ark snapshot-location create portworx-cloud \
+ --provider portworx \
+ --config type=cloud
+```
+
+During backup creation:
+
+```shell
+# Note that since in this example we have two possible volume snapshot locations for the Portworx
+# provider, we need to explicitly specify which one to use when creating a backup. Alternately,
+# you can set the --default-volume-snapshot-locations flag on the `ark server` command (run by
+# the Ark deployment) to specify which location should be used for each provider by default, in
+# which case you don't need to specify it when creating a backup.
+ark backup create local-snapshot-backup \
+ --volume-snapshot-locations portworx-local
+```
+
+Or:
+
+```shell
+ark backup create cloud-snapshot-backup \
+ --volume-snapshot-locations portworx-cloud
+```
+
+#### One location is still easy
+
+If you don't have a use case for more than one location, it's still just as easy to use Ark. Let's assume you're running on AWS, in the `us-west-1` region:
+
+During server configuration:
+
+```shell
+ark backup-location create default \
+ --provider aws \
+ --bucket ark-backups \
+ --config region=us-west-1
+
+ark snapshot-location create ebs-us-west-1 \
+ --provider aws \
+ --config region=us-west-1
+```
+
+During backup creation:
+```shell
+# Ark's will automatically use your configured backup storage location and volume snapshot location.
+# Nothing new needs to be specified when creating a backup.
+ark backup create full-cluster-backup
+```
+
+## Additional Use Cases
+
+1. If you're using Azure's AKS, you may want to store your volume snapshots outside of the "infrastructure" resource group that is automatically created when you create your AKS cluster. This is now possible using a `VolumeSnapshotLocation`, by specifying a `resourceGroup` under the `config` section of the snapshot location. See the [Azure volume snapshot location documentation][3] for details.
+
+1. If you're using Azure, you may want to store your Ark backups across multiple storage accounts and/or resource groups. This is now possible using a `BackupStorageLocation`, by specifying a `storageAccount` and/or `resourceGroup`, respectively, under the `config` section of the backup location. See the [Azure backup storage location documentation][4] for details.
+
+
+
+[1]: api-types/backupstoragelocation.md
+[2]: api-types/volumesnapshotlocation.md
+[3]: api-types/volumesnapshotlocation.md#azure
+[4]: api-types/backupstoragelocation.md#azure
diff --git a/site/docs/v0.10.0/migration-case.md b/site/docs/v0.10.0/migration-case.md
new file mode 100644
index 000000000..f3c6a4f07
--- /dev/null
+++ b/site/docs/v0.10.0/migration-case.md
@@ -0,0 +1,48 @@
+# Cluster migration
+
+*Using Backups and Restores*
+
+Heptio Ark can help you port your resources from one cluster to another, as long as you point each Ark instance to the same cloud object storage location. In this scenario, we are also assuming that your clusters are hosted by the same cloud provider. **Note that Heptio Ark does not support the migration of persistent volumes across cloud providers.**
+
+1. *(Cluster 1)* Assuming you haven't already been checkpointing your data with the Ark `schedule` operation, you need to first back up your entire cluster (replacing `` as desired):
+
+ ```
+ ark backup create
+ ```
+ The default TTL is 30 days (720 hours); you can use the `--ttl` flag to change this as necessary.
+
+1. *(Cluster 2)* Add the `--restore-only` flag to the server spec in the Ark deployment YAML.
+
+1. *(Cluster 2)* Make sure that the `BackupStorageLocation` and `VolumeSnapshotLocation` CRDs match the ones from *Cluster 1*, so that your new Ark server instance points to the same bucket.
+
+1. *(Cluster 2)* Make sure that the Ark Backup object is created. Ark resources are synchronized with the backup files in cloud storage.
+
+ ```
+ ark backup describe
+ ```
+
+ **Note:** As of version 0.10, the default sync interval is 1 minute, so make sure to wait before checking. You can configure this interval with the `--backup-sync-period` flag to the Ark server.
+
+1. *(Cluster 2)* Once you have confirmed that the right Backup (``) is now present, you can restore everything with:
+
+ ```
+ ark restore create --from-backup
+ ```
+
+## Verify both clusters
+
+Check that the second cluster is behaving as expected:
+
+1. *(Cluster 2)* Run:
+
+ ```
+ ark restore get
+ ```
+
+1. Then run:
+
+ ```
+ ark restore describe
+ ```
+
+If you encounter issues, make sure that Ark is running in the same namespace in both clusters.
\ No newline at end of file
diff --git a/site/docs/v0.10.0/namespace.md b/site/docs/v0.10.0/namespace.md
new file mode 100644
index 000000000..ca8285774
--- /dev/null
+++ b/site/docs/v0.10.0/namespace.md
@@ -0,0 +1,74 @@
+# Run in custom namespace
+
+In Ark version 0.7.0 and later, you can run Ark in any namespace. To do so, you specify the
+namespace in the YAML files that configure the Ark server. You then also specify the namespace when
+you run Ark client commands.
+
+## Edit the example files
+
+The Ark release tarballs include a set of example configs that you can use to set up your Ark server. The
+examples place the server and backup/schedule/restore/etc. data in the `heptio-ark` namespace.
+
+To run the server in another namespace, you edit the relevant files, changing `heptio-ark` to
+your desired namespace.
+
+To store your backups, schedules, restores, and config in another namespace, you edit the relevant
+files, changing `heptio-ark` to your desired namespace. You also need to create the
+`cloud-credentials` secret in your desired namespace.
+
+First, ensure you've [downloaded & extracted the latest release][0].
+
+For all cloud providers, edit `config/common/00-prereqs.yaml`. This file defines:
+
+* CustomResourceDefinitions for the Ark objects (backups, schedules, restores, downloadrequests, etc.)
+* The namespace where the Ark server runs
+* The namespace where backups, schedules, restores, etc. are stored
+* The Ark service account
+* The RBAC rules to grant permissions to the Ark service account
+
+
+### AWS
+
+For AWS, edit:
+
+* `config/aws/05-ark-backupstoragelocation.yaml`
+* `config/aws/06-ark-volumesnapshotlocation.yaml`
+* `config/aws/10-deployment.yaml`
+
+
+### Azure
+
+For Azure, edit:
+
+* `config/azure/00-ark-deployment.yaml`
+* `config/azure/05-ark-backupstoragelocation.yaml`
+* `config/azure/06-ark-volumesnapshotlocation.yaml`
+
+### GCP
+
+For GCP, edit:
+
+* `config/gcp/05-ark-backupstoragelocation.yaml`
+* `config/gcp/06-ark-volumesnapshotlocation.yaml`
+* `config/gcp/10-deployment.yaml`
+
+
+### IBM
+
+For IBM, edit:
+
+* `config/ibm/05-ark-backupstoragelocation.yaml`
+* `config/ibm/10-deployment.yaml`
+
+
+## Specify the namespace in client commands
+
+To specify the namespace for all Ark client commands, run:
+
+```
+ark client config set namespace=
+```
+
+
+
+[0]: get-started.md#download
diff --git a/site/docs/v0.10.0/output-file-format.md b/site/docs/v0.10.0/output-file-format.md
new file mode 100644
index 000000000..abdc0166b
--- /dev/null
+++ b/site/docs/v0.10.0/output-file-format.md
@@ -0,0 +1,99 @@
+# Output file format
+
+A backup is a gzip-compressed tar file whose name matches the Backup API resource's `metadata.name` (what is specified during `ark backup create `).
+
+In cloud object storage, each backup file is stored in its own subdirectory in the bucket specified in the Ark server configuration. This subdirectory includes an additional file called `ark-backup.json`. The JSON file lists all information about your associated Backup resource, including any default values. This gives you a complete historical record of the backup configuration. The JSON file also specifies `status.version`, which corresponds to the output file format.
+
+The directory structure in your cloud storage looks something like:
+
+```
+rootBucket/
+ backup1234/
+ ark-backup.json
+ backup1234.tar.gz
+```
+
+## Example backup JSON file
+
+```json
+{
+ "kind": "Backup",
+ "apiVersion": "ark.heptio.com/v1",
+ "metadata": {
+ "name": "test-backup",
+ "namespace": "heptio-ark",
+ "selfLink": "/apis/ark.heptio.com/v1/namespaces/heptio-ark/backups/testtest",
+ "uid": "a12345cb-75f5-11e7-b4c2-abcdef123456",
+ "resourceVersion": "337075",
+ "creationTimestamp": "2017-07-31T13:39:15Z"
+ },
+ "spec": {
+ "includedNamespaces": [
+ "*"
+ ],
+ "excludedNamespaces": null,
+ "includedResources": [
+ "*"
+ ],
+ "excludedResources": null,
+ "labelSelector": null,
+ "snapshotVolumes": true,
+ "ttl": "24h0m0s"
+ },
+ "status": {
+ "version": 1,
+ "expiration": "2017-08-01T13:39:15Z",
+ "phase": "Completed",
+ "volumeBackups": {
+ "pvc-e1e2d345-7583-11e7-b4c2-abcdef123456": {
+ "snapshotID": "snap-04b1a8e11dfb33ab0",
+ "type": "gp2",
+ "iops": 100
+ }
+ },
+ "validationErrors": null
+ }
+}
+```
+Note that this file includes detailed info about your volume snapshots in the `status.volumeBackups` field, which can be helpful if you want to manually check them in your cloud provider GUI.
+
+## file format version: 1
+
+When unzipped, a typical backup directory (e.g. `backup1234.tar.gz`) looks like the following:
+
+```
+resources/
+ persistentvolumes/
+ cluster/
+ pv01.json
+ ...
+ configmaps/
+ namespaces/
+ namespace1/
+ myconfigmap.json
+ ...
+ namespace2/
+ ...
+ pods/
+ namespaces/
+ namespace1/
+ mypod.json
+ ...
+ namespace2/
+ ...
+ jobs/
+ namespaces/
+ namespace1/
+ awesome-job.json
+ ...
+ namespace2/
+ ...
+ deployments/
+ namespaces/
+ namespace1/
+ cool-deployment.json
+ ...
+ namespace2/
+ ...
+ ...
+```
diff --git a/site/docs/v0.10.0/plugins.md b/site/docs/v0.10.0/plugins.md
new file mode 100644
index 000000000..4f3bc04fd
--- /dev/null
+++ b/site/docs/v0.10.0/plugins.md
@@ -0,0 +1,31 @@
+# Plugins
+
+Heptio Ark has a plugin architecture that allows users to add their own custom functionality to Ark backups & restores
+without having to modify/recompile the core Ark binary. To add custom functionality, users simply create their own binary
+containing implementations of Ark's plugin kinds (described below), plus a small amount of boilerplate code to
+expose the plugin implementations to Ark. This binary is added to a container image that serves as an init container for
+the Ark server pod and copies the binary into a shared emptyDir volume for the Ark server to access.
+
+Multiple plugins, of any type, can be implemented in this binary.
+
+A fully-functional [sample plugin repository][1] is provided to serve as a convenient starting point for plugin authors.
+
+## Plugin Kinds
+
+Ark currently supports the following kinds of plugins:
+
+- **Object Store** - persists and retrieves backups, backup logs and restore logs
+- **Block Store** - creates volume snapshots (during backup) and restores volumes from snapshots (during restore)
+- **Backup Item Action** - executes arbitrary logic for individual items prior to storing them in a backup file
+- **Restore Item Action** - executes arbitrary logic for individual items prior to restoring them into a cluster
+
+## Plugin Logging
+
+Ark provides a [logger][2] that can be used by plugins to log structured information to the main Ark server log or
+per-backup/restore logs. See the [sample repository][1] for an example of how to instantiate and use the logger
+within your plugin.
+
+
+
+[1]: https://github.com/heptio/ark-plugin-example
+[2]: https://github.com/heptio/ark/blob/master/pkg/plugin/logger.go
diff --git a/site/docs/v0.10.0/rbac.md b/site/docs/v0.10.0/rbac.md
new file mode 100644
index 000000000..ebc031671
--- /dev/null
+++ b/site/docs/v0.10.0/rbac.md
@@ -0,0 +1,47 @@
+# Run Ark more securely with restrictive RBAC settings
+
+By default Ark runs with an RBAC policy of ClusterRole `cluster-admin`. This is to make sure that Ark can back up or restore anything in your cluster. But `cluster-admin` access is wide open -- it gives Ark components access to everything in your cluster. Depending on your environment and your security needs, you should consider whether to configure additional RBAC policies with more restrictive access.
+
+**Note:** Roles and RoleBindings are associated with a single namespaces, not with an entire cluster. PersistentVolume backups are associated only with an entire cluster. This means that any backups or restores that use a restrictive Role and RoleBinding pair can manage only the resources that belong to the namespace. You do not need a wide open RBAC policy to manage PersistentVolumes, however. You can configure a ClusterRole and ClusterRoleBinding that allow backups and restores only of PersistentVolumes, not of all objects in the cluster.
+
+For more information about RBAC and access control generally in Kubernetes, see the Kubernetes documentation about [access control][1], [managing service accounts][2], and [RBAC authorization][3].
+
+## Set up Roles and RoleBindings
+
+Here's a sample Role and RoleBinding pair.
+
+```yaml
+apiVersion: rbac.authorization.k8s.io/v1
+kind: Role
+metadata:
+ namespace: YOUR_NAMESPACE_HERE
+ name: ROLE_NAME_HERE
+ labels:
+ component: ark
+rules:
+ - apiGroups:
+ - ark.heptio.com
+ verbs:
+ - "*"
+ resources:
+ - "*"
+```
+
+```yaml
+apiVersion: rbac.authorization.k8s.io/v1
+kind: RoleBinding
+metadata:
+ name: ROLEBINDING_NAME_HERE
+subjects:
+ - kind: ServiceAccount
+ name: YOUR_SERVICEACCOUNT_HERE
+roleRef:
+ kind: Role
+ name: ROLE_NAME_HERE
+ apiGroup: rbac.authorization.k8s.io
+```
+
+[1]: https://kubernetes.io/docs/reference/access-authn-authz/controlling-access/
+[2]: https://kubernetes.io/docs/reference/access-authn-authz/service-accounts-admin/
+[3]: https://kubernetes.io/docs/reference/access-authn-authz/rbac/
+[4]: namespace.md
\ No newline at end of file
diff --git a/site/docs/v0.10.0/restic.md b/site/docs/v0.10.0/restic.md
new file mode 100644
index 000000000..ebb63cdb6
--- /dev/null
+++ b/site/docs/v0.10.0/restic.md
@@ -0,0 +1,248 @@
+# Restic Integration
+
+As of version 0.9.0, Ark has support for backing up and restoring Kubernetes volumes using a free open-source backup tool called
+[restic][1].
+
+Ark has always allowed you to take snapshots of persistent volumes as part of your backups if you’re using one of
+the supported cloud providers’ block storage offerings (Amazon EBS Volumes, Azure Managed Disks, Google Persistent Disks).
+Starting with version 0.6.0, we provide a plugin model that enables anyone to implement additional object and block storage
+backends, outside the main Ark repository.
+
+We integrated restic with Ark so that users have an out-of-the-box solution for backing up and restoring almost any type of Kubernetes
+volume*. This is a new capability for Ark, not a replacement for existing functionality. If you're running on AWS, and
+taking EBS snapshots as part of your regular Ark backups, there's no need to switch to using restic. However, if you've
+been waiting for a snapshot plugin for your storage platform, or if you're using EFS, AzureFile, NFS, emptyDir,
+local, or any other volume type that doesn't have a native snapshot concept, restic might be for you.
+
+Restic is not tied to a specific storage platform, which means that this integration also paves the way for future work to enable
+cross-volume-type data migrations. Stay tuned as this evolves!
+
+\* hostPath volumes are not supported, but the [new local volume type][4] is supported.
+
+## Setup
+
+### Prerequisites
+
+- A working install of Ark version 0.10.0 or later. See [Set up Ark][2]
+- A local clone of [the latest release tag of the Ark repository][3]
+- Ark's restic integration requires the Kubernetes [MountPropagation feature][6], which is enabled by default in Kubernetes v1.10.0 and later.
+
+
+### Instructions
+
+1. Ensure you've [downloaded & extracted the latest release][3].
+
+1. In the Ark directory (i.e. where you extracted the release tarball), run the following to create new custom resource definitions:
+
+ ```bash
+ kubectl apply -f config/common/00-prereqs.yaml
+ ```
+
+1. Run one of the following for your platform to create the daemonset:
+
+ - AWS: `kubectl apply -f config/aws/20-restic-daemonset.yaml`
+ - Azure: `kubectl apply -f config/azure/20-restic-daemonset.yaml`
+ - GCP: `kubectl apply -f config/gcp/20-restic-daemonset.yaml`
+ - Minio: `kubectl apply -f config/minio/30-restic-daemonset.yaml`
+
+You're now ready to use Ark with restic.
+
+## Back up
+
+1. Run the following for each pod that contains a volume to back up:
+
+ ```bash
+ kubectl -n YOUR_POD_NAMESPACE annotate pod/YOUR_POD_NAME backup.ark.heptio.com/backup-volumes=YOUR_VOLUME_NAME_1,YOUR_VOLUME_NAME_2,...
+ ```
+
+ where the volume names are the names of the volumes in the pod spec.
+
+ For example, for the following pod:
+
+ ```bash
+ apiVersion: v1
+ kind: Pod
+ metadata:
+ name: sample
+ namespace: foo
+ spec:
+ containers:
+ - image: k8s.gcr.io/test-webserver
+ name: test-webserver
+ volumeMounts:
+ - name: pvc-volume
+ mountPath: /volume-1
+ - name: emptydir-volume
+ mountPath: /volume-2
+ volumes:
+ - name: pvc-volume
+ persistentVolumeClaim:
+ claimName: test-volume-claim
+ - name: emptydir-volume
+ emptyDir: {}
+ ```
+
+ You'd run:
+ ```bash
+ kubectl -n foo annotate pod/sample backup.ark.heptio.com/backup-volumes=pvc-volume,emptydir-volume
+ ```
+
+ This annotation can also be provided in a pod template spec if you use a controller to manage your pods.
+
+1. Take an Ark backup:
+
+ ```bash
+ ark backup create NAME OPTIONS...
+ ```
+
+1. When the backup completes, view information about the backups:
+
+ ```bash
+ ark backup describe YOUR_BACKUP_NAME
+
+ kubectl -n heptio-ark get podvolumebackups -l ark.heptio.com/backup-name=YOUR_BACKUP_NAME -o yaml
+ ```
+
+## Restore
+
+1. Restore from your Ark backup:
+
+ ```bash
+ ark restore create --from-backup BACKUP_NAME OPTIONS...
+ ```
+
+1. When the restore completes, view information about your pod volume restores:
+
+ ```bash
+ ark restore describe YOUR_RESTORE_NAME
+
+ kubectl -n heptio-ark get podvolumerestores -l ark.heptio.com/restore-name=YOUR_RESTORE_NAME -o yaml
+ ```
+
+## Limitations
+
+- `hostPath` volumes are not supported. [Local persistent volumes][4] are supported.
+- Those of you familiar with [restic][1] may know that it encrypts all of its data. We've decided to use a static,
+common encryption key for all restic repositories created by Ark. **This means that anyone who has access to your
+bucket can decrypt your restic backup data**. Make sure that you limit access to the restic bucket
+appropriately. We plan to implement full Ark backup encryption, including securing the restic encryption keys, in
+a future release.
+
+## Troubleshooting
+
+Run the following checks:
+
+Are your Ark server and daemonset pods running?
+
+```bash
+kubectl get pods -n heptio-ark
+```
+
+Does your restic repository exist, and is it ready?
+
+```bash
+ark restic repo get
+
+ark restic repo get REPO_NAME -o yaml
+```
+
+Are there any errors in your Ark backup/restore?
+
+```bash
+ark backup describe BACKUP_NAME
+ark backup logs BACKUP_NAME
+
+ark restore describe RESTORE_NAME
+ark restore logs RESTORE_NAME
+```
+
+What is the status of your pod volume backups/restores?
+
+```bash
+kubectl -n heptio-ark get podvolumebackups -l ark.heptio.com/backup-name=BACKUP_NAME -o yaml
+
+kubectl -n heptio-ark get podvolumerestores -l ark.heptio.com/restore-name=RESTORE_NAME -o yaml
+```
+
+Is there any useful information in the Ark server or daemon pod logs?
+
+```bash
+kubectl -n heptio-ark logs deploy/ark
+kubectl -n heptio-ark logs DAEMON_POD_NAME
+```
+
+**NOTE**: You can increase the verbosity of the pod logs by adding `--log-level=debug` as an argument
+to the container command in the deployment/daemonset pod template spec.
+
+## How backup and restore work with restic
+
+We introduced three custom resource definitions and associated controllers:
+
+- `ResticRepository` - represents/manages the lifecycle of Ark's [restic repositories][5]. Ark creates
+a restic repository per namespace when the first restic backup for a namespace is requested. The controller
+for this custom resource executes restic repository lifecycle commands -- `restic init`, `restic check`,
+and `restic prune`.
+
+ You can see information about your Ark restic repositories by running `ark restic repo get`.
+
+- `PodVolumeBackup` - represents a restic backup of a volume in a pod. The main Ark backup process creates
+one or more of these when it finds an annotated pod. Each node in the cluster runs a controller for this
+resource (in a daemonset) that handles the `PodVolumeBackups` for pods on that node. The controller executes
+`restic backup` commands to backup pod volume data.
+
+- `PodVolumeRestore` - represents a restic restore of a pod volume. The main Ark restore process creates one
+or more of these when it encounters a pod that has associated restic backups. Each node in the cluster runs a
+controller for this resource (in the same daemonset as above) that handles the `PodVolumeRestores` for pods
+on that node. The controller executes `restic restore` commands to restore pod volume data.
+
+### Backup
+
+1. The main Ark backup process checks each pod that it's backing up for the annotation specifying a restic backup
+should be taken (`backup.ark.heptio.com/backup-volumes`)
+1. When found, Ark first ensures a restic repository exists for the pod's namespace, by:
+ - checking if a `ResticRepository` custom resource already exists
+ - if not, creating a new one, and waiting for the `ResticRepository` controller to init/check it
+1. Ark then creates a `PodVolumeBackup` custom resource per volume listed in the pod annotation
+1. The main Ark process now waits for the `PodVolumeBackup` resources to complete or fail
+1. Meanwhile, each `PodVolumeBackup` is handled by the controller on the appropriate node, which:
+ - has a hostPath volume mount of `/var/lib/kubelet/pods` to access the pod volume data
+ - finds the pod volume's subdirectory within the above volume
+ - runs `restic backup`
+ - updates the status of the custom resource to `Completed` or `Failed`
+1. As each `PodVolumeBackup` finishes, the main Ark process captures its restic snapshot ID and adds it as an annotation
+to the copy of the pod JSON that's stored in the Ark backup. This will be used for restores, as seen in the next section.
+
+### Restore
+
+1. The main Ark restore process checks each pod that it's restoring for annotations specifying a restic backup
+exists for a volume in the pod (`snapshot.ark.heptio.com/`)
+1. When found, Ark first ensures a restic repository exists for the pod's namespace, by:
+ - checking if a `ResticRepository` custom resource already exists
+ - if not, creating a new one, and waiting for the `ResticRepository` controller to init/check it (note that
+ in this case, the actual repository should already exist in object storage, so the Ark controller will simply
+ check it for integrity)
+1. Ark adds an init container to the pod, whose job is to wait for all restic restores for the pod to complete (more
+on this shortly)
+1. Ark creates the pod, with the added init container, by submitting it to the Kubernetes API
+1. Ark creates a `PodVolumeRestore` custom resource for each volume to be restored in the pod
+1. The main Ark process now waits for each `PodVolumeRestore` resource to complete or fail
+1. Meanwhile, each `PodVolumeRestore` is handled by the controller on the appropriate node, which:
+ - has a hostPath volume mount of `/var/lib/kubelet/pods` to access the pod volume data
+ - waits for the pod to be running the init container
+ - finds the pod volume's subdirectory within the above volume
+ - runs `restic restore`
+ - on success, writes a file into the pod volume, in an `.ark` subdirectory, whose name is the UID of the Ark restore
+ that this pod volume restore is for
+ - updates the status of the custom resource to `Completed` or `Failed`
+1. The init container that was added to the pod is running a process that waits until it finds a file
+within each restored volume, under `.ark`, whose name is the UID of the Ark restore being run
+1. Once all such files are found, the init container's process terminates successfully and the pod moves
+on to running other init containers/the main containers.
+
+
+[1]: https://github.com/restic/restic
+[2]: install-overview.md
+[3]: https://github.com/heptio/ark/releases/
+[4]: https://kubernetes.io/docs/concepts/storage/volumes/#local
+[5]: http://restic.readthedocs.io/en/latest/100_references.html#terminology
+[6]: https://kubernetes.io/docs/concepts/storage/volumes/#mount-propagation
diff --git a/site/docs/v0.10.0/storage-layout-reorg-v0.10.md b/site/docs/v0.10.0/storage-layout-reorg-v0.10.md
new file mode 100644
index 000000000..dab57a936
--- /dev/null
+++ b/site/docs/v0.10.0/storage-layout-reorg-v0.10.md
@@ -0,0 +1,160 @@
+# Object Storage Layout Changes in v0.10
+
+## Overview
+
+Ark v0.10 includes breaking changes to where data is stored in your object storage bucket. You'll need to run a [one-time migration procedure](#upgrading-to-v010)
+if you're upgrading from prior versions of Ark.
+
+## Details
+
+Prior to v0.10, Ark stored data in an object storage bucket using the following structure:
+
+```
+/
+ backup-1/
+ ark-backup.json
+ backup-1.tar.gz
+ backup-1-logs.gz
+ restore-of-backup-1-logs.gz
+ restore-of-backup-1-results.gz
+ backup-2/
+ ark-backup.json
+ backup-2.tar.gz
+ backup-2-logs.gz
+ restore-of-backup-2-logs.gz
+ restore-of-backup-2-results.gz
+ ...
+```
+
+Ark also stored restic data, if applicable, in a separate object storage bucket, structured as:
+
+```
+/[/]
+ namespace-1/
+ data/
+ index/
+ keys/
+ snapshots/
+ config
+ namespace-2/
+ data/
+ index/
+ keys/
+ snapshots/
+ config
+ ...
+```
+
+As of v0.10, we've reorganized this layout to provide a cleaner and more extensible directory structure. The new layout looks like:
+
+```
+[/]/
+ backups/
+ backup-1/
+ ark-backup.json
+ backup-1.tar.gz
+ backup-1-logs.gz
+ backup-2/
+ ark-backup.json
+ backup-2.tar.gz
+ backup-2-logs.gz
+ ...
+ restores/
+ restore-of-backup-1/
+ restore-of-backup-1-logs.gz
+ restore-of-backup-1-results.gz
+ restore-of-backup-2/
+ restore-of-backup-2-logs.gz
+ restore-of-backup-2-results.gz
+ ...
+ restic/
+ namespace-1/
+ data/
+ index/
+ keys/
+ snapshots/
+ config
+ namespace-2/
+ data/
+ index/
+ keys/
+ snapshots/
+ config
+ ...
+ ...
+```
+
+## Upgrading to v0.10
+
+Before upgrading to v0.10, you'll need to run a one-time upgrade script to rearrange the contents of your existing Ark bucket(s) to be compatible with
+the new layout.
+
+Please note that the following scripts **will not** migrate existing restore logs/results into the new `restores/` subdirectory. This means that they
+will not be accessible using `ark restore describe` or `ark restore logs`. They *will* remain in the relevant backup's subdirectory so they are manually
+accessible, and will eventually be garbage-collected along with the backup. We've taken this approach in order to keep the migration scripts simple
+and less error-prone.
+
+### rclone-Based Script
+
+This script uses [rclone][1], which you can download and install following the instructions [here][2].
+Please read through the script carefully before starting and execute it step-by-step.
+
+```bash
+ARK_BUCKET=
+ARK_TEMP_MIGRATION_BUCKET=
+
+# 1. This is an interactive step that configures rclone to be
+# able to access your storage provider. Follow the instructions,
+# and keep track of the "remote name" for the next step:
+rclone config
+
+# 2. Store the name of the rclone remote that you just set up
+# in Step #1:
+RCLONE_REMOTE_NAME=
+
+# 3. Create a temporary bucket to be used as a backup of your
+# current Ark bucket's contents:
+rclone mkdir ${RCLONE_REMOTE_NAME}:${ARK_TEMP_MIGRATION_BUCKET}
+
+# 4. Do a full copy of the contents of your Ark bucket into the
+# temporary bucket:
+rclone copy ${RCLONE_REMOTE_NAME}:${ARK_BUCKET} ${RCLONE_REMOTE_NAME}:${ARK_TEMP_MIGRATION_BUCKET}
+
+# 5. Verify that the temporary bucket contains an exact copy of
+# your Ark bucket's contents. You should see a short block
+# of output stating "0 differences found":
+rclone check ${RCLONE_REMOTE_NAME}:${ARK_BUCKET} ${RCLONE_REMOTE_NAME}:${ARK_TEMP_MIGRATION_BUCKET}
+
+# 6. Delete your Ark bucket's contents (this command does not
+# delete the bucket itself, only the contents):
+rclone delete ${RCLONE_REMOTE_NAME}:${ARK_BUCKET}
+
+# 7. Copy the contents of the temporary bucket into your Ark bucket,
+# under the 'backups/' directory/prefix:
+rclone copy ${RCLONE_REMOTE_NAME}:${ARK_TEMP_MIGRATION_BUCKET} ${RCLONE_REMOTE_NAME}:${ARK_BUCKET}/backups
+
+# 8. Verify that the 'backups/' directory in your Ark bucket now
+# contains an exact copy of the temporary bucket's contents:
+rclone check ${RCLONE_REMOTE_NAME}:${ARK_BUCKET}/backups ${RCLONE_REMOTE_NAME}:${ARK_TEMP_MIGRATION_BUCKET}
+
+# 9. OPTIONAL: If you have restic data to migrate:
+
+# a. Copy the contents of your Ark restic location into your
+# Ark bucket, under the 'restic/' directory/prefix:
+ ARK_RESTIC_LOCATION=
+ rclone copy ${RCLONE_REMOTE_NAME}:${ARK_RESTIC_LOCATION} ${RCLONE_REMOTE_NAME}:${ARK_BUCKET}/restic
+
+# b. Check that the 'restic/' directory in your Ark bucket now
+# contains an exact copy of your restic location:
+ rclone check ${RCLONE_REMOTE_NAME}:${ARK_BUCKET}/restic ${RCLONE_REMOTE_NAME}:${ARK_RESTIC_LOCATION}
+
+# c. Delete your ResticRepository custom resources to allow Ark
+# to find them in the new location:
+ kubectl -n heptio-ark delete resticrepositories --all
+
+# 10. Once you've confirmed that Ark v0.10 works with your revised Ark
+# bucket, you can delete the temporary migration bucket.
+```
+
+[1]: https://rclone.org/
+[2]: https://rclone.org/downloads/
diff --git a/site/docs/v0.10.0/support-matrix.md b/site/docs/v0.10.0/support-matrix.md
new file mode 100644
index 000000000..aa0d733c6
--- /dev/null
+++ b/site/docs/v0.10.0/support-matrix.md
@@ -0,0 +1,54 @@
+# Compatible Storage Providers
+
+Ark supports a variety of storage providers for different backup and snapshot operations. As of version 0.6.0, a plugin system allows anyone to add compatibility for additional backup and volume storage platforms without modifying the Ark codebase.
+
+## Backup Storage Providers
+
+| Provider | Owner | Contact |
+|---------------------------|----------|---------------------------------|
+| [AWS S3][2] | Ark Team | [Slack][10], [GitHub Issue][11] |
+| [Azure Blob Storage][3] | Ark Team | [Slack][10], [GitHub Issue][11] |
+| [Google Cloud Storage][4] | Ark Team | [Slack][10], [GitHub Issue][11] |
+
+## S3-Compatible Backup Storage Providers
+
+Ark uses [Amazon's Go SDK][12] to connect to the S3 API. Some third-party storage providers also support the S3 API, and users have reported the following providers work with Ark:
+
+_Note that these providers are not regularly tested by the Ark team._
+
+ * [IBM Cloud][5]
+ * [Minio][9]
+ * Ceph RADOS v12.2.7
+ * [DigitalOcean][7]
+
+## Volume Snapshot Providers
+
+| Provider | Owner | Contact |
+|----------------------------------|-----------------|---------------------------------|
+| [AWS EBS][2] | Ark Team | [Slack][10], [GitHub Issue][11] |
+| [Azure Managed Disks][3] | Ark Team | [Slack][10], [GitHub Issue][11] |
+| [Google Compute Engine Disks][4] | Ark Team | [Slack][10], [GitHub Issue][11] |
+| [Restic][1] | Ark Team | [Slack][10], [GitHub Issue][11] |
+| [Portworx][6] | Portworx | [Slack][13], [GitHub Issue][14] |
+| [DigitalOcean][7] | StackPointCloud | |
+
+### Adding a new plugin
+
+To write a plugin for a new backup or volume storage system, take a look at the [example repo][8].
+
+After you publish your plugin, open a PR that adds your plugin to the appropriate list.
+
+[1]: restic.md
+[2]: aws-config.md
+[3]: azure-config.md
+[4]: gcp-config.md
+[5]: ibm-config.md
+[6]: https://docs.portworx.com/scheduler/kubernetes/ark.html
+[7]: https://github.com/StackPointCloud/ark-plugin-digitalocean
+[8]: https://github.com/heptio/ark-plugin-example/
+[9]: get-started.md
+[10]: https://kubernetes.slack.com/messages/ark-dr
+[11]: https://github.com/heptio/ark/issues
+[12]: https://github.com/aws/aws-sdk-go/aws
+[13]: https://portworx.slack.com/messages/px-k8s
+[14]: https://github.com/portworx/ark-plugin/issues
diff --git a/site/docs/v0.10.0/troubleshooting.md b/site/docs/v0.10.0/troubleshooting.md
new file mode 100644
index 000000000..2b861a11b
--- /dev/null
+++ b/site/docs/v0.10.0/troubleshooting.md
@@ -0,0 +1,71 @@
+# Troubleshooting
+
+These tips can help you troubleshoot known issues. If they don't help, you can [file an issue][4], or talk to us on the [#ark-dr channel][25] on the Kubernetes Slack server.
+
+See also:
+
+- [Debug installation/setup issues][2]
+- [Debug restores][1]
+
+## General troubleshooting information
+
+In `ark` version >= `0.1.0`, you can use the `ark bug` command to open a [Github issue][4] by launching a browser window with some prepopulated values. Values included are OS, CPU architecture, `kubectl` client and server versions (if available) and the `ark` client version. This information isn't submitted to Github until you click the `Submit new issue` button in the Github UI, so feel free to add, remove or update whatever information you like.
+
+Some general commands for troubleshooting that may be helpful:
+
+* `ark backup describe ` - describe the details of a backup
+* `ark backup logs ` - fetch the logs for this specific backup. Useful for viewing failures and warnings, including resources that could not be backed up.
+* `ark restore describe ` - describe the details of a restore
+* `ark restore logs ` - fetch the logs for this specific restore. Useful for viewing failures and warnings, including resources that could not be restored.
+* `kubectl logs deployment/ark -n heptio-ark` - fetch the logs of the Ark server pod. This provides the output of the Ark server processes.
+
+### Getting ark debug logs
+
+You can increase the verbosity of the Ark server by editing your Ark deployment to look like this:
+
+
+```
+kubectl edit deployment/ark -n heptio-ark
+...
+ containers:
+ - name: ark
+ image: gcr.io/heptio-images/ark:latest
+ command:
+ - /ark
+ args:
+ - server
+ - --log-level # Add this line
+ - debug # Add this line
+...
+```
+
+## Known issue with restoring LoadBalancer Service
+
+Because of how Kubernetes handles Service objects of `type=LoadBalancer`, when you restore these objects you might encounter an issue with changed values for Service UIDs. Kubernetes automatically generates the name of the cloud resource based on the Service UID, which is different when restored, resulting in a different name for the cloud load balancer. If the DNS CNAME for your application points to the DNS name of your cloud load balancer, you'll need to update the CNAME pointer when you perform an Ark restore.
+
+Alternatively, you might be able to use the Service's `spec.loadBalancerIP` field to keep connections valid, if your cloud provider supports this value. See [the Kubernetes documentation about Services of Type LoadBalancer](https://kubernetes.io/docs/concepts/services-networking/service/#loadbalancer).
+
+## Miscellaneous issues
+
+### Ark reports `custom resource not found` errors when starting up.
+
+Ark's server will not start if the required Custom Resource Definitions are not found in Kubernetes. Apply
+the `config/common/00-prereqs.yaml` file to create these definitions, then restart Ark.
+
+### `ark backup logs` returns a `SignatureDoesNotMatch` error
+
+Downloading artifacts from object storage utilizes temporary, signed URLs. In the case of S3-compatible
+providers, such as Ceph, there may be differences between their implementation and the official S3
+API that cause errors.
+
+Here are some things to verify if you receive `SignatureDoesNotMatch` errors:
+
+ * Make sure your S3-compatible layer is using [signature version 4][5] (such as Ceph RADOS v12.2.7)
+ * For Ceph, try using a native Ceph account for credentials instead of external providers such as OpenStack Keystone
+
+
+[1]: debugging-restores.md
+[2]: debugging-install.md
+[4]: https://github.com/heptio/ark/issues
+[5]: https://docs.aws.amazon.com/AmazonS3/latest/API/sig-v4-authenticating-requests.html
+[25]: https://kubernetes.slack.com/messages/ark-dr
diff --git a/site/docs/v0.10.0/upgrading-to-v0.10.md b/site/docs/v0.10.0/upgrading-to-v0.10.md
new file mode 100644
index 000000000..d68b30939
--- /dev/null
+++ b/site/docs/v0.10.0/upgrading-to-v0.10.md
@@ -0,0 +1,89 @@
+# Upgrading to Ark v0.10
+
+## Overview
+
+Ark v0.10 includes a number of breaking changes. Below, we outline what those changes are, and what steps you should take to ensure
+a successful upgrade from prior versions of Ark.
+
+## Breaking Changes
+
+### Switch from Config to BackupStorageLocation and VolumeSnapshotLocation CRDs, and new server flags
+
+Prior to v0.10, Ark used a `Config` CRD to capture information about your backup storage and persistent volume providers, as well
+some miscellaneous Ark settings. In v0.10, we've eliminated this CRD and replaced it with:
+
+- A [BackupStorageLocation][1] CRD to capture information about where to store your backups
+- A [VolumeSnapshotLocation][2] CRD to capture information about where to store your persistent volume snapshots
+- Command-line flags for the `ark server` command (run by your Ark deployment) to capture miscellaneous Ark settings
+
+When upgrading to v0.10, you'll need to transfer the configuration information that you currently have in the `Config` CRD
+into the above. We'll cover exactly how to do this below.
+
+For a general overview of this change, see the [Locations documentation][4].
+
+### Reorganization of data in object storage
+
+We've made [changes to the layout of data stored in object storage][3] for simplicity and extensibility. You'll need to
+rearrange any pre-v0.10 data as part of the upgrade. We've provided a script to help with this.
+
+## Step-by-Step Upgrade Instructions
+
+1. Ensure you've [downloaded & extracted the latest release][5].
+
+1. Scale down your existing Ark deployment:
+ ```bash
+ kubectl scale -n heptio-ark deploy/ark --replicas 0
+ ```
+
+1. In the Ark directory (i.e. where you extracted the release tarball), re-apply the `00-prereqs.yaml` file to create new CRDs:
+ ```bash
+ kubectl apply -f config/common/00-prereqs.yaml
+ ```
+
+1. Create one or more [BackupStorageLocation][1] resources based on the examples provided in the `config/` directory for your platform, using information from the existing `Config` resource as necessary.
+
+1. If you're using Ark to take PV snapshots, create one or more [VolumeSnapshotLocation][2] resources based on the examples provided in the `config/` directory for your platform, using information from the existing `Config` resource as necessary.
+
+1. Perform the one-time object storage migration detailed [here][3].
+
+1. In your Ark deployment YAML (see the `config/` directory for samples), specify flags to the `ark server` command under the container's `args`:
+
+ a. The names of the `BackupStorageLocation` and `VolumeSnapshotLocation(s)` that should be used by default for backups. If defaults are set here,
+ users won't need to explicitly specify location names when creating backups (though they still can, if they want to store backups/snapshots in
+ alternate locations). If no value is specified for `--default-backup-storage-location`, the Ark server looks for a `BackupStorageLocation`
+ named `default` to use.
+
+ Flag | Default Value | Description | Example
+ ---- | ------------- | ----------- | -------
+ `--default-backup-storage-location` | "default" | name of the backup storage location that should be used by default for backups | aws-us-east-1-bucket
+ `--default-volume-snapshot-locations` | [none] | name of the volume snapshot location(s) that should be used by default for PV snapshots, for each PV provider | aws:us-east-1,portworx:local
+
+ **NOTE:** the values of these flags should correspond to the names of a `BackupStorageLocation` and `VolumeSnapshotLocation(s)` custom resources
+ in the cluster.
+
+ b. Any non-default Ark server settings:
+
+ Flag | Default Value | Description
+ ---- | ------------- | -----------
+ `--backup-sync-period` | 1m | how often to ensure all Ark backups in object storage exist as Backup API objects in the cluster
+ `--restic-timeout` | 1h | how long backups/restores of pod volumes should be allowed to run before timing out (previously `podVolumeOperationTimeout` in the `Config` resource in pre-v0.10 versions)
+ `--restore-only` | false | run in a mode where only restores are allowed; backups, schedules, and garbage-collection are all disabled
+
+1. If you are using any plugins, update the Ark deployment YAML to reference the latest image tag for your plugins. This can be found under the `initContainers` section of your deployment YAML.
+
+1. Apply your updated Ark deployment YAML to your cluster and ensure the pod(s) starts up successfully.
+
+1. If you're using Ark's restic integration, ensure the daemon set pods have been re-created with the latest Ark image (if your daemon set YAML is using the `:latest` tag, you can delete the pods so they're recreated with an updated image).
+
+1. Once you've confirmed all of your settings have been migrated over correctly, delete the Config CRD:
+ ```bash
+ kubectl delete -n heptio-ark config --all
+ kubectl delete crd configs.ark.heptio.com
+ ```
+
+
+[1]: /api-types/backupstoragelocation.md
+[2]: /api-types/volumesnapshotlocation.md
+[3]: storage-layout-reorg-v0.10.md
+[4]: locations.md
+[5]: get-started.md#download
diff --git a/site/docs/v0.10.0/vendoring-dependencies.md b/site/docs/v0.10.0/vendoring-dependencies.md
new file mode 100644
index 000000000..1729f21ec
--- /dev/null
+++ b/site/docs/v0.10.0/vendoring-dependencies.md
@@ -0,0 +1,18 @@
+# Vendoring dependencies
+
+## Overview
+
+We are using [dep][0] to manage dependencies. You can install it by following [these
+instructions][1].
+
+## Adding a new dependency
+
+Run `dep ensure`. If you want to see verbose output, you can append `-v` as in
+`dep ensure -v`.
+
+## Updating an existing dependency
+
+Run `dep ensure -update [ ...]` to update one or more dependencies.
+
+[0]: https://github.com/golang/dep
+[1]: https://golang.github.io/dep/docs/installation.html
diff --git a/site/docs/v0.10.0/versions.md b/site/docs/v0.10.0/versions.md
new file mode 100644
index 000000000..10eef7b33
--- /dev/null
+++ b/site/docs/v0.10.0/versions.md
@@ -0,0 +1,26 @@
+# Upgrading Ark versions
+
+Ark supports multiple concurrent versions. Whether you're setting up Ark for the first time or upgrading to a new version, you need to pay careful attention to versioning. This doc page is new as of version 0.10.0, and will be updated with information about subsequent releases.
+
+## Minor versions, patch versions
+
+The documentation site provides docs for minor versions only, not for patch releases. Patch releases are guaranteed not to be breaking, but you should carefully read the [release notes][1] to make sure that you understand any relevant changes.
+
+If you're upgrading from a patch version to a patch version, you only need to update the image tags in your configurations. No other steps are needed.
+
+Breaking changes are documented in the release notes and in the documentation.
+
+## Breaking changes for version 0.10.0
+
+- See [Upgrading to version 0.10.0][2]
+
+## Ark versions and Kubernetes versions
+
+Not all Ark versions support all versions of Kubernetes. You should be aware of the following known limitations:
+
+- Ark version 0.9.0 requires Kubernetes version 1.8 or later. In version 0.9.1, Ark was updated to support earlier versions.
+- Restic support requires Kubernetes version 1.10 or later, or an earlier version with the mount propagation feature enabled. See [Restic Integration][3].
+
+[1]: https://github.com/heptio/ark/releases
+[2]: upgrading-to-v0.10.md
+[3]: restic.md
diff --git a/site/docs/v0.10.0/zenhub.md b/site/docs/v0.10.0/zenhub.md
new file mode 100644
index 000000000..e34b7678b
--- /dev/null
+++ b/site/docs/v0.10.0/zenhub.md
@@ -0,0 +1,15 @@
+# ZenHub
+
+As an Open Source community, it is necessary for our work, communication, and collaboration to be done in the open.
+GitHub provides a central repository for code, pull requests, issues, and documentation. When applicable, we will use Google Docs for design reviews, proposals, and other working documents.
+
+While GitHub issues, milestones, and labels generally work pretty well, the Heptio team has found that product planning requires some additional tooling that GitHub projects do not offer.
+
+In our effort to minimize tooling while enabling product management insights, we have decided to use [ZenHub Open-Source](https://www.zenhub.com/blog/open-source/) to overlay product and project tracking on top of GitHub.
+ZenHub is a GitHub application that provides Kanban visualization, Epic tracking, fine-grained prioritization, and more. It's primary backing storage system is existing GitHub issues along with additional metadata stored in ZenHub's database.
+
+If you are an Ark user or Ark Developer, you do not _need_ to use ZenHub for your regular workflow (e.g to see open bug reports or feature requests, work on pull requests). However, if you'd like to be able to visualize the high-level project goals and roadmap, you will need to use the free version of ZenHub.
+
+## Using ZenHub
+
+ZenHub can be integrated within the GitHub interface using their [Chrome or FireFox extensions](https://www.zenhub.com/extension). In addition, you can use their dedicated [web application](https://app.zenhub.com/workspace/o/heptio/ark/boards?filterLogic=all&repos=99143276).
diff --git a/site/docs/v0.11.0/README.md b/site/docs/v0.11.0/README.md
new file mode 100644
index 000000000..b3e758271
--- /dev/null
+++ b/site/docs/v0.11.0/README.md
@@ -0,0 +1,81 @@
+![100]
+
+[![Build Status][1]][2]
+
+## Overview
+
+Velero (formerly Heptio Ark) gives you tools to back up and restore your Kubernetes cluster resources and persistent volumes. Velero lets you:
+
+* Take backups of your cluster and restore in case of loss.
+* Copy cluster resources to other clusters.
+* Replicate your production environment for development and testing environments.
+
+Velero consists of:
+
+* A server that runs on your cluster
+* A command-line client that runs locally
+
+You can run Velero in clusters on a cloud provider or on-premises. For detailed information, see [Compatible Storage Providers][99].
+
+## Installation
+
+We strongly recommend that you use an [official release][6] of Velero. The tarballs for each release contain the
+command-line client **and** version-specific sample YAML files for deploying Velero to your cluster.
+Follow the instructions under the **Install** section of [our documentation][29] to get started.
+
+_The code and sample YAML files in the master branch of the Velero repository are under active development and are not guaranteed to be stable. Use them at your own risk!_
+
+## More information
+
+[The documentation][29] provides a getting started guide, plus information about building from source, architecture, extending Velero, and more.
+
+Please use the version selector at the top of the site to ensure you are using the appropriate documentation for your version of Velero.
+
+## Troubleshooting
+
+If you encounter issues, review the [troubleshooting docs][30], [file an issue][4], or talk to us on the [#velero channel][25] on the Kubernetes Slack server.
+
+## Contributing
+
+Thanks for taking the time to join our community and start contributing!
+
+Feedback and discussion are available on [the mailing list][24].
+
+### Before you start
+
+* Please familiarize yourself with the [Code of Conduct][8] before contributing.
+* See [CONTRIBUTING.md][5] for instructions on the developer certificate of origin that we require.
+* Read how [we're using ZenHub][26] for project and roadmap planning
+
+### Pull requests
+
+* We welcome pull requests. Feel free to dig through the [issues][4] and jump in.
+
+## Changelog
+
+See [the list of releases][6] to find out about feature changes.
+
+[1]: https://travis-ci.org/heptio/velero.svg?branch=master
+[2]: https://travis-ci.org/heptio/velero
+
+[4]: https://github.com/heptio/velero/issues
+[5]: https://github.com/heptio/velero/blob/master/CONTRIBUTING.md
+[6]: https://github.com/heptio/velero/releases
+
+[8]: https://github.com/heptio/velero/blob/master/CODE_OF_CONDUCT.md
+[9]: https://kubernetes.io/docs/setup/
+[10]: https://kubernetes.io/docs/tasks/tools/install-kubectl/#install-with-homebrew-on-macos
+[11]: https://kubernetes.io/docs/tasks/tools/install-kubectl/#tabset-1
+[12]: https://github.com/kubernetes/kubernetes/blob/master/cluster/addons/dns/README.md
+[14]: https://github.com/kubernetes/kubernetes
+
+[24]: https://groups.google.com/forum/#!forum/projectvelero
+[25]: https://kubernetes.slack.com/messages/velero
+[26]: https://github.com/heptio/velero/blob/master/docs/zenhub.md
+
+
+[29]: https://heptio.github.io/velero/
+[30]: /troubleshooting.md
+
+[99]: /support-matrix.md
+[100]: /img/velero.png
diff --git a/site/docs/v0.11.0/about.md b/site/docs/v0.11.0/about.md
new file mode 100644
index 000000000..e7a53b10a
--- /dev/null
+++ b/site/docs/v0.11.0/about.md
@@ -0,0 +1,80 @@
+# How Velero Works
+
+Each Velero operation -- on-demand backup, scheduled backup, restore -- is a custom resource, defined with a Kubernetes [Custom Resource Definition (CRD)][20] and stored in [etcd][22]. Velero also includes controllers that process the custom resources to perform backups, restores, and all related operations.
+
+You can back up or restore all objects in your cluster, or you can filter objects by type, namespace, and/or label.
+
+Velero is ideal for the disaster recovery use case, as well as for snapshotting your application state, prior to performing system operations on your cluster (e.g. upgrades).
+
+## On-demand backups
+
+The **backup** operation:
+
+1. Uploads a tarball of copied Kubernetes objects into cloud object storage.
+
+1. Calls the cloud provider API to make disk snapshots of persistent volumes, if specified.
+
+You can optionally specify hooks to be executed during the backup. For example, you might
+need to tell a database to flush its in-memory buffers to disk before taking a snapshot. [More about hooks][10].
+
+Note that cluster backups are not strictly atomic. If Kubernetes objects are being created or edited at the time of backup, they might not be included in the backup. The odds of capturing inconsistent information are low, but it is possible.
+
+## Scheduled backups
+
+The **schedule** operation allows you to back up your data at recurring intervals. The first backup is performed when the schedule is first created, and subsequent backups happen at the schedule's specified interval. These intervals are specified by a Cron expression.
+
+Scheduled backups are saved with the name `-`, where `` is formatted as *YYYYMMDDhhmmss*.
+
+## Restores
+
+The **restore** operation allows you to restore all of the objects and persistent volumes from a previously created backup. You can also restore only a filtered subset of objects and persistent volumes. Velero supports multiple namespace remapping--for example, in a single restore, objects in namespace "abc" can be recreated under namespace "def", and the objects in namespace "123" under "456".
+
+The default name of a restore is `-`, where `` is formatted as *YYYYMMDDhhmmss*. You can also specify a custom name. A restored object also includes a label with key `velero.io/restore-name` and value ``.
+
+You can also run the Velero server in restore-only mode, which disables backup, schedule, and garbage collection functionality during disaster recovery.
+
+## Backup workflow
+
+When you run `velero backup create test-backup`:
+
+1. The Velero client makes a call to the Kubernetes API server to create a `Backup` object.
+
+1. The `BackupController` notices the new `Backup` object and performs validation.
+
+1. The `BackupController` begins the backup process. It collects the data to back up by querying the API server for resources.
+
+1. The `BackupController` makes a call to the object storage service -- for example, AWS S3 -- to upload the backup file.
+
+By default, `velero backup create` makes disk snapshots of any persistent volumes. You can adjust the snapshots by specifying additional flags. Run `velero backup create --help` to see available flags. Snapshots can be disabled with the option `--snapshot-volumes=false`.
+
+![19]
+
+## Backed-up API versions
+
+Velero backs up resources using the Kubernetes API server's *preferred version* for each group/resource. When restoring a resource, this same API group/version must exist in the target cluster in order for the restore to be successful.
+
+For example, if the cluster being backed up has a `gizmos` resource in the `things` API group, with group/versions `things/v1alpha1`, `things/v1beta1`, and `things/v1`, and the server's preferred group/version is `things/v1`, then all `gizmos` will be backed up from the `things/v1` API endpoint. When backups from this cluster are restored, the target cluster **must** have the `things/v1` endpoint in order for `gizmos` to be restored. Note that `things/v1` **does not** need to be the preferred version in the target cluster; it just needs to exist.
+
+## Set a backup to expire
+
+When you create a backup, you can specify a TTL by adding the flag `--ttl `. If Velero sees that an existing backup resource is expired, it removes:
+
+* The backup resource
+* The backup file from cloud object storage
+* All PersistentVolume snapshots
+* All associated Restores
+
+## Object storage sync
+
+Velero treats object storage as the source of truth. It continuously checks to see that the correct backup resources are always present. If there is a properly formatted backup file in the storage bucket, but no corresponding backup resource in the Kubernetes API, Velero synchronizes the information from object storage to Kubernetes.
+
+This allows restore functionality to work in a cluster migration scenario, where the original backup objects do not exist in the new cluster.
+
+Likewise, if a backup object exists in Kubernetes but not in object storage, it will be deleted from Kubernetes since the backup tarball no longer exists.
+
+[10]: hooks.md
+[19]: /img/backup-process.png
+[20]: https://kubernetes.io/docs/concepts/api-extension/custom-resources/#customresourcedefinitions
+[21]: https://kubernetes.io/docs/concepts/api-extension/custom-resources/#custom-controllers
+[22]: https://github.com/coreos/etcd
+
diff --git a/site/docs/v0.11.0/api-types/README.md b/site/docs/v0.11.0/api-types/README.md
new file mode 100644
index 000000000..a2e14c0db
--- /dev/null
+++ b/site/docs/v0.11.0/api-types/README.md
@@ -0,0 +1,10 @@
+# Table of Contents
+
+## API types
+
+Here we list the API types that have some functionality that you can only configure via json/yaml vs the `velero` cli
+(hooks)
+
+* [Backup][1]
+
+[1]: backup.md
diff --git a/site/docs/v0.11.0/api-types/backup.md b/site/docs/v0.11.0/api-types/backup.md
new file mode 100644
index 000000000..f7dd9fdfc
--- /dev/null
+++ b/site/docs/v0.11.0/api-types/backup.md
@@ -0,0 +1,144 @@
+# Backup API Type
+
+## Use
+
+The `Backup` API type is used as a request for the Velero Server to perform a backup. Once created, the
+Velero Server immediately starts the backup process.
+
+## API GroupVersion
+
+Backup belongs to the API group version `velero.io/v1`.
+
+## Definition
+
+Here is a sample `Backup` object with each of the fields documented:
+
+```yaml
+# Standard Kubernetes API Version declaration. Required.
+apiVersion: velero.io/v1
+# Standard Kubernetes Kind declaration. Required.
+kind: Backup
+# Standard Kubernetes metadata. Required.
+metadata:
+ # Backup name. May be any valid Kubernetes object name. Required.
+ name: a
+ # Backup namespace. Required. In version 0.7.0 and later, can be any string. Must be the namespace of the Velero server.
+ namespace: velero
+# Parameters about the backup. Required.
+spec:
+ # Array of namespaces to include in the backup. If unspecified, all namespaces are included.
+ # Optional.
+ includedNamespaces:
+ - '*'
+ # Array of namespaces to exclude from the backup. Optional.
+ excludedNamespaces:
+ - some-namespace
+ # Array of resources to include in the backup. Resources may be shortcuts (e.g. 'po' for 'pods')
+ # or fully-qualified. If unspecified, all resources are included. Optional.
+ includedResources:
+ - '*'
+ # Array of resources to exclude from the backup. Resources may be shortcuts (e.g. 'po' for 'pods')
+ # or fully-qualified. Optional.
+ excludedResources:
+ - storageclasses.storage.k8s.io
+ # Whether or not to include cluster-scoped resources. Valid values are true, false, and
+ # null/unset. If true, all cluster-scoped resources are included (subject to included/excluded
+ # resources and the label selector). If false, no cluster-scoped resources are included. If unset,
+ # all cluster-scoped resources are included if and only if all namespaces are included and there are
+ # no excluded namespaces. Otherwise, if there is at least one namespace specified in either
+ # includedNamespaces or excludedNamespaces, then the only cluster-scoped resources that are backed
+ # up are those associated with namespace-scoped resources included in the backup. For example, if a
+ # PersistentVolumeClaim is included in the backup, its associated PersistentVolume (which is
+ # cluster-scoped) would also be backed up.
+ includeClusterResources: null
+ # Individual objects must match this label selector to be included in the backup. Optional.
+ labelSelector:
+ matchLabels:
+ app: velero
+ component: server
+ # Whether or not to snapshot volumes. This only applies to PersistentVolumes for Azure, GCE, and
+ # AWS. Valid values are true, false, and null/unset. If unset, Velero performs snapshots as long as
+ # a persistent volume provider is configured for Velero.
+ snapshotVolumes: null
+ # Where to store the tarball and logs.
+ storageLocation: aws-primary
+ # The list of locations in which to store volume snapshots created for this backup.
+ volumeSnapshotLocations:
+ - aws-primary
+ - gcp-primary
+ # The amount of time before this backup is eligible for garbage collection.
+ ttl: 24h0m0s
+ # Actions to perform at different times during a backup. The only hook currently supported is
+ # executing a command in a container in a pod using the pod exec API. Optional.
+ hooks:
+ # Array of hooks that are applicable to specific resources. Optional.
+ resources:
+ -
+ # Name of the hook. Will be displayed in backup log.
+ name: my-hook
+ # Array of namespaces to which this hook applies. If unspecified, the hook applies to all
+ # namespaces. Optional.
+ includedNamespaces:
+ - '*'
+ # Array of namespaces to which this hook does not apply. Optional.
+ excludedNamespaces:
+ - some-namespace
+ # Array of resources to which this hook applies. The only resource supported at this time is
+ # pods.
+ includedResources:
+ - pods
+ # Array of resources to which this hook does not apply. Optional.
+ excludedResources: []
+ # This hook only applies to objects matching this label selector. Optional.
+ labelSelector:
+ matchLabels:
+ app: velero
+ component: server
+ # An array of hooks to run before executing custom actions. Currently only "exec" hooks are supported.
+ # DEPRECATED. Use pre instead.
+ hooks:
+ # Same content as pre below.
+ # An array of hooks to run before executing custom actions. Currently only "exec" hooks are supported.
+ pre:
+ -
+ # The type of hook. This must be "exec".
+ exec:
+ # The name of the container where the command will be executed. If unspecified, the
+ # first container in the pod will be used. Optional.
+ container: my-container
+ # The command to execute, specified as an array. Required.
+ command:
+ - /bin/uname
+ - -a
+ # How to handle an error executing the command. Valid values are Fail and Continue.
+ # Defaults to Fail. Optional.
+ onError: Fail
+ # How long to wait for the command to finish executing. Defaults to 30 seconds. Optional.
+ timeout: 10s
+ # An array of hooks to run after all custom actions and additional items have been
+ # processed. Currently only "exec" hooks are supported.
+ post:
+ # Same content as pre above.
+# Status about the Backup. Users should not set any data here.
+status:
+ # The date and time when the Backup is eligible for garbage collection.
+ expiration: null
+ # The current phase. Valid values are New, FailedValidation, InProgress, Completed, Failed.
+ phase: ""
+ # An array of any validation errors encountered.
+ validationErrors: null
+ # The version of this Backup. The only version currently supported is 1.
+ version: 1
+ # Information about PersistentVolumes needed during restores.
+ volumeBackups:
+ # Each key is the name of a PersistentVolume.
+ some-pv-name:
+ # The ID used by the cloud provider for the snapshot created for this Backup.
+ snapshotID: snap-1234
+ # The type of the volume in the cloud provider API.
+ type: io1
+ # The availability zone where the volume resides in the cloud provider.
+ availabilityZone: my-zone
+ # The amount of provisioned IOPS for the volume. Optional.
+ iops: 10000
+```
diff --git a/site/docs/v0.11.0/api-types/backupstoragelocation.md b/site/docs/v0.11.0/api-types/backupstoragelocation.md
new file mode 100644
index 000000000..c756c8f5b
--- /dev/null
+++ b/site/docs/v0.11.0/api-types/backupstoragelocation.md
@@ -0,0 +1,73 @@
+# Velero Backup Storage Locations
+
+## Backup Storage Location
+
+Velero can store backups in a number of locations. These are represented in the cluster via the `BackupStorageLocation` CRD.
+
+Velero must have at least one `BackupStorageLocation`. By default, this is expected to be named `default`, however the name can be changed by specifying `--default-backup-storage-location` on `velero server`. Backups that do not explicitly specify a storage location will be saved to this `BackupStorageLocation`.
+
+> *NOTE*: `BackupStorageLocation` takes the place of the `Config.backupStorageProvider` key as of v0.10.0
+
+A sample YAML `BackupStorageLocation` looks like the following:
+
+```yaml
+apiVersion: velero.io/v1
+kind: BackupStorageLocation
+metadata:
+ name: default
+ namespace: velero
+spec:
+ provider: aws
+ objectStorage:
+ bucket: myBucket
+ config:
+ region: us-west-2
+```
+
+### Parameter Reference
+
+The configurable parameters are as follows:
+
+#### Main config parameters
+
+| Key | Type | Default | Meaning |
+| --- | --- | --- | --- |
+| `provider` | String (Velero natively supports `aws`, `gcp`, and `azure`. Other providers may be available via external plugins.)| Required Field | The name for whichever cloud provider will be used to actually store the backups. |
+| `objectStorage` | ObjectStorageLocation | Specification of the object storage for the given provider. |
+| `objectStorage/bucket` | String | Required Field | The storage bucket where backups are to be uploaded. |
+| `objectStorage/prefix` | String | Optional Field | The directory inside a storage bucket where backups are to be uploaded. |
+| `config` | map[string]string
(See the corresponding [AWS][0], [GCP][1], and [Azure][2]-specific configs or your provider's documentation.) | None (Optional) | Configuration keys/values to be passed to the cloud provider for backup storage. |
+
+#### AWS
+
+**(Or other S3-compatible storage)**
+
+##### config
+
+| Key | Type | Default | Meaning |
+| --- | --- | --- | --- |
+| `region` | string | Empty | *Example*: "us-east-1"
See [AWS documentation][3] for the full list.
Queried from the AWS S3 API if not provided. |
+| `s3ForcePathStyle` | bool | `false` | Set this to `true` if you are using a local storage service like Minio. |
+| `s3Url` | string | Required field for non-AWS-hosted storage| *Example*: http://minio:9000
You can specify the AWS S3 URL here for explicitness, but Velero can already generate it from `region`, and `bucket`. This field is primarily for local storage services like Minio.|
+| `publicUrl` | string | Empty | *Example*: https://minio.mycluster.com
If specified, use this instead of `s3Url` when generating download URLs (e.g., for logs). This field is primarily for local storage services like Minio.|
+| `kmsKeyId` | string | Empty | *Example*: "502b409c-4da1-419f-a16e-eif453b3i49f" or "alias/``"
Specify an [AWS KMS key][10] id or alias to enable encryption of the backups stored in S3. Only works with AWS S3 and may require explicitly granting key usage rights.|
+| `signatureVersion` | string | `"4"` | Version of the signature algorithm used to create signed URLs that are used by velero cli to download backups or fetch logs. Possible versions are "1" and "4". Usually the default version 4 is correct, but some S3-compatible providers like Quobyte only support version 1.|
+
+#### Azure
+
+##### config
+
+| Key | Type | Default | Meaning |
+| --- | --- | --- | --- |
+| `resourceGroup` | string | Required Field | Name of the resource group containing the storage account for this backup storage location. |
+| `storageAccount` | string | Required Field | Name of the storage account for this backup storage location. |
+
+#### GCP
+
+No parameters required.
+
+[0]: #aws
+[1]: #gcp
+[2]: #azure
+[3]: http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/using-regions-availability-zones.html#concepts-available-regions
+[10]: http://docs.aws.amazon.com/kms/latest/developerguide/overview.html
diff --git a/site/docs/v0.11.0/api-types/volumesnapshotlocation.md b/site/docs/v0.11.0/api-types/volumesnapshotlocation.md
new file mode 100644
index 000000000..734297f3d
--- /dev/null
+++ b/site/docs/v0.11.0/api-types/volumesnapshotlocation.md
@@ -0,0 +1,60 @@
+# Velero Volume Snapshot Location
+
+## Volume Snapshot Location
+
+A volume snapshot location is the location in which to store the volume snapshots created for a backup.
+
+Velero can be configured to take snapshots of volumes from multiple providers. Velero also allows you to configure multiple possible `VolumeSnapshotLocation` per provider, although you can only select one location per provider at backup time.
+
+Each VolumeSnapshotLocation describes a provider + location. These are represented in the cluster via the `VolumeSnapshotLocation` CRD. Velero must have at least one `VolumeSnapshotLocation` per cloud provider.
+
+A sample YAML `VolumeSnapshotLocation` looks like the following:
+
+```yaml
+apiVersion: velero.io/v1
+kind: VolumeSnapshotLocation
+metadata:
+ name: aws-default
+ namespace: velero
+spec:
+ provider: aws
+ config:
+ region: us-west-2
+```
+
+### Parameter Reference
+
+The configurable parameters are as follows:
+
+#### Main config parameters
+
+| Key | Type | Default | Meaning |
+| --- | --- | --- | --- |
+| `provider` | String (Velero natively supports `aws`, `gcp`, and `azure`. Other providers may be available via external plugins.)| Required Field | The name for whichever cloud provider will be used to actually store the volume. |
+| `config` | See the corresponding [AWS][0], [GCP][1], and [Azure][2]-specific configs or your provider's documentation.
+
+#### AWS
+
+##### config
+
+| Key | Type | Default | Meaning |
+| --- | --- | --- | --- |
+| `region` | string | Empty | *Example*: "us-east-1"
See [AWS documentation][3] for the full list.
Queried from the AWS S3 API if not provided. |
+
+#### Azure
+
+##### config
+
+| Key | Type | Default | Meaning |
+| --- | --- | --- | --- |
+| `apiTimeout` | metav1.Duration | 2m0s | How long to wait for an Azure API request to complete before timeout. |
+| `resourceGroup` | string | Optional | The name of the resource group where volume snapshots should be stored, if different from the cluster's resource group. |
+
+#### GCP
+
+No parameters required.
+
+[0]: #aws
+[1]: #gcp
+[2]: #azure
+[3]: http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/using-regions-availability-zones.html#concepts-available-regions
diff --git a/site/docs/v0.11.0/aws-config.md b/site/docs/v0.11.0/aws-config.md
new file mode 100644
index 000000000..bcb74a64a
--- /dev/null
+++ b/site/docs/v0.11.0/aws-config.md
@@ -0,0 +1,328 @@
+# Run Velero on AWS
+
+To set up Velero on AWS, you:
+
+* Download an official release of Velero
+* Create your S3 bucket
+* Create an AWS IAM user for Velero
+* Configure the server
+* Create a Secret for your credentials
+
+If you do not have the `aws` CLI locally installed, follow the [user guide][5] to set it up.
+
+## Download Velero
+
+1. Download the [latest release's](https://github.com/heptio/velero/releases) tarball for your client platform.
+
+1. Extract the tarball:
+ ```bash
+ tar -xvf .tar.gz -C /dir/to/extract/to
+ ```
+ We'll refer to the directory you extracted to as the "Velero directory" in subsequent steps.
+
+1. Move the `velero` binary from the Velero directory to somewhere in your PATH.
+
+_We strongly recommend that you use an [official release](https://github.com/heptio/velero/releases) of Velero. The tarballs for each release contain the
+`velero` command-line client **and** version-specific sample YAML files for deploying Velero to your cluster. The code and sample YAML files in the master
+branch of the Velero repository are under active development and are not guaranteed to be stable. Use them at your own risk!_
+
+## Create S3 bucket
+
+Velero requires an object storage bucket to store backups in, preferrably unique to a single Kubernetes cluster (see the [FAQ][20] for more details). Create an S3 bucket, replacing placeholders appropriately:
+
+```bash
+aws s3api create-bucket \
+ --bucket \
+ --region \
+ --create-bucket-configuration LocationConstraint=
+```
+NOTE: us-east-1 does not support a `LocationConstraint`. If your region is `us-east-1`, omit the bucket configuration:
+
+```bash
+aws s3api create-bucket \
+ --bucket \
+ --region us-east-1
+```
+
+## Create IAM user
+
+For more information, see [the AWS documentation on IAM users][14].
+
+1. Create the IAM user:
+
+ ```bash
+ aws iam create-user --user-name velero
+ ```
+
+ > If you'll be using Velero to backup multiple clusters with multiple S3 buckets, it may be desirable to create a unique username per cluster rather than the default `velero`.
+
+2. Attach policies to give `velero` the necessary permissions:
+
+ ```bash
+ BUCKET=
+ cat > velero-policy.json <,
+ "AccessKeyId":
+ }
+ }
+ ```
+
+4. Create a Velero-specific credentials file (`credentials-velero`) in your local directory:
+
+ ```
+ [default]
+ aws_access_key_id=
+ aws_secret_access_key=
+ ```
+
+ where the access key id and secret are the values returned from the `create-access-key` request.
+
+## Credentials and configuration
+
+In the Velero directory (i.e. where you extracted the release tarball), run the following to first set up namespaces, RBAC, and other scaffolding. To run in a custom namespace, make sure that you have edited the YAML files to specify the namespace. See [Run in custom namespace][0].
+
+```bash
+kubectl apply -f config/common/00-prereqs.yaml
+```
+
+Create a Secret. In the directory of the credentials file you just created, run:
+
+```bash
+kubectl create secret generic cloud-credentials \
+ --namespace \
+ --from-file cloud=credentials-velero
+```
+
+Specify the following values in the example files:
+
+* In `config/aws/05-backupstoragelocation.yaml`:
+
+ * Replace `` and `` (for S3 backup storage, region is optional and will be queried from the AWS S3 API if not provided). See the [BackupStorageLocation definition][21] for details.
+
+* In `config/aws/06-volumesnapshotlocation.yaml`:
+
+ * Replace ``. See the [VolumeSnapshotLocation definition][6] for details.
+
+* (Optional, use only to specify multiple volume snapshot locations) In `config/aws/10-deployment.yaml` (or `config/aws/10-deployment-kube2iam.yaml`, as appropriate):
+
+ * Uncomment the `--default-volume-snapshot-locations` and replace provider locations with the values for your environment.
+
+* (Optional) If you run the nginx example, in file `config/nginx-app/with-pv.yaml`:
+
+ * Replace `` with `gp2`. This is AWS's default `StorageClass` name.
+
+* (Optional) If you have multiple clusters and you want to support migration of resources between them, in file `config/aws/10-deployment.yaml`:
+
+ * Uncomment the environment variable `AWS_CLUSTER_NAME` and replace `` with the current cluster's name. When restoring backup, it will make Velero (and cluster it's running on) claim ownership of AWS volumes created from snapshots taken on different cluster.
+ The best way to get the current cluster's name is to either check it with used deployment tool or to read it directly from the EC2 instances tags.
+
+ The following listing shows how to get the cluster's nodes EC2 Tags. First, get the nodes external IDs (EC2 IDs):
+
+ ```bash
+ kubectl get nodes -o jsonpath='{.items[*].spec.externalID}'
+ ```
+
+ Copy one of the returned IDs `` and use it with the `aws` CLI tool to search for one of the following:
+
+ * The `kubernetes.io/cluster/` tag of the value `owned`. The `` is then your cluster's name:
+
+ ```bash
+ aws ec2 describe-tags --filters "Name=resource-id,Values=" "Name=value,Values=owned"
+ ```
+
+ * If the first output returns nothing, then check for the legacy Tag `KubernetesCluster` of the value ``:
+
+ ```bash
+ aws ec2 describe-tags --filters "Name=resource-id,Values=" "Name=key,Values=KubernetesCluster"
+ ```
+
+## Start the server
+
+In the root of your Velero directory, run:
+
+ ```bash
+ kubectl apply -f config/aws/05-backupstoragelocation.yaml
+ kubectl apply -f config/aws/06-volumesnapshotlocation.yaml
+ kubectl apply -f config/aws/10-deployment.yaml
+ ```
+
+## ALTERNATIVE: Setup permissions using kube2iam
+
+[Kube2iam](https://github.com/jtblin/kube2iam) is a Kubernetes application that allows managing AWS IAM permissions for pod via annotations rather than operating on API keys.
+
+> This path assumes you have `kube2iam` already running in your Kubernetes cluster. If that is not the case, please install it first, following the docs here: [https://github.com/jtblin/kube2iam](https://github.com/jtblin/kube2iam)
+
+It can be set up for Velero by creating a role that will have required permissions, and later by adding the permissions annotation on the velero deployment to define which role it should use internally.
+
+1. Create a Trust Policy document to allow the role being used for EC2 management & assume kube2iam role:
+
+ ```bash
+ cat > velero-trust-policy.json <:role/"
+ },
+ "Action": "sts:AssumeRole"
+ }
+ ]
+ }
+ EOF
+ ```
+
+2. Create the IAM role:
+
+ ```bash
+ aws iam create-role --role-name velero --assume-role-policy-document file://./velero-trust-policy.json
+ ```
+
+3. Attach policies to give `velero` the necessary permissions:
+
+ ```bash
+ BUCKET=
+ cat > velero-policy.json <:role/
+ ...
+ ```
+
+5. Run Velero deployment using the file `config/aws/10-deployment-kube2iam.yaml`.
+
+[0]: namespace.md
+[5]: https://docs.aws.amazon.com/cli/latest/userguide/cli-chap-welcome.html
+[6]: api-types/volumesnapshotlocation.md#aws
+[14]: http://docs.aws.amazon.com/IAM/latest/UserGuide/introduction.html
+[20]: faq.md
+[21]: api-types/backupstoragelocation.md#aws
diff --git a/site/docs/v0.11.0/azure-config.md b/site/docs/v0.11.0/azure-config.md
new file mode 100644
index 000000000..38c2edbf6
--- /dev/null
+++ b/site/docs/v0.11.0/azure-config.md
@@ -0,0 +1,172 @@
+# Run Velero on Azure
+
+To configure Velero on Azure, you:
+
+* Download an official release of Velero
+* Create your Azure storage account and blob container
+* Create Azure service principal for Velero
+* Configure the server
+* Create a Secret for your credentials
+
+If you do not have the `az` Azure CLI 2.0 installed locally, follow the [install guide][18] to set it up.
+
+Run:
+
+```bash
+az login
+```
+
+## Kubernetes cluster prerequisites
+
+Ensure that the VMs for your agent pool allow Managed Disks. If I/O performance is critical,
+consider using Premium Managed Disks, which are SSD backed.
+
+## Download Velero
+
+1. Download the [latest release's](https://github.com/heptio/velero/releases) tarball for your client platform.
+
+1. Extract the tarball:
+ ```bash
+ tar -xvf .tar.gz -C /dir/to/extract/to
+ ```
+ We'll refer to the directory you extracted to as the "Velero directory" in subsequent steps.
+
+1. Move the `velero` binary from the Velero directory to somewhere in your PATH.
+
+_We strongly recommend that you use an [official release](https://github.com/heptio/velero/releases) of Velero. The tarballs for each release contain the
+`velero` command-line client **and** version-specific sample YAML files for deploying Velero to your cluster. The code and sample YAML files in the master
+branch of the Velero repository are under active development and are not guaranteed to be stable. Use them at your own risk!_
+
+## Create Azure storage account and blob container
+
+Velero requires a storage account and blob container in which to store backups.
+
+The storage account can be created in the same Resource Group as your Kubernetes cluster or
+separated into its own Resource Group. The example below shows the storage account created in a
+separate `Velero_Backups` Resource Group.
+
+The storage account needs to be created with a globally unique id since this is used for dns. In
+the sample script below, we're generating a random name using `uuidgen`, but you can come up with
+this name however you'd like, following the [Azure naming rules for storage accounts][19]. The
+storage account is created with encryption at rest capabilities (Microsoft managed keys) and is
+configured to only allow access via https.
+
+```bash
+# Create a resource group for the backups storage account. Change the location as needed.
+AZURE_BACKUP_RESOURCE_GROUP=Velero_Backups
+az group create -n $AZURE_BACKUP_RESOURCE_GROUP --location WestUS
+
+# Create the storage account
+AZURE_STORAGE_ACCOUNT_ID="velero$(uuidgen | cut -d '-' -f5 | tr '[A-Z]' '[a-z]')"
+az storage account create \
+ --name $AZURE_STORAGE_ACCOUNT_ID \
+ --resource-group $AZURE_BACKUP_RESOURCE_GROUP \
+ --sku Standard_GRS \
+ --encryption-services blob \
+ --https-only true \
+ --kind BlobStorage \
+ --access-tier Hot
+```
+
+Create the blob container named `velero`. Feel free to use a different name, preferably unique to a single Kubernetes cluster. See the [FAQ][20] for more details.
+
+```bash
+az storage container create -n velero --public-access off --account-name $AZURE_STORAGE_ACCOUNT_ID
+```
+
+## Get resource group for persistent volume snapshots
+
+1. Set the name of the Resource Group that contains your Kubernetes cluster's virtual machines/disks.
+
+ > **WARNING**: If you're using [AKS][22], `AZURE_RESOURCE_GROUP` must be set to the name of the auto-generated resource group that is created
+ when you provision your cluster in Azure, since this is the resource group that contains your cluster's virtual machines/disks.
+
+ ```bash
+ AZURE_RESOURCE_GROUP=
+ ```
+
+ If you are unsure of the Resource Group name, run the following command to get a list that you can select from. Then set the `AZURE_RESOURCE_GROUP` environment variable to the appropriate value.
+
+ ```bash
+ az group list --query '[].{ ResourceGroup: name, Location:location }'
+ ```
+
+ Get your cluster's Resource Group name from the `ResourceGroup` value in the response, and use it to set `$AZURE_RESOURCE_GROUP`.
+
+## Create service principal
+
+To integrate Velero with Azure, you must create an Velero-specific [service principal][17].
+
+1. Obtain your Azure Account Subscription ID and Tenant ID:
+
+ ```bash
+ AZURE_SUBSCRIPTION_ID=`az account list --query '[?isDefault].id' -o tsv`
+ AZURE_TENANT_ID=`az account list --query '[?isDefault].tenantId' -o tsv`
+ ```
+
+1. Create a service principal with `Contributor` role. This will have subscription-wide access, so protect this credential. You can specify a password or let the `az ad sp create-for-rbac` command create one for you.
+
+ > If you'll be using Velero to backup multiple clusters with multiple blob containers, it may be desirable to create a unique username per cluster rather than the default `velero`.
+
+ ```bash
+ # Create service principal and specify your own password
+ AZURE_CLIENT_SECRET=super_secret_and_high_entropy_password_replace_me_with_your_own
+ az ad sp create-for-rbac --name "velero" --role "Contributor" --password $AZURE_CLIENT_SECRET
+
+ # Or create service principal and let the CLI generate a password for you. Make sure to capture the password.
+ AZURE_CLIENT_SECRET=`az ad sp create-for-rbac --name "velero" --role "Contributor" --query 'password' -o tsv`
+
+ # After creating the service principal, obtain the client id
+ AZURE_CLIENT_ID=`az ad sp list --display-name "velero" --query '[0].appId' -o tsv`
+ ```
+
+## Credentials and configuration
+
+In the Velero directory (i.e. where you extracted the release tarball), run the following to first set up namespaces, RBAC, and other scaffolding. To run in a custom namespace, make sure that you have edited the YAML file to specify the namespace. See [Run in custom namespace][0].
+
+```bash
+kubectl apply -f config/common/00-prereqs.yaml
+```
+
+Now you need to create a Secret that contains all the environment variables you just set. The command looks like the following:
+
+```bash
+kubectl create secret generic cloud-credentials \
+ --namespace \
+ --from-literal AZURE_SUBSCRIPTION_ID=${AZURE_SUBSCRIPTION_ID} \
+ --from-literal AZURE_TENANT_ID=${AZURE_TENANT_ID} \
+ --from-literal AZURE_CLIENT_ID=${AZURE_CLIENT_ID} \
+ --from-literal AZURE_CLIENT_SECRET=${AZURE_CLIENT_SECRET} \
+ --from-literal AZURE_RESOURCE_GROUP=${AZURE_RESOURCE_GROUP}
+```
+
+Now that you have your Azure credentials stored in a Secret, you need to replace some placeholder values in the template files. Specifically, you need to change the following:
+
+* In file `config/azure/05-backupstoragelocation.yaml`:
+
+ * Replace ``, ``, and ``. See the [BackupStorageLocation definition][21] for details.
+
+* In file `config/azure/06-volumesnapshotlocation.yaml`:
+
+ * Replace ``. See the [VolumeSnapshotLocation definition][8] for details.
+
+* (Optional, use only if you need to specify multiple volume snapshot locations) In `config/azure/00-deployment.yaml`:
+
+ * Uncomment the `--default-volume-snapshot-locations` and replace provider locations with the values for your environment.
+
+## Start the server
+
+In the root of your Velero directory, run:
+
+ ```bash
+ kubectl apply -f config/azure/
+ ```
+
+[0]: namespace.md
+[8]: api-types/volumesnapshotlocation.md#azure
+[17]: https://docs.microsoft.com/en-us/azure/active-directory/develop/active-directory-application-objects
+[18]: https://docs.microsoft.com/en-us/cli/azure/install-azure-cli
+[19]: https://docs.microsoft.com/en-us/azure/architecture/best-practices/naming-conventions#storage
+[20]: faq.md
+[21]: api-types/backupstoragelocation.md#azure
+[22]: https://azure.microsoft.com/en-us/services/kubernetes-service/
diff --git a/site/docs/v0.11.0/build-from-scratch.md b/site/docs/v0.11.0/build-from-scratch.md
new file mode 100644
index 000000000..ce89992b1
--- /dev/null
+++ b/site/docs/v0.11.0/build-from-scratch.md
@@ -0,0 +1,237 @@
+# Build from source
+
+* [Prerequisites][1]
+* [Getting the source][2]
+* [Build][3]
+* [Test][12]
+* [Run][7]
+* [Vendoring dependencies][10]
+
+## Prerequisites
+
+* Access to a Kubernetes cluster, version 1.7 or later. Version 1.7.5 or later is required to run `velero backup delete`.
+* A DNS server on the cluster
+* `kubectl` installed
+* [Go][5] installed (minimum version 1.8)
+
+## Getting the source
+
+### Option 1) Get latest (recommended)
+
+```bash
+mkdir $HOME/go
+export GOPATH=$HOME/go
+go get github.com/heptio/velero
+```
+
+Where `go` is your [import path][4] for Go.
+
+For Go development, it is recommended to add the Go import path (`$HOME/go` in this example) to your path.
+
+### Option 2) Release archive
+Download the archive named `Source code` from the [release page][22] and extract it in your Go import path as `src/github.com/heptio/velero`.
+
+Note that the Makefile targets assume building from a git repository. When building from an archive, you will be limited to the `go build` commands described below.
+
+## Build
+
+You can build your Velero image locally on the machine where you run your cluster, or you can push it to a private registry. This section covers both workflows.
+
+Set the `$REGISTRY` environment variable (used in the `Makefile`) to push the Velero images to your own registry. This allows any node in your cluster to pull your locally built image.
+
+In the Velero root directory, to build your container with the tag `$REGISTRY/velero:$VERSION`, run:
+
+```
+make container
+```
+
+To push your image to a registry, use `make push`.
+
+To build only the `velero` binary, run:
+```
+go build ./cmd/velero
+```
+
+### Update generated files
+
+The following files are automatically generated from the source code:
+
+* The clientset
+* Listers
+* Shared informers
+* Documentation
+* Protobuf/gRPC types
+
+Run `make update` to regenerate files if you make the following changes:
+
+* Add/edit/remove command line flags and/or their help text
+* Add/edit/remove commands or subcommands
+* Add new API types
+
+Run [generate-proto.sh][13] to regenerate files if you make the following changes:
+
+* Add/edit/remove protobuf message or service definitions. These changes require the [proto compiler][14] and compiler plugin `protoc-gen-go` version v1.0.0.
+
+### Cross compiling
+
+By default, `make build` builds an `velero` binary for `linux-amd64`.
+To build for another platform, run `make build--`.
+For example, to build for the Mac, run `make build-darwin-amd64`.
+All binaries are placed in `_output/bin//`-- for example, `_output/bin/darwin/amd64/velero`.
+
+Velero's `Makefile` has a convenience target, `all-build`, that builds the following platforms:
+
+* linux-amd64
+* linux-arm
+* linux-arm64
+* darwin-amd64
+* windows-amd64
+
+## 3. Test
+
+To run unit tests, use `make test`. You can also run `make verify` to ensure that all generated
+files (clientset, listers, shared informers, docs) are up to date.
+
+## 4. Run
+
+### Prerequisites
+
+When running Velero, you will need to account for the following (all of which are handled in the [`/examples`][6] manifests):
+
+* Appropriate RBAC permissions in the cluster
+ * Read access for all data from the source cluster and namespaces
+ * Write access to the target cluster and namespaces
+* Cloud provider credentials
+ * Read/write access to volumes
+ * Read/write access to object storage for backup data
+* A [BackupStorageLocation][20] object definition for the Velero server
+* (Optional) A [VolumeSnapshotLocation][21] object definition for the Velero server, to take PV snapshots
+
+### Create a cluster
+
+To provision a cluster on AWS using Amazon’s official CloudFormation templates, here are two options:
+
+* EC2 [Quick Start for Kubernetes][17]
+
+* eksctl - [a CLI for Amazon EKS][18]
+
+### Option 1: Run your Velero server locally
+
+Running the Velero server locally can speed up iterative development. This eliminates the need to rebuild the Velero server
+image and redeploy it to the cluster with each change.
+
+#### 1. Set enviroment variables
+
+Set the appropriate environment variable for your cloud provider:
+
+AWS: [AWS_SHARED_CREDENTIALS_FILE][15]
+
+GCP: [GOOGLE_APPLICATION_CREDENTIALS][16]
+
+Azure:
+
+ 1. AZURE_CLIENT_ID
+
+ 2. AZURE_CLIENT_SECRET
+
+ 3. AZURE_SUBSCRIPTION_ID
+
+ 4. AZURE_TENANT_ID
+
+ 5. AZURE_STORAGE_ACCOUNT_ID
+
+ 6. AZURE_STORAGE_KEY
+
+ 7. AZURE_RESOURCE_GROUP
+
+#### 2. Create resources in a cluster
+
+You may create resources on a cluster using our [example configurations][19].
+
+##### Example
+
+Here is how to setup using an existing cluster in AWS: At the root of the Velero repo:
+
+- Edit `examples/aws/05-backupstoragelocation.yaml` to point to your AWS S3 bucket and region. Note: you can run `aws s3api list-buckets` to get the name of all your buckets.
+
+- (Optional) Edit `examples/aws/06-volumesnapshotlocation.yaml` to point to your AWS region.
+
+Then run the commands below.
+
+`00-prereqs.yaml` contains all our CustomResourceDefinitions (CRDs) that allow us to perform CRUD operations on backups, restores, schedules, etc. it also contains the `velero` namespace, the `velero` ServiceAccount, and a cluster role binding to grant the `velero` ServiceAccount the cluster-admin role:
+
+```bash
+kubectl apply -f examples/common/00-prereqs.yaml
+```
+
+`10-deployment.yaml` is a sample Velero config resource for AWS:
+
+```bash
+kubectl apply -f examples/aws/10-deployment.yaml
+```
+
+And `05-backupstoragelocation.yaml` specifies the location of your backup storage, together with the optional `06-volumesnapshotlocation.yaml`:
+
+```bash
+kubectl apply -f examples/aws/05-backupstoragelocation.yaml
+```
+
+or
+
+```bash
+kubectl apply -f examples/aws/05-backupstoragelocation.yaml examples/aws/06-volumesnapshotlocation.yaml
+```
+
+### 3. Start the Velero server
+
+* Make sure `velero` is in your `PATH` or specify the full path.
+
+* Set variable for Velero as needed. The variables below can be exported as environment variables or passed as CLI cmd flags:
+ * `--kubeconfig`: set the path to the kubeconfig file the Velero server uses to talk to the Kubernetes apiserver
+ * `--namespace`: the set namespace where the Velero server should look for backups, schedules, restores
+ * `--log-level`: set the Velero server's log level
+ * `--plugin-dir`: set the directory where the Velero server looks for plugins
+ * `--metrics-address`: set the bind address and port where Prometheus metrics are exposed
+
+* Start the server: `velero server`
+
+### Option 2: Run your Velero server in a deployment
+
+1. Install Velero using a deployment:
+
+We have examples of deployments for different cloud providers in `examples//10-deployment.yaml`.
+
+2. Replace the deployment's default Velero image with the image that you built. Run:
+
+```
+kubectl --namespace=velero set image deployment/velero velero=$REGISTRY/velero:$VERSION
+```
+
+where `$REGISTRY` and `$VERSION` are the values that you built Velero with.
+
+## 5. Vendoring dependencies
+
+If you need to add or update the vendored dependencies, see [Vendoring dependencies][11].
+
+[0]: ../README.md
+[1]: #prerequisites
+[2]: #getting-the-source
+[3]: #build
+[4]: https://blog.golang.org/organizing-go-code
+[5]: https://golang.org/doc/install
+[6]: https://github.com/heptio/velero/tree/master/examples
+[7]: #run
+[8]: config-definition.md
+[10]: #vendoring-dependencies
+[11]: vendoring-dependencies.md
+[12]: #test
+[13]: https://github.com/heptio/velero/blob/master/hack/generate-proto.sh
+[14]: https://grpc.io/docs/quickstart/go.html#install-protocol-buffers-v3
+[15]: https://docs.aws.amazon.com/cli/latest/topic/config-vars.html#the-shared-credentials-file
+[16]: https://cloud.google.com/docs/authentication/getting-started#setting_the_environment_variable
+[17]: https://aws.amazon.com/quickstart/architecture/heptio-kubernetes/
+[18]: https://eksctl.io/
+[19]: ../examples/README.md
+[20]: api-types/backupstoragelocation.md
+[21]: api-types/volumesnapshotlocation.md
+[22]: https://github.com/heptio/velero/releases
diff --git a/site/docs/v0.11.0/debugging-install.md b/site/docs/v0.11.0/debugging-install.md
new file mode 100644
index 000000000..aaf25986d
--- /dev/null
+++ b/site/docs/v0.11.0/debugging-install.md
@@ -0,0 +1,66 @@
+# Debugging Installation Issues
+
+## General
+
+### `invalid configuration: no configuration has been provided`
+This typically means that no `kubeconfig` file can be found for the Velero client to use. Velero looks for a kubeconfig in the
+following locations:
+* the path specified by the `--kubeconfig` flag, if any
+* the path specified by the `$KUBECONFIG` environment variable, if any
+* `~/.kube/config`
+
+### Backups or restores stuck in `New` phase
+This means that the Velero controllers are not processing the backups/restores, which usually happens because the Velero server is not running. Check the pod description and logs for errors:
+```
+kubectl -n velero describe pods
+kubectl -n velero logs deployment/velero
+```
+
+
+## AWS
+
+### `NoCredentialProviders: no valid providers in chain`
+
+#### Using credentials
+This means that the secret containing the AWS IAM user credentials for Velero has not been created/mounted properly
+into the Velero server pod. Ensure the following:
+* The `cloud-credentials` secret exists in the Velero server's namespace
+* The `cloud-credentials` secret has a single key, `cloud`, whose value is the contents of the `credentials-velero` file
+* The `credentials-velero` file is formatted properly and has the correct values:
+
+ ```
+ [default]
+ aws_access_key_id=
+ aws_secret_access_key=
+ ```
+* The `cloud-credentials` secret is defined as a volume for the Velero deployment
+* The `cloud-credentials` secret is being mounted into the Velero server pod at `/credentials`
+
+#### Using kube2iam
+This means that Ark can't read the content of the S3 bucket. Ensure the following:
+* There is a Trust Policy document allowing the role used by kube2iam to assume Ark's role, as stated in the AWS config documentation.
+* The new Ark role has all the permissions listed in the documentation regarding S3.
+
+
+## Azure
+
+### `Failed to refresh the Token` or `adal: Refresh request failed`
+This means that the secrets containing the Azure service principal credentials for Velero has not been created/mounted
+properly into the Velero server pod. Ensure the following:
+* The `cloud-credentials` secret exists in the Velero server's namespace
+* The `cloud-credentials` secret has all of the expected keys and each one has the correct value (see [setup instructions](0))
+* The `cloud-credentials` secret is defined as a volume for the Velero deployment
+* The `cloud-credentials` secret is being mounted into the Velero server pod at `/credentials`
+
+
+## GCE/GKE
+
+### `open credentials/cloud: no such file or directory`
+This means that the secret containing the GCE service account credentials for Velero has not been created/mounted properly
+into the Velero server pod. Ensure the following:
+* The `cloud-credentials` secret exists in the Velero server's namespace
+* The `cloud-credentials` secret has a single key, `cloud`, whose value is the contents of the `credentials-velero` file
+* The `cloud-credentials` secret is defined as a volume for the Velero deployment
+* The `cloud-credentials` secret is being mounted into the Velero server pod at `/credentials`
+
+[0]: azure-config#credentials-and-configuration
diff --git a/site/docs/v0.11.0/debugging-restores.md b/site/docs/v0.11.0/debugging-restores.md
new file mode 100644
index 000000000..7ff6153be
--- /dev/null
+++ b/site/docs/v0.11.0/debugging-restores.md
@@ -0,0 +1,103 @@
+# Debugging Restores
+
+* [Example][0]
+* [Structure][1]
+
+## Example
+
+When Velero finishes a Restore, its status changes to "Completed" regardless of whether or not there are issues during the process. The number of warnings and errors are indicated in the output columns from `velero restore get`:
+
+```
+NAME BACKUP STATUS WARNINGS ERRORS CREATED SELECTOR
+backup-test-20170726180512 backup-test Completed 155 76 2017-07-26 11:41:14 -0400 EDT
+backup-test-20170726180513 backup-test Completed 121 14 2017-07-26 11:48:24 -0400 EDT
+backup-test-2-20170726180514 backup-test-2 Completed 0 0 2017-07-26 13:31:21 -0400 EDT
+backup-test-2-20170726180515 backup-test-2 Completed 0 1 2017-07-26 13:32:59 -0400 EDT
+```
+
+To delve into the warnings and errors into more detail, you can use `velero restore describe`:
+```
+velero restore describe backup-test-20170726180512
+```
+The output looks like this:
+```
+Name: backup-test-20170726180512
+Namespace: velero
+Labels:
+Annotations:
+
+Backup: backup-test
+
+Namespaces:
+ Included: *
+ Excluded:
+
+Resources:
+ Included: serviceaccounts
+ Excluded: nodes, events, events.events.k8s.io
+ Cluster-scoped: auto
+
+Namespace mappings:
+
+Label selector:
+
+Restore PVs: auto
+
+Phase: Completed
+
+Validation errors:
+
+Warnings:
+ Velero:
+ Cluster:
+ Namespaces:
+ velero: serviceaccounts "velero" already exists
+ serviceaccounts "default" already exists
+ kube-public: serviceaccounts "default" already exists
+ kube-system: serviceaccounts "attachdetach-controller" already exists
+ serviceaccounts "certificate-controller" already exists
+ serviceaccounts "cronjob-controller" already exists
+ serviceaccounts "daemon-set-controller" already exists
+ serviceaccounts "default" already exists
+ serviceaccounts "deployment-controller" already exists
+ serviceaccounts "disruption-controller" already exists
+ serviceaccounts "endpoint-controller" already exists
+ serviceaccounts "generic-garbage-collector" already exists
+ serviceaccounts "horizontal-pod-autoscaler" already exists
+ serviceaccounts "job-controller" already exists
+ serviceaccounts "kube-dns" already exists
+ serviceaccounts "namespace-controller" already exists
+ serviceaccounts "node-controller" already exists
+ serviceaccounts "persistent-volume-binder" already exists
+ serviceaccounts "pod-garbage-collector" already exists
+ serviceaccounts "replicaset-controller" already exists
+ serviceaccounts "replication-controller" already exists
+ serviceaccounts "resourcequota-controller" already exists
+ serviceaccounts "service-account-controller" already exists
+ serviceaccounts "service-controller" already exists
+ serviceaccounts "statefulset-controller" already exists
+ serviceaccounts "ttl-controller" already exists
+ default: serviceaccounts "default" already exists
+
+Errors:
+ Velero:
+ Cluster:
+ Namespaces:
+```
+
+## Structure
+
+Errors appear for incomplete or partial restores. Warnings appear for non-blocking issues (e.g. the
+restore looks "normal" and all resources referenced in the backup exist in some form, although some
+of them may have been pre-existing).
+
+Both errors and warnings are structured in the same way:
+
+* `Velero`: A list of system-related issues encountered by the Velero server (e.g. couldn't read directory).
+
+* `Cluster`: A list of issues related to the restore of cluster-scoped resources.
+
+* `Namespaces`: A map of namespaces to the list of issues related to the restore of their respective resources.
+
+[0]: #example
+[1]: #structure
diff --git a/site/docs/v0.11.0/disaster-case.md b/site/docs/v0.11.0/disaster-case.md
new file mode 100644
index 000000000..595811908
--- /dev/null
+++ b/site/docs/v0.11.0/disaster-case.md
@@ -0,0 +1,24 @@
+# Disaster recovery
+
+*Using Schedules and Restore-Only Mode*
+
+If you periodically back up your cluster's resources, you are able to return to a previous state in case of some unexpected mishap, such as a service outage. Doing so with Velero looks like the following:
+
+1. After you first run the Velero server on your cluster, set up a daily backup (replacing `` in the command as desired):
+
+ ```
+ velero schedule create --schedule "0 7 * * *"
+ ```
+ This creates a Backup object with the name `-`.
+
+1. A disaster happens and you need to recreate your resources.
+
+1. Update the Velero server deployment, adding the argument for the `server` command flag `restore-only` set to `true`. This prevents Backup objects from being created or deleted during your Restore process.
+
+1. Create a restore with your most recent Velero Backup:
+ ```
+ velero restore create --from-backup -
+ ```
+
+
+
diff --git a/site/docs/v0.11.0/expose-minio.md b/site/docs/v0.11.0/expose-minio.md
new file mode 100644
index 000000000..236d03809
--- /dev/null
+++ b/site/docs/v0.11.0/expose-minio.md
@@ -0,0 +1,50 @@
+# Expose Minio outside your cluster
+
+When you run commands to get logs or describe a backup, the Velero server generates a pre-signed URL to download the requested items. To access these URLs from outside the cluster -- that is, from your Velero client -- you need to make Minio available outside the cluster. You can:
+
+- Change the Minio Service type from `ClusterIP` to `NodePort`.
+- Set up Ingress for your cluster, keeping Minio Service type `ClusterIP`.
+
+In Velero 0.10, you can also specify the value of a new `publicUrl` field for the pre-signed URL in your backup storage config.
+
+For basic instructions on how to install the Velero server and client, see [the getting started example][1].
+
+## Expose Minio with Service of type NodePort
+
+The Minio deployment by default specifies a Service of type `ClusterIP`. You can change this to `NodePort` to easily expose a cluster service externally if you can reach the node from your Velero client.
+
+You must also get the Minio URL, which you can then specify as the value of the new `publicUrl` field in your backup storage config.
+
+1. In `examples/minio/00-minio-deployment.yaml`, change the value of Service `spec.type` from `ClusterIP` to `NodePort`.
+
+1. Get the Minio URL:
+
+ - if you're running Minikube:
+
+ ```shell
+ minikube service minio --namespace=velero --url
+ ```
+
+ - in any other environment:
+
+ 1. Get the value of an external IP address or DNS name of any node in your cluster. You must be able to reach this address from the Velero client.
+
+ 1. Append the value of the NodePort to get a complete URL. You can get this value by running:
+
+ ```shell
+ kubectl -n velero get svc/minio -o jsonpath='{.spec.ports[0].nodePort}'
+ ```
+
+1. In `examples/minio/05-backupstoragelocation.yaml`, uncomment the `publicUrl` line and provide this Minio URL as the value of the `publicUrl` field. You must include the `http://` or `https://` prefix.
+
+## Work with Ingress
+
+Configuring Ingress for your cluster is out of scope for the Velero documentation. If you have already set up Ingress, however, it makes sense to continue with it while you run the example Velero configuration with Minio.
+
+In this case:
+
+1. Keep the Service type as `ClusterIP`.
+
+1. In `examples/minio/05-backupstoragelocation.yaml`, uncomment the `publicUrl` line and provide the URL and port of your Ingress as the value of the `publicUrl` field.
+
+[1]: get-started.md
diff --git a/site/docs/v0.11.0/extend.md b/site/docs/v0.11.0/extend.md
new file mode 100644
index 000000000..5a1c68533
--- /dev/null
+++ b/site/docs/v0.11.0/extend.md
@@ -0,0 +1,9 @@
+# Extend Velero
+
+Velero includes mechanisms for extending the core functionality to meet your individual backup/restore needs:
+
+* [Hooks][27] allow you to specify commands to be executed within running pods during a backup. This is useful if you need to run a workload-specific command prior to taking a backup (for example, to flush disk buffers or to freeze a database).
+* [Plugins][28] allow you to develop custom object/block storage back-ends or per-item backup/restore actions that can execute arbitrary logic, including modifying the items being backed up/restored. Plugins can be used by Velero without needing to be compiled into the core Velero binary.
+
+[27]: hooks.md
+[28]: plugins.md
diff --git a/site/docs/v0.11.0/faq.md b/site/docs/v0.11.0/faq.md
new file mode 100644
index 000000000..2cd9025c7
--- /dev/null
+++ b/site/docs/v0.11.0/faq.md
@@ -0,0 +1,37 @@
+# FAQ
+
+## When is it appropriate to use Velero instead of etcd's built in backup/restore?
+
+Etcd's backup/restore tooling is good for recovering from data loss in a single etcd cluster. For
+example, it is a good idea to take a backup of etcd prior to upgrading etcd itself. For more
+sophisticated management of your Kubernetes cluster backups and restores, we feel that Velero is
+generally a better approach. It gives you the ability to throw away an unstable cluster and restore
+your Kubernetes resources and data into a new cluster, which you can't do easily just by backing up
+and restoring etcd.
+
+Examples of cases where Velero is useful:
+
+* you don't have access to etcd (e.g. you're running on GKE)
+* backing up both Kubernetes resources and persistent volume state
+* cluster migrations
+* backing up a subset of your Kubernetes resources
+* backing up Kubernetes resources that are stored across multiple etcd clusters (for example if you
+ run a custom apiserver)
+
+## Will Velero restore my Kubernetes resources exactly the way they were before?
+
+Yes, with some exceptions. For example, when Velero restores pods it deletes the `nodeName` from the
+pod so that it can be scheduled onto a new node. You can see some more examples of the differences
+in [pod_action.go](https://github.com/heptio/velero/blob/master/pkg/restore/pod_action.go)
+
+## I'm using Velero in multiple clusters. Should I use the same bucket to store all of my backups?
+
+We **strongly** recommend that you use a separate bucket per cluster to store backups. Sharing a bucket
+across multiple Velero instances can lead to numerous problems - failed backups, overwritten backups,
+inadvertently deleted backups, etc., all of which can be avoided by using a separate bucket per Velero
+instance.
+
+Related to this, if you need to restore a backup from cluster A into cluster B, please use restore-only
+mode in cluster B's Velero instance (via the `--restore-only` flag on the `velero server` command specified
+in your Velero deployment) while it's configured to use cluster A's bucket. This will ensure no
+new backups are created, and no existing backups are deleted or overwritten.
diff --git a/site/docs/v0.11.0/gcp-config.md b/site/docs/v0.11.0/gcp-config.md
new file mode 100644
index 000000000..79b6220a5
--- /dev/null
+++ b/site/docs/v0.11.0/gcp-config.md
@@ -0,0 +1,159 @@
+# Run Velero on GCP
+
+You can run Kubernetes on Google Cloud Platform in either:
+
+* Kubernetes on Google Compute Engine virtual machines
+* Google Kubernetes Engine
+
+If you do not have the `gcloud` and `gsutil` CLIs locally installed, follow the [user guide][16] to set them up.
+
+## Download Velero
+
+1. Download the [latest release's](https://github.com/heptio/velero/releases) tarball for your client platform.
+
+1. Extract the tarball:
+ ```bash
+ tar -xvf .tar.gz -C /dir/to/extract/to
+ ```
+ We'll refer to the directory you extracted to as the "Velero directory" in subsequent steps.
+
+1. Move the `velero` binary from the Velero directory to somewhere in your PATH.
+
+_We strongly recommend that you use an [official release](https://github.com/heptio/velero/releases) of Velero. The tarballs for each release contain the
+`velero` command-line client **and** version-specific sample YAML files for deploying Velero to your cluster. The code and sample YAML files in the master
+branch of the Velero repository are under active development and are not guaranteed to be stable. Use them at your own risk!_
+
+## Create GCS bucket
+
+Velero requires an object storage bucket in which to store backups, preferably unique to a single Kubernetes cluster (see the [FAQ][20] for more details). Create a GCS bucket, replacing the placeholder with the name of your bucket:
+
+```bash
+BUCKET=
+
+gsutil mb gs://$BUCKET/
+```
+
+## Create service account
+
+To integrate Velero with GCP, create an Velero-specific [Service Account][15]:
+
+1. View your current config settings:
+
+ ```bash
+ gcloud config list
+ ```
+
+ Store the `project` value from the results in the environment variable `$PROJECT_ID`.
+
+ ```bash
+ PROJECT_ID=$(gcloud config get-value project)
+ ```
+
+2. Create a service account:
+
+ ```bash
+ gcloud iam service-accounts create velero \
+ --display-name "Velero service account"
+ ```
+
+ > If you'll be using Velero to backup multiple clusters with multiple GCS buckets, it may be desirable to create a unique username per cluster rather than the default `velero`.
+
+ Then list all accounts and find the `velero` account you just created:
+ ```bash
+ gcloud iam service-accounts list
+ ```
+
+ Set the `$SERVICE_ACCOUNT_EMAIL` variable to match its `email` value.
+
+ ```bash
+ SERVICE_ACCOUNT_EMAIL=$(gcloud iam service-accounts list \
+ --filter="displayName:Velero service account" \
+ --format 'value(email)')
+ ```
+
+3. Attach policies to give `velero` the necessary permissions to function:
+
+ ```bash
+
+ ROLE_PERMISSIONS=(
+ compute.disks.get
+ compute.disks.create
+ compute.disks.createSnapshot
+ compute.snapshots.get
+ compute.snapshots.create
+ compute.snapshots.useReadOnly
+ compute.snapshots.delete
+ compute.zones.get
+ )
+
+ gcloud iam roles create velero.server \
+ --project $PROJECT_ID \
+ --title "Velero Server" \
+ --permissions "$(IFS=","; echo "${ROLE_PERMISSIONS[*]}")"
+
+ gcloud projects add-iam-policy-binding $PROJECT_ID \
+ --member serviceAccount:$SERVICE_ACCOUNT_EMAIL \
+ --role projects/$PROJECT_ID/roles/velero.server
+
+ gsutil iam ch serviceAccount:$SERVICE_ACCOUNT_EMAIL:objectAdmin gs://${BUCKET}
+ ```
+
+4. Create a service account key, specifying an output file (`credentials-velero`) in your local directory:
+
+ ```bash
+ gcloud iam service-accounts keys create credentials-velero \
+ --iam-account $SERVICE_ACCOUNT_EMAIL
+ ```
+
+## Credentials and configuration
+
+If you run Google Kubernetes Engine (GKE), make sure that your current IAM user is a cluster-admin. This role is required to create RBAC objects.
+See [the GKE documentation][22] for more information.
+
+In the Velero directory (i.e. where you extracted the release tarball), run the following to first set up namespaces, RBAC, and other scaffolding. To run in a custom namespace, make sure that you have edited the YAML files to specify the namespace. See [Run in custom namespace][0].
+
+```bash
+kubectl apply -f config/common/00-prereqs.yaml
+```
+
+Create a Secret. In the directory of the credentials file you just created, run:
+
+```bash
+kubectl create secret generic cloud-credentials \
+ --namespace velero \
+ --from-file cloud=credentials-velero
+```
+
+**Note: If you use a custom namespace, replace `velero` with the name of the custom namespace**
+
+Specify the following values in the example files:
+
+* In file `config/gcp/05-backupstoragelocation.yaml`:
+
+ * Replace ``. See the [BackupStorageLocation definition][7] for details.
+
+* (Optional) If you run the nginx example, in file `config/nginx-app/with-pv.yaml`:
+
+ * Replace `` with `standard`. This is GCP's default `StorageClass` name.
+
+* (Optional, use only if you need to specify multiple volume snapshot locations) In `config/gcp/10-deployment.yaml`:
+
+ * Uncomment the `--default-volume-snapshot-locations` and replace provider locations with the values for your environment.
+
+## Start the server
+
+In the root of your Velero directory, run:
+
+ ```bash
+ kubectl apply -f config/gcp/05-backupstoragelocation.yaml
+ kubectl apply -f config/gcp/06-volumesnapshotlocation.yaml
+ kubectl apply -f config/gcp/10-deployment.yaml
+ ```
+
+ [0]: namespace.md
+ [7]: api-types/backupstoragelocation.md#gcp
+ [15]: https://cloud.google.com/compute/docs/access/service-accounts
+ [16]: https://cloud.google.com/sdk/docs/
+ [20]: faq.md
+ [22]: https://cloud.google.com/kubernetes-engine/docs/how-to/role-based-access-control#prerequisites_for_using_role-based_access_control
+
diff --git a/site/docs/v0.11.0/get-started.md b/site/docs/v0.11.0/get-started.md
new file mode 100644
index 000000000..e43d1eb10
--- /dev/null
+++ b/site/docs/v0.11.0/get-started.md
@@ -0,0 +1,179 @@
+## Getting started
+
+The following example sets up the Velero server and client, then backs up and restores a sample application.
+
+For simplicity, the example uses Minio, an S3-compatible storage service that runs locally on your cluster.
+For additional functionality with this setup, see the docs on how to [expose Minio outside your cluster][31].
+
+**NOTE** The example lets you explore basic Velero functionality. Configuring Minio for production is out of scope.
+
+See [Set up Velero on your platform][3] for how to configure Velero for a production environment.
+
+If you encounter issues with installing or configuring, see [Debugging Installation Issues](debugging-install.md).
+
+### Prerequisites
+
+* Access to a Kubernetes cluster, version 1.7 or later. Version 1.7.5 or later is required to run `velero backup delete`.
+* A DNS server on the cluster
+* `kubectl` installed
+
+## Download Velero
+
+1. Download the [latest release's](https://github.com/heptio/velero/releases) tarball for your client platform.
+
+1. Extract the tarball:
+ ```bash
+ tar -xvf .tar.gz -C /dir/to/extract/to
+ ```
+ We'll refer to the directory you extracted to as the "Velero directory" in subsequent steps.
+
+1. Move the `velero` binary from the Velero directory to somewhere in your PATH.
+
+_We strongly recommend that you use an [official release](https://github.com/heptio/velero/releases) of Velero. The tarballs for each release contain the
+`velero` command-line client **and** version-specific sample YAML files for deploying Velero to your cluster. The code and sample YAML files in the master
+branch of the Velero repository are under active development and are not guaranteed to be stable. Use them at your own risk!_
+
+#### MacOS Installation
+
+On Mac, you can use [HomeBrew](https://brew.sh) to install the `velero` client:
+```bash
+brew install velero
+```
+
+### Set up server
+
+These instructions start the Velero server and a Minio instance that is accessible from within the cluster only. See [Expose Minio outside your cluster][31] for information about configuring your cluster for outside access to Minio. Outside access is required to access logs and run `velero describe` commands.
+
+1. Start the server and the local storage service. In the Velero directory, run:
+
+ ```bash
+ kubectl apply -f config/common/00-prereqs.yaml
+ kubectl apply -f config/minio/
+ ```
+
+1. Deploy the example nginx application:
+
+ ```bash
+ kubectl apply -f config/nginx-app/base.yaml
+ ```
+
+1. Check to see that both the Velero and nginx deployments are successfully created:
+
+ ```
+ kubectl get deployments -l component=velero --namespace=velero
+ kubectl get deployments --namespace=nginx-example
+ ```
+
+### Back up
+
+1. Create a backup for any object that matches the `app=nginx` label selector:
+
+ ```
+ velero backup create nginx-backup --selector app=nginx
+ ```
+
+ Alternatively if you want to backup all objects *except* those matching the label `backup=ignore`:
+
+ ```
+ velero backup create nginx-backup --selector 'backup notin (ignore)'
+ ```
+
+1. (Optional) Create regularly scheduled backups based on a cron expression using the `app=nginx` label selector:
+
+ ```
+ velero schedule create nginx-daily --schedule="0 1 * * *" --selector app=nginx
+ ```
+
+ Alternatively, you can use some non-standard shorthand cron expressions:
+
+ ```
+ velero schedule create nginx-daily --schedule="@daily" --selector app=nginx
+ ```
+
+ See the [cron package's documentation][30] for more usage examples.
+
+1. Simulate a disaster:
+
+ ```
+ kubectl delete namespace nginx-example
+ ```
+
+1. To check that the nginx deployment and service are gone, run:
+
+ ```
+ kubectl get deployments --namespace=nginx-example
+ kubectl get services --namespace=nginx-example
+ kubectl get namespace/nginx-example
+ ```
+
+ You should get no results.
+
+ NOTE: You might need to wait for a few minutes for the namespace to be fully cleaned up.
+
+### Restore
+
+1. Run:
+
+ ```
+ velero restore create --from-backup nginx-backup
+ ```
+
+1. Run:
+
+ ```
+ velero restore get
+ ```
+
+ After the restore finishes, the output looks like the following:
+
+ ```
+ NAME BACKUP STATUS WARNINGS ERRORS CREATED SELECTOR
+ nginx-backup-20170727200524 nginx-backup Completed 0 0 2017-07-27 20:05:24 +0000 UTC
+ ```
+
+NOTE: The restore can take a few moments to finish. During this time, the `STATUS` column reads `InProgress`.
+
+After a successful restore, the `STATUS` column is `Completed`, and `WARNINGS` and `ERRORS` are 0. All objects in the `nginx-example` namespace should be just as they were before you deleted them.
+
+If there are errors or warnings, you can look at them in detail:
+
+```
+velero restore describe
+```
+
+For more information, see [the debugging information][18].
+
+### Clean up
+
+If you want to delete any backups you created, including data in object storage and persistent
+volume snapshots, you can run:
+
+```
+velero backup delete BACKUP_NAME
+```
+
+This asks the Velero server to delete all backup data associated with `BACKUP_NAME`. You need to do
+this for each backup you want to permanently delete. A future version of Velero will allow you to
+delete multiple backups by name or label selector.
+
+Once fully removed, the backup is no longer visible when you run:
+
+```
+velero backup get BACKUP_NAME
+```
+
+If you want to uninstall Velero but preserve the backup data in object storage and persistent volume
+snapshots, it is safe to remove the `velero` namespace and everything else created for this
+example:
+
+```
+kubectl delete -f config/common/
+kubectl delete -f config/minio/
+kubectl delete -f config/nginx-app/base.yaml
+```
+
+[31]: expose-minio.md
+[3]: install-overview.md
+[18]: debugging-restores.md
+[26]: https://github.com/heptio/velero/releases
+[30]: https://godoc.org/github.com/robfig/cron
diff --git a/site/docs/v0.11.0/hooks.md b/site/docs/v0.11.0/hooks.md
new file mode 100644
index 000000000..dffac5385
--- /dev/null
+++ b/site/docs/v0.11.0/hooks.md
@@ -0,0 +1,81 @@
+# Hooks
+
+Velero currently supports executing commands in containers in pods during a backup.
+
+## Backup Hooks
+
+When performing a backup, you can specify one or more commands to execute in a container in a pod
+when that pod is being backed up.
+
+Velero versions prior to v0.7.0 only support hooks that execute prior to any custom action processing
+("pre" hooks).
+
+As of version v0.7.0, Velero also supports "post" hooks - these execute after all custom actions have
+completed, as well as after all the additional items specified by custom actions have been backed
+up.
+
+There are two ways to specify hooks: annotations on the pod itself, and in the Backup spec.
+
+### Specifying Hooks As Pod Annotations
+
+You can use the following annotations on a pod to make Velero execute a hook when backing up the pod:
+
+#### Pre hooks
+
+| Annotation Name | Description |
+| --- | --- |
+| `pre.hook.backup.velero.io/container` | The container where the command should be executed. Defaults to the first container in the pod. Optional. |
+| `pre.hook.backup.velero.io/command` | The command to execute. If you need multiple arguments, specify the command as a JSON array, such as `["/usr/bin/uname", "-a"]` |
+| `pre.hook.backup.velero.io/on-error` | What to do if the command returns a non-zero exit code. Defaults to Fail. Valid values are Fail and Continue. Optional. |
+| `pre.hook.backup.velero.io/timeout` | How long to wait for the command to execute. The hook is considered in error if the command exceeds the timeout. Defaults to 30s. Optional. |
+
+
+#### Post hooks (v0.7.0+)
+
+| Annotation Name | Description |
+| --- | --- |
+| `post.hook.backup.velero.io/container` | The container where the command should be executed. Defaults to the first container in the pod. Optional. |
+| `post.hook.backup.velero.io/command` | The command to execute. If you need multiple arguments, specify the command as a JSON array, such as `["/usr/bin/uname", "-a"]` |
+| `post.hook.backup.velero.io/on-error` | What to do if the command returns a non-zero exit code. Defaults to Fail. Valid values are Fail and Continue. Optional. |
+| `post.hook.backup.velero.io/timeout` | How long to wait for the command to execute. The hook is considered in error if the command exceeds the timeout. Defaults to 30s. Optional. |
+
+### Specifying Hooks in the Backup Spec
+
+Please see the documentation on the [Backup API Type][1] for how to specify hooks in the Backup
+spec.
+
+## Hook Example with fsfreeze
+
+We are going to walk through using both pre and post hooks for freezing a file system. Freezing the
+file system is useful to ensure that all pending disk I/O operations have completed prior to taking a snapshot.
+
+We will be using [examples/nginx-app/with-pv.yaml][2] for this example. Follow the [steps for your provider][3] to
+setup this example.
+
+### Annotations
+
+The Velero [example/nginx-app/with-pv.yaml][2] serves as an example of adding the pre and post hook annotations directly
+to your declarative deployment. Below is an example of what updating an object in place might look like.
+
+```shell
+kubectl annotate pod -n nginx-example -l app=nginx \
+ pre.hook.backup.velero.io/command='["/sbin/fsfreeze", "--freeze", "/var/log/nginx"]' \
+ pre.hook.backup.velero.io/container=fsfreeze \
+ post.hook.backup.velero.io/command='["/sbin/fsfreeze", "--unfreeze", "/var/log/nginx"]' \
+ post.hook.backup.velero.io/container=fsfreeze
+```
+
+Now test the pre and post hooks by creating a backup. You can use the Velero logs to verify that the pre and post
+hooks are running and exiting without error.
+
+```shell
+velero backup create nginx-hook-test
+
+velero backup get nginx-hook-test
+velero backup logs nginx-hook-test | grep hookCommand
+```
+
+
+[1]: api-types/backup.md
+[2]: examples/nginx-app/with-pv.yaml
+[3]: cloud-common.md
diff --git a/site/docs/v0.11.0/ibm-config.md b/site/docs/v0.11.0/ibm-config.md
new file mode 100644
index 000000000..4c8709e86
--- /dev/null
+++ b/site/docs/v0.11.0/ibm-config.md
@@ -0,0 +1,96 @@
+# Use IBM Cloud Object Storage as Velero's storage destination.
+You can deploy Velero on IBM [Public][5] or [Private][4] clouds, or even on any other Kubernetes cluster, but anyway you can use IBM Cloud Object Store as a destination for Velero's backups.
+
+To set up IBM Cloud Object Storage (COS) as Velero's destination, you:
+
+* Download an official release of Velero
+* Create your COS instance
+* Create an S3 bucket
+* Define a service that can store data in the bucket
+* Configure and start the Velero server
+
+## Download Velero
+
+1. Download the [latest release's](https://github.com/heptio/velero/releases) tarball for your client platform.
+
+1. Extract the tarball:
+ ```bash
+ tar -xvf .tar.gz -C /dir/to/extract/to
+ ```
+ We'll refer to the directory you extracted to as the "Velero directory" in subsequent steps.
+
+1. Move the `velero` binary from the Velero directory to somewhere in your PATH.
+
+_We strongly recommend that you use an [official release](https://github.com/heptio/velero/releases) of Velero. The tarballs for each release contain the
+`velero` command-line client **and** version-specific sample YAML files for deploying Velero to your cluster. The code and sample YAML files in the master
+branch of the Velero repository are under active development and are not guaranteed to be stable. Use them at your own risk!_
+
+## Create COS instance
+If you don’t have a COS instance, you can create a new one, according to the detailed instructions in [Creating a new resource instance][1].
+
+## Create an S3 bucket
+Velero requires an object storage bucket to store backups in. See instructions in [Create some buckets to store your data][2].
+
+## Define a service that can store data in the bucket.
+The process of creating service credentials is described in [Service credentials][3].
+Several comments:
+
+1. The Velero service will write its backup into the bucket, so it requires the “Writer” access role.
+
+2. Velero uses an AWS S3 compatible API. Which means it authenticates using a signature created from a pair of access and secret keys — a set of HMAC credentials. You can create these HMAC credentials by specifying `{“HMAC”:true}` as an optional inline parameter. See step 3 in the [Service credentials][3] guide.
+
+3. After successfully creating a Service credential, you can view the JSON definition of the credential. Under the `cos_hmac_keys` entry there are `access_key_id` and `secret_access_key`. We will use them in the next step.
+
+4. Create an Velero-specific credentials file (`credentials-velero`) in your local directory:
+
+ ```
+ [default]
+ aws_access_key_id=
+ aws_secret_access_key=
+ ```
+
+ where the access key id and secret are the values that we got above.
+
+## Credentials and configuration
+
+In the Velero directory (i.e. where you extracted the release tarball), run the following to first set up namespaces, RBAC, and other scaffolding. To run in a custom namespace, make sure that you have edited the YAML files to specify the namespace. See [Run in custom namespace][0].
+
+```bash
+kubectl apply -f config/common/00-prereqs.yaml
+```
+
+Create a Secret. In the directory of the credentials file you just created, run:
+
+```bash
+kubectl create secret generic cloud-credentials \
+ --namespace \
+ --from-file cloud=credentials-velero
+```
+
+Specify the following values in the example files:
+
+* In `config/ibm/05-backupstoragelocation.yaml`:
+
+ * Replace ``, `` and ``. See the [BackupStorageLocation definition][6] for details.
+
+* (Optional) If you run the nginx example, in file `config/nginx-app/with-pv.yaml`:
+
+ * Replace `` with your `StorageClass` name.
+
+## Start the Velero server
+
+In the root of your Velero directory, run:
+
+ ```bash
+ kubectl apply -f config/ibm/05-backupstoragelocation.yaml
+ kubectl apply -f config/ibm/10-deployment.yaml
+ ```
+
+ [0]: namespace.md
+ [1]: https://console.bluemix.net/docs/services/cloud-object-storage/basics/order-storage.html#creating-a-new-resource-instance
+ [2]: https://console.bluemix.net/docs/services/cloud-object-storage/getting-started.html#create-buckets
+ [3]: https://console.bluemix.net/docs/services/cloud-object-storage/iam/service-credentials.html#service-credentials
+ [4]: https://www.ibm.com/support/knowledgecenter/SSBS6K_2.1.0/kc_welcome_containers.html
+ [5]: https://console.bluemix.net/docs/containers/container_index.html#container_index
+ [6]: api-types/backupstoragelocation.md#aws
+ [14]: http://docs.aws.amazon.com/IAM/latest/UserGuide/introduction.html
diff --git a/site/docs/v0.11.0/image-tagging.md b/site/docs/v0.11.0/image-tagging.md
new file mode 100644
index 000000000..43e61834a
--- /dev/null
+++ b/site/docs/v0.11.0/image-tagging.md
@@ -0,0 +1,21 @@
+# Image tagging policy
+
+This document describes Velero's image tagging policy.
+
+## Released versions
+
+`gcr.io/heptio-images/velero:`
+
+Velero follows the [Semantic Versioning](http://semver.org/) standard for releases. Each tag in the `github.com/heptio/velero` repository has a matching image, e.g. `gcr.io/heptio-images/velero:v0.11.0`.
+
+### Latest
+
+`gcr.io/heptio-images/velero:latest`
+
+The `latest` tag follows the most recently released version of Velero.
+
+## Development
+
+`gcr.io/heptio-images/velero:master`
+
+The `master` tag follows the latest commit to land on the `master` branch.
diff --git a/site/docs/v0.11.0/img/README.md b/site/docs/v0.11.0/img/README.md
new file mode 100644
index 000000000..85c071c63
--- /dev/null
+++ b/site/docs/v0.11.0/img/README.md
@@ -0,0 +1 @@
+Some of these diagrams (for instance backup-process.png), have been created on [draw.io](https://www.draw.io), using the "Include a copy of my diagram" option. If you want to make changes to these diagrams, try importing them into draw.io, and you should have access to the original shapes/text that went into the originals.
diff --git a/site/docs/v0.11.0/img/backup-process.png b/site/docs/v0.11.0/img/backup-process.png
new file mode 100644
index 000000000..744b37abe
Binary files /dev/null and b/site/docs/v0.11.0/img/backup-process.png differ
diff --git a/site/docs/v0.11.0/img/velero.png b/site/docs/v0.11.0/img/velero.png
new file mode 100644
index 000000000..a1937a1dc
Binary files /dev/null and b/site/docs/v0.11.0/img/velero.png differ
diff --git a/site/docs/v0.11.0/install-overview.md b/site/docs/v0.11.0/install-overview.md
new file mode 100644
index 000000000..a1f10c83a
--- /dev/null
+++ b/site/docs/v0.11.0/install-overview.md
@@ -0,0 +1,109 @@
+# Set up Velero on your platform
+
+You can run Velero with a cloud provider or on-premises. For detailed information about the platforms that Velero supports, see [Compatible Storage Providers][99].
+
+In version 0.7.0 and later, you can run Velero in any namespace, which requires additional customization. See [Run in custom namespace][3].
+
+In version 0.9.0 and later, you can use Velero's integration with restic, which requires additional setup. See [restic instructions][20].
+
+## Customize configuration
+
+Whether you run Velero on a cloud provider or on-premises, if you have more than one volume snapshot location for a given volume provider, you can specify its default location for backups by setting a server flag in your Velero deployment YAML.
+
+For details, see the documentation topics for individual cloud providers.
+
+## Cloud provider
+
+The Velero repository includes a set of example YAML files that specify the settings for each supported cloud provider. For provider-specific instructions, see:
+
+* [Run Velero on AWS][0]
+* [Run Velero on GCP][1]
+* [Run Velero on Azure][2]
+* [Use IBM Cloud Object Store as Velero's storage destination][4]
+
+## On-premises
+
+You can run Velero in an on-premises cluster in different ways depending on your requirements.
+
+First, you must select an object storage backend that Velero can use to store backup data. [Compatible Storage Providers][99] contains information on various
+options that are supported or have been reported to work by users. [Minio][101] is an option if you want to keep your backup data on-premises and you are
+not using another storage platform that offers an S3-compatible object storage API.
+
+Second, if you need to back up persistent volume data, you must select a volume backup solution. [Volume Snapshot Providers][100] contains information on
+the supported options. For example, if you use [Portworx][102] for persistent storage, you can install their Velero plugin to get native Portworx snapshots as part
+of your Velero backups. If there is no native snapshot plugin available for your storage platform, you can use Velero's [restic integration][20], which provides a
+platform-agnostic backup solution for volume data.
+
+## Examples
+
+After you set up the Velero server, try these examples:
+
+### Basic example (without PersistentVolumes)
+
+1. Start the sample nginx app:
+
+ ```bash
+ kubectl apply -f config/nginx-app/base.yaml
+ ```
+
+1. Create a backup:
+
+ ```bash
+ velero backup create nginx-backup --include-namespaces nginx-example
+ ```
+
+1. Simulate a disaster:
+
+ ```bash
+ kubectl delete namespaces nginx-example
+ ```
+
+ Wait for the namespace to be deleted.
+
+1. Restore your lost resources:
+
+ ```bash
+ velero restore create --from-backup nginx-backup
+ ```
+
+### Snapshot example (with PersistentVolumes)
+
+> NOTE: For Azure, you must run Kubernetes version 1.7.2 or later to support PV snapshotting of managed disks.
+
+1. Start the sample nginx app:
+
+ ```bash
+ kubectl apply -f config/nginx-app/with-pv.yaml
+ ```
+
+1. Create a backup with PV snapshotting:
+
+ ```bash
+ velero backup create nginx-backup --include-namespaces nginx-example
+ ```
+
+1. Simulate a disaster:
+
+ ```bash
+ kubectl delete namespaces nginx-example
+ ```
+
+ Because the default [reclaim policy][19] for dynamically-provisioned PVs is "Delete", these commands should trigger your cloud provider to delete the disk that backs the PV. Deletion is asynchronous, so this may take some time. **Before continuing to the next step, check your cloud provider to confirm that the disk no longer exists.**
+
+1. Restore your lost resources:
+
+ ```bash
+ velero restore create --from-backup nginx-backup
+ ```
+
+[0]: aws-config.md
+[1]: gcp-config.md
+[2]: azure-config.md
+[3]: namespace.md
+[4]: ibm-config.md
+[19]: https://kubernetes.io/docs/concepts/storage/persistent-volumes/#reclaiming
+[20]: restic.md
+[99]: support-matrix.md
+[100]: support-matrix.md#volume-snapshot-providers
+[101]: https://www.minio.io
+[102]: https://portworx.com
diff --git a/site/docs/v0.11.0/locations.md b/site/docs/v0.11.0/locations.md
new file mode 100644
index 000000000..f1af86ea5
--- /dev/null
+++ b/site/docs/v0.11.0/locations.md
@@ -0,0 +1,168 @@
+# Backup Storage Locations and Volume Snapshot Locations
+
+Velero v0.10 introduces a new way of configuring where Velero backups and their associated persistent volume snapshots are stored.
+
+## Motivations
+
+In Velero versions prior to v0.10, the configuration for where to store backups & volume snapshots is specified in a `Config` custom resource. The `backupStorageProvider` section captures the place where all Velero backups should be stored. This is defined by a **provider** (e.g. `aws`, `azure`, `gcp`, `minio`, etc.), a **bucket**, and possibly some additional provider-specific settings (e.g. `region`). Similarly, the `persistentVolumeProvider` section captures the place where all persistent volume snapshots taken as part of Velero backups should be stored, and is defined by a **provider** and additional provider-specific settings (e.g. `region`).
+
+There are a number of use cases that this basic design does not support, such as:
+
+- Take snapshots of more than one kind of persistent volume in a single Velero backup (e.g. in a cluster with both EBS volumes and Portworx volumes)
+- Have some Velero backups go to a bucket in an eastern USA region, and others go to a bucket in a western USA region
+- For volume providers that support it (e.g. Portworx), have some snapshots be stored locally on the cluster and have others be stored in the cloud
+
+Additionally, as we look ahead to backup replication, a major feature on our roadmap, we know that we'll need Velero to be able to support multiple possible storage locations.
+
+## Overview
+
+In Velero v0.10 we got rid of the `Config` custom resource, and replaced it with two new custom resources, `BackupStorageLocation` and `VolumeSnapshotLocation`. The new resources directly replace the legacy `backupStorageProvider` and `persistentVolumeProvider` sections of the `Config` resource, respectively.
+
+Now, the user can pre-define more than one possible `BackupStorageLocation` and more than one `VolumeSnapshotLocation`, and can select *at backup creation time* the location in which the backup and associated snapshots should be stored.
+
+A `BackupStorageLocation` is defined as a bucket, a prefix within that bucket under which all Velero data should be stored, and a set of additional provider-specific fields (e.g. AWS region, Azure storage account, etc.) The [API documentation][1] captures the configurable parameters for each in-tree provider.
+
+A `VolumeSnapshotLocation` is defined entirely by provider-specific fields (e.g. AWS region, Azure resource group, Portworx snapshot type, etc.) The [API documentation][2] captures the configurable parameters for each in-tree provider.
+
+Additionally, since multiple `VolumeSnapshotLocations` can be created, the user can now configure locations for more than one volume provider, and if the cluster has volumes from multiple providers (e.g. AWS EBS and Portworx), all of them can be snapshotted in a single Velero backup.
+
+## Limitations / Caveats
+
+- Volume snapshots are still limited by where your provider allows you to create snapshots. For example, AWS and Azure do not allow you to create a volume snapshot in a different region than where the volume is. If you try to take an Velero backup using a volume snapshot location with a different region than where your cluster's volumes are, the backup will fail.
+
+- Each Velero backup has one `BackupStorageLocation`, and one `VolumeSnapshotLocation` per volume provider. It is not possible (yet) to send a single Velero backup to multiple backup storage locations simultaneously, or a single volume snapshot to multiple locations simultaneously. However, you can always set up multiple scheduled backups that differ only in the storage locations used if redundancy of backups across locations is important.
+
+- Cross-provider snapshots are not supported. If you have a cluster with more than one type of volume (e.g. EBS and Portworx), but you only have a `VolumeSnapshotLocation` configured for EBS, then Velero will **only** snapshot the EBS volumes.
+
+- Restic data is now stored under a prefix/subdirectory of the main Velero bucket, and will go into the bucket corresponding to the `BackupStorageLocation` selected by the user at backup creation time.
+
+## Examples
+
+Let's look at some examples of how we can use this new mechanism to address each of our previously unsupported use cases:
+
+#### Take snapshots of more than one kind of persistent volume in a single Velero backup (e.g. in a cluster with both EBS volumes and Portworx volumes)
+
+During server configuration:
+
+```shell
+velero snapshot-location create ebs-us-east-1 \
+ --provider aws \
+ --config region=us-east-1
+
+velero snapshot-location create portworx-cloud \
+ --provider portworx \
+ --config type=cloud
+```
+
+During backup creation:
+
+```shell
+velero backup create full-cluster-backup \
+ --volume-snapshot-locations ebs-us-east-1,portworx-cloud
+```
+
+Alternately, since in this example there's only one possible volume snapshot location configured for each of our two providers (`ebs-us-east-1` for `aws`, and `portworx-cloud` for `portworx`), Velero doesn't require them to be explicitly specified when creating the backup:
+
+```shell
+velero backup create full-cluster-backup
+```
+
+#### Have some Velero backups go to a bucket in an eastern USA region, and others go to a bucket in a western USA region
+
+During server configuration:
+
+```shell
+velero backup-location create default \
+ --provider aws \
+ --bucket velero-backups \
+ --config region=us-east-1
+
+velero backup-location create s3-alt-region \
+ --provider aws \
+ --bucket velero-backups-alt \
+ --config region=us-west-1
+```
+
+During backup creation:
+```shell
+# The Velero server will automatically store backups in the backup storage location named "default" if
+# one is not specified when creating the backup. You can alter which backup storage location is used
+# by default by setting the --default-backup-storage-location flag on the `velero server` command (run
+# by the Velero deployment) to the name of a different backup storage location.
+velero backup create full-cluster-backup
+```
+Or:
+```shell
+velero backup create full-cluster-alternate-location-backup \
+ --storage-location s3-alt-region
+```
+
+#### For volume providers that support it (e.g. Portworx), have some snapshots be stored locally on the cluster and have others be stored in the cloud
+
+During server configuration:
+
+```shell
+velero snapshot-location create portworx-local \
+ --provider portworx \
+ --config type=local
+
+velero snapshot-location create portworx-cloud \
+ --provider portworx \
+ --config type=cloud
+```
+
+During backup creation:
+
+```shell
+# Note that since in this example we have two possible volume snapshot locations for the Portworx
+# provider, we need to explicitly specify which one to use when creating a backup. Alternately,
+# you can set the --default-volume-snapshot-locations flag on the `velero server` command (run by
+# the Velero deployment) to specify which location should be used for each provider by default, in
+# which case you don't need to specify it when creating a backup.
+velero backup create local-snapshot-backup \
+ --volume-snapshot-locations portworx-local
+```
+
+Or:
+
+```shell
+velero backup create cloud-snapshot-backup \
+ --volume-snapshot-locations portworx-cloud
+```
+
+#### One location is still easy
+
+If you don't have a use case for more than one location, it's still just as easy to use Velero. Let's assume you're running on AWS, in the `us-west-1` region:
+
+During server configuration:
+
+```shell
+velero backup-location create default \
+ --provider aws \
+ --bucket velero-backups \
+ --config region=us-west-1
+
+velero snapshot-location create ebs-us-west-1 \
+ --provider aws \
+ --config region=us-west-1
+```
+
+During backup creation:
+```shell
+# Velero's will automatically use your configured backup storage location and volume snapshot location.
+# Nothing new needs to be specified when creating a backup.
+velero backup create full-cluster-backup
+```
+
+## Additional Use Cases
+
+1. If you're using Azure's AKS, you may want to store your volume snapshots outside of the "infrastructure" resource group that is automatically created when you create your AKS cluster. This is now possible using a `VolumeSnapshotLocation`, by specifying a `resourceGroup` under the `config` section of the snapshot location. See the [Azure volume snapshot location documentation][3] for details.
+
+1. If you're using Azure, you may want to store your Velero backups across multiple storage accounts and/or resource groups. This is now possible using a `BackupStorageLocation`, by specifying a `storageAccount` and/or `resourceGroup`, respectively, under the `config` section of the backup location. See the [Azure backup storage location documentation][4] for details.
+
+
+
+[1]: api-types/backupstoragelocation.md
+[2]: api-types/volumesnapshotlocation.md
+[3]: api-types/volumesnapshotlocation.md#azure
+[4]: api-types/backupstoragelocation.md#azure
diff --git a/site/docs/v0.11.0/migrating-to-velero.md b/site/docs/v0.11.0/migrating-to-velero.md
new file mode 100644
index 000000000..47573fcbc
--- /dev/null
+++ b/site/docs/v0.11.0/migrating-to-velero.md
@@ -0,0 +1,82 @@
+# Migrating from Heptio Ark to Velero
+
+As of v0.11.0, Heptio Ark has become Velero. This means the following changes have been made:
+
+* The `ark` CLI client is now `velero`.
+* The default Kubernetes namespace and ServiceAccount are now named `velero` (formerly `heptio-ark`).
+* The container image name is now `gcr.io/heptio-images/velero` (formerly `gcr.io/heptio-images/ark`).
+* CRDs are now under the new `velero.io` API group name (formerly `ark.heptio.com`).
+
+
+The following instructions will help you migrate your existing Ark installation to Velero.
+
+# Prerequisites
+
+* Ark v0.10.x installed. See the v0.10.x [upgrade instructions][1] to upgrade from older versions.
+* `kubectl` installed.
+* `cluster-admin` permissions.
+
+# Migration process
+
+At a high level, the migration process involves the following steps:
+
+* Scale down the `ark` deployment, so it will not process schedules, backups, or restores during the migration period.
+* Create a new namespace (named `velero` by default).
+* Apply the new CRDs.
+* Migrate existing Ark CRD objects, labels, and annotations to the new Velero equivalents.
+* Recreate the existing cloud credentials secret(s) in the velero namespace.
+* Apply the updated Kubernetes deployment and daemonset (for restic support) to use the new container images and namespace.
+* Remove the existing Ark namespace (which includes the deployment), CRDs, and ClusterRoleBinding.
+
+These steps are provided in a script here:
+
+```bash
+kubectl scale --namespace heptio-ark deployment/ark --replicas 0
+ OS=$(uname | tr '[:upper:]' '[:lower:]') # Determine if the OS is Linux or macOS
+ ARCH="amd64"
+
+# Download the velero client/example tarball to and unpack
+curl -L https://github.com/heptio/velero/releases/download/v0.11.0/velero-v0.11.0-${OS}-${ARCH}.tar.gz --output velero-v0.11.0-${OS}-${ARCH}.tar.gz
+tar xvf velero-v0.11.0-${OS}-${ARCH}.tar.gz
+
+# Create the prerequisite CRDs and namespace
+kubectl apply -f config/common/00-prereqs.yaml
+
+# Download and unpack the crd-migrator tool
+curl -L https://github.com/vmware/crd-migration-tool/releases/download/v1.0.0/crd-migration-tool-v1.0.0-${OS}-${ARCH}.tar.gz --output crd-migration-tool-v1.0.0-${OS}-${ARCH}.tar.gz
+tar xvf crd-migration-tool-v1.0.0-${OS}-${ARCH}.tar.gz
+
+# Run the tool against your cluster.
+./crd-migrator \
+ --from ark.heptio.com/v1 \
+ --to velero.io/v1 \
+ --label-mappings ark.heptio.com:velero.io,ark-schedule:velero.io/schedule-name \
+ --annotation-mappings ark.heptio.com:velero.io \
+ --namespace-mappings heptio-ark:velero
+
+
+# Copy the necessary secret from the ark namespace
+kubectl get secret --namespace heptio-ark cloud-credentials --export -o yaml | kubectl apply --namespace velero -f -
+
+# Apply the Velero deployment and restic DaemonSet for your platform
+## GCP
+#kubectl apply -f config/gcp/10-deployment.yaml
+#kubectl apply -f config/gcp/20-restic-daemonset.yaml
+## AWS
+#kubectl apply -f config/aws/10-deployment.yaml
+#kubectl apply -f config/aws/20-restic-daemonset.yaml
+## Azure
+#kubectl apply -f config/azure/00-deployment.yaml
+#kubectl apply -f config/azure/20-restic-daemonset.yaml
+
+# Verify your data is still present
+./velero get backup
+./velero get restore
+
+# Remove old Ark data
+kubectl delete namespace heptio-ark
+kubectl delete crds -l component=ark
+kubectl delete clusterrolebindings -l component=ark
+```
+
+[1]: https://heptio.github.io/velero/v0.10.0/upgrading-to-v0.10
diff --git a/site/docs/v0.11.0/migration-case.md b/site/docs/v0.11.0/migration-case.md
new file mode 100644
index 000000000..9d3a659ac
--- /dev/null
+++ b/site/docs/v0.11.0/migration-case.md
@@ -0,0 +1,48 @@
+# Cluster migration
+
+*Using Backups and Restores*
+
+Velero can help you port your resources from one cluster to another, as long as you point each Velero instance to the same cloud object storage location. In this scenario, we are also assuming that your clusters are hosted by the same cloud provider. **Note that Velero does not support the migration of persistent volumes across cloud providers.**
+
+1. *(Cluster 1)* Assuming you haven't already been checkpointing your data with the Velero `schedule` operation, you need to first back up your entire cluster (replacing `` as desired):
+
+ ```
+ velero backup create
+ ```
+ The default TTL is 30 days (720 hours); you can use the `--ttl` flag to change this as necessary.
+
+1. *(Cluster 2)* Add the `--restore-only` flag to the server spec in the Velero deployment YAML.
+
+1. *(Cluster 2)* Make sure that the `BackupStorageLocation` and `VolumeSnapshotLocation` CRDs match the ones from *Cluster 1*, so that your new Velero server instance points to the same bucket.
+
+1. *(Cluster 2)* Make sure that the Velero Backup object is created. Velero resources are synchronized with the backup files in cloud storage.
+
+ ```
+ velero backup describe
+ ```
+
+ **Note:** As of version 0.10, the default sync interval is 1 minute, so make sure to wait before checking. You can configure this interval with the `--backup-sync-period` flag to the Velero server.
+
+1. *(Cluster 2)* Once you have confirmed that the right Backup (``) is now present, you can restore everything with:
+
+ ```
+ velero restore create --from-backup
+ ```
+
+## Verify both clusters
+
+Check that the second cluster is behaving as expected:
+
+1. *(Cluster 2)* Run:
+
+ ```
+ velero restore get
+ ```
+
+1. Then run:
+
+ ```
+ velero restore describe
+ ```
+
+If you encounter issues, make sure that Velero is running in the same namespace in both clusters.
\ No newline at end of file
diff --git a/site/docs/v0.11.0/namespace.md b/site/docs/v0.11.0/namespace.md
new file mode 100644
index 000000000..b77615b8c
--- /dev/null
+++ b/site/docs/v0.11.0/namespace.md
@@ -0,0 +1,74 @@
+# Run in custom namespace
+
+In Velero version 0.7.0 and later, you can run Velero in any namespace. To do so, you specify the
+namespace in the YAML files that configure the Velero server. You then also specify the namespace when
+you run Velero client commands.
+
+## Edit the example files
+
+The Velero release tarballs include a set of example configs that you can use to set up your Velero server. The
+examples place the server and backup/schedule/restore/etc. data in the `velero` namespace.
+
+To run the server in another namespace, you edit the relevant files, changing `velero` to
+your desired namespace.
+
+To store your backups, schedules, restores, and config in another namespace, you edit the relevant
+files, changing `velero` to your desired namespace. You also need to create the
+`cloud-credentials` secret in your desired namespace.
+
+First, ensure you've [downloaded & extracted the latest release][0].
+
+For all cloud providers, edit `config/common/00-prereqs.yaml`. This file defines:
+
+* CustomResourceDefinitions for the Velero objects (backups, schedules, restores, downloadrequests, etc.)
+* The namespace where the Velero server runs
+* The namespace where backups, schedules, restores, etc. are stored
+* The Velero service account
+* The RBAC rules to grant permissions to the Velero service account
+
+
+### AWS
+
+For AWS, edit:
+
+* `config/aws/05-backupstoragelocation.yaml`
+* `config/aws/06-volumesnapshotlocation.yaml`
+* `config/aws/10-deployment.yaml`
+
+
+### Azure
+
+For Azure, edit:
+
+* `config/azure/00-deployment.yaml`
+* `config/azure/05-backupstoragelocation.yaml`
+* `config/azure/06-volumesnapshotlocation.yaml`
+
+### GCP
+
+For GCP, edit:
+
+* `config/gcp/05-backupstoragelocation.yaml`
+* `config/gcp/06-volumesnapshotlocation.yaml`
+* `config/gcp/10-deployment.yaml`
+
+
+### IBM
+
+For IBM, edit:
+
+* `config/ibm/05-backupstoragelocation.yaml`
+* `config/ibm/10-deployment.yaml`
+
+
+## Specify the namespace in client commands
+
+To specify the namespace for all Velero client commands, run:
+
+```
+velero client config set namespace=
+```
+
+
+
+[0]: get-started.md#download
diff --git a/site/docs/v0.11.0/output-file-format.md b/site/docs/v0.11.0/output-file-format.md
new file mode 100644
index 000000000..04420be91
--- /dev/null
+++ b/site/docs/v0.11.0/output-file-format.md
@@ -0,0 +1,99 @@
+# Output file format
+
+A backup is a gzip-compressed tar file whose name matches the Backup API resource's `metadata.name` (what is specified during `velero backup create `).
+
+In cloud object storage, each backup file is stored in its own subdirectory in the bucket specified in the Velero server configuration. This subdirectory includes an additional file called `velero-backup.json`. The JSON file lists all information about your associated Backup resource, including any default values. This gives you a complete historical record of the backup configuration. The JSON file also specifies `status.version`, which corresponds to the output file format.
+
+The directory structure in your cloud storage looks something like:
+
+```
+rootBucket/
+ backup1234/
+ velero-backup.json
+ backup1234.tar.gz
+```
+
+## Example backup JSON file
+
+```json
+{
+ "kind": "Backup",
+ "apiVersion": "velero.io/v1",
+ "metadata": {
+ "name": "test-backup",
+ "namespace": "velero",
+ "selfLink": "/apis/velero.io/v1/namespaces/velero/backups/testtest",
+ "uid": "a12345cb-75f5-11e7-b4c2-abcdef123456",
+ "resourceVersion": "337075",
+ "creationTimestamp": "2017-07-31T13:39:15Z"
+ },
+ "spec": {
+ "includedNamespaces": [
+ "*"
+ ],
+ "excludedNamespaces": null,
+ "includedResources": [
+ "*"
+ ],
+ "excludedResources": null,
+ "labelSelector": null,
+ "snapshotVolumes": true,
+ "ttl": "24h0m0s"
+ },
+ "status": {
+ "version": 1,
+ "expiration": "2017-08-01T13:39:15Z",
+ "phase": "Completed",
+ "volumeBackups": {
+ "pvc-e1e2d345-7583-11e7-b4c2-abcdef123456": {
+ "snapshotID": "snap-04b1a8e11dfb33ab0",
+ "type": "gp2",
+ "iops": 100
+ }
+ },
+ "validationErrors": null
+ }
+}
+```
+Note that this file includes detailed info about your volume snapshots in the `status.volumeBackups` field, which can be helpful if you want to manually check them in your cloud provider GUI.
+
+## file format version: 1
+
+When unzipped, a typical backup directory (e.g. `backup1234.tar.gz`) looks like the following:
+
+```
+resources/
+ persistentvolumes/
+ cluster/
+ pv01.json
+ ...
+ configmaps/
+ namespaces/
+ namespace1/
+ myconfigmap.json
+ ...
+ namespace2/
+ ...
+ pods/
+ namespaces/
+ namespace1/
+ mypod.json
+ ...
+ namespace2/
+ ...
+ jobs/
+ namespaces/
+ namespace1/
+ awesome-job.json
+ ...
+ namespace2/
+ ...
+ deployments/
+ namespaces/
+ namespace1/
+ cool-deployment.json
+ ...
+ namespace2/
+ ...
+ ...
+```
diff --git a/site/docs/v0.11.0/plugins.md b/site/docs/v0.11.0/plugins.md
new file mode 100644
index 000000000..dceb2f2be
--- /dev/null
+++ b/site/docs/v0.11.0/plugins.md
@@ -0,0 +1,31 @@
+# Plugins
+
+Velero has a plugin architecture that allows users to add their own custom functionality to Velero backups & restores
+without having to modify/recompile the core Velero binary. To add custom functionality, users simply create their own binary
+containing implementations of Velero's plugin kinds (described below), plus a small amount of boilerplate code to
+expose the plugin implementations to Velero. This binary is added to a container image that serves as an init container for
+the Velero server pod and copies the binary into a shared emptyDir volume for the Velero server to access.
+
+Multiple plugins, of any type, can be implemented in this binary.
+
+A fully-functional [sample plugin repository][1] is provided to serve as a convenient starting point for plugin authors.
+
+## Plugin Kinds
+
+Velero currently supports the following kinds of plugins:
+
+- **Object Store** - persists and retrieves backups, backup logs and restore logs
+- **Block Store** - creates volume snapshots (during backup) and restores volumes from snapshots (during restore)
+- **Backup Item Action** - executes arbitrary logic for individual items prior to storing them in a backup file
+- **Restore Item Action** - executes arbitrary logic for individual items prior to restoring them into a cluster
+
+## Plugin Logging
+
+Velero provides a [logger][2] that can be used by plugins to log structured information to the main Velero server log or
+per-backup/restore logs. See the [sample repository][1] for an example of how to instantiate and use the logger
+within your plugin.
+
+
+
+[1]: https://github.com/heptio/velero-plugin-example
+[2]: https://github.com/heptio/velero/blob/master/pkg/plugin/logger.go
diff --git a/site/docs/v0.11.0/rbac.md b/site/docs/v0.11.0/rbac.md
new file mode 100644
index 000000000..d8686bf6e
--- /dev/null
+++ b/site/docs/v0.11.0/rbac.md
@@ -0,0 +1,47 @@
+# Run Velero more securely with restrictive RBAC settings
+
+By default Velero runs with an RBAC policy of ClusterRole `cluster-admin`. This is to make sure that Velero can back up or restore anything in your cluster. But `cluster-admin` access is wide open -- it gives Velero components access to everything in your cluster. Depending on your environment and your security needs, you should consider whether to configure additional RBAC policies with more restrictive access.
+
+**Note:** Roles and RoleBindings are associated with a single namespaces, not with an entire cluster. PersistentVolume backups are associated only with an entire cluster. This means that any backups or restores that use a restrictive Role and RoleBinding pair can manage only the resources that belong to the namespace. You do not need a wide open RBAC policy to manage PersistentVolumes, however. You can configure a ClusterRole and ClusterRoleBinding that allow backups and restores only of PersistentVolumes, not of all objects in the cluster.
+
+For more information about RBAC and access control generally in Kubernetes, see the Kubernetes documentation about [access control][1], [managing service accounts][2], and [RBAC authorization][3].
+
+## Set up Roles and RoleBindings
+
+Here's a sample Role and RoleBinding pair.
+
+```yaml
+apiVersion: rbac.authorization.k8s.io/v1
+kind: Role
+metadata:
+ namespace: YOUR_NAMESPACE_HERE
+ name: ROLE_NAME_HERE
+ labels:
+ component: velero
+rules:
+ - apiGroups:
+ - velero.io
+ verbs:
+ - "*"
+ resources:
+ - "*"
+```
+
+```yaml
+apiVersion: rbac.authorization.k8s.io/v1
+kind: RoleBinding
+metadata:
+ name: ROLEBINDING_NAME_HERE
+subjects:
+ - kind: ServiceAccount
+ name: YOUR_SERVICEACCOUNT_HERE
+roleRef:
+ kind: Role
+ name: ROLE_NAME_HERE
+ apiGroup: rbac.authorization.k8s.io
+```
+
+[1]: https://kubernetes.io/docs/reference/access-authn-authz/controlling-access/
+[2]: https://kubernetes.io/docs/reference/access-authn-authz/service-accounts-admin/
+[3]: https://kubernetes.io/docs/reference/access-authn-authz/rbac/
+[4]: namespace.md
diff --git a/site/docs/v0.11.0/restic.md b/site/docs/v0.11.0/restic.md
new file mode 100644
index 000000000..690b4c373
--- /dev/null
+++ b/site/docs/v0.11.0/restic.md
@@ -0,0 +1,248 @@
+# Restic Integration
+
+As of version 0.9.0, Velero has support for backing up and restoring Kubernetes volumes using a free open-source backup tool called
+[restic][1].
+
+Velero has always allowed you to take snapshots of persistent volumes as part of your backups if you’re using one of
+the supported cloud providers’ block storage offerings (Amazon EBS Volumes, Azure Managed Disks, Google Persistent Disks).
+Starting with version 0.6.0, we provide a plugin model that enables anyone to implement additional object and block storage
+backends, outside the main Velero repository.
+
+We integrated restic with Velero so that users have an out-of-the-box solution for backing up and restoring almost any type of Kubernetes
+volume*. This is a new capability for Velero, not a replacement for existing functionality. If you're running on AWS, and
+taking EBS snapshots as part of your regular Velero backups, there's no need to switch to using restic. However, if you've
+been waiting for a snapshot plugin for your storage platform, or if you're using EFS, AzureFile, NFS, emptyDir,
+local, or any other volume type that doesn't have a native snapshot concept, restic might be for you.
+
+Restic is not tied to a specific storage platform, which means that this integration also paves the way for future work to enable
+cross-volume-type data migrations. Stay tuned as this evolves!
+
+\* hostPath volumes are not supported, but the [new local volume type][4] is supported.
+
+## Setup
+
+### Prerequisites
+
+- A working install of Velero version 0.10.0 or later. See [Set up Velero][2]
+- A local clone of [the latest release tag of the Velero repository][3]
+- Velero's restic integration requires the Kubernetes [MountPropagation feature][6], which is enabled by default in Kubernetes v1.10.0 and later.
+
+
+### Instructions
+
+1. Ensure you've [downloaded & extracted the latest release][3].
+
+1. In the Velero directory (i.e. where you extracted the release tarball), run the following to create new custom resource definitions:
+
+ ```bash
+ kubectl apply -f config/common/00-prereqs.yaml
+ ```
+
+1. Run one of the following for your platform to create the daemonset:
+
+ - AWS: `kubectl apply -f config/aws/20-restic-daemonset.yaml`
+ - Azure: `kubectl apply -f config/azure/20-restic-daemonset.yaml`
+ - GCP: `kubectl apply -f config/gcp/20-restic-daemonset.yaml`
+ - Minio: `kubectl apply -f config/minio/30-restic-daemonset.yaml`
+
+You're now ready to use Velero with restic.
+
+## Back up
+
+1. Run the following for each pod that contains a volume to back up:
+
+ ```bash
+ kubectl -n YOUR_POD_NAMESPACE annotate pod/YOUR_POD_NAME backup.velero.io/backup-volumes=YOUR_VOLUME_NAME_1,YOUR_VOLUME_NAME_2,...
+ ```
+
+ where the volume names are the names of the volumes in the pod spec.
+
+ For example, for the following pod:
+
+ ```bash
+ apiVersion: v1
+ kind: Pod
+ metadata:
+ name: sample
+ namespace: foo
+ spec:
+ containers:
+ - image: k8s.gcr.io/test-webserver
+ name: test-webserver
+ volumeMounts:
+ - name: pvc-volume
+ mountPath: /volume-1
+ - name: emptydir-volume
+ mountPath: /volume-2
+ volumes:
+ - name: pvc-volume
+ persistentVolumeClaim:
+ claimName: test-volume-claim
+ - name: emptydir-volume
+ emptyDir: {}
+ ```
+
+ You'd run:
+ ```bash
+ kubectl -n foo annotate pod/sample backup.velero.io/backup-volumes=pvc-volume,emptydir-volume
+ ```
+
+ This annotation can also be provided in a pod template spec if you use a controller to manage your pods.
+
+1. Take an Velero backup:
+
+ ```bash
+ velero backup create NAME OPTIONS...
+ ```
+
+1. When the backup completes, view information about the backups:
+
+ ```bash
+ velero backup describe YOUR_BACKUP_NAME
+
+ kubectl -n velero get podvolumebackups -l velero.io/backup-name=YOUR_BACKUP_NAME -o yaml
+ ```
+
+## Restore
+
+1. Restore from your Velero backup:
+
+ ```bash
+ velero restore create --from-backup BACKUP_NAME OPTIONS...
+ ```
+
+1. When the restore completes, view information about your pod volume restores:
+
+ ```bash
+ velero restore describe YOUR_RESTORE_NAME
+
+ kubectl -n velero get podvolumerestores -l velero.io/restore-name=YOUR_RESTORE_NAME -o yaml
+ ```
+
+## Limitations
+
+- `hostPath` volumes are not supported. [Local persistent volumes][4] are supported.
+- Those of you familiar with [restic][1] may know that it encrypts all of its data. We've decided to use a static,
+common encryption key for all restic repositories created by Velero. **This means that anyone who has access to your
+bucket can decrypt your restic backup data**. Make sure that you limit access to the restic bucket
+appropriately. We plan to implement full Velero backup encryption, including securing the restic encryption keys, in
+a future release.
+
+## Troubleshooting
+
+Run the following checks:
+
+Are your Velero server and daemonset pods running?
+
+```bash
+kubectl get pods -n velero
+```
+
+Does your restic repository exist, and is it ready?
+
+```bash
+velero restic repo get
+
+velero restic repo get REPO_NAME -o yaml
+```
+
+Are there any errors in your Velero backup/restore?
+
+```bash
+velero backup describe BACKUP_NAME
+velero backup logs BACKUP_NAME
+
+velero restore describe RESTORE_NAME
+velero restore logs RESTORE_NAME
+```
+
+What is the status of your pod volume backups/restores?
+
+```bash
+kubectl -n velero get podvolumebackups -l velero.io/backup-name=BACKUP_NAME -o yaml
+
+kubectl -n velero get podvolumerestores -l velero.io/restore-name=RESTORE_NAME -o yaml
+```
+
+Is there any useful information in the Velero server or daemon pod logs?
+
+```bash
+kubectl -n velero logs deploy/velero
+kubectl -n velero logs DAEMON_POD_NAME
+```
+
+**NOTE**: You can increase the verbosity of the pod logs by adding `--log-level=debug` as an argument
+to the container command in the deployment/daemonset pod template spec.
+
+## How backup and restore work with restic
+
+We introduced three custom resource definitions and associated controllers:
+
+- `ResticRepository` - represents/manages the lifecycle of Velero's [restic repositories][5]. Velero creates
+a restic repository per namespace when the first restic backup for a namespace is requested. The controller
+for this custom resource executes restic repository lifecycle commands -- `restic init`, `restic check`,
+and `restic prune`.
+
+ You can see information about your Velero restic repositories by running `velero restic repo get`.
+
+- `PodVolumeBackup` - represents a restic backup of a volume in a pod. The main Velero backup process creates
+one or more of these when it finds an annotated pod. Each node in the cluster runs a controller for this
+resource (in a daemonset) that handles the `PodVolumeBackups` for pods on that node. The controller executes
+`restic backup` commands to backup pod volume data.
+
+- `PodVolumeRestore` - represents a restic restore of a pod volume. The main Velero restore process creates one
+or more of these when it encounters a pod that has associated restic backups. Each node in the cluster runs a
+controller for this resource (in the same daemonset as above) that handles the `PodVolumeRestores` for pods
+on that node. The controller executes `restic restore` commands to restore pod volume data.
+
+### Backup
+
+1. The main Velero backup process checks each pod that it's backing up for the annotation specifying a restic backup
+should be taken (`backup.velero.io/backup-volumes`)
+1. When found, Velero first ensures a restic repository exists for the pod's namespace, by:
+ - checking if a `ResticRepository` custom resource already exists
+ - if not, creating a new one, and waiting for the `ResticRepository` controller to init/check it
+1. Velero then creates a `PodVolumeBackup` custom resource per volume listed in the pod annotation
+1. The main Velero process now waits for the `PodVolumeBackup` resources to complete or fail
+1. Meanwhile, each `PodVolumeBackup` is handled by the controller on the appropriate node, which:
+ - has a hostPath volume mount of `/var/lib/kubelet/pods` to access the pod volume data
+ - finds the pod volume's subdirectory within the above volume
+ - runs `restic backup`
+ - updates the status of the custom resource to `Completed` or `Failed`
+1. As each `PodVolumeBackup` finishes, the main Velero process captures its restic snapshot ID and adds it as an annotation
+to the copy of the pod JSON that's stored in the Velero backup. This will be used for restores, as seen in the next section.
+
+### Restore
+
+1. The main Velero restore process checks each pod that it's restoring for annotations specifying a restic backup
+exists for a volume in the pod (`snapshot.velero.io/`)
+1. When found, Velero first ensures a restic repository exists for the pod's namespace, by:
+ - checking if a `ResticRepository` custom resource already exists
+ - if not, creating a new one, and waiting for the `ResticRepository` controller to init/check it (note that
+ in this case, the actual repository should already exist in object storage, so the Velero controller will simply
+ check it for integrity)
+1. Velero adds an init container to the pod, whose job is to wait for all restic restores for the pod to complete (more
+on this shortly)
+1. Velero creates the pod, with the added init container, by submitting it to the Kubernetes API
+1. Velero creates a `PodVolumeRestore` custom resource for each volume to be restored in the pod
+1. The main Velero process now waits for each `PodVolumeRestore` resource to complete or fail
+1. Meanwhile, each `PodVolumeRestore` is handled by the controller on the appropriate node, which:
+ - has a hostPath volume mount of `/var/lib/kubelet/pods` to access the pod volume data
+ - waits for the pod to be running the init container
+ - finds the pod volume's subdirectory within the above volume
+ - runs `restic restore`
+ - on success, writes a file into the pod volume, in a `.velero` subdirectory, whose name is the UID of the Velero restore
+ that this pod volume restore is for
+ - updates the status of the custom resource to `Completed` or `Failed`
+1. The init container that was added to the pod is running a process that waits until it finds a file
+within each restored volume, under `.velero`, whose name is the UID of the Velero restore being run
+1. Once all such files are found, the init container's process terminates successfully and the pod moves
+on to running other init containers/the main containers.
+
+
+[1]: https://github.com/restic/restic
+[2]: install-overview.md
+[3]: https://github.com/heptio/velero/releases/
+[4]: https://kubernetes.io/docs/concepts/storage/volumes/#local
+[5]: http://restic.readthedocs.io/en/latest/100_references.html#terminology
+[6]: https://kubernetes.io/docs/concepts/storage/volumes/#mount-propagation
diff --git a/site/docs/v0.11.0/support-matrix.md b/site/docs/v0.11.0/support-matrix.md
new file mode 100644
index 000000000..faf85dffc
--- /dev/null
+++ b/site/docs/v0.11.0/support-matrix.md
@@ -0,0 +1,58 @@
+# Compatible Storage Providers
+
+Velero supports a variety of storage providers for different backup and snapshot operations. As of version 0.6.0, a plugin system allows anyone to add compatibility for additional backup and volume storage platforms without modifying the Velero codebase.
+
+## Backup Storage Providers
+
+| Provider | Owner | Contact |
+|---------------------------|----------|---------------------------------|
+| [AWS S3][2] | Velero Team | [Slack][10], [GitHub Issue][11] |
+| [Azure Blob Storage][3] | Velero Team | [Slack][10], [GitHub Issue][11] |
+| [Google Cloud Storage][4] | Velero Team | [Slack][10], [GitHub Issue][11] |
+
+## S3-Compatible Backup Storage Providers
+
+Velero uses [Amazon's Go SDK][12] to connect to the S3 API. Some third-party storage providers also support the S3 API, and users have reported the following providers work with Velero:
+
+_Note that these providers are not regularly tested by the Velero team._
+
+ * [IBM Cloud][5]
+ * [Minio][9]
+ * Ceph RADOS v12.2.7
+ * [DigitalOcean][7]
+ * Quobyte
+
+_Some storage providers, like Quobyte, may need a different [signature algorithm version][15]._
+
+## Volume Snapshot Providers
+
+| Provider | Owner | Contact |
+|----------------------------------|-----------------|---------------------------------|
+| [AWS EBS][2] | Velero Team | [Slack][10], [GitHub Issue][11] |
+| [Azure Managed Disks][3] | Velero Team | [Slack][10], [GitHub Issue][11] |
+| [Google Compute Engine Disks][4] | Velero Team | [Slack][10], [GitHub Issue][11] |
+| [Restic][1] | Velero Team | [Slack][10], [GitHub Issue][11] |
+| [Portworx][6] | Portworx | [Slack][13], [GitHub Issue][14] |
+| [DigitalOcean][7] | StackPointCloud | |
+
+### Adding a new plugin
+
+To write a plugin for a new backup or volume storage system, take a look at the [example repo][8].
+
+After you publish your plugin, open a PR that adds your plugin to the appropriate list.
+
+[1]: restic.md
+[2]: aws-config.md
+[3]: azure-config.md
+[4]: gcp-config.md
+[5]: ibm-config.md
+[6]: https://docs.portworx.com/scheduler/kubernetes/ark.html
+[7]: https://github.com/StackPointCloud/ark-plugin-digitalocean
+[8]: https://github.com/heptio/velero-plugin-example/
+[9]: get-started.md
+[10]: https://kubernetes.slack.com/messages/velero
+[11]: https://github.com/heptio/velero/issues
+[12]: https://github.com/aws/aws-sdk-go/aws
+[13]: https://portworx.slack.com/messages/px-k8s
+[14]: https://github.com/portworx/ark-plugin/issues
+[15]: api-types/backupstoragelocation.md#aws
diff --git a/site/docs/v0.11.0/troubleshooting.md b/site/docs/v0.11.0/troubleshooting.md
new file mode 100644
index 000000000..0c70b876d
--- /dev/null
+++ b/site/docs/v0.11.0/troubleshooting.md
@@ -0,0 +1,71 @@
+# Troubleshooting
+
+These tips can help you troubleshoot known issues. If they don't help, you can [file an issue][4], or talk to us on the [#velero channel][25] on the Kubernetes Slack server.
+
+See also:
+
+- [Debug installation/setup issues][2]
+- [Debug restores][1]
+
+## General troubleshooting information
+
+In `velero` version >= `0.10.0`, you can use the `velero bug` command to open a [Github issue][4] by launching a browser window with some prepopulated values. Values included are OS, CPU architecture, `kubectl` client and server versions (if available) and the `velero` client version. This information isn't submitted to Github until you click the `Submit new issue` button in the Github UI, so feel free to add, remove or update whatever information you like.
+
+Some general commands for troubleshooting that may be helpful:
+
+* `velero backup describe ` - describe the details of a backup
+* `velero backup logs ` - fetch the logs for this specific backup. Useful for viewing failures and warnings, including resources that could not be backed up.
+* `velero restore describe ` - describe the details of a restore
+* `velero restore logs ` - fetch the logs for this specific restore. Useful for viewing failures and warnings, including resources that could not be restored.
+* `kubectl logs deployment/velero -n velero` - fetch the logs of the Velero server pod. This provides the output of the Velero server processes.
+
+### Getting velero debug logs
+
+You can increase the verbosity of the Velero server by editing your Velero deployment to look like this:
+
+
+```
+kubectl edit deployment/velero -n velero
+...
+ containers:
+ - name: velero
+ image: gcr.io/heptio-images/velero:latest
+ command:
+ - /velero
+ args:
+ - server
+ - --log-level # Add this line
+ - debug # Add this line
+...
+```
+
+## Known issue with restoring LoadBalancer Service
+
+Because of how Kubernetes handles Service objects of `type=LoadBalancer`, when you restore these objects you might encounter an issue with changed values for Service UIDs. Kubernetes automatically generates the name of the cloud resource based on the Service UID, which is different when restored, resulting in a different name for the cloud load balancer. If the DNS CNAME for your application points to the DNS name of your cloud load balancer, you'll need to update the CNAME pointer when you perform an Velero restore.
+
+Alternatively, you might be able to use the Service's `spec.loadBalancerIP` field to keep connections valid, if your cloud provider supports this value. See [the Kubernetes documentation about Services of Type LoadBalancer](https://kubernetes.io/docs/concepts/services-networking/service/#loadbalancer).
+
+## Miscellaneous issues
+
+### Velero reports `custom resource not found` errors when starting up.
+
+Velero's server will not start if the required Custom Resource Definitions are not found in Kubernetes. Apply
+the `config/common/00-prereqs.yaml` file to create these definitions, then restart Velero.
+
+### `velero backup logs` returns a `SignatureDoesNotMatch` error
+
+Downloading artifacts from object storage utilizes temporary, signed URLs. In the case of S3-compatible
+providers, such as Ceph, there may be differences between their implementation and the official S3
+API that cause errors.
+
+Here are some things to verify if you receive `SignatureDoesNotMatch` errors:
+
+ * Make sure your S3-compatible layer is using [signature version 4][5] (such as Ceph RADOS v12.2.7)
+ * For Ceph, try using a native Ceph account for credentials instead of external providers such as OpenStack Keystone
+
+
+[1]: debugging-restores.md
+[2]: debugging-install.md
+[4]: https://github.com/heptio/velero/issues
+[5]: https://docs.aws.amazon.com/AmazonS3/latest/API/sig-v4-authenticating-requests.html
+[25]: https://kubernetes.slack.com/messages/velero
diff --git a/site/docs/v0.11.0/vendoring-dependencies.md b/site/docs/v0.11.0/vendoring-dependencies.md
new file mode 100644
index 000000000..1729f21ec
--- /dev/null
+++ b/site/docs/v0.11.0/vendoring-dependencies.md
@@ -0,0 +1,18 @@
+# Vendoring dependencies
+
+## Overview
+
+We are using [dep][0] to manage dependencies. You can install it by following [these
+instructions][1].
+
+## Adding a new dependency
+
+Run `dep ensure`. If you want to see verbose output, you can append `-v` as in
+`dep ensure -v`.
+
+## Updating an existing dependency
+
+Run `dep ensure -update [ ...]` to update one or more dependencies.
+
+[0]: https://github.com/golang/dep
+[1]: https://golang.github.io/dep/docs/installation.html
diff --git a/site/docs/v0.11.0/versions.md b/site/docs/v0.11.0/versions.md
new file mode 100644
index 000000000..bac2bb946
--- /dev/null
+++ b/site/docs/v0.11.0/versions.md
@@ -0,0 +1,26 @@
+# Upgrading Velero versions
+
+Velero supports multiple concurrent versions. Whether you're setting up Velero for the first time or upgrading to a new version, you need to pay careful attention to versioning. This doc page is new as of version 0.10.0, and will be updated with information about subsequent releases.
+
+## Minor versions, patch versions
+
+The documentation site provides docs for minor versions only, not for patch releases. Patch releases are guaranteed not to be breaking, but you should carefully read the [release notes][1] to make sure that you understand any relevant changes.
+
+If you're upgrading from a patch version to a patch version, you only need to update the image tags in your configurations. No other steps are needed.
+
+Breaking changes are documented in the release notes and in the documentation.
+
+## Breaking changes for version 0.10.0
+
+- See [Upgrading to version 0.10.0][2]
+
+## Velero versions and Kubernetes versions
+
+Not all Velero versions support all versions of Kubernetes. You should be aware of the following known limitations:
+
+- Velero version 0.9.0 requires Kubernetes version 1.8 or later. In version 0.9.1, Velero was updated to support earlier versions.
+- Restic support requires Kubernetes version 1.10 or later, or an earlier version with the mount propagation feature enabled. See [Restic Integration][3].
+
+[1]: https://github.com/heptio/velero/releases
+[2]: https://heptio.github.io/velero/v0.10.0/upgrading-to-v0.10
+[3]: restic.md
diff --git a/site/docs/v0.11.0/zenhub.md b/site/docs/v0.11.0/zenhub.md
new file mode 100644
index 000000000..7bb32a387
--- /dev/null
+++ b/site/docs/v0.11.0/zenhub.md
@@ -0,0 +1,15 @@
+# ZenHub
+
+As an Open Source community, it is necessary for our work, communication, and collaboration to be done in the open.
+GitHub provides a central repository for code, pull requests, issues, and documentation. When applicable, we will use Google Docs for design reviews, proposals, and other working documents.
+
+While GitHub issues, milestones, and labels generally work pretty well, the Velero team has found that product planning requires some additional tooling that GitHub projects do not offer.
+
+In our effort to minimize tooling while enabling product management insights, we have decided to use [ZenHub Open-Source](https://www.zenhub.com/blog/open-source/) to overlay product and project tracking on top of GitHub.
+ZenHub is a GitHub application that provides Kanban visualization, Epic tracking, fine-grained prioritization, and more. It's primary backing storage system is existing GitHub issues along with additional metadata stored in ZenHub's database.
+
+If you are an Velero user or Velero Developer, you do not _need_ to use ZenHub for your regular workflow (e.g to see open bug reports or feature requests, work on pull requests). However, if you'd like to be able to visualize the high-level project goals and roadmap, you will need to use the free version of ZenHub.
+
+## Using ZenHub
+
+ZenHub can be integrated within the GitHub interface using their [Chrome or FireFox extensions](https://www.zenhub.com/extension). In addition, you can use their dedicated [web application](https://app.zenhub.com/workspace/o/heptio/velero/boards?filterLogic=all&repos=99143276).
diff --git a/site/docs/v0.3.0/README.md b/site/docs/v0.3.0/README.md
new file mode 100644
index 000000000..45161366b
--- /dev/null
+++ b/site/docs/v0.3.0/README.md
@@ -0,0 +1,206 @@
+# Heptio Ark
+
+**Maintainers:** [Heptio][0]
+
+[![Build Status][1]][2]
+
+## Overview
+Heptio Ark is a utility for managing disaster recovery, specifically for your [Kubernetes][14] cluster resources and persistent volumes. It provides a simple, configurable, and operationally robust way to back up and restore applications and PVs from a series of checkpoints. This allows you to better automate in the following scenarios:
+
+* **Disaster recovery** with reduced TTR (time to respond), in the case of:
+ * Infrastructure loss
+ * Data corruption
+ * Service outages
+
+* **Cross-cloud-provider migration** for Kubernetes API objects (cross-cloud-provider migration of persistent volume snapshots not yet supported)
+
+* **Dev and testing environment setup (+ CI)**, via replication of prod environment
+
+More concretely, Heptio Ark combines an in-cluster service with a CLI that allows you to record both:
+1. *Configurable subsets of Kubernetes API objects* -- as tarballs stored in object storage
+2. *Disk snapshots of Persistent Volumes* -- via the cloud provider APIs
+
+Heptio Ark currently supports the [AWS][15], [GCP][16], and [Azure][17] cloud provider platforms.
+
+## Quickstart
+
+This guide gets Ark up and running on your cluster, and goes through an example using the following:
+* **Minio, an S3-compatible storage service** that runs locally on your cluster. This is the storage service where backup files are uploaded. *Note that Ark is intended to run on a cloud provider--we are using Minio here to keep the example convenient and self-contained.*
+
+* **A sample nginx app** under the `nginx-example` namespace, used to demonstrate Ark's backup and restore functionality.
+
+Note that this example *does not* include a demonstration of PV disk snapshots, because that feature requires integration with a cloud provider API. For snapshotting examples and instructions specific to AWS, GCP, and Azure, see [Cloud Provider Specifics][23].
+
+### 0. Prerequisites
+
+* *You should have access to an up-and-running Kubernetes cluster (minimum version 1.7).* If you do not have a cluster, [choose a setup solution][9] from the official Kubernetes docs.
+
+* *You will need to have a DNS server set up on your cluster for the example files to work.* You can check this with `kubectl get svc -l k8s-app=kube-dns --namespace=kube-system`. If said service does not exist, [these instructions][12] may help.
+
+* *You should have `kubectl` installed.* If not, follow the instructions for [installing via Homebrew (MacOS)][10] or [building the binary (Linux)][11].
+
+### 1. Download
+Clone or fork the Heptio Ark repo:
+```
+git clone git@github.com:heptio/ark.git
+```
+
+### 2. Setup
+
+There are two types of Ark instances that work in tandem:
+1. **Ark server**: Runs persistently on the cluster.
+2. **Ark client**: Launched by the user whenever they want to initiate an operation (e.g. a backup).
+
+To get the server started on your cluster (as well as the local storage service), execute the following commands in Ark's root directory:
+
+```
+kubectl apply -f examples/common/00-prereqs.yaml
+kubectl apply -f examples/minio/
+kubectl apply -f examples/common/10-deployment.yaml
+```
+
+*NOTE: If you encounter an error related to Config creation, wait for a minute and run the command again. (The Config CRD does not always finish registering in time.)*
+
+Now deploy the example nginx app:
+```
+kubectl apply -f examples/nginx-app/base.yaml
+```
+
+Check to see that both the Ark and nginx deployments have been successfully created:
+```
+kubectl get deployments -l component=ark --namespace=heptio-ark
+kubectl get deployments --namespace=nginx-example
+```
+
+Finally, create an alias for the Ark client's Docker executable. (Make sure that your `KUBECONFIG` environment variable is pointing at the proper config first). This will save a lot of future typing:
+
+```
+alias ark='docker run --rm -v $(dirname $KUBECONFIG):/kubeconfig -e KUBECONFIG=/kubeconfig/$(basename $KUBECONFIG) gcr.io/heptio-images/ark:latest'
+```
+*NOTE*: Depending on how your Kubeconfig is written--if it refers to the Kubernetes API server using the host machine's `localhost`, for instance--you may need to add an additional `--net="host"` flag to the `docker run` command.
+
+
+### 3. Back up and restore
+First, create a backup specifically for any object matching the `app=nginx` label selector:
+
+```
+ark backup create nginx-backup --selector app=nginx
+```
+
+Now you can mimic a disaster with the following:
+```
+kubectl delete namespace nginx-example
+```
+Oh no! The nginx deployment and service are both gone, as you can see (though you may have to wait a minute or two for the namespace be fully cleaned up):
+```
+kubectl get deployments --namespace=nginx-example
+kubectl get services --namespace=nginx-example
+```
+Neither commands should yield any results. However, because Ark has your back(up), you can run this command:
+```
+ark restore create nginx-backup
+```
+
+To check on the status of the Restore:
+```
+ark restore get
+```
+
+The output should look something like the table below:
+```
+NAME BACKUP STATUS WARNINGS ERRORS CREATED SELECTOR
+nginx-backup-20170727200524 nginx-backup Completed 0 0 2017-07-27 20:05:24 +0000 UTC
+```
+
+If the Restore's `STATUS` column is "Completed", and `WARNINGS` and `ERRORS` are both zero, the restore is a success. All of the objects in the `nginx-example` namespace should be just as they were before.
+
+Otherwise, if there are warnings or errors indicated, you can run the following command to look at them in more detail:
+```
+ark restore get -o yaml
+```
+See the [debugging documentation][18] for more details.
+
+*NOTE*: In the example files, the `storage` volume is defined via `hostPath` for better visibility. If you're curious to see the [structure of the backup files][13] firsthand, you can find the compressed results in `/tmp/minio/ark/nginx-backup`.
+
+### 4. Tear Down
+Using the following command, you can remove all Kubernetes objects associated with this example:
+```
+kubectl delete -f examples/common/
+kubectl delete -f examples/minio/
+kubectl delete -f examples/nginx-app/base.yaml
+```
+
+## Architecture
+
+Each of Heptio Ark's operations (Backups, Schedules, and Restores) are custom resources themselves, defined using [CRDs][20]. Their accompanying [custom controllers][21] handle them when they are submitted to the Kubernetes API server.
+
+As mentioned before, Ark runs in two different modes:
+
+* **Ark client**: Allows you to query, create, and delete the Ark resources as desired.
+
+* **Ark server**: Runs all of the Ark controllers. Each controller watches its respective custom resource for API operations, performs validation, and handles the majority of the cloud API logic (e.g. interfacing with object storage and persistent volumes).
+
+Looking at a specific example--an `ark backup create test-backup --snapshot-volumes` command triggers the following operations:
+
+![19]
+
+1. The *ark client* makes a call to the Kubernetes API server, creating a `Backup` custom resource (which is stored in [etcd][22]).
+
+2. The `BackupController` sees that a new `Backup` has been created, and validates it.
+
+3. Once validation passes, the `BackupController` begins the backup process. It collects data by querying the Kubernetes API Server for resources.
+
+4. Once the data has been aggregated, the `BackupController` makes a call to the object storage service (e.g. Amazon S3) to upload the backup file.
+
+5. If the `--snapshot-volumes` flag is specified, Ark also makes disk snapshots of any persistent volumes, using the appropriate cloud service API.
+
+## Further documentation
+
+ To learn more about Heptio Ark operations and their applications, see the [`/docs` directory][3].
+
+## Troubleshooting
+
+If you encounter any problems that the documentation does not address, [file an issue][4].
+
+## Contributing
+
+Thanks for taking the time to join our community and start contributing!
+
+#### Before you start
+
+* Please familiarize yourself with the [Code of Conduct][8] before contributing.
+* See [CONTRIBUTING.md][5] for instructions on the developer certificate of origin that we require.
+
+#### Pull requests
+
+* We welcome pull requests. Feel free to dig through the [issues][4] and jump in.
+
+
+## Changelog
+
+See [the list of releases][6] to find out about feature changes.
+
+[0]: https://github.com/heptio
+[1]: https://jenkins.i.heptio.com/buildStatus/icon?job=ark-prbuilder
+[2]: https://jenkins.i.heptio.com/job/ark-prbuilder/
+[3]: /
+[4]: https://github.com/heptio/ark/issues
+[5]: https://github.com/heptio/ark/tree/v0.3.0/CONTRIBUTING.md
+[6]: https://github.com/heptio/ark/tree/v0.3.0/CHANGELOG.md
+[7]: /build-from-scratch.md
+[8]: https://github.com/heptio/ark/tree/v0.3.0/CODE_OF_CONDUCT.md
+[9]: https://kubernetes.io/docs/setup/
+[10]: https://kubernetes.io/docs/tasks/tools/install-kubectl/#install-with-homebrew-on-macos
+[11]: https://kubernetes.io/docs/tasks/tools/install-kubectl/#tabset-1
+[12]: https://github.com/kubernetes/kubernetes/blob/master/cluster/addons/dns/README.md
+[13]: /output-file-format.md
+[14]: https://github.com/kubernetes/kubernetes
+[15]: https://aws.amazon.com/
+[16]: https://cloud.google.com/
+[17]: https://azure.microsoft.com/
+[18]: /debugging-restores.md
+[19]: /img/backup-process.png
+[20]: https://kubernetes.io/docs/concepts/api-extension/custom-resources/#customresourcedefinitions
+[21]: https://kubernetes.io/docs/concepts/api-extension/custom-resources/#custom-controllers
+[22]: https://github.com/coreos/etcd
+[23]: /cloud-provider-specifics.md
diff --git a/site/docs/v0.3.0/build-from-scratch.md b/site/docs/v0.3.0/build-from-scratch.md
new file mode 100644
index 000000000..ce451ad6f
--- /dev/null
+++ b/site/docs/v0.3.0/build-from-scratch.md
@@ -0,0 +1,56 @@
+# Build From Scratch
+
+While the [README][0] pulls from the Heptio image registry, you can also build your own Heptio Ark container with the following steps:
+
+* [0. Prerequisites][1]
+* [1. Download][2]
+* [2. Build][3]
+* [3. Run][7]
+
+## 0. Prerequisites
+
+In addition to the handling the prerequisites mentioned in the [Quickstart][4], you should have [Go][5] installed (minimum version 1.8).
+
+## 1. Download
+
+Install with go:
+```
+go get github.com/heptio/ark
+```
+The files are installed in `$GOPATH/src/github.com/heptio/ark`.
+
+## 2. Build
+
+Set the `$REGISTRY` environment variable (used in the `Makefile`) if you want to push the Heptio Ark images to your own registry. This allows any node in your cluster to pull your locally built image.
+
+`$PROJECT` and `$VERSION` environment variables are also specified in the `Makefile`, and can be similarly modified as desired.
+
+Run the following in the Ark root directory to build your container with the tag `$REGISTRY/$PROJECT:$VERSION`:
+```
+sudo make all
+```
+
+To push your image to a registry, use `make push`.
+
+## 3. Run
+When running Heptio Ark, you will need to account for the following (all of which are handled in the [`/examples`][6] manifests):
+* Appropriate RBAC permissions in the cluster
+ * *Read access* for all data from the source cluster and namespaces
+ * *Write access* to the target cluster and namespaces
+* Cloud provider credentials
+ * *Read/write access* to volumes
+ * *Read/write access* to object storage for backup data
+* A [Config object][8] definition for the Ark server
+
+See [Cloud Provider Specifics][9] for a more detailed guide.
+
+[0]: ../README.md
+[1]: #0-prerequisites
+[2]: #1-download
+[3]: #2-build
+[4]: ../README.md#quickstart
+[5]: https://golang.org/doc/install
+[6]: /examples
+[7]: #3-run
+[8]: reference.md#ark-config-definition
+[9]: cloud-provider-specifics.md
diff --git a/site/docs/v0.3.0/cli-reference/README.md b/site/docs/v0.3.0/cli-reference/README.md
new file mode 100644
index 000000000..e3d87c872
--- /dev/null
+++ b/site/docs/v0.3.0/cli-reference/README.md
@@ -0,0 +1,21 @@
+# Command line reference
+
+The Ark client provides a CLI that allows you to initiate ad-hoc backups, scheduled backups, or restores.
+
+*The files in this directory enumerate each of the possible `ark` commands and their flags. Note that you can also find this info with the CLI itself, using the `--help` flag.*
+
+## Running the client
+
+While it is possible to build and run the `ark` executable yourself, it is recommended to use the containerized version. Use the alias described in the quickstart:
+
+```
+alias ark='docker run --rm -v $(dirname $KUBECONFIG):/kubeconfig -e KUBECONFIG=/kubeconfig/$(basename $KUBECONFIG) gcr.io/heptio-images/ark:latest'
+```
+
+Assuming that your `KUBECONFIG` variable is set, this alias takes care of specifying the appropriate Kubernetes cluster credentials for you.
+
+## Kubernetes cluster credentials
+In general, Ark will search for your cluster credentials in the following order:
+* `--kubeconfig` command line flag
+* `$KUBECONFIG` environment variable
+* In-cluster credentials--this only works when you are running Ark in a pod
diff --git a/site/docs/v0.3.0/cli-reference/ark.md b/site/docs/v0.3.0/cli-reference/ark.md
new file mode 100644
index 000000000..d548d5af6
--- /dev/null
+++ b/site/docs/v0.3.0/cli-reference/ark.md
@@ -0,0 +1,32 @@
+## ark
+
+Back up and restore Kubernetes cluster resources.
+
+### Synopsis
+
+
+Heptio Ark is a tool for managing disaster recovery, specifically for
+Kubernetes cluster resources. It provides a simple, configurable,
+and operationally robust way to back up your application state and
+associated data.
+
+### Options
+
+```
+ --alsologtostderr log to standard error as well as files
+ --kubeconfig string Path to the kubeconfig file to use to talk to the Kubernetes apiserver. If unset, try the environment variable KUBECONFIG, as well as in-cluster configuration
+ --log_backtrace_at traceLocation when logging hits line file:N, emit a stack trace (default :0)
+ --log_dir string If non-empty, write log files in this directory
+ --logtostderr log to standard error instead of files
+ --stderrthreshold severity logs at or above this threshold go to stderr (default 2)
+ -v, --v Level log level for V logs
+ --vmodule moduleSpec comma-separated list of pattern=N settings for file-filtered logging
+```
+
+### SEE ALSO
+* [ark backup](ark_backup.md) - Work with backups
+* [ark restore](ark_restore.md) - Work with restores
+* [ark schedule](ark_schedule.md) - Work with schedules
+* [ark server](ark_server.md) - Run the ark server
+* [ark version](ark_version.md) - Print the ark version and associated image
+
diff --git a/site/docs/v0.3.0/cli-reference/ark_backup.md b/site/docs/v0.3.0/cli-reference/ark_backup.md
new file mode 100644
index 000000000..6191610bb
--- /dev/null
+++ b/site/docs/v0.3.0/cli-reference/ark_backup.md
@@ -0,0 +1,27 @@
+## ark backup
+
+Work with backups
+
+### Synopsis
+
+
+Work with backups
+
+### Options inherited from parent commands
+
+```
+ --alsologtostderr log to standard error as well as files
+ --kubeconfig string Path to the kubeconfig file to use to talk to the Kubernetes apiserver. If unset, try the environment variable KUBECONFIG, as well as in-cluster configuration
+ --log_backtrace_at traceLocation when logging hits line file:N, emit a stack trace (default :0)
+ --log_dir string If non-empty, write log files in this directory
+ --logtostderr log to standard error instead of files
+ --stderrthreshold severity logs at or above this threshold go to stderr (default 2)
+ -v, --v Level log level for V logs
+ --vmodule moduleSpec comma-separated list of pattern=N settings for file-filtered logging
+```
+
+### SEE ALSO
+* [ark](ark.md) - Back up and restore Kubernetes cluster resources.
+* [ark backup create](ark_backup_create.md) - Create a backup
+* [ark backup get](ark_backup_get.md) - Get backups
+
diff --git a/site/docs/v0.3.0/cli-reference/ark_backup_create.md b/site/docs/v0.3.0/cli-reference/ark_backup_create.md
new file mode 100644
index 000000000..1f03a8ce5
--- /dev/null
+++ b/site/docs/v0.3.0/cli-reference/ark_backup_create.md
@@ -0,0 +1,45 @@
+## ark backup create
+
+Create a backup
+
+### Synopsis
+
+
+Create a backup
+
+```
+ark backup create NAME
+```
+
+### Options
+
+```
+ --exclude-namespaces stringArray namespaces to exclude from the backup
+ --exclude-resources stringArray resources to exclude from the backup, formatted as resource.group, such as storageclasses.storage.k8s.io
+ --include-namespaces stringArray namespaces to include in the backup (use '*' for all namespaces) (default *)
+ --include-resources stringArray resources to include in the backup, formatted as resource.group, such as storageclasses.storage.k8s.io (use '*' for all resources)
+ --label-columns stringArray a comma-separated list of labels to be displayed as columns
+ --labels mapStringString labels to apply to the backup
+ -o, --output string Output display format. For create commands, display the object but do not send it to the server. Valid formats are 'table', 'json', and 'yaml'.
+ -l, --selector labelSelector only back up resources matching this label selector (default )
+ --show-labels show labels in the last column
+ --snapshot-volumes take snapshots of PersistentVolumes as part of the backup
+ --ttl duration how long before the backup can be garbage collected (default 24h0m0s)
+```
+
+### Options inherited from parent commands
+
+```
+ --alsologtostderr log to standard error as well as files
+ --kubeconfig string Path to the kubeconfig file to use to talk to the Kubernetes apiserver. If unset, try the environment variable KUBECONFIG, as well as in-cluster configuration
+ --log_backtrace_at traceLocation when logging hits line file:N, emit a stack trace (default :0)
+ --log_dir string If non-empty, write log files in this directory
+ --logtostderr log to standard error instead of files
+ --stderrthreshold severity logs at or above this threshold go to stderr (default 2)
+ -v, --v Level log level for V logs
+ --vmodule moduleSpec comma-separated list of pattern=N settings for file-filtered logging
+```
+
+### SEE ALSO
+* [ark backup](ark_backup.md) - Work with backups
+
diff --git a/site/docs/v0.3.0/cli-reference/ark_backup_get.md b/site/docs/v0.3.0/cli-reference/ark_backup_get.md
new file mode 100644
index 000000000..d1ef6e53a
--- /dev/null
+++ b/site/docs/v0.3.0/cli-reference/ark_backup_get.md
@@ -0,0 +1,38 @@
+## ark backup get
+
+Get backups
+
+### Synopsis
+
+
+Get backups
+
+```
+ark backup get
+```
+
+### Options
+
+```
+ --label-columns stringArray a comma-separated list of labels to be displayed as columns
+ -o, --output string Output display format. For create commands, display the object but do not send it to the server. Valid formats are 'table', 'json', and 'yaml'. (default "table")
+ -l, --selector string only show items matching this label selector
+ --show-labels show labels in the last column
+```
+
+### Options inherited from parent commands
+
+```
+ --alsologtostderr log to standard error as well as files
+ --kubeconfig string Path to the kubeconfig file to use to talk to the Kubernetes apiserver. If unset, try the environment variable KUBECONFIG, as well as in-cluster configuration
+ --log_backtrace_at traceLocation when logging hits line file:N, emit a stack trace (default :0)
+ --log_dir string If non-empty, write log files in this directory
+ --logtostderr log to standard error instead of files
+ --stderrthreshold severity logs at or above this threshold go to stderr (default 2)
+ -v, --v Level log level for V logs
+ --vmodule moduleSpec comma-separated list of pattern=N settings for file-filtered logging
+```
+
+### SEE ALSO
+* [ark backup](ark_backup.md) - Work with backups
+
diff --git a/site/docs/v0.3.0/cli-reference/ark_restore.md b/site/docs/v0.3.0/cli-reference/ark_restore.md
new file mode 100644
index 000000000..4c8c4bc7d
--- /dev/null
+++ b/site/docs/v0.3.0/cli-reference/ark_restore.md
@@ -0,0 +1,28 @@
+## ark restore
+
+Work with restores
+
+### Synopsis
+
+
+Work with restores
+
+### Options inherited from parent commands
+
+```
+ --alsologtostderr log to standard error as well as files
+ --kubeconfig string Path to the kubeconfig file to use to talk to the Kubernetes apiserver. If unset, try the environment variable KUBECONFIG, as well as in-cluster configuration
+ --log_backtrace_at traceLocation when logging hits line file:N, emit a stack trace (default :0)
+ --log_dir string If non-empty, write log files in this directory
+ --logtostderr log to standard error instead of files
+ --stderrthreshold severity logs at or above this threshold go to stderr (default 2)
+ -v, --v Level log level for V logs
+ --vmodule moduleSpec comma-separated list of pattern=N settings for file-filtered logging
+```
+
+### SEE ALSO
+* [ark](ark.md) - Back up and restore Kubernetes cluster resources.
+* [ark restore create](ark_restore_create.md) - Create a restore
+* [ark restore delete](ark_restore_delete.md) - Delete a restore
+* [ark restore get](ark_restore_get.md) - get restores
+
diff --git a/site/docs/v0.3.0/cli-reference/ark_restore_create.md b/site/docs/v0.3.0/cli-reference/ark_restore_create.md
new file mode 100644
index 000000000..223222f4e
--- /dev/null
+++ b/site/docs/v0.3.0/cli-reference/ark_restore_create.md
@@ -0,0 +1,42 @@
+## ark restore create
+
+Create a restore
+
+### Synopsis
+
+
+Create a restore
+
+```
+ark restore create BACKUP
+```
+
+### Options
+
+```
+ --label-columns stringArray a comma-separated list of labels to be displayed as columns
+ --labels mapStringString labels to apply to the restore
+ --namespace-mappings mapStringString namespace mappings from name in the backup to desired restored name in the form src1:dst1,src2:dst2,...
+ --namespaces stringArray comma-separated list of namespaces to restore
+ -o, --output string Output display format. For create commands, display the object but do not send it to the server. Valid formats are 'table', 'json', and 'yaml'.
+ --restore-volumes whether to restore volumes from snapshots
+ -l, --selector labelSelector only restore resources matching this label selector (default )
+ --show-labels show labels in the last column
+```
+
+### Options inherited from parent commands
+
+```
+ --alsologtostderr log to standard error as well as files
+ --kubeconfig string Path to the kubeconfig file to use to talk to the Kubernetes apiserver. If unset, try the environment variable KUBECONFIG, as well as in-cluster configuration
+ --log_backtrace_at traceLocation when logging hits line file:N, emit a stack trace (default :0)
+ --log_dir string If non-empty, write log files in this directory
+ --logtostderr log to standard error instead of files
+ --stderrthreshold severity logs at or above this threshold go to stderr (default 2)
+ -v, --v Level log level for V logs
+ --vmodule moduleSpec comma-separated list of pattern=N settings for file-filtered logging
+```
+
+### SEE ALSO
+* [ark restore](ark_restore.md) - Work with restores
+
diff --git a/site/docs/v0.3.0/cli-reference/ark_restore_delete.md b/site/docs/v0.3.0/cli-reference/ark_restore_delete.md
new file mode 100644
index 000000000..bd2276e74
--- /dev/null
+++ b/site/docs/v0.3.0/cli-reference/ark_restore_delete.md
@@ -0,0 +1,29 @@
+## ark restore delete
+
+Delete a restore
+
+### Synopsis
+
+
+Delete a restore
+
+```
+ark restore delete NAME
+```
+
+### Options inherited from parent commands
+
+```
+ --alsologtostderr log to standard error as well as files
+ --kubeconfig string Path to the kubeconfig file to use to talk to the Kubernetes apiserver. If unset, try the environment variable KUBECONFIG, as well as in-cluster configuration
+ --log_backtrace_at traceLocation when logging hits line file:N, emit a stack trace (default :0)
+ --log_dir string If non-empty, write log files in this directory
+ --logtostderr log to standard error instead of files
+ --stderrthreshold severity logs at or above this threshold go to stderr (default 2)
+ -v, --v Level log level for V logs
+ --vmodule moduleSpec comma-separated list of pattern=N settings for file-filtered logging
+```
+
+### SEE ALSO
+* [ark restore](ark_restore.md) - Work with restores
+
diff --git a/site/docs/v0.3.0/cli-reference/ark_restore_get.md b/site/docs/v0.3.0/cli-reference/ark_restore_get.md
new file mode 100644
index 000000000..cd37983b0
--- /dev/null
+++ b/site/docs/v0.3.0/cli-reference/ark_restore_get.md
@@ -0,0 +1,38 @@
+## ark restore get
+
+get restores
+
+### Synopsis
+
+
+get restores
+
+```
+ark restore get
+```
+
+### Options
+
+```
+ --label-columns stringArray a comma-separated list of labels to be displayed as columns
+ -o, --output string Output display format. For create commands, display the object but do not send it to the server. Valid formats are 'table', 'json', and 'yaml'. (default "table")
+ -l, --selector string only show items matching this label selector
+ --show-labels show labels in the last column
+```
+
+### Options inherited from parent commands
+
+```
+ --alsologtostderr log to standard error as well as files
+ --kubeconfig string Path to the kubeconfig file to use to talk to the Kubernetes apiserver. If unset, try the environment variable KUBECONFIG, as well as in-cluster configuration
+ --log_backtrace_at traceLocation when logging hits line file:N, emit a stack trace (default :0)
+ --log_dir string If non-empty, write log files in this directory
+ --logtostderr log to standard error instead of files
+ --stderrthreshold severity logs at or above this threshold go to stderr (default 2)
+ -v, --v Level log level for V logs
+ --vmodule moduleSpec comma-separated list of pattern=N settings for file-filtered logging
+```
+
+### SEE ALSO
+* [ark restore](ark_restore.md) - Work with restores
+
diff --git a/site/docs/v0.3.0/cli-reference/ark_schedule.md b/site/docs/v0.3.0/cli-reference/ark_schedule.md
new file mode 100644
index 000000000..7c146b11e
--- /dev/null
+++ b/site/docs/v0.3.0/cli-reference/ark_schedule.md
@@ -0,0 +1,28 @@
+## ark schedule
+
+Work with schedules
+
+### Synopsis
+
+
+Work with schedules
+
+### Options inherited from parent commands
+
+```
+ --alsologtostderr log to standard error as well as files
+ --kubeconfig string Path to the kubeconfig file to use to talk to the Kubernetes apiserver. If unset, try the environment variable KUBECONFIG, as well as in-cluster configuration
+ --log_backtrace_at traceLocation when logging hits line file:N, emit a stack trace (default :0)
+ --log_dir string If non-empty, write log files in this directory
+ --logtostderr log to standard error instead of files
+ --stderrthreshold severity logs at or above this threshold go to stderr (default 2)
+ -v, --v Level log level for V logs
+ --vmodule moduleSpec comma-separated list of pattern=N settings for file-filtered logging
+```
+
+### SEE ALSO
+* [ark](ark.md) - Back up and restore Kubernetes cluster resources.
+* [ark schedule create](ark_schedule_create.md) - Create a schedule
+* [ark schedule delete](ark_schedule_delete.md) - Delete a schedule
+* [ark schedule get](ark_schedule_get.md) - Get schedules
+
diff --git a/site/docs/v0.3.0/cli-reference/ark_schedule_create.md b/site/docs/v0.3.0/cli-reference/ark_schedule_create.md
new file mode 100644
index 000000000..8ec9c383a
--- /dev/null
+++ b/site/docs/v0.3.0/cli-reference/ark_schedule_create.md
@@ -0,0 +1,46 @@
+## ark schedule create
+
+Create a schedule
+
+### Synopsis
+
+
+Create a schedule
+
+```
+ark schedule create NAME
+```
+
+### Options
+
+```
+ --exclude-namespaces stringArray namespaces to exclude from the backup
+ --exclude-resources stringArray resources to exclude from the backup, formatted as resource.group, such as storageclasses.storage.k8s.io
+ --include-namespaces stringArray namespaces to include in the backup (use '*' for all namespaces) (default *)
+ --include-resources stringArray resources to include in the backup, formatted as resource.group, such as storageclasses.storage.k8s.io (use '*' for all resources)
+ --label-columns stringArray a comma-separated list of labels to be displayed as columns
+ --labels mapStringString labels to apply to the backup
+ -o, --output string Output display format. For create commands, display the object but do not send it to the server. Valid formats are 'table', 'json', and 'yaml'.
+ --schedule string a cron expression specifying a recurring schedule for this backup to run
+ -l, --selector labelSelector only back up resources matching this label selector (default )
+ --show-labels show labels in the last column
+ --snapshot-volumes take snapshots of PersistentVolumes as part of the backup
+ --ttl duration how long before the backup can be garbage collected (default 24h0m0s)
+```
+
+### Options inherited from parent commands
+
+```
+ --alsologtostderr log to standard error as well as files
+ --kubeconfig string Path to the kubeconfig file to use to talk to the Kubernetes apiserver. If unset, try the environment variable KUBECONFIG, as well as in-cluster configuration
+ --log_backtrace_at traceLocation when logging hits line file:N, emit a stack trace (default :0)
+ --log_dir string If non-empty, write log files in this directory
+ --logtostderr log to standard error instead of files
+ --stderrthreshold severity logs at or above this threshold go to stderr (default 2)
+ -v, --v Level log level for V logs
+ --vmodule moduleSpec comma-separated list of pattern=N settings for file-filtered logging
+```
+
+### SEE ALSO
+* [ark schedule](ark_schedule.md) - Work with schedules
+
diff --git a/site/docs/v0.3.0/cli-reference/ark_schedule_delete.md b/site/docs/v0.3.0/cli-reference/ark_schedule_delete.md
new file mode 100644
index 000000000..e8057b3c5
--- /dev/null
+++ b/site/docs/v0.3.0/cli-reference/ark_schedule_delete.md
@@ -0,0 +1,29 @@
+## ark schedule delete
+
+Delete a schedule
+
+### Synopsis
+
+
+Delete a schedule
+
+```
+ark schedule delete NAME
+```
+
+### Options inherited from parent commands
+
+```
+ --alsologtostderr log to standard error as well as files
+ --kubeconfig string Path to the kubeconfig file to use to talk to the Kubernetes apiserver. If unset, try the environment variable KUBECONFIG, as well as in-cluster configuration
+ --log_backtrace_at traceLocation when logging hits line file:N, emit a stack trace (default :0)
+ --log_dir string If non-empty, write log files in this directory
+ --logtostderr log to standard error instead of files
+ --stderrthreshold severity logs at or above this threshold go to stderr (default 2)
+ -v, --v Level log level for V logs
+ --vmodule moduleSpec comma-separated list of pattern=N settings for file-filtered logging
+```
+
+### SEE ALSO
+* [ark schedule](ark_schedule.md) - Work with schedules
+
diff --git a/site/docs/v0.3.0/cli-reference/ark_schedule_get.md b/site/docs/v0.3.0/cli-reference/ark_schedule_get.md
new file mode 100644
index 000000000..9852eea53
--- /dev/null
+++ b/site/docs/v0.3.0/cli-reference/ark_schedule_get.md
@@ -0,0 +1,38 @@
+## ark schedule get
+
+Get schedules
+
+### Synopsis
+
+
+Get schedules
+
+```
+ark schedule get
+```
+
+### Options
+
+```
+ --label-columns stringArray a comma-separated list of labels to be displayed as columns
+ -o, --output string Output display format. For create commands, display the object but do not send it to the server. Valid formats are 'table', 'json', and 'yaml'. (default "table")
+ -l, --selector string only show items matching this label selector
+ --show-labels show labels in the last column
+```
+
+### Options inherited from parent commands
+
+```
+ --alsologtostderr log to standard error as well as files
+ --kubeconfig string Path to the kubeconfig file to use to talk to the Kubernetes apiserver. If unset, try the environment variable KUBECONFIG, as well as in-cluster configuration
+ --log_backtrace_at traceLocation when logging hits line file:N, emit a stack trace (default :0)
+ --log_dir string If non-empty, write log files in this directory
+ --logtostderr log to standard error instead of files
+ --stderrthreshold severity logs at or above this threshold go to stderr (default 2)
+ -v, --v Level log level for V logs
+ --vmodule moduleSpec comma-separated list of pattern=N settings for file-filtered logging
+```
+
+### SEE ALSO
+* [ark schedule](ark_schedule.md) - Work with schedules
+
diff --git a/site/docs/v0.3.0/cli-reference/ark_server.md b/site/docs/v0.3.0/cli-reference/ark_server.md
new file mode 100644
index 000000000..15729ec22
--- /dev/null
+++ b/site/docs/v0.3.0/cli-reference/ark_server.md
@@ -0,0 +1,34 @@
+## ark server
+
+Run the ark server
+
+### Synopsis
+
+
+Run the ark server
+
+```
+ark server
+```
+
+### Options
+
+```
+ --kubeconfig string Path to the kubeconfig file to use to talk to the Kubernetes apiserver. If unset, try the environment variable KUBECONFIG, as well as in-cluster configuration
+```
+
+### Options inherited from parent commands
+
+```
+ --alsologtostderr log to standard error as well as files
+ --log_backtrace_at traceLocation when logging hits line file:N, emit a stack trace (default :0)
+ --log_dir string If non-empty, write log files in this directory
+ --logtostderr log to standard error instead of files
+ --stderrthreshold severity logs at or above this threshold go to stderr (default 2)
+ -v, --v Level log level for V logs
+ --vmodule moduleSpec comma-separated list of pattern=N settings for file-filtered logging
+```
+
+### SEE ALSO
+* [ark](ark.md) - Back up and restore Kubernetes cluster resources.
+
diff --git a/site/docs/v0.3.0/cli-reference/ark_version.md b/site/docs/v0.3.0/cli-reference/ark_version.md
new file mode 100644
index 000000000..5f08ff16c
--- /dev/null
+++ b/site/docs/v0.3.0/cli-reference/ark_version.md
@@ -0,0 +1,29 @@
+## ark version
+
+Print the ark version and associated image
+
+### Synopsis
+
+
+Print the ark version and associated image
+
+```
+ark version
+```
+
+### Options inherited from parent commands
+
+```
+ --alsologtostderr log to standard error as well as files
+ --kubeconfig string Path to the kubeconfig file to use to talk to the Kubernetes apiserver. If unset, try the environment variable KUBECONFIG, as well as in-cluster configuration
+ --log_backtrace_at traceLocation when logging hits line file:N, emit a stack trace (default :0)
+ --log_dir string If non-empty, write log files in this directory
+ --logtostderr log to standard error instead of files
+ --stderrthreshold severity logs at or above this threshold go to stderr (default 2)
+ -v, --v Level log level for V logs
+ --vmodule moduleSpec comma-separated list of pattern=N settings for file-filtered logging
+```
+
+### SEE ALSO
+* [ark](ark.md) - Back up and restore Kubernetes cluster resources.
+
diff --git a/site/docs/v0.3.0/cloud-provider-specifics.md b/site/docs/v0.3.0/cloud-provider-specifics.md
new file mode 100644
index 000000000..3b8f94b19
--- /dev/null
+++ b/site/docs/v0.3.0/cloud-provider-specifics.md
@@ -0,0 +1,358 @@
+# Cloud Provider Specifics
+
+While the [Quickstart][0] uses a local storage service to quickly set up Heptio Ark as a demonstration, this document details additional configurations that are required when integrating with the cloud providers below:
+
+* [Setup][12]
+ * [AWS][1]
+ * [GCP][2]
+ * [Azure][3]
+* [Run][13]
+ * [Ark server][9]
+ * [Basic example (no PVs)][10]
+ * [Snapshot example (with PVs)][11]
+
+
+## Setup
+### AWS
+
+#### IAM user creation
+
+To integrate Heptio Ark with AWS, you should follow the instructions below to create an Ark-specific [IAM user][14].
+
+1. If you do not have the AWS CLI locally installed, follow the [user guide][5] to set it up.
+
+2. Create an IAM user:
+
+ ```
+ aws iam create-user --user-name heptio-ark
+ ```
+
+3. Attach a policy to give `heptio-ark` the necessary permissions:
+
+ ```
+ aws iam attach-user-policy \
+ --policy-arn arn:aws:iam::aws:policy/AmazonS3FullAccess \
+ --user-name heptio-ark
+ aws iam attach-user-policy \
+ --policy-arn arn:aws:iam::aws:policy/AmazonEC2FullAccess \
+ --user-name heptio-ark
+ ```
+
+4. Create an access key for the user:
+
+ ```
+ aws iam create-access-key --user-name heptio-ark
+ ```
+
+ The result should look like:
+
+ ```
+ {
+ "AccessKey": {
+ "UserName": "heptio-ark",
+ "Status": "Active",
+ "CreateDate": "2017-07-31T22:24:41.576Z",
+ "SecretAccessKey": ,
+ "AccessKeyId":
+ }
+ }
+ ```
+5. Using the output from the previous command, create an Ark-specific credentials file (`credentials-ark`) in your local directory that looks like the following:
+
+ ```
+ [default]
+ aws_access_key_id=
+ aws_secret_access_key= |
+ {% endif %}
+ 
+