From 5235036ba504ca4792224cf2c0bb5b8108502041 Mon Sep 17 00:00:00 2001
From: Mike Pirog <mike@thinktandem.io>
Date: Wed, 3 Nov 2021 09:02:45 -0400
Subject: [PATCH 01/16] #130: Doc PR tests

---
 .github/workflows/pr-docs-tests.yml | 31 +++++++++++++++++++++++++++++
 1 file changed, 31 insertions(+)
 create mode 100644 .github/workflows/pr-docs-tests.yml

diff --git a/.github/workflows/pr-docs-tests.yml b/.github/workflows/pr-docs-tests.yml
new file mode 100644
index 0000000..f568096
--- /dev/null
+++ b/.github/workflows/pr-docs-tests.yml
@@ -0,0 +1,31 @@
+name: Run Docs Tests
+
+on:
+  pull_request:
+
+jobs:
+  unit-tests:
+    runs-on: ${{ matrix.os }}
+    strategy:
+      matrix:
+        os:
+          - ubuntu-20.04
+        node-version:
+          - '14'
+    steps:
+      # Install deps and cache
+      - name: Checkout code
+        uses: actions/checkout@v2
+      - name: Install node ${{ matrix.node-version }}
+        uses: actions/setup-node@v2
+        with:
+          node-version: ${{ matrix.node-version }}
+          cache: yarn
+      - name: Install Yarn dependencies
+        run: yarn install --prefer-offline --frozen-lockfile
+
+      # Run tests
+      - name: Run linter
+        run: yarn docs:lint
+      - name: Test build
+        run: yarn docs:build

From 12afb20feac04192fd5e439ea6c1a4f5d10a56a6 Mon Sep 17 00:00:00 2001
From: Mike Pirog <mike@thinktandem.io>
Date: Wed, 3 Nov 2021 09:06:36 -0400
Subject: [PATCH 02/16] #130: Fix busted CarbonAds styling

---
 docs/.vuepress/config.js                      | 1 -
 docs/.vuepress/theme/components/CarbonAds.vue | 3 ---
 2 files changed, 4 deletions(-)

diff --git a/docs/.vuepress/config.js b/docs/.vuepress/config.js
index 3236eff..37ce31f 100644
--- a/docs/.vuepress/config.js
+++ b/docs/.vuepress/config.js
@@ -6,7 +6,6 @@ module.exports = {
   description: 'Lando Platform.sh Plugin Documentation',
   head: [
     ['link', {rel: 'icon', href: '/favicon.ico'}],
-    ['link', {rel: 'stylesheet', href: '/styles/overrides.css'}],
     ['link', {rel: 'stylesheet', href: '//fonts.googleapis.com/css?family=Poppins:700|Source+Sans+Pro&display=swap'}],
   ],
   theme: path.resolve(__dirname, 'theme'),
diff --git a/docs/.vuepress/theme/components/CarbonAds.vue b/docs/.vuepress/theme/components/CarbonAds.vue
index 9061bd2..536d3b2 100644
--- a/docs/.vuepress/theme/components/CarbonAds.vue
+++ b/docs/.vuepress/theme/components/CarbonAds.vue
@@ -1,6 +1,3 @@
-<template>
-  <div></div>
-</template>
 <script>
 import { h } from 'vue';
 

From 6a83e8aa1ff3b56fb3592cac2d28a11a098a0ff5 Mon Sep 17 00:00:00 2001
From: Mike Pirog <mike@thinktandem.io>
Date: Wed, 3 Nov 2021 09:30:46 -0400
Subject: [PATCH 03/16] #130: Test git plugin on netlify

---
 docs/.vuepress/config.js      | 1 +
 docs/.vuepress/theme/index.js | 1 +
 2 files changed, 2 insertions(+)

diff --git a/docs/.vuepress/config.js b/docs/.vuepress/config.js
index 37ce31f..7b78d3d 100644
--- a/docs/.vuepress/config.js
+++ b/docs/.vuepress/config.js
@@ -11,6 +11,7 @@ module.exports = {
   theme: path.resolve(__dirname, 'theme'),
   themeConfig: {
     logo: '/images/logo-pink-small.png',
+    repo: 'lando/platformsh',
     navbar: [
       {text: 'Getting Started', link: 'https://docs.lando.dev/basics/'},
       {text: 'Config', link: '/config/lando.md'},
diff --git a/docs/.vuepress/theme/index.js b/docs/.vuepress/theme/index.js
index 5cf2d52..b6475b3 100644
--- a/docs/.vuepress/theme/index.js
+++ b/docs/.vuepress/theme/index.js
@@ -1,6 +1,7 @@
 const {path} = require('@vuepress/utils');
 
 module.exports = (options, app) => {
+  // console.log(options);
   return {
     name: '@lando/vuepress-docs-theme',
     extends: '@vuepress/theme-default',

From 40965ee442236ec6c4e40866d9f28cb6fe27ac54 Mon Sep 17 00:00:00 2001
From: Mike Pirog <mike@thinktandem.io>
Date: Wed, 3 Nov 2021 10:27:36 -0400
Subject: [PATCH 04/16] #130: Make CarbonAds configurable and eslint update

---
 .eslintrc.json                          |  5 ++++-
 app.js                                  |  6 +++---
 docs/.eslintrc.json                     |  4 +++-
 docs/.vuepress/config.js                |  2 ++
 docs/.vuepress/theme/index.js           | 18 ++++++++++++++++++
 docs/.vuepress/theme/layouts/Layout.vue | 18 ++++++++++--------
 package.json                            |  1 +
 yarn.lock                               | 11 ++++++++++-
 8 files changed, 51 insertions(+), 14 deletions(-)

diff --git a/.eslintrc.json b/.eslintrc.json
index 6865388..18ddef1 100644
--- a/.eslintrc.json
+++ b/.eslintrc.json
@@ -3,8 +3,11 @@
     "node": true,
     "mocha": true
   },
+  "parser": "@babel/eslint-parser",
   "parserOptions": {
-    "ecmaVersion": 6
+    "sourceType": "module",
+    "ecmaVersion": 8,
+    "requireConfigFile": false
   },
   "extends": "google",
   "rules": {
diff --git a/app.js b/app.js
index 6ac89ae..5213a68 100644
--- a/app.js
+++ b/app.js
@@ -140,7 +140,7 @@ module.exports = (app, lando) => {
       // Add relationships keyed by the service name
       app.platformsh.relationships = pshconf.parseRelationships(
         platformConfig.applications,
-        app.platformsh.closestOpenCache
+        app.platformsh.closestOpenCache,
       );
       app.log.verbose('determined platformsh relationships');
       app.log.silly('platformsh relationships are', app.platformsh.relationships);
@@ -153,7 +153,7 @@ module.exports = (app, lando) => {
       // Figure out what relationships are pullable and not
       app.platformsh.closestApp.syncableRelationships = pshconf.getSyncableRelationships(
         app.platformsh.closestApp.relationships,
-        app.platformsh.services
+        app.platformsh.services,
       );
 
       // Go through our platform config and generate an array of configuration files for each
@@ -258,7 +258,7 @@ module.exports = (app, lando) => {
           serviceTooling: tooling.getServiceTooling(
             application.serviceContainers,
             application.openData,
-            application.name
+            application.name,
           ),
         }))
         // Merge it all together
diff --git a/docs/.eslintrc.json b/docs/.eslintrc.json
index 29eb114..25a5930 100644
--- a/docs/.eslintrc.json
+++ b/docs/.eslintrc.json
@@ -1,7 +1,9 @@
 {
+  "parser": "@babel/eslint-parser",
   "parserOptions": {
     "sourceType": "module",
-    "ecmaVersion": 6
+    "ecmaVersion": 8,
+    "requireConfigFile": false
   },
   "extends": [
     "plugin:vue/recommended",
diff --git a/docs/.vuepress/config.js b/docs/.vuepress/config.js
index 7b78d3d..c3aa78b 100644
--- a/docs/.vuepress/config.js
+++ b/docs/.vuepress/config.js
@@ -12,6 +12,8 @@ module.exports = {
   themeConfig: {
     logo: '/images/logo-pink-small.png',
     repo: 'lando/platformsh',
+    docsDir: 'docs',
+    docsBranch: 'main',
     navbar: [
       {text: 'Getting Started', link: 'https://docs.lando.dev/basics/'},
       {text: 'Config', link: '/config/lando.md'},
diff --git a/docs/.vuepress/theme/index.js b/docs/.vuepress/theme/index.js
index b6475b3..8b517bb 100644
--- a/docs/.vuepress/theme/index.js
+++ b/docs/.vuepress/theme/index.js
@@ -2,6 +2,22 @@ const {path} = require('@vuepress/utils');
 
 module.exports = (options, app) => {
   // console.log(options);
+
+  // Define default options
+  const defaultOptions = {
+    // Shows the CarbonAds in the top sidebar
+    showCarbonAds: true,
+    // Shows the special sponsors on the right
+    // Can be true|false|or a list of sponsors to show
+    // showSponsors: ['platformsh'],
+    // Metadata for our sponsors
+    // sponsors:
+  };
+
+  // Merge together
+  options = {...defaultOptions, ...options};
+  console.log(options);
+
   return {
     name: '@lando/vuepress-docs-theme',
     extends: '@vuepress/theme-default',
@@ -14,6 +30,8 @@ module.exports = (options, app) => {
     //   console.log('hi');
     //   console.log(md.renderer);
     // },
+    // extendsPageData: page => {
+    // },
     plugins: [
       [
         '@vuepress/plugin-palette',
diff --git a/docs/.vuepress/theme/layouts/Layout.vue b/docs/.vuepress/theme/layouts/Layout.vue
index 3caf9d4..f47c587 100644
--- a/docs/.vuepress/theme/layouts/Layout.vue
+++ b/docs/.vuepress/theme/layouts/Layout.vue
@@ -1,20 +1,22 @@
 <template>
   <ParentLayout>
     <template #sidebar-top>
-      <CarbonAds />
+      <CarbonAds v-if="showCarbonAds" />
     </template>
   </ParentLayout>
 </template>
 
-<script>
+<script setup>
+import { computed } from 'vue'
 import ParentLayout from '@vuepress/theme-default/lib/client/layouts/Layout.vue'
 import CarbonAds from '../components/CarbonAds.vue';
-export default {
-  components: {
-    ParentLayout,
-    CarbonAds,
-  },
-};
+import { useThemeData } from '@vuepress/plugin-theme-data/lib/client'
+
+// Get theme data
+const themeData = useThemeData();
+// Get the config from themedata
+const {showCarbonAds = true} = themeData.value;
+
 </script>
 
 <style lang="scss">
diff --git a/package.json b/package.json
index 2e118d6..5de0e4a 100644
--- a/package.json
+++ b/package.json
@@ -47,6 +47,7 @@
     "tar": "^6.1.11"
   },
   "devDependencies": {
+    "@babel/eslint-parser": "^7.16.0",
     "@lando/leia": "^0.6.4",
     "chai": "^4.3.4",
     "command-line-test": "^1.0.10",
diff --git a/yarn.lock b/yarn.lock
index 96ea2e2..d105bbd 100644
--- a/yarn.lock
+++ b/yarn.lock
@@ -49,6 +49,15 @@
     semver "^6.3.0"
     source-map "^0.5.0"
 
+"@babel/eslint-parser@^7.16.0":
+  version "7.16.0"
+  resolved "https://registry.yarnpkg.com/@babel/eslint-parser/-/eslint-parser-7.16.0.tgz#032cf6c8d844a95ad62f779d2708fb4f77e1a81c"
+  integrity sha512-c+AsYOHjI+FgCa+ifLd8sDXp4U4mjkfFgL9NdQWhuA731kAUJs0WdJIXET4A14EJAR9Jv9FFF/MzPWJfV9Oirw==
+  dependencies:
+    eslint-scope "^5.1.1"
+    eslint-visitor-keys "^2.1.0"
+    semver "^6.3.0"
+
 "@babel/generator@^7.15.4":
   version "7.15.4"
   resolved "https://registry.yarnpkg.com/@babel/generator/-/generator-7.15.4.tgz#85acb159a267ca6324f9793986991ee2022a05b0"
@@ -2262,7 +2271,7 @@ eslint-visitor-keys@^1.1.0, eslint-visitor-keys@^1.3.0:
   resolved "https://registry.yarnpkg.com/eslint-visitor-keys/-/eslint-visitor-keys-1.3.0.tgz#30ebd1ef7c2fdff01c3a4f151044af25fab0523e"
   integrity sha512-6J72N8UNa462wa/KFODt/PJ3IU60SDpC3QXC1Hjc1BXXpfL2C9R5+AU7jhe0F6GREqVMh4Juu+NY7xn+6dipUQ==
 
-eslint-visitor-keys@^2.0.0:
+eslint-visitor-keys@^2.0.0, eslint-visitor-keys@^2.1.0:
   version "2.1.0"
   resolved "https://registry.yarnpkg.com/eslint-visitor-keys/-/eslint-visitor-keys-2.1.0.tgz#f65328259305927392c938ed44eb0a5c9b2bd303"
   integrity sha512-0rSmRBzXgDzIsD6mGdJgevzgezI534Cer5L/vyMX0kHzT/jiB43jRhd9YUlMGYLQy2zprNmoT8qasCGtY+QaKw==

From 1539136f26b758b30b56af016b6f8b28071625f6 Mon Sep 17 00:00:00 2001
From: John Ouellet <john@thinktandem.io>
Date: Wed, 3 Nov 2021 13:26:53 -0400
Subject: [PATCH 05/16] #130 Add in start of sponsorship display

---
 docs/.vuepress/config.js                     |  1 +
 docs/.vuepress/theme/components/Sponsors.vue | 61 ++++++++++++++++++++
 docs/.vuepress/theme/index.js                |  2 +-
 docs/.vuepress/theme/layouts/Layout.vue      | 31 ++++++++++
 4 files changed, 94 insertions(+), 1 deletion(-)
 create mode 100644 docs/.vuepress/theme/components/Sponsors.vue

diff --git a/docs/.vuepress/config.js b/docs/.vuepress/config.js
index c3aa78b..c1ed0eb 100644
--- a/docs/.vuepress/config.js
+++ b/docs/.vuepress/config.js
@@ -14,6 +14,7 @@ module.exports = {
     repo: 'lando/platformsh',
     docsDir: 'docs',
     docsBranch: 'main',
+    showSponsors: ['Platform.sh'],
     navbar: [
       {text: 'Getting Started', link: 'https://docs.lando.dev/basics/'},
       {text: 'Config', link: '/config/lando.md'},
diff --git a/docs/.vuepress/theme/components/Sponsors.vue b/docs/.vuepress/theme/components/Sponsors.vue
new file mode 100644
index 0000000..d775739
--- /dev/null
+++ b/docs/.vuepress/theme/components/Sponsors.vue
@@ -0,0 +1,61 @@
+<template>
+  <div id="special_sponsors">
+    <h4>special sponsors</h4>
+    <div class="special-sponsor-block" v-for="(patriot, index) in patriots" :key="index">
+      <a :href="patriot.url" target="_blank">
+        <div class="special-sponsor-image"><img :src="patriot.logo" :alt="patriot.name"></div>
+      </a>
+    </div>
+    <div class="special-sponsor-footer">
+      <a href="https://lando.dev/sponsor" target="_blank">become a sponsor</a>
+    </div>
+  </div>
+</template>
+
+
+<script>
+import {filter} from 'lodash';
+export default {
+  props: [
+    'sponsors',
+    'showSponsors'
+  ],
+  data() {
+    return {
+      patriots: [],
+    };
+  },
+  mounted() {
+    this.patriots = !Array.isArray(this.showSponsors) 
+      ? this.sponsors
+      : filter(this.sponsors, sponsor => {
+          return this.showSponsors.includes(sponsor.name);
+      });
+  },
+};
+</script>
+
+<style lang="scss">
+  #special_sponsors {
+    padding: 3em;
+    position: absolute;
+    right: 2em;
+    top: 6em;
+    width: 150px;
+    background: white;
+    opacity: .75;
+    text-align: center;
+    font-size: .8em;
+  }
+  .special-sponsor-block {
+    img {
+      width: 100px;
+      padding-bottom: 2em;
+    }
+  }
+  @media (max-width: 1300px) {
+    #special_sponsors {
+      display: none;
+    }
+  }
+</style>
\ No newline at end of file
diff --git a/docs/.vuepress/theme/index.js b/docs/.vuepress/theme/index.js
index 8b517bb..f60b6a6 100644
--- a/docs/.vuepress/theme/index.js
+++ b/docs/.vuepress/theme/index.js
@@ -9,7 +9,7 @@ module.exports = (options, app) => {
     showCarbonAds: true,
     // Shows the special sponsors on the right
     // Can be true|false|or a list of sponsors to show
-    // showSponsors: ['platformsh'],
+    showSponsors: true,
     // Metadata for our sponsors
     // sponsors:
   };
diff --git a/docs/.vuepress/theme/layouts/Layout.vue b/docs/.vuepress/theme/layouts/Layout.vue
index f47c587..fa9cbfe 100644
--- a/docs/.vuepress/theme/layouts/Layout.vue
+++ b/docs/.vuepress/theme/layouts/Layout.vue
@@ -3,6 +3,9 @@
     <template #sidebar-top>
       <CarbonAds v-if="showCarbonAds" />
     </template>
+    <template #page-top>
+      <Sponsors v-if="showSponsors" :sponsors="sponsors" :showSponsors="showSponsors" />
+    </template>
   </ParentLayout>
 </template>
 
@@ -10,12 +13,40 @@
 import { computed } from 'vue'
 import ParentLayout from '@vuepress/theme-default/lib/client/layouts/Layout.vue'
 import CarbonAds from '../components/CarbonAds.vue';
+import Sponsors from '../components/Sponsors.vue';
 import { useThemeData } from '@vuepress/plugin-theme-data/lib/client'
 
 // Get theme data
 const themeData = useThemeData();
 // Get the config from themedata
 const {showCarbonAds = true} = themeData.value;
+const {showSponsors = true} = themeData.value;
+const sponsors = [
+  {
+    "name": "Platform.sh",
+    "type": "patriot",
+    "url": "https://platform.sh",
+    "logo": "https://lando.dev/images/platform_sh_logo.png"
+  },
+  {
+    "name": "amazee.io",
+    "type": "patriot",
+    "url": "https://www.amazee.io/",
+    "logo": "https://lando.dev/images/amazee_io_logo.png"
+  },
+  {
+    "name": "Pantheon",
+    "type": "patriot",
+    "url": "https://pantheon.io/",
+    "logo": "https://lando.dev/images/pantheon_logo.png"
+  },
+  {
+    "name": "Blackmesh by Contegix",
+    "type": "patriot",
+    "url": "https://www.blackmesh.com/",
+    "logo": "https://lando.dev/images/blackmesh_logo.png"
+  },
+];
 
 </script>
 

From c47ecaeac693b8fee443546ed83803b5ce168a6b Mon Sep 17 00:00:00 2001
From: John Ouellet <john@thinktandem.io>
Date: Wed, 3 Nov 2021 14:52:50 -0400
Subject: [PATCH 06/16] #130 convert components to use vue3 setup style

---
 docs/.vuepress/config.js                     | 32 +++++++++++++++++++-
 docs/.vuepress/theme/components/Sponsors.vue | 32 +++++++++++++-------
 docs/.vuepress/theme/layouts/Layout.vue      | 28 +----------------
 3 files changed, 53 insertions(+), 39 deletions(-)

diff --git a/docs/.vuepress/config.js b/docs/.vuepress/config.js
index c1ed0eb..74ed900 100644
--- a/docs/.vuepress/config.js
+++ b/docs/.vuepress/config.js
@@ -12,9 +12,39 @@ module.exports = {
   themeConfig: {
     logo: '/images/logo-pink-small.png',
     repo: 'lando/platformsh',
+    sponsors: [
+      {
+        "name": "Platform.sh",
+        "id": "platformsh",
+        "type": "patriot",
+        "url": "https://platform.sh",
+        "logo": "https://lando.dev/images/platform_sh_logo.png"
+      },
+      {
+        "name": "amazee.io",
+        "id": "amazeeio",
+        "type": "patriot",
+        "url": "https://www.amazee.io/",
+        "logo": "https://lando.dev/images/amazee_io_logo.png"
+      },
+      {
+        "name": "Pantheon",
+        "id": "pantheon",
+        "type": "patriot",
+        "url": "https://pantheon.io/",
+        "logo": "https://lando.dev/images/pantheon_logo.png"
+      },
+      {
+        "name": "Blackmesh by Contegix",
+        "id": "blackmesh",
+        "type": "patriot",
+        "url": "https://www.blackmesh.com/",
+        "logo": "https://lando.dev/images/blackmesh_logo.png"
+      }
+    ],
     docsDir: 'docs',
     docsBranch: 'main',
-    showSponsors: ['Platform.sh'],
+    showSponsors: ['platformsh'],
     navbar: [
       {text: 'Getting Started', link: 'https://docs.lando.dev/basics/'},
       {text: 'Config', link: '/config/lando.md'},
diff --git a/docs/.vuepress/theme/components/Sponsors.vue b/docs/.vuepress/theme/components/Sponsors.vue
index d775739..76a7907 100644
--- a/docs/.vuepress/theme/components/Sponsors.vue
+++ b/docs/.vuepress/theme/components/Sponsors.vue
@@ -1,9 +1,9 @@
 <template>
   <div id="special_sponsors">
     <h4>special sponsors</h4>
-    <div class="special-sponsor-block" v-for="(patriot, index) in patriots" :key="index">
-      <a :href="patriot.url" target="_blank">
-        <div class="special-sponsor-image"><img :src="patriot.logo" :alt="patriot.name"></div>
+    <div class="special-sponsor-block" v-for="(sponsor, index) in sponsorList" :key="index">
+      <a :href="sponsor.url" target="_blank">
+        <div class="special-sponsor-image"><img :src="sponsor.logo" :alt="sponsor.name"></div>
       </a>
     </div>
     <div class="special-sponsor-footer">
@@ -14,22 +14,32 @@
 
 
 <script>
-import {filter} from 'lodash';
+import { filter } from 'lodash';
+import { useThemeData } from '@vuepress/plugin-theme-data/lib/client';
+
 export default {
-  props: [
-    'sponsors',
-    'showSponsors'
-  ],
   data() {
     return {
-      patriots: [],
+      sponsorList: [],
     };
   },
+  setup() {
+    // Get theme data
+    const themeData = useThemeData();
+    // Get the config from themedata
+    const {showSponsors = true} = themeData.value;
+    const {sponsors = []} = themeData.value;
+
+    return {
+      showSponsors,
+      sponsors
+    }
+  },
   mounted() {
-    this.patriots = !Array.isArray(this.showSponsors) 
+    this.sponsorList = !Array.isArray(this.showSponsors) 
       ? this.sponsors
       : filter(this.sponsors, sponsor => {
-          return this.showSponsors.includes(sponsor.name);
+          return this.showSponsors.includes(sponsor.id);
       });
   },
 };
diff --git a/docs/.vuepress/theme/layouts/Layout.vue b/docs/.vuepress/theme/layouts/Layout.vue
index fa9cbfe..18c6259 100644
--- a/docs/.vuepress/theme/layouts/Layout.vue
+++ b/docs/.vuepress/theme/layouts/Layout.vue
@@ -4,7 +4,7 @@
       <CarbonAds v-if="showCarbonAds" />
     </template>
     <template #page-top>
-      <Sponsors v-if="showSponsors" :sponsors="sponsors" :showSponsors="showSponsors" />
+      <Sponsors v-if="showSponsors" />
     </template>
   </ParentLayout>
 </template>
@@ -21,32 +21,6 @@ const themeData = useThemeData();
 // Get the config from themedata
 const {showCarbonAds = true} = themeData.value;
 const {showSponsors = true} = themeData.value;
-const sponsors = [
-  {
-    "name": "Platform.sh",
-    "type": "patriot",
-    "url": "https://platform.sh",
-    "logo": "https://lando.dev/images/platform_sh_logo.png"
-  },
-  {
-    "name": "amazee.io",
-    "type": "patriot",
-    "url": "https://www.amazee.io/",
-    "logo": "https://lando.dev/images/amazee_io_logo.png"
-  },
-  {
-    "name": "Pantheon",
-    "type": "patriot",
-    "url": "https://pantheon.io/",
-    "logo": "https://lando.dev/images/pantheon_logo.png"
-  },
-  {
-    "name": "Blackmesh by Contegix",
-    "type": "patriot",
-    "url": "https://www.blackmesh.com/",
-    "logo": "https://lando.dev/images/blackmesh_logo.png"
-  },
-];
 
 </script>
 

From 81bf07a1257f49b01ad165198e556d4521ec1ca8 Mon Sep 17 00:00:00 2001
From: John Ouellet <john@thinktandem.io>
Date: Wed, 3 Nov 2021 15:26:22 -0400
Subject: [PATCH 07/16] #130 Adjust mobile sponsor stuffs

---
 docs/.vuepress/config.js                     |  2 +-
 docs/.vuepress/theme/components/Sponsors.vue | 33 +++++++++++++++++---
 2 files changed, 29 insertions(+), 6 deletions(-)

diff --git a/docs/.vuepress/config.js b/docs/.vuepress/config.js
index 74ed900..4cc139e 100644
--- a/docs/.vuepress/config.js
+++ b/docs/.vuepress/config.js
@@ -44,7 +44,7 @@ module.exports = {
     ],
     docsDir: 'docs',
     docsBranch: 'main',
-    showSponsors: ['platformsh'],
+    //showSponsors: ['platformsh'],
     navbar: [
       {text: 'Getting Started', link: 'https://docs.lando.dev/basics/'},
       {text: 'Config', link: '/config/lando.md'},
diff --git a/docs/.vuepress/theme/components/Sponsors.vue b/docs/.vuepress/theme/components/Sponsors.vue
index 76a7907..b636578 100644
--- a/docs/.vuepress/theme/components/Sponsors.vue
+++ b/docs/.vuepress/theme/components/Sponsors.vue
@@ -1,11 +1,14 @@
 <template>
   <div id="special_sponsors">
     <h4>special sponsors</h4>
-    <div class="special-sponsor-block" v-for="(sponsor, index) in sponsorList" :key="index">
-      <a :href="sponsor.url" target="_blank">
-        <div class="special-sponsor-image"><img :src="sponsor.logo" :alt="sponsor.name"></div>
-      </a>
+    <div class="sponsor-wrapper">
+      <div class="special-sponsor-block" v-for="(sponsor, index) in sponsorList" :key="index">
+        <a :href="sponsor.url" target="_blank">
+          <div class="special-sponsor-image"><img :src="sponsor.logo" :alt="sponsor.name"></div>
+        </a>
+      </div>
     </div>
+
     <div class="special-sponsor-footer">
       <a href="https://lando.dev/sponsor" target="_blank">become a sponsor</a>
     </div>
@@ -65,7 +68,27 @@ export default {
   }
   @media (max-width: 1300px) {
     #special_sponsors {
-      display: none;
+      position: initial;
+      padding: 1em;
+      right: initial;
+      top: initial;
+      width: initial;
+      .sponsor-wrapper {
+        display: flex;
+        justify-content: center;
+        .special-sponsor-block {
+          margin-top: auto;
+          margin-bottom: auto;
+          padding-right: 1em;
+          img {
+            height: auto;
+            padding: 0;
+          }
+        }
+      }
+      .special-sponsor-footer {
+        padding-top: 2em;
+      }
     }
   }
 </style>
\ No newline at end of file

From ef8403a9c357ce0c55e6d701f6dd071b7cd39d63 Mon Sep 17 00:00:00 2001
From: John Ouellet <john@thinktandem.io>
Date: Wed, 3 Nov 2021 16:05:15 -0400
Subject: [PATCH 08/16] #130 Add in sponsor file

---
 docs/.vuepress/config.js               | 35 +++-----------------------
 docs/.vuepress/public/api/sponsors.yml | 20 +++++++++++++++
 2 files changed, 24 insertions(+), 31 deletions(-)
 create mode 100644 docs/.vuepress/public/api/sponsors.yml

diff --git a/docs/.vuepress/config.js b/docs/.vuepress/config.js
index 4cc139e..01d974f 100644
--- a/docs/.vuepress/config.js
+++ b/docs/.vuepress/config.js
@@ -1,4 +1,6 @@
 const {path} = require('@vuepress/utils');
+const yaml = require('js-yaml');
+const fs = require('fs');
 
 module.exports = {
   lang: 'en-US',
@@ -12,39 +14,10 @@ module.exports = {
   themeConfig: {
     logo: '/images/logo-pink-small.png',
     repo: 'lando/platformsh',
-    sponsors: [
-      {
-        "name": "Platform.sh",
-        "id": "platformsh",
-        "type": "patriot",
-        "url": "https://platform.sh",
-        "logo": "https://lando.dev/images/platform_sh_logo.png"
-      },
-      {
-        "name": "amazee.io",
-        "id": "amazeeio",
-        "type": "patriot",
-        "url": "https://www.amazee.io/",
-        "logo": "https://lando.dev/images/amazee_io_logo.png"
-      },
-      {
-        "name": "Pantheon",
-        "id": "pantheon",
-        "type": "patriot",
-        "url": "https://pantheon.io/",
-        "logo": "https://lando.dev/images/pantheon_logo.png"
-      },
-      {
-        "name": "Blackmesh by Contegix",
-        "id": "blackmesh",
-        "type": "patriot",
-        "url": "https://www.blackmesh.com/",
-        "logo": "https://lando.dev/images/blackmesh_logo.png"
-      }
-    ],
+    sponsors: yaml.load(fs.readFileSync(path.resolve(__dirname, 'public') + '/api/sponsors.yml', 'utf8')),
     docsDir: 'docs',
     docsBranch: 'main',
-    //showSponsors: ['platformsh'],
+    showSponsors: ['platformsh'],
     navbar: [
       {text: 'Getting Started', link: 'https://docs.lando.dev/basics/'},
       {text: 'Config', link: '/config/lando.md'},
diff --git a/docs/.vuepress/public/api/sponsors.yml b/docs/.vuepress/public/api/sponsors.yml
new file mode 100644
index 0000000..d5e8976
--- /dev/null
+++ b/docs/.vuepress/public/api/sponsors.yml
@@ -0,0 +1,20 @@
+- name: Platform.sh
+  id: platformsh
+  type: patriot
+  url: https://platform.sh
+  logo: https://lando.dev/images/platform_sh_logo.png
+- name: amazee.io
+  id: amazeeio
+  type: patriot
+  url: https://www.amazee.io/
+  logo: https://lando.dev/images/amazee_io_logo.png
+- name: Pantheon
+  id: pantheon
+  type: patriot
+  url: https://pantheon.io/
+  logo: https://lando.dev/images/pantheon_logo.png
+- name: Blackmesh by Contegix
+  id: blackmesh
+  type: patriot
+  url: https://www.blackmesh.com/
+  logo: https://lando.dev/images/blackmesh_logo.png
\ No newline at end of file

From 9b868d690cc18ca7e24240bbae83e960c9573d4d Mon Sep 17 00:00:00 2001
From: John Ouellet <john@thinktandem.io>
Date: Wed, 3 Nov 2021 16:16:00 -0400
Subject: [PATCH 09/16] #130 Mobile CSS tweak

---
 docs/.vuepress/theme/components/Sponsors.vue | 3 +++
 1 file changed, 3 insertions(+)

diff --git a/docs/.vuepress/theme/components/Sponsors.vue b/docs/.vuepress/theme/components/Sponsors.vue
index b636578..c9b607c 100644
--- a/docs/.vuepress/theme/components/Sponsors.vue
+++ b/docs/.vuepress/theme/components/Sponsors.vue
@@ -80,6 +80,9 @@ export default {
           margin-top: auto;
           margin-bottom: auto;
           padding-right: 1em;
+          &:last-of-type {
+            padding-right: 0;
+          }
           img {
             height: auto;
             padding: 0;

From e91fcd050c79aede5be6264e61d8379f6747a623 Mon Sep 17 00:00:00 2001
From: Mike Pirog <mike@thinktandem.io>
Date: Wed, 3 Nov 2021 19:49:16 -0400
Subject: [PATCH 10/16] #130: Dark mode for carbon adds and trim some fat

---
 docs/.vuepress/config.js                      | 6 ++++--
 docs/.vuepress/public/api/sponsors.yml        | 6 +-----
 docs/.vuepress/theme/components/CarbonAds.vue | 5 +++++
 3 files changed, 10 insertions(+), 7 deletions(-)

diff --git a/docs/.vuepress/config.js b/docs/.vuepress/config.js
index 01d974f..0997f7c 100644
--- a/docs/.vuepress/config.js
+++ b/docs/.vuepress/config.js
@@ -14,10 +14,12 @@ module.exports = {
   themeConfig: {
     logo: '/images/logo-pink-small.png',
     repo: 'lando/platformsh',
-    sponsors: yaml.load(fs.readFileSync(path.resolve(__dirname, 'public') + '/api/sponsors.yml', 'utf8')),
     docsDir: 'docs',
     docsBranch: 'main',
-    showSponsors: ['platformsh'],
+    sponsors: yaml.load(fs.readFileSync(path.resolve(__dirname, 'public') + '/api/sponsors.yml', 'utf8')),
+    // showSponsors: ['platformsh'],
+    showCarbonAds: true,
+    showSponsors: true,
     navbar: [
       {text: 'Getting Started', link: 'https://docs.lando.dev/basics/'},
       {text: 'Config', link: '/config/lando.md'},
diff --git a/docs/.vuepress/public/api/sponsors.yml b/docs/.vuepress/public/api/sponsors.yml
index d5e8976..516c19f 100644
--- a/docs/.vuepress/public/api/sponsors.yml
+++ b/docs/.vuepress/public/api/sponsors.yml
@@ -1,20 +1,16 @@
 - name: Platform.sh
   id: platformsh
-  type: patriot
   url: https://platform.sh
   logo: https://lando.dev/images/platform_sh_logo.png
 - name: amazee.io
   id: amazeeio
-  type: patriot
   url: https://www.amazee.io/
   logo: https://lando.dev/images/amazee_io_logo.png
 - name: Pantheon
   id: pantheon
-  type: patriot
   url: https://pantheon.io/
   logo: https://lando.dev/images/pantheon_logo.png
 - name: Blackmesh by Contegix
   id: blackmesh
-  type: patriot
   url: https://www.blackmesh.com/
-  logo: https://lando.dev/images/blackmesh_logo.png
\ No newline at end of file
+  logo: https://lando.dev/images/blackmesh_logo.png
diff --git a/docs/.vuepress/theme/components/CarbonAds.vue b/docs/.vuepress/theme/components/CarbonAds.vue
index 536d3b2..587961f 100644
--- a/docs/.vuepress/theme/components/CarbonAds.vue
+++ b/docs/.vuepress/theme/components/CarbonAds.vue
@@ -66,6 +66,11 @@ export default {
 		margin-top: 0.5em;
 	}
 }
+.dark {
+  a.carbon-text {
+    color: var(--c-text-light);
+  }
+}
 @media (max-width: $MQMobile) {
   .carbon-ads .carbon-img img {
     width: 100px;

From ccb330ecb651c811483849d32b4043402a0668d6 Mon Sep 17 00:00:00 2001
From: John Ouellet <john@thinktandem.io>
Date: Thu, 4 Nov 2021 11:57:02 -0400
Subject: [PATCH 11/16] #130 add in start of search + adjust sponsor background

---
 docs/.vuepress/config.js                     |   9 +
 docs/.vuepress/theme/components/Sponsors.vue |   2 +-
 package.json                                 |   1 +
 yarn.lock                                    | 212 +++++++++++++++++++
 4 files changed, 223 insertions(+), 1 deletion(-)

diff --git a/docs/.vuepress/config.js b/docs/.vuepress/config.js
index 0997f7c..c626365 100644
--- a/docs/.vuepress/config.js
+++ b/docs/.vuepress/config.js
@@ -26,5 +26,14 @@ module.exports = {
       {text: 'Guides', link: '/guides/lando-101/lando-overview'},
       {text: 'Help and Support', link: '/help/logs/'},
     ],
+    plugins: [
+      [
+        '@vuepress/docsearch',
+        {
+          apiKey: '15e332850128e9ec96929f44c62f6c88',
+          indexName: 'lando',
+        },
+      ],
+    ]
   },
 };
diff --git a/docs/.vuepress/theme/components/Sponsors.vue b/docs/.vuepress/theme/components/Sponsors.vue
index c9b607c..e640fc9 100644
--- a/docs/.vuepress/theme/components/Sponsors.vue
+++ b/docs/.vuepress/theme/components/Sponsors.vue
@@ -55,7 +55,7 @@ export default {
     right: 2em;
     top: 6em;
     width: 150px;
-    background: white;
+    background: transparent;
     opacity: .75;
     text-align: center;
     font-size: .8em;
diff --git a/package.json b/package.json
index 5de0e4a..4601758 100644
--- a/package.json
+++ b/package.json
@@ -49,6 +49,7 @@
   "devDependencies": {
     "@babel/eslint-parser": "^7.16.0",
     "@lando/leia": "^0.6.4",
+    "@vuepress/plugin-docsearch": "^2.0.0-beta.27",
     "chai": "^4.3.4",
     "command-line-test": "^1.0.10",
     "eslint": "^7.32.0",
diff --git a/yarn.lock b/yarn.lock
index d105bbd..60c06e3 100644
--- a/yarn.lock
+++ b/yarn.lock
@@ -2,6 +2,129 @@
 # yarn lockfile v1
 
 
+"@algolia/autocomplete-core@1.0.0-alpha.44":
+  version "1.0.0-alpha.44"
+  resolved "https://registry.yarnpkg.com/@algolia/autocomplete-core/-/autocomplete-core-1.0.0-alpha.44.tgz#e626dba45f5f3950d6beb0ab055395ef0f7e8bb2"
+  integrity sha512-2iMXthldMIDXtlbg9omRKLgg1bLo2ZzINAEqwhNjUeyj1ceEyL1ck6FY0VnJpf2LsjmNthHCz2BuFk+nYUeDNA==
+  dependencies:
+    "@algolia/autocomplete-shared" "1.0.0-alpha.44"
+
+"@algolia/autocomplete-preset-algolia@1.0.0-alpha.44":
+  version "1.0.0-alpha.44"
+  resolved "https://registry.yarnpkg.com/@algolia/autocomplete-preset-algolia/-/autocomplete-preset-algolia-1.0.0-alpha.44.tgz#0ea0b255d0be10fbe262e281472dd6e4619b62ba"
+  integrity sha512-DCHwo5ovzg9k2ejUolGNTLFnIA7GpsrkbNJTy1sFbMnYfBmeK8egZPZnEl7lBTr27OaZu7IkWpTepLVSztZyng==
+  dependencies:
+    "@algolia/autocomplete-shared" "1.0.0-alpha.44"
+
+"@algolia/autocomplete-shared@1.0.0-alpha.44":
+  version "1.0.0-alpha.44"
+  resolved "https://registry.yarnpkg.com/@algolia/autocomplete-shared/-/autocomplete-shared-1.0.0-alpha.44.tgz#db13902ad1667e455711b77d08cae1a0feafaa48"
+  integrity sha512-2oQZPERYV+yNx/yoVWYjZZdOqsitJ5dfxXJjL18yczOXH6ujnsq+DTczSrX+RjzjQdVeJ1UAG053EJQF/FOiMg==
+
+"@algolia/cache-browser-local-storage@4.11.0":
+  version "4.11.0"
+  resolved "https://registry.yarnpkg.com/@algolia/cache-browser-local-storage/-/cache-browser-local-storage-4.11.0.tgz#1c168add00b398a860db6c86039e33b2843a9425"
+  integrity sha512-4sr9vHIG1fVA9dONagdzhsI/6M5mjs/qOe2xUP0yBmwsTsuwiZq3+Xu6D3dsxsuFetcJgC6ydQoCW8b7fDJHYQ==
+  dependencies:
+    "@algolia/cache-common" "4.11.0"
+
+"@algolia/cache-common@4.11.0":
+  version "4.11.0"
+  resolved "https://registry.yarnpkg.com/@algolia/cache-common/-/cache-common-4.11.0.tgz#066fe6d58b18e4b028dbef9bb8de07c5e22a3594"
+  integrity sha512-lODcJRuPXqf+6mp0h6bOxPMlbNoyn3VfjBVcQh70EDP0/xExZbkpecgHyyZK4kWg+evu+mmgvTK3GVHnet/xKw==
+
+"@algolia/cache-in-memory@4.11.0":
+  version "4.11.0"
+  resolved "https://registry.yarnpkg.com/@algolia/cache-in-memory/-/cache-in-memory-4.11.0.tgz#763c8cb655e6fd2261588e04214fca0959ac07c1"
+  integrity sha512-aBz+stMSTBOBaBEQ43zJXz2DnwS7fL6dR0e2myehAgtfAWlWwLDHruc/98VOy1ZAcBk1blE2LCU02bT5HekGxQ==
+  dependencies:
+    "@algolia/cache-common" "4.11.0"
+
+"@algolia/client-account@4.11.0":
+  version "4.11.0"
+  resolved "https://registry.yarnpkg.com/@algolia/client-account/-/client-account-4.11.0.tgz#67fadd3b0802b013ebaaa4b47bb7babae892374e"
+  integrity sha512-jwmFBoUSzoMwMqgD3PmzFJV/d19p1RJXB6C1ADz4ju4mU7rkaQLtqyZroQpheLoU5s5Tilmn/T8/0U2XLoJCRQ==
+  dependencies:
+    "@algolia/client-common" "4.11.0"
+    "@algolia/client-search" "4.11.0"
+    "@algolia/transporter" "4.11.0"
+
+"@algolia/client-analytics@4.11.0":
+  version "4.11.0"
+  resolved "https://registry.yarnpkg.com/@algolia/client-analytics/-/client-analytics-4.11.0.tgz#cbdc8128205e2da749cafc79e54708d14c413974"
+  integrity sha512-v5U9585aeEdYml7JqggHAj3E5CQ+jPwGVztPVhakBk8H/cmLyPS2g8wvmIbaEZCHmWn4TqFj3EBHVYxAl36fSA==
+  dependencies:
+    "@algolia/client-common" "4.11.0"
+    "@algolia/client-search" "4.11.0"
+    "@algolia/requester-common" "4.11.0"
+    "@algolia/transporter" "4.11.0"
+
+"@algolia/client-common@4.11.0":
+  version "4.11.0"
+  resolved "https://registry.yarnpkg.com/@algolia/client-common/-/client-common-4.11.0.tgz#9a2d1f6f8eaad25ba5d6d4ce307ba5bd84e6f999"
+  integrity sha512-Qy+F+TZq12kc7tgfC+FM3RvYH/Ati7sUiUv/LkvlxFwNwNPwWGoZO81AzVSareXT/ksDDrabD4mHbdTbBPTRmQ==
+  dependencies:
+    "@algolia/requester-common" "4.11.0"
+    "@algolia/transporter" "4.11.0"
+
+"@algolia/client-personalization@4.11.0":
+  version "4.11.0"
+  resolved "https://registry.yarnpkg.com/@algolia/client-personalization/-/client-personalization-4.11.0.tgz#d3bf0e760f85df876b4baf5b81996f0aa3a59940"
+  integrity sha512-mI+X5IKiijHAzf9fy8VSl/GTT67dzFDnJ0QAM8D9cMPevnfX4U72HRln3Mjd0xEaYUOGve8TK/fMg7d3Z5yG6g==
+  dependencies:
+    "@algolia/client-common" "4.11.0"
+    "@algolia/requester-common" "4.11.0"
+    "@algolia/transporter" "4.11.0"
+
+"@algolia/client-search@4.11.0":
+  version "4.11.0"
+  resolved "https://registry.yarnpkg.com/@algolia/client-search/-/client-search-4.11.0.tgz#c1105d715a2a04ba27231eca86f5d6620f68f4ae"
+  integrity sha512-iovPLc5YgiXBdw2qMhU65sINgo9umWbHFzInxoNErWnYoTQWfXsW6P54/NlKx5uscoLVjSf+5RUWwFu5BX+lpw==
+  dependencies:
+    "@algolia/client-common" "4.11.0"
+    "@algolia/requester-common" "4.11.0"
+    "@algolia/transporter" "4.11.0"
+
+"@algolia/logger-common@4.11.0":
+  version "4.11.0"
+  resolved "https://registry.yarnpkg.com/@algolia/logger-common/-/logger-common-4.11.0.tgz#bac1c2d59d29dee378b57412c8edd435b97de663"
+  integrity sha512-pRMJFeOY8hoWKIxWuGHIrqnEKN/kqKh7UilDffG/+PeEGxBuku+Wq5CfdTFG0C9ewUvn8mAJn5BhYA5k8y0Jqg==
+
+"@algolia/logger-console@4.11.0":
+  version "4.11.0"
+  resolved "https://registry.yarnpkg.com/@algolia/logger-console/-/logger-console-4.11.0.tgz#ced19e3abb22eb782ed5268d51efb5aa9ef109ef"
+  integrity sha512-wXztMk0a3VbNmYP8Kpc+F7ekuvaqZmozM2eTLok0XIshpAeZ/NJDHDffXK2Pw+NF0wmHqurptLYwKoikjBYvhQ==
+  dependencies:
+    "@algolia/logger-common" "4.11.0"
+
+"@algolia/requester-browser-xhr@4.11.0":
+  version "4.11.0"
+  resolved "https://registry.yarnpkg.com/@algolia/requester-browser-xhr/-/requester-browser-xhr-4.11.0.tgz#f9e1ad56f185432aa8dde8cad53ae271fd5d6181"
+  integrity sha512-Fp3SfDihAAFR8bllg8P5ouWi3+qpEVN5e7hrtVIYldKBOuI/qFv80Zv/3/AMKNJQRYglS4zWyPuqrXm58nz6KA==
+  dependencies:
+    "@algolia/requester-common" "4.11.0"
+
+"@algolia/requester-common@4.11.0":
+  version "4.11.0"
+  resolved "https://registry.yarnpkg.com/@algolia/requester-common/-/requester-common-4.11.0.tgz#d16de98d3ff72434bac39e4d915eab08035946a9"
+  integrity sha512-+cZGe/9fuYgGuxjaBC+xTGBkK7OIYdfapxhfvEf03dviLMPmhmVYFJtJlzAjQ2YmGDJpHrGgAYj3i/fbs8yhiA==
+
+"@algolia/requester-node-http@4.11.0":
+  version "4.11.0"
+  resolved "https://registry.yarnpkg.com/@algolia/requester-node-http/-/requester-node-http-4.11.0.tgz#beb2b6b68d5f4ce15aec80ede623f0ac96991368"
+  integrity sha512-qJIk9SHRFkKDi6dMT9hba8X1J1z92T5AZIgl+tsApjTGIRQXJLTIm+0q4yOefokfu4CoxYwRZ9QAq+ouGwfeOg==
+  dependencies:
+    "@algolia/requester-common" "4.11.0"
+
+"@algolia/transporter@4.11.0":
+  version "4.11.0"
+  resolved "https://registry.yarnpkg.com/@algolia/transporter/-/transporter-4.11.0.tgz#a8de3c173093ceceb02b26b577395ce3b3d4b96f"
+  integrity sha512-k4dyxiaEfYpw4UqybK9q7lrFzehygo6KV3OCYJMMdX0IMWV0m4DXdU27c1zYRYtthaFYaBzGF4Kjcl8p8vxCKw==
+  dependencies:
+    "@algolia/cache-common" "4.11.0"
+    "@algolia/logger-common" "4.11.0"
+    "@algolia/requester-common" "4.11.0"
+
 "@babel/code-frame@7.12.11":
   version "7.12.11"
   resolved "https://registry.yarnpkg.com/@babel/code-frame/-/code-frame-7.12.11.tgz#f4ad435aa263db935b8f10f2c552d23fb716a63f"
@@ -229,6 +352,29 @@
     "@babel/helper-validator-identifier" "^7.14.9"
     to-fast-properties "^2.0.0"
 
+"@docsearch/css@3.0.0-alpha.34":
+  version "3.0.0-alpha.34"
+  resolved "https://registry.yarnpkg.com/@docsearch/css/-/css-3.0.0-alpha.34.tgz#5d5c39955956e237884a9997eb29e28c8adc99fa"
+  integrity sha512-ZUbmxbN9gQp3vuBo9GDnm+ywB9aZQSh0ogjt6865PmeRUvyCCvgSwyZktliLPvAztoGX56qewQjxNcso3RrSow==
+
+"@docsearch/js@3.0.0-alpha.34":
+  version "3.0.0-alpha.34"
+  resolved "https://registry.yarnpkg.com/@docsearch/js/-/js-3.0.0-alpha.34.tgz#5c83a21b6f04bfb11fbf1d2a5175e6aa1365230f"
+  integrity sha512-6tQV/8FsDGo1tnubur0Rgh4dS1F5XU94WT0xfm628aSoQPizS7Q9ET+YJHzy40sIHlb4jI7v+bZwzo/D5fw/NA==
+  dependencies:
+    "@docsearch/react" "3.0.0-alpha.34"
+    preact "^10.0.0"
+
+"@docsearch/react@3.0.0-alpha.34":
+  version "3.0.0-alpha.34"
+  resolved "https://registry.yarnpkg.com/@docsearch/react/-/react-3.0.0-alpha.34.tgz#fb7e31e31593c26dadb607b9451d274b84b0b05a"
+  integrity sha512-BBVxu2qY1fyhxJfrGZvknFL6j1fJ3wLZvf2DsmVfmihu/RhYYnf8/C1gbc7RWX2fSoSzbQCcSuNbn4RvjuUJ+A==
+  dependencies:
+    "@algolia/autocomplete-core" "1.0.0-alpha.44"
+    "@algolia/autocomplete-preset-algolia" "1.0.0-alpha.44"
+    "@docsearch/css" "3.0.0-alpha.34"
+    algoliasearch "^4.0.0"
+
 "@eslint/eslintrc@^0.4.3":
   version "0.4.3"
   resolved "https://registry.yarnpkg.com/@eslint/eslintrc/-/eslintrc-0.4.3.tgz#9e42981ef035beb3dd49add17acb96e8ff6f394c"
@@ -518,6 +664,11 @@
   resolved "https://registry.yarnpkg.com/@types/parse-json/-/parse-json-4.0.0.tgz#2f8bb441434d163b35fb8ffdccd7138927ffb8c0"
   integrity sha512-//oorEZjL6sbPcKUaCdIGlIUeH26mgzimjBB77G6XRgnDl/L5wOnpyBGRe/Mmf5CVW3PwEBE1NjiMZ/ssFh4wA==
 
+"@types/prop-types@*":
+  version "15.7.4"
+  resolved "https://registry.yarnpkg.com/@types/prop-types/-/prop-types-15.7.4.tgz#fcf7205c25dff795ee79af1e30da2c9790808f11"
+  integrity sha512-rZ5drC/jWjrArrS8BR6SIr4cWpW09RNTYt9AMZo3Jwwif+iacXAqgVjm0B0Bv/S1jhDXKHqRVNCbACkJ89RAnQ==
+
 "@types/qs@*":
   version "6.9.7"
   resolved "https://registry.yarnpkg.com/@types/qs/-/qs-6.9.7.tgz#63bb7d067db107cc1e457c303bc25d511febf6cb"
@@ -528,11 +679,25 @@
   resolved "https://registry.yarnpkg.com/@types/range-parser/-/range-parser-1.2.4.tgz#cd667bcfdd025213aafb7ca5915a932590acdcdc"
   integrity sha512-EEhsLsD6UsDM1yFhAvy0Cjr6VwmpMWqFBCb9w07wVugF7w9nfajxLuVmngTIpgS6svCnm6Vaw+MZhoDCKnOfsw==
 
+"@types/react@^17.0.33":
+  version "17.0.34"
+  resolved "https://registry.yarnpkg.com/@types/react/-/react-17.0.34.tgz#797b66d359b692e3f19991b6b07e4b0c706c0102"
+  integrity sha512-46FEGrMjc2+8XhHXILr+3+/sTe3OfzSPU9YGKILLrUYbQ1CLQC9Daqo1KzENGXAWwrFwiY0l4ZbF20gRvgpWTg==
+  dependencies:
+    "@types/prop-types" "*"
+    "@types/scheduler" "*"
+    csstype "^3.0.2"
+
 "@types/retry@^0.12.0":
   version "0.12.1"
   resolved "https://registry.yarnpkg.com/@types/retry/-/retry-0.12.1.tgz#d8f1c0d0dc23afad6dc16a9e993a0865774b4065"
   integrity sha512-xoDlM2S4ortawSWORYqsdU+2rxdh4LRW9ytc3zmT37RIKQh6IHyKwwtKhKis9ah8ol07DCkZxPt8BBvPjC6v4g==
 
+"@types/scheduler@*":
+  version "0.16.2"
+  resolved "https://registry.yarnpkg.com/@types/scheduler/-/scheduler-0.16.2.tgz#1a62f89525723dde24ba1b01b092bf5df8ad4d39"
+  integrity sha512-hppQEBDmlwhFAXKJX2KnWLYu5yMfi91yazPb2l+lbJiwW+wdo1gNeRA+3RgNSO39WYX2euey41KEwnqesU2Jew==
+
 "@types/serve-static@*":
   version "1.13.10"
   resolved "https://registry.yarnpkg.com/@types/serve-static/-/serve-static-1.13.10.tgz#f5e0ce8797d2d7cc5ebeda48a52c96c4fa47a8d9"
@@ -761,6 +926,23 @@
     markdown-it "^12.2.0"
     markdown-it-container "^3.0.0"
 
+"@vuepress/plugin-docsearch@^2.0.0-beta.27":
+  version "2.0.0-beta.27"
+  resolved "https://registry.yarnpkg.com/@vuepress/plugin-docsearch/-/plugin-docsearch-2.0.0-beta.27.tgz#dea138646d39b72978baebeb20ea49dd08dc2984"
+  integrity sha512-r/YTwPfSBCFH4xCCpRKdQCoLpBJr5X9mXPOEJg8mjbeh5BsX1+5mcEDo8Rlk+iUQ+NoHt0KEoooIGnspGn0sEA==
+  dependencies:
+    "@docsearch/css" "3.0.0-alpha.34"
+    "@docsearch/js" "3.0.0-alpha.34"
+    "@docsearch/react" "3.0.0-alpha.34"
+    "@types/react" "^17.0.33"
+    "@vuepress/client" "2.0.0-beta.27"
+    "@vuepress/core" "2.0.0-beta.27"
+    "@vuepress/shared" "2.0.0-beta.27"
+    "@vuepress/utils" "2.0.0-beta.27"
+    preact "^10.5.15"
+    vue "^3.2.20"
+    vue-router "^4.0.12"
+
 "@vuepress/plugin-git@2.0.0-beta.27":
   version "2.0.0-beta.27"
   resolved "https://registry.yarnpkg.com/@vuepress/plugin-git/-/plugin-git-2.0.0-beta.27.tgz#dbead5658be76574863b3ef631ec9aaa656143b2"
@@ -1075,6 +1257,26 @@ ajv@^8.0.1:
     require-from-string "^2.0.2"
     uri-js "^4.2.2"
 
+algoliasearch@^4.0.0:
+  version "4.11.0"
+  resolved "https://registry.yarnpkg.com/algoliasearch/-/algoliasearch-4.11.0.tgz#234befb3ac355c094077f0edf3777240b1ee013c"
+  integrity sha512-IXRj8kAP2WrMmj+eoPqPc6P7Ncq1yZkFiyDrjTBObV1ADNL8Z/KdZ+dWC5MmYcBLAbcB/mMCpak5N/D1UIZvsA==
+  dependencies:
+    "@algolia/cache-browser-local-storage" "4.11.0"
+    "@algolia/cache-common" "4.11.0"
+    "@algolia/cache-in-memory" "4.11.0"
+    "@algolia/client-account" "4.11.0"
+    "@algolia/client-analytics" "4.11.0"
+    "@algolia/client-common" "4.11.0"
+    "@algolia/client-personalization" "4.11.0"
+    "@algolia/client-search" "4.11.0"
+    "@algolia/logger-common" "4.11.0"
+    "@algolia/logger-console" "4.11.0"
+    "@algolia/requester-browser-xhr" "4.11.0"
+    "@algolia/requester-common" "4.11.0"
+    "@algolia/requester-node-http" "4.11.0"
+    "@algolia/transporter" "4.11.0"
+
 ansi-colors@4.1.1, ansi-colors@^4.1.1:
   version "4.1.1"
   resolved "https://registry.yarnpkg.com/ansi-colors/-/ansi-colors-4.1.1.tgz#cbb9ae256bf750af1eab344f229aa27fe94ba348"
@@ -1753,6 +1955,11 @@ csstype@^2.6.8:
   resolved "https://registry.yarnpkg.com/csstype/-/csstype-2.6.18.tgz#980a8b53085f34af313410af064f2bd241784218"
   integrity sha512-RSU6Hyeg14am3Ah4VZEmeX8H7kLwEEirXe6aU2IPfKNvhXwTflK5HQRDNI0ypQXoqmm+QPyG2IaPuQE5zMwSIQ==
 
+csstype@^3.0.2:
+  version "3.0.9"
+  resolved "https://registry.yarnpkg.com/csstype/-/csstype-3.0.9.tgz#6410af31b26bd0520933d02cbc64fce9ce3fbf0b"
+  integrity sha512-rpw6JPxK6Rfg1zLOYCSwle2GFOOsnjmDYDaBwEcwoOg4qlsIVCN789VkBZDJAGi4T07gI4YSutR43t9Zz4Lzuw==
+
 debug@2.6.9:
   version "2.6.9"
   resolved "https://registry.yarnpkg.com/debug/-/debug-2.6.9.tgz#5d128515df134ff327e90a4c93f4e077a536341f"
@@ -4359,6 +4566,11 @@ postcss@^8.1.10, postcss@^8.2.15, postcss@^8.3.11:
     picocolors "^1.0.0"
     source-map-js "^0.6.2"
 
+preact@^10.0.0, preact@^10.5.15:
+  version "10.5.15"
+  resolved "https://registry.yarnpkg.com/preact/-/preact-10.5.15.tgz#6df94d8afecf3f9e10a742fd8c362ddab464225f"
+  integrity sha512-5chK29n6QcJc3m1lVrKQSQ+V7K1Gb8HeQY6FViQ5AxCAEGu3DaHffWNDkC9+miZgsLvbvU9rxbV1qinGHMHzqA==
+
 prelude-ls@^1.2.1:
   version "1.2.1"
   resolved "https://registry.yarnpkg.com/prelude-ls/-/prelude-ls-1.2.1.tgz#debc6489d7a6e6b0e7611888cec880337d316396"

From 4f98f5971699056f31825bc32eda9388329f5ca2 Mon Sep 17 00:00:00 2001
From: John Ouellet <john@thinktandem.io>
Date: Thu, 4 Nov 2021 14:09:14 -0400
Subject: [PATCH 12/16] #130 Add in start of guide transfer

---
 docs/.vuepress/components/GuideFooter.vue     |  69 ++
 docs/.vuepress/components/GuideHeader.vue     |  65 ++
 docs/.vuepress/components/Newsletter.vue      | 130 ++++
 docs/.vuepress/components/NewsletterLearn.vue | 134 ++++
 docs/.vuepress/components/RelatedGuides.vue   |  50 ++
 docs/.vuepress/components/TeamList.vue        |  49 ++
 docs/.vuepress/components/YouTube.vue         |  38 ++
 docs/.vuepress/config.js                      |  25 +-
 docs/.vuepress/theme/components/Subscribe.vue | 198 ++++++
 docs/.vuepress/theme/styles/palette.scss      |   8 +
 docs/guides/access-by-other-devices.md        |  47 ++
 docs/guides/db-export.md                      |  73 ++
 docs/guides/db-import.md                      |  84 +++
 .../guides/drupal-7-landoize-an-extant-app.md | 109 +++
 docs/guides/drupal-multisite-on-lando.md      | 150 ++++
 docs/guides/external-access.md                | 138 ++++
 docs/guides/frontend.md                       |  76 +++
 ...pull-sync-my-database-on-lamp-y-recipes.md | 159 +++++
 .../how-do-i-configure-a-lando-recipe.md      |  80 +++
 ...o-i-set-the-timezone-of-a-lando-service.md |  63 ++
 ...up-browsersync-and-gulp-in-my-lando-app.md | 186 +++++
 ...stalling-node-in-your-lando-php-service.md | 110 +++
 .../installing-php-extensions-on-lando.md     | 111 +++
 docs/guides/lando-101/lando-config.md         |  65 ++
 docs/guides/lando-101/lando-init.md           | 117 ++++
 docs/guides/lando-101/lando-overview.md       |  48 ++
 docs/guides/lando-101/lando-proxy.md          |  69 ++
 docs/guides/lando-101/lando-services.md       |  75 ++
 docs/guides/lando-101/lando-start.md          |  72 ++
 docs/guides/lando-101/lando-tooling.md        |  77 +++
 docs/guides/lando-info.md                     |  45 ++
 docs/guides/lando-phpstorm.md                 |  43 ++
 docs/guides/lando-with-vscode.md              | 277 ++++++++
 docs/guides/macos-pantheon-no-proxy.md        |  81 +++
 docs/guides/offline-dev.md                    |  75 ++
 docs/guides/overriding-a-service-version.md   |  74 ++
 docs/guides/phpmyadmin-themes.md              | 101 +++
 .../setup-lando-on-windows-with-wsl-2.md      |  75 ++
 .../updating-local-pantheon-environments.md   |  62 ++
 docs/guides/updating-to-rc2.md                | 638 ++++++++++++++++++
 .../using-compass-on-a-lando-node-service.md  |  84 +++
 package.json                                  |   1 +
 yarn.lock                                     |   9 +
 43 files changed, 4231 insertions(+), 9 deletions(-)
 create mode 100644 docs/.vuepress/components/GuideFooter.vue
 create mode 100644 docs/.vuepress/components/GuideHeader.vue
 create mode 100644 docs/.vuepress/components/Newsletter.vue
 create mode 100644 docs/.vuepress/components/NewsletterLearn.vue
 create mode 100644 docs/.vuepress/components/RelatedGuides.vue
 create mode 100644 docs/.vuepress/components/TeamList.vue
 create mode 100644 docs/.vuepress/components/YouTube.vue
 create mode 100644 docs/.vuepress/theme/components/Subscribe.vue
 create mode 100644 docs/guides/access-by-other-devices.md
 create mode 100644 docs/guides/db-export.md
 create mode 100644 docs/guides/db-import.md
 create mode 100644 docs/guides/drupal-7-landoize-an-extant-app.md
 create mode 100644 docs/guides/drupal-multisite-on-lando.md
 create mode 100644 docs/guides/external-access.md
 create mode 100644 docs/guides/frontend.md
 create mode 100644 docs/guides/how-can-i-pull-sync-my-database-on-lamp-y-recipes.md
 create mode 100644 docs/guides/how-do-i-configure-a-lando-recipe.md
 create mode 100644 docs/guides/how-do-i-set-the-timezone-of-a-lando-service.md
 create mode 100644 docs/guides/how-to-wire-up-browsersync-and-gulp-in-my-lando-app.md
 create mode 100644 docs/guides/installing-node-in-your-lando-php-service.md
 create mode 100644 docs/guides/installing-php-extensions-on-lando.md
 create mode 100644 docs/guides/lando-101/lando-config.md
 create mode 100644 docs/guides/lando-101/lando-init.md
 create mode 100644 docs/guides/lando-101/lando-overview.md
 create mode 100644 docs/guides/lando-101/lando-proxy.md
 create mode 100644 docs/guides/lando-101/lando-services.md
 create mode 100644 docs/guides/lando-101/lando-start.md
 create mode 100644 docs/guides/lando-101/lando-tooling.md
 create mode 100644 docs/guides/lando-info.md
 create mode 100644 docs/guides/lando-phpstorm.md
 create mode 100644 docs/guides/lando-with-vscode.md
 create mode 100644 docs/guides/macos-pantheon-no-proxy.md
 create mode 100644 docs/guides/offline-dev.md
 create mode 100644 docs/guides/overriding-a-service-version.md
 create mode 100644 docs/guides/phpmyadmin-themes.md
 create mode 100644 docs/guides/setup-lando-on-windows-with-wsl-2.md
 create mode 100644 docs/guides/updating-local-pantheon-environments.md
 create mode 100644 docs/guides/updating-to-rc2.md
 create mode 100644 docs/guides/using-compass-on-a-lando-node-service.md

diff --git a/docs/.vuepress/components/GuideFooter.vue b/docs/.vuepress/components/GuideFooter.vue
new file mode 100644
index 0000000..8d0d288
--- /dev/null
+++ b/docs/.vuepress/components/GuideFooter.vue
@@ -0,0 +1,69 @@
+<template>
+  <div class="originally-appeared">
+    <div v-if="repo" class="tip custom-block">
+      <h3>FULL CODE EXAMPLE!</h3>
+      <p>If you are interested in checking out the fully-armed and operational source code for this guide then check out <a target="_blank" :href="repo">this repo here</a>.</p>
+    </div>
+    <div class="original-rule"></div>
+    <div class="original-article" v-if="original">
+      This guide is adapted from other content. If you are interested in the original then <a target="_blank" :href="original">check it out here</a>.
+    </div>
+    <div class="original-article">
+      Have a Lando question you'd like to see as a guide? <a target="_blank" href="https://github.com/lando/lando/issues/new/choose"> Suggest one!</a>
+    </div>
+    <div class="original-article">
+      Want to write a Lando guide? <a href="./../theme/contrib/guides-intro.html"> Learn how!</a>
+    </div>
+  </div>
+</template>
+
+<script>
+export default {
+  name: 'GuideFooter',
+  props: {
+    original: {
+      type: String,
+      default: '',
+    },
+    repo: {
+      type: String,
+      default: '',
+    },
+    test: {
+      type: String,
+    },
+  },
+};
+</script>
+
+<style lang="scss">
+@import '../theme/styles/index.scss';
+@import '../theme/styles/palette.scss';
+@import '@vuepress/plugin-palette/palette';
+
+.originally-appeared {
+  margin-top: 2rem;
+  padding-top: 1rem;
+  img {
+    width: 24px;
+    border-radius: 100%;
+    float: right;
+    position: relative;
+    bottom: 6px;
+  }
+  .original-article {
+    font-size: 0.85em;
+    font-style: italic;
+  }
+  .original-rule {
+    border-bottom: 1px dotted #ddd;
+    padding-top: 1em;
+    margin-bottom: 1em;
+  }
+  .custom-block {
+    &.tip {
+      border-color: $landoGreen;
+    }
+  }
+}
+</style>
diff --git a/docs/.vuepress/components/GuideHeader.vue b/docs/.vuepress/components/GuideHeader.vue
new file mode 100644
index 0000000..114d6bb
--- /dev/null
+++ b/docs/.vuepress/components/GuideHeader.vue
@@ -0,0 +1,65 @@
+<template>
+  <div class="written-by">
+    Written by:
+    <a :href="link" target="_blank">{{ name }}</a>
+    <a :href="link" target="_blank"><img :src="pic" :alt="name" /></a>
+    <div v-if="test" class="tested-by">
+      Guide Tested: <a :href="test" target="_blank">Yes</a>
+    </div>
+    <div v-else>
+      Guide Tested: <span class="not-tested">No</span>
+    </div>
+  </div>
+
+</template>
+
+<script>
+export default {
+  name: 'GuideHeader',
+  props: {
+    name: {
+      type: String,
+      default: 'Team Lando',
+    },
+    pic: {
+      type: String,
+      default: 'https://www.gravatar.com/avatar/db2470075fb67c330c155cab9698826f',
+    },
+    link: {
+      type: String,
+      default: 'https://twitter.com/devwithlando',
+    },
+    test: {
+      type: String,
+      default: null,
+    },
+  },
+};
+</script>
+
+<style lang="scss">
+@import '../theme/styles/index.scss';
+@import '../theme/styles/palette.scss';
+@import '@vuepress/plugin-palette/palette';
+
+.written-by {
+  font-size: 0.85em;
+  padding-bottom: 1rem;
+  border-bottom: 1px dotted #ddd;
+  img {
+    width: 24px;
+    border-radius: 100%;
+    float: right;
+    position: relative;
+    bottom: 6px;
+  }
+  .tested-by {
+    a {
+      color: #2ecc71;
+    }
+  }
+  .not-tested {
+    color: #f00;
+  }
+}
+</style>
diff --git a/docs/.vuepress/components/Newsletter.vue b/docs/.vuepress/components/Newsletter.vue
new file mode 100644
index 0000000..0c1f70a
--- /dev/null
+++ b/docs/.vuepress/components/Newsletter.vue
@@ -0,0 +1,130 @@
+<template>
+  <div class="newsletter post-subscribe">
+    <div class="newsletter__wrap">
+      <div class="newsletter__title">Want new guide content?</div>
+      <div class="newsletter__content">Sign up and we'll send you the latest and greatest!</div>
+      <Subscribe
+        successMessage="More awesome guide material will be heading your way!"
+        :customStyles="stylez"
+        :interests="interests"
+        title=""
+      />
+    </div>
+  </div>
+</template>
+
+<script>
+import Subscribe from '@theme/components/Subscribe.vue';
+
+export default {
+  name: 'Newsletter',
+  components: {Subscribe}, // eslint-disable-line
+  data() {
+    return {
+      stylez: {
+        width: '100%',
+      },
+      interests: [{
+        id: 1,
+        group: 37781,
+        checked: true,
+        hidden: true,
+        label: 'Updates',
+      }],
+    };
+  },
+};
+</script>
+
+<style lang="scss">
+@import '../theme/styles/index.scss';
+@import '../theme/styles/palette.scss';
+@import '@vuepress/plugin-palette/palette';
+
+.newsletter {
+  text-align: center;
+  width: 100%;
+  font-size: 1rem;
+  color: var(--c-text);
+}
+.newsletter__wrap {
+  margin: 1.5rem auto;
+  padding: 1.8rem 2.3rem;
+  border-radius: 3px;
+  box-sizing: border-box;
+  width: auto;
+  background-color: #f8f8f8;
+}
+.newsletter__title {
+  font-size: 1.7rem;
+}
+.newsletter__content {
+  margin-top: 1.5rem;
+  margin-bottom: 1.5rem;
+  line-height: 1.7rem;
+}
+.newsletter__input {
+  font-size: inherit;
+  border: 1px solid var(  --c-border);
+  width: 100%;
+  padding: 0.6rem 1.2rem;
+  box-sizing: border-box;
+  border-radius: 3px;
+  margin-bottom: 0.8rem;
+  outline: none;
+}
+.newsletter__button {
+  font-size: inherit;
+  border: none;
+  cursor: pointer;
+  background: var(  --c-text-accent);
+  color: #fff;
+  padding: 0.6rem 1.8rem;
+  box-sizing: border-box;
+  border-radius: 3px;
+  width: 100%;
+  outline: none;
+}
+.post-subscribe {
+  .subscribe {
+    width: 100%;
+    padding: 0;
+    .button {
+      font-size: inherit;
+      border: none;
+      cursor: pointer;
+      background: #ed3f7a;
+      color: #fff;
+      padding: 0.6rem 1.2rem;
+      box-sizing: border-box;
+      border-radius: 3px;
+      width: 100%;
+      outline: none;
+      text-transform: none;
+      font-weight: 400;
+      height: auto;
+    }
+  }
+  .subscribe-input {
+    background-color: #fff;
+    font-size: inherit;
+    border: 1px solid #ddd;
+    width: 100%;
+    padding: 0.6rem 1.2rem;
+    box-sizing: border-box;
+    border-radius: 3px;
+    margin-bottom: 0.8rem;
+    outline: none;
+    height: auto;
+    margin: 1em 0;
+  }
+  .newsletter__wrap {
+    background-color: #f8f8f8;
+  }
+  @media (max-width: $MQMobile) {
+    .post-subscribe .subscribe-form {
+      display: block;
+    }
+  }
+}
+</style>
diff --git a/docs/.vuepress/components/NewsletterLearn.vue b/docs/.vuepress/components/NewsletterLearn.vue
new file mode 100644
index 0000000..80c485a
--- /dev/null
+++ b/docs/.vuepress/components/NewsletterLearn.vue
@@ -0,0 +1,134 @@
+<template>
+  <div class="newsletter post-subscribe">
+    <div class="newsletter__wrap">
+      <div class="newsletter__title">Want more helpful onboarding content?</div>
+      <div class="newsletter__content">Sign up and we'll send you a new and helpful guide every week!</div>
+      <Subscribe
+        successMessage="Soon you will be the master!"
+        :customStyles="stylez"
+        :groups="groups"
+        title=""
+      />
+    </div>
+  </div>
+</template>
+
+<script>
+import Subscribe from '@theme/components/Subscribe.vue';
+
+export default {
+  name: 'NewsletterLearn',
+  components: {Subscribe}, // eslint-disable-line
+  data() {
+    return {
+      stylez: {
+        width: '100%',
+      },
+      groups: ['NEWSLETTER', 'NEWUSER'],
+    };
+  },
+};
+</script>
+
+<style lang="scss">
+@import '../theme/styles/index.scss';
+@import '../theme/styles/palette.scss';
+@import '@vuepress/plugin-palette/palette';
+
+.newsletter {
+	text-align: center;
+	width: 100%;
+	font-size: 1rem;
+	color: var(--c-text);
+}
+.newsletter__wrap {
+	margin: 1.5rem auto;
+	padding: 1.8rem 2.3rem;
+	border-radius: 3px;
+	box-sizing: border-box;
+	width: auto;
+	background-color: #f8f8f8;
+}
+.newsletter__title {
+	font-size: 1.7rem;
+}
+.newsletter__content {
+	margin-top: 1.5rem;
+	margin-bottom: 1.5rem;
+	line-height: 1.7rem;
+}
+.newsletter__input {
+	font-size: inherit;
+	border: 1px solid var(  --c-border);
+	width: 100%;
+	padding: 0.6rem 1.2rem;
+	box-sizing: border-box;
+	border-radius: 3px;
+	margin-bottom: 0.8rem;
+	outline: none;
+}
+.newsletter__button {
+	font-size: inherit;
+	border: none;
+	cursor: pointer;
+	background: var(  --c-text-accent);
+	color: #fff;
+	padding: 0.6rem 1.8rem;
+	box-sizing: border-box;
+	border-radius: 3px;
+	width: 100%;
+	outline: none;
+}
+.post-subscribe {
+	.subscribe {
+		width: 100%;
+		padding: 0;
+		.button {
+			font-size: inherit;
+			border: none;
+			cursor: pointer;
+			background: #ed3f7a;
+			color: #fff;
+			padding: 0.6rem 1.2rem;
+			box-sizing: border-box;
+			border-radius: 3px;
+			width: 100%;
+			outline: none;
+			text-transform: none;
+			font-weight: 400;
+			height: auto;
+		}
+	}
+	.subscribe-form {
+		display: grid;
+		grid-template-columns: 1fr 1fr;
+		grid-gap: 10px;
+	}
+	.subscribe-input {
+		background-color: #fff;
+		font-size: inherit;
+		border: 1px solid #ddd;
+		width: 100%;
+		padding: 0.6rem 1.2rem;
+		box-sizing: border-box;
+		border-radius: 3px;
+		margin-bottom: 0.8rem;
+		outline: none;
+		height: auto;
+		margin: 1em 0;
+		&:focus {
+			outline: none;
+			border: 0;
+			border-color: transparent;
+		}
+	}
+  @media (max-width: $MQMobile) {
+    .subscribe-form {
+      display: block;
+    }
+    .newsletter__wrap {
+      background-color: #f8f8f8;
+    }
+  }
+}
+</style>
diff --git a/docs/.vuepress/components/RelatedGuides.vue b/docs/.vuepress/components/RelatedGuides.vue
new file mode 100644
index 0000000..3eb8ab5
--- /dev/null
+++ b/docs/.vuepress/components/RelatedGuides.vue
@@ -0,0 +1,50 @@
+<template>
+  <div v-if="tag && content.length > 0" class="related-guides">
+    <h2>Related Guides and Tutorials</h2>
+    <ul>
+      <li v-for="page in content" :key="page.key">
+        <a :href="page.path">{{ page.title }}</a>
+      </li>
+    </ul>
+  </div>
+</template>
+
+<script>
+import {resolveSidebarItems} from '@parent-theme/util';
+
+export default {
+  name: 'RelatedGuides',
+  props: {
+    tag: {
+      type: String,
+      default: '',
+    },
+  },
+  data() {
+    return {
+      content: [],
+    };
+  },
+  mounted() {
+    const guides = resolveSidebarItems(this.$page, '/guides/', this.$site, '/');
+    const section = guides.find(item => item.title.toLowerCase() === this.tag.toLowerCase());
+    this.content = section.children;
+  },
+};
+</script>
+
+<style lang="scss">
+@import '../theme/styles/index.scss';
+@import '../theme/styles/palette.scss';
+@import '@vuepress/plugin-palette/palette';
+
+.related-guides {
+	margin-top: 2rem;
+	padding-top: 1rem;
+	a {
+		display: block;
+		padding-bottom: 0.3em;
+	}
+}
+
+</style>
diff --git a/docs/.vuepress/components/TeamList.vue b/docs/.vuepress/components/TeamList.vue
new file mode 100644
index 0000000..968e405
--- /dev/null
+++ b/docs/.vuepress/components/TeamList.vue
@@ -0,0 +1,49 @@
+<template>
+  <div id="current-team" class="current-team-wrapper">
+    <TeamMember v-for="(member, index) in members" :key="index" :member="member" />
+  </div>
+</template>
+
+<script>
+import TeamMember from '@theme/components/TeamMember.vue';
+
+export default {
+  name: 'TeamList',
+  components: {TeamMember},
+  data() {
+    return {
+      members: [],
+    };
+  },
+  mounted() {
+    this.members = this.$contributors;
+  },
+};
+</script>
+
+<style lang="scss">
+@import '../theme/styles/index.scss';
+@import '../theme/styles/palette.scss';
+@import '@vuepress/plugin-palette/palette';
+
+.current-team {
+	.current-team-wrapper {
+		max-width: 740px;
+		margin: 0 auto;
+		padding: 0rem 2.5rem;
+		padding-top: 3.75rem;
+		padding-bottom: 1rem;
+	}
+	.theme-default-content {
+		max-width: 740px;
+		margin: 0 auto;
+		padding: 0rem 2.5rem;
+		&:not(.custom) {
+			& > *:first-child {
+				margin-top: 0px;
+			}
+		}
+	}
+}
+
+</style>
diff --git a/docs/.vuepress/components/YouTube.vue b/docs/.vuepress/components/YouTube.vue
new file mode 100644
index 0000000..947e8b2
--- /dev/null
+++ b/docs/.vuepress/components/YouTube.vue
@@ -0,0 +1,38 @@
+<template>
+  <div v-if="url" class="video-responsive">
+    <iframe width="100%" height="400" :src="url" frameborder="0" allow="accelerometer; autoplay; encrypted-media; gyroscope; picture-in-picture" allowfullscreen></iframe>
+  </div>
+</template>
+
+<script>
+
+export default {
+  name: 'YouTube',
+  props: {
+    url: {
+      type: String,
+    },
+  },
+};
+</script>
+
+<style lang="scss">
+@import '../theme/styles/index.scss';
+@import '../theme/styles/palette.scss';
+@import '@vuepress/plugin-palette/palette';
+
+.video-responsive {
+	margin-top: 1em;
+	overflow: hidden;
+	padding-bottom: 56.25%;
+	position: relative;
+	height: 0;
+	iframe {
+		left: 0;
+		top: 0;
+		height: 100%;
+		width: 100%;
+		position: absolute;
+	}
+}
+</style>
diff --git a/docs/.vuepress/config.js b/docs/.vuepress/config.js
index c626365..6855c09 100644
--- a/docs/.vuepress/config.js
+++ b/docs/.vuepress/config.js
@@ -26,14 +26,21 @@ module.exports = {
       {text: 'Guides', link: '/guides/lando-101/lando-overview'},
       {text: 'Help and Support', link: '/help/logs/'},
     ],
-    plugins: [
-      [
-        '@vuepress/docsearch',
-        {
-          apiKey: '15e332850128e9ec96929f44c62f6c88',
-          indexName: 'lando',
-        },
-      ],
-    ]
   },
+  plugins: [
+    [
+      '@vuepress/docsearch',
+      {
+        apiKey: '15e332850128e9ec96929f44c62f6c88',
+        indexName: 'lando',
+      },
+    ],
+    [
+      '@vuepress/register-components',
+      {
+        componentsDir: path.resolve(__dirname, './components'),
+        componentsPatterns: ['*.vue', '**/*.vue']
+      },
+    ],
+  ]
 };
diff --git a/docs/.vuepress/theme/components/Subscribe.vue b/docs/.vuepress/theme/components/Subscribe.vue
new file mode 100644
index 0000000..20d0ec1
--- /dev/null
+++ b/docs/.vuepress/theme/components/Subscribe.vue
@@ -0,0 +1,198 @@
+<template>
+  <div :class="{ subscribe: true, 'subscribe-dark': theme === 'dark' }" :style="customStyles">
+    <h3>{{ title }}</h3>
+    <div id="mc_embed_signup">
+      <form action="https://dev.us12.list-manage.com/subscribe/post?u=59874b4d6910fa65e724a4648&amp;id=613837077f" method="post" id="mc-embedded-subscribe-form" name="mc-embedded-subscribe-form" class="validate subscribe-form" target="_blank" novalidate>
+        <input
+          id="mce-EMAIL"
+          type="email"
+          v-model="email"
+          placeholder="Email address"
+          name="EMAIL"
+          class="subscribe-input" />
+
+        <ul style="display: none;" v-if="interests.length > 0">
+          <li v-for="(interest, index) in interests" :key="index">
+            <input
+              type="checkbox"
+              :checked="interest.checked"
+              :value="interest.id"
+              :name="`group[${interest.group}][${interest.id}]`"
+              :id="`mce-group[${interest.group}]-${interest.group}-${index}`">
+            <label :for="`mce-group[${interest.group}]-${interest.group}-${index}`">{{ interest.label }}</label>
+          </li>
+        </ul>
+
+        <div id="mce-responses" class="clear">
+          <div class="response" id="mce-error-response" style="display:none"></div>
+          <div class="response" id="mce-success-response" style="display:none"></div>
+        </div>
+        <div style="position: absolute; left: -5000px;" aria-hidden="true">
+          <input type="text" name="b_59874b4d6910fa65e724a4648_613837077f" tabindex="-1" value="">
+        </div>
+
+        <input
+          id="mc-embedded-subscribe"
+          :class="{ button: true, disabled: !email }"
+          :disabled="!email"
+          type="submit"
+          :value="buttonLabel"
+          name="subscribe" />
+      </form>
+    </div>
+  </div>
+</template>
+
+<script>
+
+export default {
+  props: {
+    buttonLabel: {
+      type: String,
+      default: 'Subscribe',
+    },
+    customStyles: {
+      type: Object,
+      default: () => ({
+        width: '90%',
+      }),
+    },
+    interests: {
+      type: Array,
+      default: () => ([]),
+    },
+    hideInterests: {
+      type: Boolean,
+      default: true,
+    },
+    title: {
+      type: String,
+      default: 'Get the latest updates',
+    },
+    theme: {
+      type: String,
+      default: 'light',
+    },
+  },
+  data() {
+    return {
+      email: '',
+    };
+  },
+};
+</script>
+
+<style lang="scss">
+.subscribe {
+  margin: auto;
+  width: 90%;
+  padding: 2em 0;
+  text-align: center;
+  h3 {
+    color: $landoPink;
+  }
+  &.subscribe-dark {
+    background-color: darken($landoBlue, 12%);
+    h3 {
+      color: lighten($landoBlue, 90%);
+    }
+  }
+  .button {
+    text-transform: uppercase;
+    background-color: $landoPink;
+    margin: 1em 0;
+    font-size: 1.2em;
+    font-weight: 500;
+    letter-spacing: .05em;
+    min-width: 8em;
+    text-align: center;
+    &:not(:last-child) {
+      margin-right: 1%;
+    }
+    &.disabled {
+      opacity: .5;
+    }
+  }
+  .hidden-field {
+    visibility: hidden;
+  }
+  .subscribe-alliance,
+  .subscribe-devnetwork,
+  .subscribe-sponsors {
+    padding-top: 2em;
+    padding-bottom: 2em;
+    p {
+      color: lighten($landoBlue, 90%);
+      font-size: 1.2em;
+    }
+    .subscribe-alliance-wrapper,
+    .subscribe-devnetwork-checkbox,
+    .subscribe-sponsors-wrapper {
+      padding-top: 1em;
+      padding-bottom: 1em;
+      input.subscribe-alliance-checkbox {
+        font-size: 16px;
+      }
+      label {
+        cursor: pointer;
+        color: lighten($landoBlue, 90%);
+        font-size: 2em;
+        font-weight: 800;
+      }
+      small {
+        font-family: "Source Sans Pro", "Helvetica Neue", Arial, sans-serif;
+        color: lighten($landoBlue, 90%);
+        text-align: center;
+        font-size: 1.4em;
+        letter-spacing: 0;
+      }
+    }
+    .subscribe-devnetwork-checkbox {
+      padding-top: .5em;
+      padding-bottom: .5em;
+      label {
+        font-size: 1em;
+      }
+    }
+  }
+  .subscribe-input {
+    width: 100%;
+    box-sizing: border-box;
+    padding: 10px 80px 10px 20px;
+    margin-bottom: 1em;
+    height: 50px;
+    border-radius: 50px;
+    border: 1px solid #ccc;
+    font-size: 16px;
+    background-color: lighten($landoBlue, 96%);
+    &:focus {
+      outline: none;
+      border-color: lighten($landoPink, 18%);
+    }
+    &.disabled {
+      opacity: .5;
+    }
+  }
+
+  .subscribe-error,
+  .subscribe-success {
+    padding: 1em;
+    color: red;
+    text-transform: uppercase;
+    font-weight: 800;
+    font-size: 0.75rem;
+    .subscribe-success {
+      color: $landoPink
+    }
+  }
+}
+
+@media (max-width: $MQMobile) {
+  .subscribe {
+    .subscribe-input {
+      width: 90%;
+    }
+  }
+}
+
+</style>
diff --git a/docs/.vuepress/theme/styles/palette.scss b/docs/.vuepress/theme/styles/palette.scss
index 34a8037..f50b3a9 100644
--- a/docs/.vuepress/theme/styles/palette.scss
+++ b/docs/.vuepress/theme/styles/palette.scss
@@ -1,3 +1,11 @@
+// More things
+$landoPink: #ed3f7a;
+$landoGrey: #47474A;
+$landoBlue: #035785;
+$landoOrange: #FF7042;
+$landoGreen: #00A38F;
+$landoGrey: #2c3e50;
+
 // responsive breakpoints
 $MQNarrow: 959px !default;
 $MQMobile: 719px !default;
diff --git a/docs/guides/access-by-other-devices.md b/docs/guides/access-by-other-devices.md
new file mode 100644
index 0000000..90afd07
--- /dev/null
+++ b/docs/guides/access-by-other-devices.md
@@ -0,0 +1,47 @@
+---
+description: Learn how to access your Lando sites from other devices on your network like mobile phones or tablets.
+author:
+  name: Team Lando
+  twitter: devwithlando
+date: 2019-11-05
+---
+
+# Accessing Lando from Other Devices on Your Local Network
+
+<GuideHeader />
+<YouTube url="" />
+
+You may want to use another device (e.g., a smartphone or tablet) to test your Lando app.  You can access your lando app easily from another device as follows.
+
+## lando share (Testing over the Internet)
+
+The fastest way to do this is to use the [lando share](./../basics/share.html) command.  This will provide you with a URL that you can use to access your app via the Internet.  You can close the connection at any time by pressing a key in the terminal on your local machine.
+
+## Changing the Bind
+
+If you would rather test only on your local network and not over the Internet, you first need to change the `bindAddress` to expose your services on the LAN. Note that there are security implications to this and it is not recommended. Please consult the [Security Docs](./../config/security.md).
+
+Once you've done that you can ...
+
+### 1. First, get the IP address of the machine running lando.
+
+#### Windows
+
+Open a command prompt and enter the command `ipconfig /all` and look for the "IPv4 Address" for the network adapter you use to connect to the Internet.  Make sure NOT to use the IP address of the Docker network adapter.  It should be a number like `192.168.0.123`.
+
+#### macOS
+
+Open System Preferences, Network, and then choose the network adapter you are using to connect to the Internet (Ethernet or Wireless).  The local IP address will then be displayed.
+
+#### Linux
+
+Open a command prompt and enter the command `hostname -I | cut -d' ' -f1`.
+
+### 2. Next, get the port of your lando app.
+
+You can do this by running `lando info` from a command prompt and looking for the URL to your site, which should look something like this: `http://localhost:33333`.  In this case, `33333` is the port number.
+
+You can now visit your lando app from other devices by going to `IP address: Port number`.  (Example: `http://192.168.0.123:33333`)
+
+<GuideFooter />
+<Newsletter />
diff --git a/docs/guides/db-export.md b/docs/guides/db-export.md
new file mode 100644
index 0000000..4e3b837
--- /dev/null
+++ b/docs/guides/db-export.md
@@ -0,0 +1,73 @@
+---
+metaTitle: Exporting SQL Databases | Lando
+description: Learn how to export your MySQL, MariaDB or Postgres databases from Lando.
+date: 2019-11-05
+---
+
+# SQL Export
+
+<GuideHeader test="https://circleci.com/gh/lando/lando/tree/master"/>
+
+Lando ships with a helper `db-export` script that is available in all our `LAMP` and `LEMP` based recipes. Used in the recipe context it should export a database dump `DATABASE.TIMESTAMP.gz` into the `/app` directory.
+
+You can also export databases from other services.
+
+## Usage
+
+At the command line execute:
+
+```bash
+lando db-export
+```
+
+### Examples
+
+```bash
+# Export to a file named `DATABASE.TIMESTAMP.gz`
+lando db-export
+
+# Export to a file called dump.sql.gz
+lando db-export dump.sql
+
+# Export from a secondary database
+lando db-export --host db2
+
+# Dump the result to stdout
+lando db-export --stdout
+
+# Dump to an absolute path
+# NOTE: this is an absolute path in the target container, not on you host
+lando db-export /db/dump.zip
+```
+
+### Options
+
+```bash
+Options:
+  --host, -h      The database service to use                  [default: "database"]
+  --stdout        Dump database to stdout
+```
+
+## Adding the `db-export` command
+
+If you are not using one of our LAMPy [recipes](./../config/recipes.md) you can add the `db-export` command and default options to the ['tooling'](./../config/tooling.md) section of your [Landofile](./../config/lando.md).
+
+```yaml
+tooling:
+  'db-export [file]':
+    service: :host
+    description: Exports database from a database service to a file
+    cmd: /helpers/sql-export.sh
+    user: root
+    options:
+      host:
+        description: The database service to use
+        default: database
+        alias:
+          - h
+      stdout:
+        description: Dump database to stdout
+```
+
+<GuideFooter test="https://circleci.com/gh/lando/lando/tree/master" repo="https://github.com/lando/cli/tree/main/examples/sql-export" />
+<Newsletter />
diff --git a/docs/guides/db-import.md b/docs/guides/db-import.md
new file mode 100644
index 0000000..115a98f
--- /dev/null
+++ b/docs/guides/db-import.md
@@ -0,0 +1,84 @@
+---
+metaTitle: Importing SQL Databases | Lando
+description: Learn how to import your MySQL, MariaDB or Postgres databases to Lando.
+date: 2019-11-05
+---
+
+# SQL Import
+
+<GuideHeader test="https://circleci.com/gh/lando/lando/tree/master"/>
+
+Lando ships with a helper `db-import` script that is available in all our `LAMP` and `LEMP` based recipes. Used in the recipe context it should import a database dump into the recipe-provided database by default but can be used on additional database services as well.
+
+You can also import databases into other hosts and databases. It will currently handle uncompressed, gzipped or zipped dump files.
+
+**This command will wipe out the target database before it runs the import unless you use the `--no-wipe` flag!**
+
+## Usage
+
+```bash
+lando db-import somedumpfile.sql.gz
+```
+
+::: warning DB dump must reside within app directory!
+Due to restrictions in how Docker handles file sharing your database dump **MUST** exist somewhere inside of your app directory. This means that **IT IS A VERY GOOD IDEA** to make sure you add SQL dumps to your `.gitignore` file.
+:::
+
+### Examples
+
+```bash
+# Import a file into the recipe-provided db
+lando db-import dump.sql
+
+# Import a file into an auxiliary second database called 'db2'
+# with a db called `dataz`
+lando db-import dump.zip --host db2
+
+# Import without destroying the target database
+lando db-import dump.zip --no-wipe
+
+# Import using an absolute path
+# NOTE: this is an absolute path in the target container, not on you host
+lando db-import /db/dump.zip
+
+# Import from a subdirectory
+lando db-import subdir/test.sql
+
+# Pipe stdout into db-import
+# NOTE: this is a bit finicky right now
+cat dump.sql | lando db-import
+```
+
+### Options
+
+```bash
+Options:
+  --host, -h      The database service to use                  [default: "database"]
+  --no-wipe       Do not destroy the existing database before an import
+```
+
+## Adding the `db-import` command
+
+If you are not using one of our LAMPy [recipes](./../config/recipes.md) you can add the `db-import` command and default options to the ['tooling'](./../config/tooling.md) section of your [Landofile](./../config/lando.md).
+
+```yaml
+tooling:
+  'db-import <file>':
+    service: :host
+    description: Imports a dump file into a database service
+    cmd: /helpers/sql-import.sh
+    user: root
+    options:
+      host:
+        description: The database service to use
+        default: database
+        alias:
+          - h
+      no-wipe:
+        description: Do not destroy the existing database before an import
+        boolean: true
+```
+
+<GuideFooter test="https://circleci.com/gh/lando/lando/tree/master" repo="https://github.com/lando/cli/tree/main/examples/sql-import" />
+<Newsletter />
+
diff --git a/docs/guides/drupal-7-landoize-an-extant-app.md b/docs/guides/drupal-7-landoize-an-extant-app.md
new file mode 100644
index 0000000..4857b65
--- /dev/null
+++ b/docs/guides/drupal-7-landoize-an-extant-app.md
@@ -0,0 +1,109 @@
+---
+title: Drupal 7 Landoize an Extant App
+metaTitle: Drupal 7 Landoize an Extant App | Lando
+description: Use Lando as local development environment for an existing Drupal 7 app.
+date: 2020-01-21T17:34:56.556Z
+original: 
+repo: 
+
+author:
+  name: Geoff St. Pierre
+  pic: https://www.gravatar.com/avatar/e103c2a2a8f8caf5848b38b80422cdd9
+  link: https://twitter.com/serundeputy
+
+feed:
+  enable: true
+  author:
+    - name: Geoff St. Pierre
+      email: alliance@lando.dev
+      link: https://twitter.com/serundeputy
+  contributor:
+    - name: Geoff St. Pierre
+      email: alliance@lando.dev
+      link: https://twitter.com/serundeputy
+---
+
+# Drupal 7 Landoize an Extant App
+
+<GuideHeader name="Geoff St. Pierre" pic="https://www.gravatar.com/avatar/e103c2a2a8f8caf5848b38b80422cdd9" link="https://twitter.com/serundeputy" />
+
+If you and your team have an existing Drupal 7 application that you would like to use Lando for local development you just need to add a `.lando.yml` configuration file
+to the project and commit it to git.
+
+First in a terminal move to the directory that contains your Drupal 7 project:
+
+```bash
+cd PATH/TO/YOUR/DRUPAL7/APP
+```
+
+## Lando Init
+
+
+Then use the `lando init` command to build your `.lando.yml` file:
+
+```bash
+lando init
+```
+
+Lando will ask you `From where should we get your app's codebase?` select `current working directory`.
+
+<img src="/images/drupal7-extant/landoInit.jpg" />
+
+Then Lando will ask you `What recipe do you want to use?` select `drupal7`.
+
+<img src="/images/drupal7-extant/landoCodeBase.jpg" />
+
+Then Lando needs to know what directory has the Drupal code it asks `Where is your webroot relative to the init destination?` If your
+code is in the current directory you can just hit enter.
+
+
+<img src="/images/drupal7-extant/landoWebroot.jpg" />
+
+::: tip Nested Web Root
+If you are using a nested web root then you should
+specify the path to the Drupal code here like: `web`
+:::
+
+Then Lando prompts for the app name: ` What do you want to call this app?` you can type anything you like, i.e. MyApp.
+
+<img src="/images/drupal7-extant/landoAppName.jpg" />
+
+The `lando init` command will create the `.lando.yml` config file for you. If you chose the `drupal7` recipe your config file should look like this:
+
+```yaml
+name: myapp
+recipe: drupal7
+config:
+  webroot: .
+```
+
+## Lando Start
+
+
+Now you are ready to start your app.
+
+```bash
+lando start
+```
+
+This will build out the containers necessary for your Drupal 7 app. You'll end up with a screen like this once the app is started:
+
+<img src="/images/drupal7-extant/landoStart.jpg" />
+
+Now you can copy any one of the resulting URLs and paste it into a browser to visit your Drupal 7 app running in Lando!
+
+## Pro Tips
+
+If you issue additional terminal commands or clear the screen you can get the URLs and other info about your app anytime by using the `lando info` command:
+
+```bash
+lando info
+```
+
+The info command will give you lots of useful information about your app:
+
+<img src="/images/drupal7-extant/landoInfo.jpg" />
+
+
+<GuideFooter />
+<Newsletter />
diff --git a/docs/guides/drupal-multisite-on-lando.md b/docs/guides/drupal-multisite-on-lando.md
new file mode 100644
index 0000000..34c5158
--- /dev/null
+++ b/docs/guides/drupal-multisite-on-lando.md
@@ -0,0 +1,150 @@
+---
+title: Running Drupal Multisite on Lando
+metaTitle: How to run Drupal Multisite on Lando | Lando
+description: How to run multisite Drupal installs on Lando.
+summary: How to run multisite Drupal installs on Lando.
+date: 2021-03-17T14:05:33.088Z
+original:
+repo:
+
+author:
+  name: Brook Heaton
+  pic: https://avatars.githubusercontent.com/u/19474864
+  link: https://github.com/brooke-heaton
+
+feed:
+  enable: true
+  author:
+    - name: Brook Heaton
+      email: alliance@lando.dev
+      link: https://github.com/brooke-heaton
+  contributor:
+    - name: Brook Heaton
+      email: alliance@lando.dev
+      link: https://github.com/brooke-heaton
+---
+
+# How to Run Drupal Multisite on Lando
+
+<GuideHeader test="" name="Brook Heaton" pic="https://avatars.githubusercontent.com/u/19474864" link="https://github.com/brooke-heaton" />
+<YouTube url="" />
+
+[Drupal multisite](https://www.drupal.org/docs/multisite-drupal) is a feature of Drupal that allows you to run multiple Drupal installs off of a common codebase.
+It's common in universities and other settings where you might want to share themes and modules between a collection of many websites.
+
+## Configuring Lando
+
+To run Drupal multisite you need to do several things:
+
+1. Your `.lando.yml` will need proxies for each multisite in the appserver array
+2. The `settings.local.php` file within your subsite directory (ex: `docroot/sites/site1/`) needs settings to connect to the appropriate Lando-hosted database.
+3. You need Drush aliases pointing to your local. If you use Drupal console, you'll need to specify your uri (ex: `drupal --uri=http://site1.lndo.site cr all`).
+
+## 1. Configure .lando.yml
+
+Create proxies for each multisite in the appserver array in your `.lando.yml` file. Ex:
+
+```yaml
+proxy:
+  appserver:
+    - site1.lndo.site
+    - site2.lndo.s
+services:
+  site1:
+    type: mysql:5.7
+    portforward: 33068
+    config:
+      confd: lando/mysql/conf.d
+  site2:
+    type: mysql:5.7
+    portforward: 33069
+    config:
+      confd: .lando/mysql/conf.d
+```
+
+## 2. Configure each subsite's local.settings.php
+
+Configure each subsite to include the default Lando config to connect to the database, along with specifying the appserver name you defined in `.lando.yml`. For example, in `docroot/sites/site1/settings/local.settings.php` you would include...
+
+```php
+/**
+ * Database configuration.
+ */
+$databases['default'] = array (
+  'default' => array (
+    'driver' => 'mysql',
+    'database' => 'database',
+    'username' => 'mysql',
+    'password' => 'password',
+    'prefix' => '',
+    'port' => 3306,
+  )
+);
+// The only thing to add from the out-of-the-box Lando db is the special host for each subsite
+$databases['default']['default']['host'] = 'site1';
+```
+
+::: warning If you're on Acquia...
+You must specify $_Server['PWD']=DRUPAL_ROOT if you use Drush 9 on Acquia (this may apply to some other hosts as well). Update your main `sites/default/settings.php` to tell our local Drupal to use the `/settings/local.settings.php` within each subsite:
+
+```php
+if (!key_exists('AH_SITE_ENVIRONMENT', $_ENV)) {
+  $environment_settings = __DIR__  . '/settings/local.settings.php';
+  if (file_exists($environment_settings)) {
+    include $environment_settings;
+  }
+}
+// Temporary fix because drush9 blocks superglobals
+$_SERVER['PWD']=DRUPAL_ROOT;
+```
+:::
+
+## 3. Define Drush aliases for each subsite
+
+Finally you'll need some Drush aliases so Drush can find your subsite installs. Here `docroot` is where our Drupal root is. For example, in `site_root/drush/sites/site-aliases/site1.site.yml` we would define...
+
+```yaml
+local:
+  uri: 'https://site1.lndo.site'
+  paths:
+  - files: /path_to_your_local_site/site_root/docroot'
+dev:
+  host: 'site1dev.ssh.prod.acquia-sites.com'
+  user: 'site1.dev'
+  root: '/var/www/html/site1.dev/docroot'
+  uri: 'site1dev.prod.acquia-sites.com'
+  ac-site: 'site1'
+  ac-env: 'dev'
+  ac-realm: 'prod'
+  paths:
+    drush-script: 'drush8'
+test:
+  root: '/var/www/html/site1.test/docroot'
+  ac-site: 'site1'
+  ac-env: 'test'
+  ac-realm: 'prod'
+  uri: 'site1stg.prod.acquia-sites.com'
+  host: 'site1stg.ssh.prod.acquia-sites.com'
+  user: 'site1.test'
+  paths:
+    drush-script: 'drush8'
+prod:
+  root: '/var/www/html/site1.prod/docroot'
+  ac-site: 'site1'
+  ac-env: 'prod'
+  ac-realm: 'prod'
+  uri: 'site1.prod.acquia-sites.com'
+  host: 'site1.ssh.prod.acquia-sites.com'
+  user: 'site1.prod'
+  paths:
+    drush-script: 'drush8'
+```
+
+I'm using drush8 against the cloud here by specifying that in the drush-script, since I've had issues trying to use drush9 and have no defined drush9 aliases, but that's purely a concern of working with Acquia Cloud.
+
+
+
+
+
+<GuideFooter test="" original="" repo=""/>
+<Newsletter />
diff --git a/docs/guides/external-access.md b/docs/guides/external-access.md
new file mode 100644
index 0000000..4726cdf
--- /dev/null
+++ b/docs/guides/external-access.md
@@ -0,0 +1,138 @@
+---
+description: Learn how to access your Lando services externally from your host machine.
+date: 2019-11-05
+---
+
+# Accessing Your Services Externally
+
+<GuideHeader />
+
+It is often desirable to interact with your services on the host machine level. Common examples of this are accessing a SQL database through a GUI client like SequelPro, or running unit tests through an IDE like PhpStorm.
+
+Lando makes this process relatively painless.
+
+## Checking Connection Info
+
+If you've spun up a Lando app using one of our [recipes](./../config/recipes.md) then its likely relevant services are already exposed and ready for access.
+
+```bash
+# Get info about it
+lando info
+
+{
+  "appserver": {
+    "type": "php",
+    "version": "7.0",
+    "via": "apache",
+    "webroot": "www",
+    "urls": [
+      "https://localhost:32785",
+      "http://localhost:32786",
+      "http://backdrop.lndo.site",
+      "https://backdrop.lndo.site"
+    ]
+  },
+  "database": {
+    "type": "mariadb",
+    "version": "latest",
+    "creds": {
+      "user": "backdrop",
+      "password": "backdrop",
+      "database": "backdrop"
+    },
+    "internal_connection": {
+      "host": "database",
+      "port": 3306
+    },
+    "external_connection": {
+      "host": "localhost",
+      "port": "32787"
+    }
+  }
+}
+```
+
+In the example above you can access the `mariadb` database from your host at `localhost:32787`. Note that this port is automatically assigned by Docker itself and will change every time you restart your app.
+
+That said, Lando provides a way to "lock down" these ports so they are more predictable.
+
+## Locking Down Ports
+
+Say you've spun up an app using our Backdrop recipe but you are frustrated by the external database port always changing. You can modify your `.lando.yml` with some recipe overrides to assign a static port.
+
+::: warning THE PORT YOU FORWARD MUST BE AVAILABLE ON YOUR HOST!
+You are going to need to select a port that is actually available on your host machine. If you don't, then this will fail. It's a good idea to avoid common ports like `3306` which likely are in use already. To that end it's good practice to use a port CLOSE TO the default eg `3307` for `3306` or `5433` for `5432`.
+:::
+
+```yml
+name: myapp
+recipe: backdrop
+services:
+  database:
+    portforward: 3307
+```
+
+```bash
+# rebuild from app directory
+lando rebuild --yes
+
+# Check to see the locked down port
+lando info
+
+{
+  "appserver": {
+    "type": "php",
+    "version": "7.0",
+    "via": "apache",
+    "webroot": "www",
+    "urls": [
+      "https://localhost:32785",
+      "http://localhost:32786",
+      "http://backdrop.lndo.site",
+      "https://backdrop.lndo.site"
+    ]
+  },
+  "database": {
+    "type": "mariadb",
+    "version": "latest",
+    "creds": {
+      "user": "backdrop",
+      "password": "backdrop",
+      "database": "backdrop"
+    },
+    "internal_connection": {
+      "host": "database",
+      "port": 3306
+    },
+    "external_connection": {
+      "host": "localhost",
+      "port": "3307"
+    }
+  }
+}
+```
+
+## Mapping to The Lando Network
+
+Some IDEs, such as PhpStorm, will spin up a separate container to run their appserver for services like built-in unit testing.  This means that it is separate from the Lando network and cannot communicate with Lando's other containers, such as the database.  In order to allow them to communicate, you need to tell your interpreter which network to listen on.
+
+::: warning If you got this message...
+`php_network_getaddresses: getaddrinfo failed: Name or service not known` while PHPUnit testing in PHPStorm and use a MySQL test database, you're in the right place!
+:::
+
+First, find your Lando network name by going to the terminal, and _outside of Lando_ run `$ docker network ls`.  You should find a record matching your Lando project.  For example, if your Lando project is named `d7dev`, then you should see something like:
+
+```
+    NETWORK ID          NAME                                        DRIVER              SCOPE
+    d9526b32d92c        d7dev_default                               bridge              local
+
+```
+
+Next, ensure your framework (PHP) interpreter is configured to use a Docker container matching your project's appserver configuration.  For example, if your running PHP 7.1 on Apache, this would look like `devwithlando/php:7.1-apache`.
+
+Finally, when configuring your framework, edit the Docker Container settings and change the Network Mode to the name of your Lando docker network.
+
+Now your IDE should be able to communicate with Lando.
+
+<GuideFooter />
+<Newsletter />
diff --git a/docs/guides/frontend.md b/docs/guides/frontend.md
new file mode 100644
index 0000000..fe79308
--- /dev/null
+++ b/docs/guides/frontend.md
@@ -0,0 +1,76 @@
+---
+description: Learn how to add node services to your Lando app so you can use yarn, npm, grunt, gulp, webpack, etc for all the frontend magic.
+date: 2019-11-05
+---
+
+# Frontend Tooling
+
+<GuideHeader />
+
+Most modern frontend tooling relies upon the NPM package manager. In this tutorial we'll show you how to add Node to your app, download tools like Gulp/Grunt/Webpack, and run them in your Lando app.
+
+When you're done, you should be able to distribute your Lando app with a full set of frontend tools that are standardized to work the same on every team member's computer.
+
+## Add Node Service
+
+Assuming you're starting with a "Lando-ized" app, open the `.lando.yml` file in the root of your app directory. In this example we'll assume you're using a very basic [LAMP](./../config/lamp.md) recipe.
+
+To install our frontend tooling we need to be able to run Node. Fortunately it's very easy for us to add a basic Node service to our app:
+
+```yml
+name: myapp
+recipe: lamp
+
+services:
+  node:
+    type: node
+    build:
+      - npm install
+```
+
+Note the `build` section. This bash command will automatically run when we start our app, installing any Node packages specified in our package.json file.
+
+## Adding Grunt/Gulp/Etc.
+
+While we're now able to install Node packages for our project, we still need to be able to install global tooling like Grunt, Gulp, or other task runners that form the backbone of our frontend tooling. Fortunately, Lando makes this easy through the `globals` tag:
+
+
+```yml
+services:
+  node:
+    type: node
+    build:
+      - npm install
+      - gulp
+    globals:
+      gulp-cli: latest
+```
+
+You can do the same thing for any NPM project; for example Grunt would be `grunt-cli: "latest"`. This is the equivalent to installing a package with `npm install -g project-name`.
+
+Note we've now added a another command to `build` to automatically run `gulp` every time we start the app. This, of course, assumes that the default `gulp` task is defined otherwise you should expect your build step to fail.
+
+::: tip Package Versions Are Fully Armed and Customizable
+You can lock your app tooling to whatever package version you like. Don't use node:6.10? Change to one of the other available versions in the [service documentation](./../config/node.md). And you're free to download whatever version of a global service your heart desires. For example, if you want to lock your team to something more stable than the latest gulp-cli, change that entry in `globals` to `gulp-cli:1.3.0`.
+:::
+
+## Making Tooling Available on the CLI
+
+Almost there! All our services are installed, but how do we run a command on the fly, say starting a watch task or running `lando npm install hot-new-thing` to start experimenting with a new package? We could SSH into our node container, but that's SO 2016. Instead, we'll expose our new tooling via the CLI by adding this [`tooling`](./../config/tooling.md) section to our `.lando.yml` file:
+
+```yml
+tooling:
+  npm:
+    service: node
+  node:
+    service: node
+  gulp:
+    service: node
+  yarn:
+    service: node
+```
+
+After restarting your app, you should be able to run `lando node`, `lando gulp` or `lando npm` and have the corresponding commands run. This is particularly useful if you want to kickoff a watch task you might have configured, say `lando gulp watch`.
+
+<GuideFooter />
+<Newsletter />
diff --git a/docs/guides/how-can-i-pull-sync-my-database-on-lamp-y-recipes.md b/docs/guides/how-can-i-pull-sync-my-database-on-lamp-y-recipes.md
new file mode 100644
index 0000000..c9a8cc0
--- /dev/null
+++ b/docs/guides/how-can-i-pull-sync-my-database-on-lamp-y-recipes.md
@@ -0,0 +1,159 @@
+---
+title: Importing a remote database and files into Lando using Laravel Envoy
+description: Add a pull command for LAMP, LEMP, Drupal, Backdrop, Laravel, PHP apps hosted on metal.
+summary: Add a pull command for LAMP, LEMP, Drupal, Backdrop, Laravel, PHP apps hosted on metal.
+date: 2020-03-30T19:23:00.720Z
+original:
+repo:
+
+author:
+  name: Geoff St. Pierre
+  pic: https://www.gravatar.com/avatar/e103c2a2a8f8caf5848b38b80422cdd9
+  link: https://twitter.com/serundeputy
+
+feed:
+  enable: true
+  author:
+    - name: Geoff St. Pierre
+      email: alliance@lando.dev
+      link: https://twitter.com/serundeputy
+  contributor:
+    - name: Geoff St. Pierre
+      email: alliance@lando.dev
+      link: https://twitter.com/serundeputy
+---
+
+# Importing a remote database and files into Lando using Laravel Envoy
+
+<GuideHeader name="Geoff St. Pierre" pic="https://www.gravatar.com/avatar/e103c2a2a8f8caf5848b38b80422cdd9" link="https://twitter.com/serundeputy" />
+<YouTube url="" />
+
+If you are hosted on a server like Linode, Digital Ocean, AWS or the like you can still cook up a `lando pull` command to pull your database and/or file assets down from production using Laravel Envoy.
+
+This will work for all Lando apps that extend from `laempy` recipes like: LAMP, LEMP, Dupal 6/7/8, Backdrop, Joomla, WordPress and Laravel.
+
+## Requirements
+
+We'll need a few things to get this set up for our `laempy` apps. We need to require the `laravel/envoy` composer package in our app, configure a `.env` file, configure an `Envoy.blade.php` file to define our tasks, and configure some `tooling` in our `.lando.yml` file. Let's jump in.
+
+## laravel/envoy
+
+To get the `laravel/envoy` package just use `composer`:
+
+```bash
+lando composer require laravel/envoy
+```
+
+## .env
+
+If you don't have a `.env` file create one and add this to it, if you already have on just add this:
+
+```bash
+LP_DB_PWD=<your_db_password>
+LP_DB=<your_db_name>
+LP_PROJECT_ROOT=<path/to/project/root/on/your/server> # like: /var/www/myapp
+LP_SITE_ROOT=<path/to/site/root> # like for nested web root /var/www/myapp/web
+LP_DB_BACK_PATH=<path/to/db/backups> # like /home/me/backups/appname/dbs
+LP_FILES_BACK_PATH=<path/to/files/backups/f.tgz # like /home/me/backups/appname/files/f.tgz
+LP_SSH_CMD=<user>@<server_ip> # like me@server_ip
+```
+after creating or updating your `.env` file you'll need to rebuild the app.
+
+```bash
+lando rebuild -y
+```
+
+## Envoy.blade.php
+
+Create a file in the root of your app called `Envoy.blade.php` and add this to it:
+
+```php
+@setup
+  $ssh = getenv('LP_SSH_CMD');
+@endsetup
+
+@servers(['web' => $ssh, 'localhost' => '127.0.0.1'])
+
+@story('pull')
+  dump
+  getdb
+  cleandb
+  backupfiles
+  getfiles
+  cleanfiles
+@endstory
+
+@task('dump', ['on' => 'web'])
+  mysqldump -u root -p{{ getenv('LP_DB_PWD') }} {{ getenv('LP_DB') }} > {{ getenv('LP_DB_BACK_PATH') }}
+@endtask
+
+@task('getdb', ['on' => 'localhost'])
+  scp {{ getenv('LP_SSH_CMD') }}:{{ getenv('LP_DB_BACK_PATH') }} db.sql
+@endtask
+
+@task('cleandb', ['on' => 'web'])
+  rm {{ getenv('LP_DB_BACK_PATH') }}
+@endtask
+
+@task('backupfiles', ['on' => 'web'])
+  cd {{ getenv('LP_SITE_ROOT') }}
+  tar czf {{ getenv('LP_FILES_BACK_PATH') }} files
+@endtask
+
+@task('getfiles', ['on' => 'localhost'])
+  scp {{ getenv('LP_SSH_CMD') }}:{{ getenv('LP_FILES_BACK_PATH') }} /app/f.tgz
+@endtask
+
+@task('cleanfiles', ['on' => 'web'])
+  rm {{ getenv('LP_FILES_BACK_PATH') }}
+@endtask
+```
+
+## .lando.yml
+
+In your `.lando.yml` file tell Lando about your `.env` file and add tooling for the `pull` command.
+
+If you don't have an `env_file` section add one.
+
+```yaml
+env_file:
+  - .env
+```
+
+If you just added this your app will require a rebuild.
+
+```bash
+lando rebuild -y
+```
+
+In your `tooling` section add.
+
+```yaml
+tooling:
+  envoy:
+    service: appserver
+  pull:
+    service: appserver
+    description: Pull and import the database from production.
+    cmd:
+      - appserver: envoy run pull
+      - database: /helpers/sql-import.sh db.sql
+      - appserver: rm db.sql
+      - appserver: rm -rf /app/web/files # change this to the /path/to/file/assets for your app.
+      - appserver: tar xvzf f.tgz -C /app/web
+      - appserver: rm f.tgz
+```
+
+## Using the pull command
+
+Now to use your pull command you'll need to configure the `backups` directories as specified in `LP_DB_BACK_PATH` and `LP_FILES_BACK_PATH`
+to exist on your server. Then just run:
+
+```bash
+lando pull
+```
+
+and that will backup your db and file assets and pull them down for you! Happy Lando travels folks.
+
+<GuideFooter test="" original="" repo=""/>
+<Newsletter />
diff --git a/docs/guides/how-do-i-configure-a-lando-recipe.md b/docs/guides/how-do-i-configure-a-lando-recipe.md
new file mode 100644
index 0000000..ed9da3d
--- /dev/null
+++ b/docs/guides/how-do-i-configure-a-lando-recipe.md
@@ -0,0 +1,80 @@
+---
+title: How do I configure a Lando Recipe?
+metaTitle: How do I configure a Lando Recipe? | Lando
+description: Using the lando config key to configure your recipe.
+date: 2020-02-04T18:00:18.702Z
+original: 
+repo: 
+
+author:
+  name: Team Lando
+  pic: https://gravatar.com/avatar/c335f31e62b453f747f39a84240b3bbd
+  link: https://twitter.com/devwithlando
+
+feed:
+  enable: true
+  author:
+    - name: Team Lando
+      email: alliance@lando.dev
+      link: https://twitter.com/devwithlando
+  contributor:
+    - name: Team Lando
+      email: alliance@lando.dev
+      link: https://twitter.com/devwithlando
+---
+
+# How do I configure a Lando Recipe?
+
+<GuideHeader name="Team Lando" pic="https://gravatar.com/avatar/c335f31e62b453f747f39a84240b3bbd" link="https://twitter.com/devwithlando" test="https://github.com/lando/cli/tree/main/examples/lamp"/>
+
+When you first initialize a lando app (`lando init`) you get a very simple `.lando.yml` configuration file. Here is the `.lando.yml` file for the LAMP recipe.
+
+```yaml
+name: mylamp
+recipe: lamp
+config:
+  webroot: .
+```
+
+By using the `config` key in the `lando.yml` file you can configure aspects of your app to say match the production instance. For example say your production server
+is using PHP 5.6; you can set that under the `config` key like so:
+
+```yaml
+name: mylamp
+recipe: lamp
+config:
+  webroot: .
+  php: 5.6
+```
+
+Now be sure to `rebuild` your app so that the new changes take effect:
+
+```bash
+lando rebuild -y
+```
+
+You can check that the change took by using `lando php -v`:
+
+```bash
+└─ $ ∴ lando php -v
+PHP 5.6.40 (cli) (built: Jan 23 2019 00:10:05) 
+Copyright (c) 1997-2016 The PHP Group
+Zend Engine v2.6.0, Copyright (c) 1998-2016 Zend Technologies
+    with Zend OPcache v7.0.6-dev, Copyright (c) 1999-2016, by Zend Technologies
+```
+
+Similarly you can pin down the database backend and version of your app. Say you want MariaDB 10.3:
+
+```yaml
+name: mylamp
+recipe: lamp
+config:
+  webroot: .
+  php: 5.6
+  database: mariadb:10.3
+```
+
+Again rebuild for the changes: `lando rebuild -y` and 💥 you now have PHP 5.6 and MariaDB 10.3!
+
+<GuideFooter original="" repo=""/>
+<Newsletter />
diff --git a/docs/guides/how-do-i-set-the-timezone-of-a-lando-service.md b/docs/guides/how-do-i-set-the-timezone-of-a-lando-service.md
new file mode 100644
index 0000000..cf2f6d5
--- /dev/null
+++ b/docs/guides/how-do-i-set-the-timezone-of-a-lando-service.md
@@ -0,0 +1,63 @@
+---
+title: How do I set the timezone of a Lando service?
+metaTitle: How do I set the timezone of a Lando service? | Lando
+description: Set the timezone of a Lando service for testing time sensitive operations
+summary: Set the timezone of a Lando service for testing time sensitive operations
+date: 2020-03-27T22:30:09.777Z
+original:
+repo:
+
+author:
+  name: Team Lando
+  pic: https://gravatar.com/avatar/c335f31e62b453f747f39a84240b3bbd
+  link: https://twitter.com/devwithlando
+
+feed:
+  enable: true
+  author:
+    - name: Team Lando
+      email: alliance@lando.dev
+      link: https://twitter.com/devwithlando
+  contributor:
+    - name: Team Lando
+      email: alliance@lando.dev
+      link: https://twitter.com/devwithlando
+---
+
+# How do I set the timezone of a Lando service?
+
+<GuideHeader test="https://github.com/lando/cli/tree/main/examples/services" name="Team Lando" pic="https://gravatar.com/avatar/c335f31e62b453f747f39a84240b3bbd" link="https://twitter.com/devwithlando" />
+
+<YouTube url="https://www.youtube.com/embed/P8n2z4m0_s0" />
+
+If you need to set the timezone of a Lando service here is how! Just symlink the appropriate timezone you need in a `run_as_root` build step. Here is an example `.lando.yml` file.
+
+```yaml
+name: timezone
+recipe: lemp
+config:
+  webroot: .
+
+services:
+  appserver:
+    run_as_root:
+      - ln -snf /usr/share/zoneinfo/America/New_York /etc/localtime
+      - echo "America/New_York" > /etc/timezone
+```
+
+Just copy the `run_as_root` section into your `services` key for any service you need it for, i.e. `appserver`, `database`, or whatever service you need to set. Be sure to swap out `America/New_York` to the timezone that you need.
+
+::: warning Tested on Debian only
+Note that we test this on Debian flavored services so these instructions might differ slightly or be unapplicable for non-Debian services.
+:::
+
+Then run a rebuild:
+
+```bash
+lando rebuild -y
+```
+
+and you'll have the timezone set in those services.
+
+<GuideFooter original="" repo=""/>
+<Newsletter />
diff --git a/docs/guides/how-to-wire-up-browsersync-and-gulp-in-my-lando-app.md b/docs/guides/how-to-wire-up-browsersync-and-gulp-in-my-lando-app.md
new file mode 100644
index 0000000..5eee2f3
--- /dev/null
+++ b/docs/guides/how-to-wire-up-browsersync-and-gulp-in-my-lando-app.md
@@ -0,0 +1,186 @@
+---
+title: How do I wire up Browsersync and Gulp in my Lando app?
+metaTitle: How to wire up Browsersync and Gulp in my Lando app | Lando
+description: How to setup Lando with Browsersync & Gulp so that edits to scss files are reflected immediately in your browser.
+summary: How to setup Lando with Browsersync & Gulp so that edits to scss files are reflected immediately in your browser.
+date: 2020-04-07T14:05:33.088Z
+original:
+repo:
+
+author:
+  name: Jonathan Shaw
+  pic: https://www.gravatar.com/avatar/ba46283b2033d3a0201f2042746f81e7
+  link: https://github.com/jonathanjfshaw
+
+feed:
+  enable: true
+  author:
+    - name: Jonathan Shaw
+      email: alliance@lando.dev
+      link: https://github.com/jonathanjfshaw
+  contributor:
+    - name: Jonathan Shaw
+      email: alliance@lando.dev
+      link: https://github.com/jonathanjfshaw
+---
+
+# How do I wire up Browsersync and Gulp in my Lando app?
+
+<GuideHeader test="" name="Jonathan Shaw" pic="https://www.gravatar.com/avatar/ba46283b2033d3a0201f2042746f81e7" link="https://github.com/jonathanjfshaw" />
+<YouTube url="" />
+
+[Browsersync](https://www.browsersync.io) is a nodejs package that synchronizes website changes to the browser.
+While it can be used for many things, this guide shows how to use it to push changes made to css files to the browser.
+
+This guide also assumes you're using Gulp to automate your theming tasks, and are editing SASS/SCSS files that need compiling
+into css before they can be previewed in your browser.
+
+## Configuring Lando for Browsersync
+
+### Create the proxy
+
+First you must create a proxy domain for browsersync to use. Changes you make to your scss files will only show up when
+you are looking at this `https://bs.myproject.lndo.site`, not at the usual domain `https://myproject.lndo.site`.
+Add your equivalent of this to your .lando.yml file:
+
+```yaml
+proxy:
+  node:
+    - bs.myproject.lndo.site:3000
+```
+
+### Stream changes whenever Lando is running
+It's most convenient if Browsersync is running in the background whenever your Lando site is up.
+One simple way to achieve this is to fire off a gulp task whenever Lando starts up.
+If you had a gulp task called 'watch' then you'd put this in .lando.yml:
+
+```yaml
+services:
+  node:
+    type: node
+    ssl: true
+    command: cd /app/path/to/gulpfile && node_modules/.bin/gulp watch
+```
+
+## Configuring Gulp to push scss
+
+### Compiling scss
+
+Here's an example of a `gulpfile.js` that defines a task that compiles scss into css.
+Note the addition of `browserSync.stream()` at the end of the pipeline.
+This will send the compiled css to the browser, if browsersync is running.
+
+```js
+// Live CSS reload & browser Syncing.
+var browserSync = require('browser-sync').create();
+
+// Gulp plugin for showing scss file in browser inspect tools rather than the compiled css file.
+var sourcemaps = require('gulp-sourcemaps');
+
+// Gulp plugin for sass.
+var sass = require('gulp-sass');
+
+// Allows you to use glob syntax in imports (i.e. @import "dir/*.sass"). Use as a custom importer for node-sass.
+var importer = require('node-sass-globbing');
+
+// Default configuration.
+var config = {
+  scss: './scss/*.scss', // The top level scss files that include all other scss.
+  watch: './scss/**', // All scss files that should trigger a recompile.
+  css: './css', // The path to the generated css files.
+  node_modules: './node_modules', // The path to the node modules directory.
+};
+
+// A gulp task that compiles scss into css. Execute with 'gulp scss-compile'
+gulp.task('scss-compile', function () {
+ return gulp.src(config.scss)
+  .pipe(plumber())
+   // Start making a source map, so that the browser can show a developer which scss file is responsible for a css rule.
+  .pipe(sourcemaps.init({loadMaps: true})) //Not sure if loadMaps is a good idea.
+   // Compile the scss to css.
+  .pipe(sass({
+    importer: importer,
+    // Include some useful scss from external node packages.
+    includePaths: [
+      config.node_modules + '/breakpoint-sass/stylesheets/',
+      config.node_modules + '/compass-mixins/lib/'
+    ],
+    // Tweak output styling to make things easier for developers.
+    outputStyle: 'expanded',
+    sourceComments: true,
+    indentWidth: 2
+  }).on('error', sass.logError))
+  .pipe(sourcemaps.write('maps'))
+   // Write out the generated css.
+  .pipe(gulp.dest(config.css))
+   // Push the css to the browser.
+  .pipe(browserSync.stream());
+});
+```
+
+### Recompiling whenever the scss changes
+
+```js
+// Watch the scss files and push changes automatically.
+gulp.task('watch', function () {
+  // Setup a browsersync server.
+  browserSync.init({
+    proxy: 'http://appserver_nginx', // Could be 'http://appserver' if you're running apache.
+    socket: {
+      domain: 'https://bs.myproject.lndo.site', // The node proxy domain you defined in .lando.yaml. Must be https?
+      port: 80 // NOT the 3000 you might expect.
+    },
+    open: false,
+    logLevel: "debug",
+    logConnections: true,
+  });
+  // Trigger the scss-compile task whenever any file in the defined location changes.
+  gulp.watch(config.watch, gulp.series('scss-compile'));
+});
+```
+
+## Trying it out
+
+* Run `lando rebuild -y` so your new proxy domain is exposed.
+* Verify that the output includes under `NODE URLS` your new proxy `https://bs.myproject.lndo.site`, and it is green.
+* Run `lando logs -s node -f` to continuously stream the logs of the node service. You should see something like:
+
+```bash
+Using gulpfile /app/path/to/my/theme/gulpfile.js
+Starting 'watch'...
+...
+[Browsersync] Proxying: http://appserver_nginx
+[Browsersync] Access URLs:
+  Local: http://localhost:3000
+  External: http://172.20.0.6:3000
+```
+
+* Visit your browsersync url `https://bs.myproject.lndo.site` in your browser. It should load normally.
+* In the source of this page search for "browser-sync". You should see the browser-sync-client script has been injected into the page.
+* Look again at the streaming node logs; something like this should have appeared
+
+```bash
+[Browsersync] Browser Connected: Chrome, version: 80.0.3987.149
+```
+
+* In your IDE edit a style rule in an scss file, save if necessary, and wait a few seconds.
+* Look again at the logs; something like this should have appeared:
+
+```bash
+Starting 'scss-compile'...
+[Browsersync] 2 files changed (style.css.map, style.css)
+Finished 'scss-compile' after 1.88 s
+```
+
+* Look at your open browser window again (without refreshing). You should see the impact of your scss edit.
+* Feel very excited!
+
+## Known issues
+
+* When submitting a form on `https://bs.myproject.lndo.site` you will be redirected to `https://appserver_nginx` (which is not a working url).
+If you know a solution for this problem, please update this guide.
+* So to use the forms on a site use the non-browsersync URL, i.e. `https://myproject.lndo.site`.
+
+
+<GuideFooter test="" original="" repo=""/>
+<Newsletter />
diff --git a/docs/guides/installing-node-in-your-lando-php-service.md b/docs/guides/installing-node-in-your-lando-php-service.md
new file mode 100644
index 0000000..0d2079c
--- /dev/null
+++ b/docs/guides/installing-node-in-your-lando-php-service.md
@@ -0,0 +1,110 @@
+---
+title: Installing node in your Lando PHP service
+metaTitle: Installing node in your Lando PHP service | Lando
+description: Learn how to install node in a Lando PHP service for things like Pattern Lab or Emulsify
+summary: Learn how to install node in a Lando PHP service for things like Pattern Lab or Emulsify
+date: 2020-05-12T18:06:56.254Z
+original:
+repo:
+
+author:
+  name: Team Lando
+  pic: https://gravatar.com/avatar/c335f31e62b453f747f39a84240b3bbd
+  link: https://twitter.com/devwithlando
+
+feed:
+  enable: true
+  author:
+    - name: Team Lando
+      email: alliance@lando.dev
+      link: https://twitter.com/devwithlando
+  contributor:
+    - name: Team Lando
+      email: alliance@lando.dev
+      link: https://twitter.com/devwithlando
+---
+
+# Installing node in your Lando PHP service
+
+<GuideHeader test="https://circleci.com/gh/lando/lando/tree/master" name="Team Lando" pic="https://gravatar.com/avatar/c335f31e62b453f747f39a84240b3bbd" link="https://twitter.com/devwithlando" />
+<YouTube url="" />
+
+Some frontend tooling kits like [Emulsify](https://www.drupal.org/project/emulsify_drupal) or [Pattern Lab](https://patternlab.io/) _may_ assume that `composer/php` can invoke `yarn/npm/node` and vice-versa. This pattern, sadly, is fundamentally at odds with Lando's one-thing-per-container model.
+
+You can, however, get around it by installing the needed dependencies directly in the service that requires them.
+
+We've found installing `node` inside a Lando PHP service to generally be the path of least resistance.
+
+## 1. Using build steps
+
+Below is an example that installs `node12` using [build-steps](./../config/services.md#build-steps).
+
+```yaml
+services:
+  myservice:
+    type: php
+    build_as_root:
+      # Note that you will want to use the script for the major version of node you want to install
+      # See: https://github.com/nodesource/distributions/blob/master/README.md#installation-instructions
+      - curl -sL https://deb.nodesource.com/setup_12.x | bash -
+      - apt-get install -y nodejs
+tooling:
+  node:
+    service: myservice
+  npm:
+    service: myservice
+```
+
+You can verify with:
+
+```bash
+lando node -v
+lando npm -v
+```
+
+## 2. Extending a Dockerfile
+
+If you are planning to extend your service with _additional_ build steps or would like to cache the build steps for a faster `lando rebuild` you should instead consider [extending with a Dockerfile](./../config/services.md#using-dockerfiles) as in the example below:
+
+**.lando.yml**
+
+```yaml
+services:
+  myservice:
+    type: php:custom
+    via: cli
+    overrides:
+      image: lando/php:7.4-with-node12
+      build:
+        context: ./
+        dockerfile: Dockerfile.node
+tooling:
+  node:
+    service: myservice
+  npm:
+    service: myservice
+```
+
+**Dockerfile.node**
+
+```docker
+FROM devwithlando/php:7.4-apache-2
+
+# Choose the major node version
+ENV NODE_VERSION=12
+
+# Install node
+RUN curl -sL "https://deb.nodesource.com/setup_${NODE_VERSION}.x" | bash - \
+  && apt-get install -y nodejs
+```
+
+Again, you can verify with:
+
+```bash
+lando node -v
+lando npm -v
+```
+
+
+<GuideFooter test="https://circleci.com/gh/lando/lando/tree/master" original="" repo="https://github.com/lando/cli/tree/main/examples/php"/>
+<Newsletter />
diff --git a/docs/guides/installing-php-extensions-on-lando.md b/docs/guides/installing-php-extensions-on-lando.md
new file mode 100644
index 0000000..85d0bc1
--- /dev/null
+++ b/docs/guides/installing-php-extensions-on-lando.md
@@ -0,0 +1,111 @@
+---
+title: Installing PHP Extensions on Lando
+metaTitle: Installing PHP Extensions on Lando | Lando
+description: Learn a few ways you can install extra php extensions to your Lando PHP service
+summary: Learn a few ways you can install extra php extensions to your Lando PHP service
+date: 2020-05-12T16:52:31.824Z
+original:
+repo:
+
+author:
+  name: Team Lando
+  pic: https://gravatar.com/avatar/c335f31e62b453f747f39a84240b3bbd
+  link: https://twitter.com/devwithlando
+
+feed:
+  enable: true
+  author:
+    - name: Team Lando
+      email: alliance@lando.dev
+      link: https://twitter.com/devwithlando
+  contributor:
+    - name: Team Lando
+      email: alliance@lando.dev
+      link: https://twitter.com/devwithlando
+---
+
+# Installing PHP Extensions on Lando
+
+<GuideHeader test="https://circleci.com/gh/lando/lando/tree/master" name="Team Lando" pic="https://gravatar.com/avatar/c335f31e62b453f747f39a84240b3bbd" link="https://twitter.com/devwithlando" />
+<YouTube url="" />
+
+You may wish to add additional PHP extensions to your Lando [PHP service](./../config/php.md). There are a few different ways you can do this:
+
+[[toc]]
+
+Note that both of these strategies make use of underlying utilities provided by the [Official Docker PHP Image]() which is the base image used by Lando's PHP service. We recommend you read more about them [over on their docs](https://hub.docker.com/_/php).
+
+Also note that you may need to adapt these slightly depending on the PHP version you are using.
+
+## 1. Using build steps
+
+If installing your PHP extension is fairly trivial and not a long-running operation you may wish to simply use Lando [build-steps](./../config/services.md#build-steps)
+
+Here is an example that uses build-steps to install the `xsl` and `stats` extensions.
+
+```yaml
+services:
+  myservice:
+    type: php
+    build_as_root:
+      - apt-get update -y
+      - apt install libxslt1-dev -y
+      - pecl install stats-2.0.3
+      - docker-php-ext-install xsl
+      - docker-php-ext-enable stats
+```
+
+You can verify the extension was enabled by running:
+
+```bash
+lando ssh -s myservice -c "php -m"
+```
+
+A downside of this approach is these steps till run _EVERY TIME_ you do a `lando rebuild`.
+
+## 2. Using Dockerfiles
+
+If you have complex, lengthy or long running build steps you may wish to create a `Dockerfile` in your repo that directly extends one of [Lando's PHP images](https://hub.docker.com/r/devwithlando/php/tags).
+
+This approach is great if you care about rebuild speed. Docker will cache the resultant image and only rebuild if the Dockerfile changes. By extension this means your `lando rebuild` will be pretty fast as well.
+
+It also ensures your Landofile does not get unruly.
+
+Here is an example that installs the `oci8` and `pdo_sqlsrv` extension.
+
+**.lando.yml**
+
+```yaml
+services:
+  myservice:
+    type: php:custom
+    overrides:
+      image: lando/php:7.3-custom
+      build:
+        context: ./
+        dockerfile: Dockerfile.custom
+      ports:
+        - "80"
+```
+
+**Dockerfile.custom**
+
+```docker
+FROM devwithlando/php:7.3-apache-2
+
+# Add php extension helper
+ADD https://github.com/mlocati/docker-php-extension-installer/releases/latest/download/install-php-extensions /usr/local/bin/
+
+# Install Oracle Instantclient, OCI8 and Microsoft SQL Server extensions
+RUN chmod +x /usr/local/bin/install-php-extensions && sync && \
+  install-php-extensions oci8-2.2.0 sqlsrv pdo_sqlsrv
+```
+
+You can verify the extension was enabled by running
+
+```bash
+lando ssh -s myservice -c "php -m"
+```
+
+<GuideFooter test="https://circleci.com/gh/lando/lando/tree/master" original="" repo="https://github.com/lando/cli/tree/main/examples/php-extensions"/>
+<Newsletter />
diff --git a/docs/guides/lando-101/lando-config.md b/docs/guides/lando-101/lando-config.md
new file mode 100644
index 0000000..8746a24
--- /dev/null
+++ b/docs/guides/lando-101/lando-config.md
@@ -0,0 +1,65 @@
+---
+title: Lando Configure
+metaTitle: Lando Configure | Lando
+description: An example using the config key to configure a Lando recipe.
+summary: An example of extending a Lando recipe using the config key.
+date: 2020-08-12T14:38:22.169Z
+original: 
+repo: 
+
+author:
+  name: Team Lando
+  pic: https://gravatar.com/avatar/c335f31e62b453f747f39a84240b3bbd
+  link: https://twitter.com/devwithlando
+
+feed:
+  enable: true
+  author:
+    - name: Team Lando
+      email: alliance@lando.dev
+      link: https://twitter.com/devwithlando
+  contributor:
+    - name: Team Lando
+      email: alliance@lando.dev
+      link: https://twitter.com/devwithlando
+---
+
+# Lando Configuration
+
+<GuideHeader test="https://github.com/lando/lando/blob/master/examples/lando-101/README.md" name="Team Lando" pic="https://gravatar.com/avatar/c335f31e62b453f747f39a84240b3bbd" link="https://twitter.com/devwithlando" />
+<YouTube url="" />
+
+As we've seen Lando recipes are very useful and dead simple. So far our `.lando.yml` file for the LAMP recipe is just two lines:
+
+```yaml
+name: lando-101
+recipe: lamp
+```
+
+The power of Lando is our ability to configure and change it to meet our needs. We can configure it to match production for instance. Let's add a PHP file to our `lando-101` app just so we have something to view in our app. Open a file in your favorite text editor and add a call to `phpinfo()` and save it as `index.php`.
+
+```php
+<?php
+phpinfo();
+```
+
+Now if we visit our Lando provide URL for the `lando-101` app `https://lando-101.lndo.site` we will see:
+
+<img src="/images/lando-101/lando-101-index.jpg" />
+
+We can see that this reports the PHP version as `7.3`. Enter the `config` key. Say our production server for the `lando-101` app is running PHP 7.4 and we want to match that in our Lando development environment. We can do that by using the [config](/config/lamp.html#configuration) key in our `.lando.yml` file to configure how the recipe is built. In this case we want PHP 7.4. Edit your `.lando.yml` file like this:
+
+```yaml
+name: lando-101
+recipe: lamp
+config:
+  php: 7.4
+```
+
+Now let's rebuild our app with the `lando rebuild -y` command. Now if we visit our app in a browser we will see the the PHP version is reported as `7.4`. Simple! Just like that we've configured our app to use a different version of PHP.
+
+You can read the details about the `config` key in the docs: [config](/config/recipes.html#config).
+
+
+<GuideFooter test="" original="" repo=""/>
+<Newsletter />
diff --git a/docs/guides/lando-101/lando-init.md b/docs/guides/lando-101/lando-init.md
new file mode 100644
index 0000000..1744bac
--- /dev/null
+++ b/docs/guides/lando-101/lando-init.md
@@ -0,0 +1,117 @@
+---
+title: Lando Init
+metaTitle: Lando Init | Lando
+description: Introduction to Lando ~ Using lando init command.
+summary: Introduction to Lando ~ Using lando init command.
+date: 2020-06-16T13:44:13.109Z
+original: 
+repo: 
+
+author:
+  name: Team Lando
+  pic: https://gravatar.com/avatar/c335f31e62b453f747f39a84240b3bbd
+  link: https://twitter.com/devwithlando
+
+feed:
+  enable: true
+  author:
+    - name: Team Lando
+      email: alliance@lando.dev
+      link: https://twitter.com/devwithlando
+  contributor:
+    - name: Team Lando
+      email: alliance@lando.dev
+      link: https://twitter.com/devwithlando
+---
+
+# Lando Init
+
+<GuideHeader test="https://github.com/lando/lando/blob/master/examples/lando-101/README.md" name="Team Lando" pic="https://gravatar.com/avatar/c335f31e62b453f747f39a84240b3bbd" link="https://twitter.com/devwithlando" />
+<YouTube url="" />
+
+The `lando init` command follows the pattern of `git init` or `npm init`. Where `lando init` will prompt you with some questions and prepares a `.lando.yml` configuration file for you. You can run `lando init` from an empty directory or from an extant codebase.
+
+Let's step through the questions that `lando init` prompts us with:
+
+```bash
+gff ~/code/lando-ops/guides-example-code/introduction-to-lando/lando-init 
+() └─ ∴ lando init
+? From where should we get your app's codebase? 
+  current working directory 
+  github 
+  pantheon 
+  platformsh 
+❯ remote git repo or archive 
+```
+
+The first question is `? From where should we get your app's codebase?` and it wants to know where the application code lives, i.e. if you are in an application that you want to initialize for use with Lando you would choose `current working directory`.
+
+The next question is `? What recipe do you want to use?`. Recipes are pre-configured start states that Lando knows about. For this course we'll choose the LAMP recipe.
+
+```bash
+? What recipe do you want to use? (Use arrow keys)
+❯ lamp 
+  laravel 
+  lemp 
+  mean 
+  pantheon 
+  platformsh 
+  wordpress 
+(Move up and down to reveal more choices)
+```
+
+Next up Lando prompts us for the webroot of the application: `? Where is your webroot relative to the init destination?` The webroot can be nested or it can be in the same location as the `.lando.yml` file the project root. For this course we'll leave the default `.` for the current working directory.
+
+```bash
+? Where is your webroot relative to the init destination? (.)
+```
+
+Then Lando needs to know a name for our application:
+
+```bash
+? What do you want to call this app? Lando 101
+```
+
+We'll name this app `Lando 101`.
+
+That's it!
+
+We've successfully initialized our first Lando app. We should see a message similar to:
+
+```bash
+? What do you want to call this app? lando-101
+
+   _  __                       _         
+  / |/ /__ _    __  _    _____( )_______ 
+ /    / _ \ |/|/ / | |/|/ / -_)// __/ -_)
+/_/|_/\___/__,__/  |__,__/\__/ /_/  \__/ 
+                                         
+  _________  ____  __ _______  _______  _      ______________ __  ___________  ______
+ / ___/ __ \/ __ \/ //_/  _/ |/ / ___/ | | /| / /  _/_  __/ // / / __/  _/ _ \/ __/ /
+/ /__/ /_/ / /_/ / ,< _/ //    / (_ /  | |/ |/ // /  / / / _  / / _/_/ // , _/ _//_/ 
+\___/\____/\____/_/|_/___/_/|_/\___/   |__/|__/___/ /_/ /_//_/ /_/ /___/_/|_/___(_)  
+                                                                                     
+Your app has been initialized!
+
+Go to the directory where your app was initialized and run lando start to get rolling.
+Check the LOCATION printed below if you are unsure where to go.
+
+Oh... and here are some vitals:
+
+ NAME      lando-101                                                                     
+ LOCATION  /home/gff/code/lando-ops/guides-example-code/introduction-to-lando/lando-init 
+ RECIPE    lamp                                                                          
+ DOCS      https://docs.lando.dev/config/lamp.html   
+```
+
+And the result is that Lando has written a `.lando.yml` configuration file for us in the project root. If you are following along that file should look like this:
+
+```yaml
+name: lando-101
+recipe: lamp
+```
+The `.lando.yml` file gives Lando the information it needs to spin up your application. In this case just two lines! The `name` of the app and the `recipe` to use. We recommend that you commit the `.lando.yml` file to version control so that everyone on your team can have the exact same configuration for development.
+
+You can see the full documentation for [lando init](/basics/init.html).
+<GuideFooter test="" original="" repo=""/>
+<Newsletter />
diff --git a/docs/guides/lando-101/lando-overview.md b/docs/guides/lando-101/lando-overview.md
new file mode 100644
index 0000000..671a501
--- /dev/null
+++ b/docs/guides/lando-101/lando-overview.md
@@ -0,0 +1,48 @@
+---
+title: Lando Overview
+metaTitle: Lando Overview | Lando
+description: Overview of Lando ecosystem ~ install, init, configure, services, tooling, build steps, and events.
+summary: Overview of Lando ecosystem install, init, configure, services, tooling, build steps, and events.
+date: 2020-07-10T14:38:22.169Z
+original: 
+repo: 
+
+author:
+  name: Team Lando
+  pic: https://gravatar.com/avatar/c335f31e62b453f747f39a84240b3bbd
+  link: https://twitter.com/devwithlando
+
+feed:
+  enable: true
+  author:
+    - name: Team Lando
+      email: alliance@lando.dev
+      link: https://twitter.com/devwithlando
+  contributor:
+    - name: Team Lando
+      email: alliance@lando.dev
+      link: https://twitter.com/devwithlando
+---
+
+# Lando Overview
+
+<GuideHeader test="https://github.com/lando/lando/blob/master/examples/lando-101/README.md" name="Team Lando" pic="https://gravatar.com/avatar/c335f31e62b453f747f39a84240b3bbd" link="https://twitter.com/devwithlando" />
+<YouTube url="" />
+
+Lando can isolate all your dev needs on a per app basis. This course will walk you through some examples of what can be accomplished with Lando development environments. If you have not installed Lando yet head over to [installing](/basics/installation.html) first.
+
+Here is the outline of content the Lando 101 course will cover:
+
+* [Init](/guides/lando-101/lando-init.html)
+* [Start](/guides/lando-101/lando-start.html)
+* [Configure](/guides/lando-101/lando-config.html)
+* [Add a Service](/guides/lando-101/lando-services.html)
+* [Add a Proxy URL](/guides/lando-101/lando-proxy.html)
+* [Add Tooling](/guides/lando-101/lando-tooling.html)
+* Add a Build step
+* Add an Event
+
+Throughout the Lando 101 course you'll see a number of hyperlinks in the text. These usually link to the full documentation or deep dives on a topic. We'd recommend that for your first read through that you simply ignore those links and go back to them after to deepen your understanding of Lando once you have the basics down.
+
+<GuideFooter test="" original="" repo=""/>
+<Newsletter />
diff --git a/docs/guides/lando-101/lando-proxy.md b/docs/guides/lando-101/lando-proxy.md
new file mode 100644
index 0000000..c521224
--- /dev/null
+++ b/docs/guides/lando-101/lando-proxy.md
@@ -0,0 +1,69 @@
+---
+title: Lando Proxy
+metaTitle: Lando Proxy | Lando
+description: An example of using the Lando proxy key. 
+summary: An example of adding the a proxy URL to a Lando service.
+date: 2020-09-04T14:38:22.169Z
+original: 
+repo: 
+
+author:
+  name: Team Lando
+  pic: https://gravatar.com/avatar/c335f31e62b453f747f39a84240b3bbd
+  link: https://twitter.com/devwithlando
+
+feed:
+  enable: true
+  author:
+    - name: Team Lando
+      email: alliance@lando.dev
+      link: https://twitter.com/devwithlando
+  contributor:
+    - name: Team Lando
+      email: alliance@lando.dev
+      link: https://twitter.com/devwithlando
+---
+
+# Lando Proxy
+
+<GuideHeader test="https://github.com/lando/lando/blob/master/examples/lando-101/README.md" name="Team Lando" pic="https://gravatar.com/avatar/c335f31e62b453f747f39a84240b3bbd" link="https://twitter.com/devwithlando" />
+<YouTube url="" />
+
+Some `services` like `mailhog` provide an admin interface via a browser. In such cases it is convenient to assign a URL to the service container. We do so via the `proxy` key in our `.lando.yml` file.
+
+Let's add a URL to our `mailhog` service so we can access the MailHog dashboard. Open up your Lando 101 `.lando.yml` file and add a proxy section like so:
+
+```yaml
+name: lando-101
+recipe: lamp
+config:
+  php: 7.4
+services:
+  mailhog:
+    type: mailhog:v1.0.0
+    portforward: true
+    hogfrom:
+      - appserver
+proxy:
+  mailhog:
+    - mail.lando-101.lndo.site
+```
+
+The new config being the `proxy` key which takes a `service` and the `service` gets an array of URLs in this case `- mail.lando-101.lndo.site`. You can add a URL to any service you like.
+
+::: warning Rebuild Required
+After adding a `proxy` make sure to `rebuild` the Lando 101 app.
+
+```bash
+lando rebuild -y
+```
+:::
+
+After rebuilding we can now access the new `mail.lando-101.lndo.site` URL to view the MailHog dashboard.
+
+<img src="/images/lando-101/mh.jpg" />
+
+Using the `proxy` key in our `.lando.yml` file we can add a URL to any `service` in a Lando app! If you need to dig deeper you can find the read the [full proxy documentatioin](/config/proxy.html).
+
+<GuideFooter test="" original="" repo=""/>
+<Newsletter />
diff --git a/docs/guides/lando-101/lando-services.md b/docs/guides/lando-101/lando-services.md
new file mode 100644
index 0000000..6749acd
--- /dev/null
+++ b/docs/guides/lando-101/lando-services.md
@@ -0,0 +1,75 @@
+---
+title: Lando Services
+metaTitle: Lando Services | Lando
+description: An example adding the mailhog service to a Lando recipe.
+summary: An example of adding the mailhog service to a Lando recipe using the services key.
+date: 2020-08-28T14:38:22.169Z
+original: 
+repo: 
+
+author:
+  name: Team Lando
+  pic: https://gravatar.com/avatar/c335f31e62b453f747f39a84240b3bbd
+  link: https://twitter.com/devwithlando
+
+feed:
+  enable: true
+  author:
+    - name: Team Lando
+      email: alliance@lando.dev
+      link: https://twitter.com/devwithlando
+  contributor:
+    - name: Team Lando
+      email: alliance@lando.dev
+      link: https://twitter.com/devwithlando
+---
+
+# Lando Services
+
+<GuideHeader test="https://github.com/lando/lando/blob/master/examples/lando-101/README.md" name="Team Lando" pic="https://gravatar.com/avatar/c335f31e62b453f747f39a84240b3bbd" link="https://twitter.com/devwithlando" />
+<YouTube url="" />
+
+Another way you can extend Lando recipes is by adding additional [services](/config/services.html). If you need to add a second database to your app, a node container for theming, or any number of use cases you can handle them by adding the appropriate service to your app. In this example we'll add a [mailhog](/config/mailhog.html) service to our Lando 101 app!
+
+Open up your `.lando.yml` configuration file in your favorite text editor. If you are following along with Lando 101 that file currently looks like this:
+
+```yaml
+name: lando-101
+recipe: lamp
+config:
+  php: 7.4
+```
+
+We'll now add the `services` key to our `.lando.yml` file and add in our `mailhog` service:
+
+```yaml
+name: lando-101
+recipe: lamp
+config:
+  php: 7.4
+services:
+  mailhog:
+    type: mailhog:v1.0.0
+    portforward: true
+    hogfrom:
+      - appserver
+```
+
+The new configuration for our `mailhog` service is under the `services` key in our `.lando.yml` file. The service name can be anything. We've named it `mailhog` after the service it provides, but you can name it anything you like. The `type` tells lando what `service` to use (what image to initially fetch and subsequently use). Then the `portforward` key will automatically set a port for the new service, and finally the `hogfrom` key is specific to the the `mailhog` service and tells mailhog where it should be grabbing the mail from for the Lando 101 app that is the appserver.
+
+After adding or changing a `service` in our app a rebuild is required.
+
+```bash
+lando rebuild -y
+```
+
+After rebuilding the Lando 101 app the new `mailhog` service will be available to our app! You can verify that by running: `docker ps` and you should see a line similar to this:
+
+```bash
+00daf795ccd0        mailhog/mailhog:v1.0.0               "/lando-entrypoint.s…"   25 seconds ago      Up 24 seconds       8025/tcp, 127.0.0.1:32780->80/tcp, 127.0.0.1:32778->1025/tcp              lando101_mailhog_1
+```
+
+You can see that our `lando101_mailhog_1` container is up and running and ready for us to use! Some services, like the `mailhog` service, will need to have a URL exposed in order to make use of them. In the next section we'll demonstrate how to add a proxy URL for the `mailhog` service.
+
+<GuideFooter test="" original="" repo=""/>
+<Newsletter />
diff --git a/docs/guides/lando-101/lando-start.md b/docs/guides/lando-101/lando-start.md
new file mode 100644
index 0000000..0f0a1ae
--- /dev/null
+++ b/docs/guides/lando-101/lando-start.md
@@ -0,0 +1,72 @@
+---
+title: Lando Start
+metaTitle: Lando Start | Lando
+description: Start a Lando app and some vocabulary to help us talk about Lando.
+summary: Lando start command and some vocabulary to help us understand the Lando ecosystem.
+date: 2020-07-27T14:38:22.169Z
+original: 
+repo: 
+
+author:
+  name: Team Lando
+  pic: https://gravatar.com/avatar/c335f31e62b453f747f39a84240b3bbd
+  link: https://twitter.com/devwithlando
+
+feed:
+  enable: true
+  author:
+    - name: Team Lando
+      email: alliance@lando.dev
+      link: https://twitter.com/devwithlando
+  contributor:
+    - name: Team Lando
+      email: alliance@lando.dev
+      link: https://twitter.com/devwithlando
+---
+
+# Lando Start
+
+<GuideHeader test="https://github.com/lando/lando/blob/master/examples/lando-101/README.md" name="Team Lando" pic="https://gravatar.com/avatar/c335f31e62b453f747f39a84240b3bbd" link="https://twitter.com/devwithlando" />
+<YouTube url="" />
+
+This lesson is primarily about vocabulary to help us understand the Lando ecosystem. A `recipe` in Lando is a pre-configured start state for an application. Lando comes [with more than 12 recipes](/config/recipes.html) out of the box. In the Lando 101 course we are using the [LAMP](/config/lamp.html#getting-started) recipe. This tells Lando that we'll need an application container with Apache and PHP and a MySQL container.
+
+So, if we `lando start` our `Lando 101` app we'll see those corresponding containers. Here is some of the output from `lando start`:
+
+```bash
+Scanning to determine which services are ready... Please standby...
+
+   ___                      __        __        __     __        ______
+  / _ )___  ___  __ _  ___ / /  ___ _/ /_____ _/ /__ _/ /_____ _/ / / /
+ / _  / _ \/ _ \/  ' \(_-</ _ \/ _ `/  '_/ _ `/ / _ `/  '_/ _ `/_/_/_/ 
+/____/\___/\___/_/_/_/___/_//_/\_,_/_/\_\\_,_/_/\_,_/_/\_\\_,_(_|_|_)  
+                                                                       
+
+Your app has started up correctly.
+Here are some vitals:
+
+ NAME            lando-101                                                                     
+ LOCATION        /home/gff/code/lando-ops/guides-example-code/introduction-to-lando/lando-init 
+ SERVICES        appserver, database                                                           
+ APPSERVER URLS  https://localhost:32952                                                       
+                 http://localhost:32953                                                        
+                 http://lando-101.lndo.site/                                                   
+                 https://lando-101.lndo.site/                                                  
+```
+
+And if you run the docker command: `docker ps` you can see the containers for the Lando 101 app:
+
+```bash
+gff ~/code/lando-ops/guides-example-code/introduction-to-lando/lando-init 
+() └─ ∴ docker ps
+CONTAINER ID        IMAGE                                COMMAND                  CREATED             STATUS              PORTS                                                                     NAMES
+c92d36534d66        devwithlando/php:7.3-apache-2        "/lando-entrypoint.s…"   25 seconds ago      Up 23 seconds       127.0.0.1:32953->80/tcp, 127.0.0.1:32952->443/tcp                         lando101_appserver_1
+a5d7060a15be        bitnami/mysql:5.7.29-debian-10-r51   "/lando-entrypoint.s…"   25 seconds ago      Up 23 seconds       127.0.0.1:32951->3306/tcp                                                 lando101_database_1
+7f64e8add1fd        traefik:2.2.0                        "/lando-entrypoint.s…"   30 hours ago        Up 25 seconds       127.0.0.1:80->80/tcp, 127.0.0.1:443->443/tcp, 127.0.0.1:32950->8080/tcp   landoproxyhyperion5000gandalfedition_proxy_1
+
+```
+
+So you can see that Lando has started up `lando101_appserver_1`, `lando101_database_1`, and `landoproxyhyperion5000gandalfedition_proxy_1` containers. Behind the scenes Lando is managing the containers, persistent storage, and the networking for the containers to communication with each other. We don't need to worry about that Lando handles it for us. If later we want to take a deep dive you can see how Lando leverages docker-compose to get that all done for us, but for now just know Lando takes care of the right configurations for the recipe we choose.
+
+<GuideFooter test="" original="" repo=""/>
+<Newsletter />
diff --git a/docs/guides/lando-101/lando-tooling.md b/docs/guides/lando-101/lando-tooling.md
new file mode 100644
index 0000000..4a09042
--- /dev/null
+++ b/docs/guides/lando-101/lando-tooling.md
@@ -0,0 +1,77 @@
+---
+title: Lando Tooling
+metaTitle: Lando Proxy | Lando
+description: An example of adding tooling to a Lando app.
+summary: An example of adding tooling to your Lando app. 
+date: 2020-09-05T14:38:22.169Z
+original: 
+repo: 
+
+author:
+  name: Team Lando
+  pic: https://gravatar.com/avatar/c335f31e62b453f747f39a84240b3bbd
+  link: https://twitter.com/devwithlando
+
+feed:
+  enable: true
+  author:
+    - name: Team Lando
+      email: alliance@lando.dev
+      link: https://twitter.com/devwithlando
+  contributor:
+    - name: Team Lando
+      email: alliance@lando.dev
+      link: https://twitter.com/devwithlando
+---
+
+# Lando Tooling
+
+<GuideHeader test="https://github.com/lando/lando/blob/master/examples/lando-101/README.md" name="Team Lando" pic="https://gravatar.com/avatar/c335f31e62b453f747f39a84240b3bbd" link="https://twitter.com/devwithlando" />
+<YouTube url="" />
+
+Lando provides context specific tooling for the provided recipes, for example, the `lando-101` app is using the `lamp` recipe and out of the box provides us with tooling commands for `php` cli, `composer`, and a `mysql` shell among others. You can see the available commands for any given Lando app by typing `lando` at your command prompt.
+
+Sometimes we might need or want to add our own tooling to a Lando app to simplify workflows, use in CI, and reduce documentation. Let's add a `phpcs` tooling command to our Lando 101 app.
+
+First lets use the Lando provided `composer` tooling to add `phpcs` to our Lando 101 app:
+
+```bash
+lando composer require squizlabs/php_codesniffer
+```
+
+That will place the `phpcs` binary in `/app/vendor/bin/phpcs` and we'll use that path to expose the tooling to our Lando 101 app.
+
+Open up your `.lando.yml` config file in your favorite text editor:
+
+```yaml
+name: lando-101
+recipe: lamp
+config:
+  php: 7.4
+services:
+  mailhog:
+    type: mailhog:v1.0.0
+    portforward: true
+    hogfrom:
+      - appserver
+proxy:
+  mailhog:
+    - mail.lando-101.lndo.site
+tooling:
+  phpcs:
+    service: appserver
+    cmd: /app/vendor/bin/phpcs
+```
+
+The new part of our config is the `tooling` key under which we have nested the command we want to expose, `phpcs` in this case. Told Lando which service to run the tooling command against with `service: appserver`. Provided the `cmd: /app/vendor/bin/phpcs` to tell Lando what command to run under the hood.
+
+Now all the developers on our team for the Lando 101 app can code sniff their code to provide uniform standards across the project. For example, if you want to check the syntax of the `index.php` file; you do so like this:
+
+```bash
+lando phpcs index.php
+```
+
+Adding the `phpcs` command is simple, but just one example of the types of tooling you can add to your apps. To take a deep dive and learn more about Lando tooling read the [tooling docs page](/config/tooling.html).
+
+<GuideFooter test="" original="" repo=""/>
+<Newsletter />
diff --git a/docs/guides/lando-info.md b/docs/guides/lando-info.md
new file mode 100644
index 0000000..a911ea8
--- /dev/null
+++ b/docs/guides/lando-info.md
@@ -0,0 +1,45 @@
+---
+description: Learn how to use Lando's default environment variables inside you application.
+date: 2019-11-05
+---
+
+# Using $LANDO_INFO
+
+<GuideHeader />
+
+Lando will inject an environment variable called `$LANDO_INFO` into each service. This is a `JSON` string representation of the `lando info` command and you can use it to see valuable information about other services such as service hostnames and database connection information and credentials.
+
+This is helpful if you want to set application configuration in a way that is portable and dynamic between many lando apps.
+
+::: warning Use `internal_connection` information!
+For services with both `external_connection` and `internal_connection` information. ALWAYS use the `internal_connection` information inside of your application.
+:::
+
+Here are some examples of code on how to parse `$LANDO_INFO`.
+
+## Using PHP
+
+```php
+$info = json_decode(getenv('LANDO_INFO'), TRUE);
+print_r($info);
+```
+
+## Using Javascript/NodeJS
+
+```js
+'use strict';
+
+var info = JSON.parse(process.env.LANDO_INFO);
+
+console.log(info);
+```
+
+## Using Other
+
+More examples coming soon but in the meantime consult the documentation for your language on how to:
+
+* Grab an environment variable
+* Decode a JSON string to an object
+
+<GuideFooter />
+<Newsletter />
diff --git a/docs/guides/lando-phpstorm.md b/docs/guides/lando-phpstorm.md
new file mode 100644
index 0000000..4a75374
--- /dev/null
+++ b/docs/guides/lando-phpstorm.md
@@ -0,0 +1,43 @@
+---
+description: Learn how to configure xdebug in Lando using PhpStorm.
+date: 2019-11-05
+---
+
+# Lando + PhpStorm + Xdebug
+
+<GuideHeader />
+<YouTube url="https://www.youtube.com/embed/sHNJxx0L9r0" />
+
+[PhpStorm](https://www.jetbrains.com/phpstorm/) is a popular code IDE for PHP
+and Drupal development. This video tutorial shows you how to set up PhpStorm with Xdebug.
+
+If you’ve a local php installation (for example php 7.1 installed with homebrew on macOS) that listens on port 9000 you may need to change the containers php.ini port specification to another port (i.e. `xdebug.remote_port=9001`) and tell phpstorm to listen on that port. See also [Debugging Drupal 8 with PHPstorm and Lando on your Mac](https://www.isovera.com/2020/11/24/debugging-drupal-8-with-phpstorm-and-lando-on-your-mac/).
+
+### PHP 7.3 and later
+With PHP 7.3, the setting `xdebug.remote_port` has been deprecated, and the setting `xdebug.client_port` should be used instead.
+Also the default xdebug port changed from `9000` to `9003`.
+
+https://xdebug.org/docs/upgrade_guide#changed-xdebug.remote_port
+
+## Debugging Drush Commands
+
+By default our Drupal recipes come with Drush out of the box. In order to debug any Drush command using Xdebug using
+PhpStorm or a similar IDE, you will need to set an additional environment variable `PHP_IDE_CONFIG` and configure the
+path mapping in your IDE accordingly.
+
+```yaml
+services:
+  appserver:
+    overrides:
+      environment:
+        # Support debugging Drush with XDEBUG.
+        PHP_IDE_CONFIG: "serverName=appserver"
+```
+
+You are free to assign any name to "serverName" as long as it matches the server you define in the IDE settings.
+In the example above we set the variable to `appserver` and created a path mapping for the server accordingly:
+
+![screenshot](/images/drush-xdebug-phpstorm.png)
+
+<GuideFooter />
+<Newsletter />
diff --git a/docs/guides/lando-with-vscode.md b/docs/guides/lando-with-vscode.md
new file mode 100644
index 0000000..34f6f4a
--- /dev/null
+++ b/docs/guides/lando-with-vscode.md
@@ -0,0 +1,277 @@
+---
+description: Learn how to configure xdebug in Lando using VSCode.
+date: 2019-11-05
+---
+
+# Using Lando with VSCode
+
+<GuideHeader />
+
+[Visual Studio Code](https://github.com/Microsoft/vscode/) is a great open source editor for programming. Debugging PHP applications with it can be easy too.
+
+This is a basic setup to help you in this task.
+
+[[toc]]
+
+## Getting Started
+
+Enable Xdebug by adding some lines to your Lando recipe.
+
+**Lando beta versions and rc.1** need `conf:` at file root as follow:
+
+```yaml
+name: mywebsite
+recipe: drupal8
+config:
+  webroot: docroot
+  xdebug: true
+  conf:
+    php: .vscode/php.ini
+```
+
+**Lando rc.2+** needs `config:` under `services:` as follow:
+
+```yaml
+name: mywebsite
+recipe: drupal8
+services:
+  appserver:
+    webroot: web
+    xdebug: true
+    config:
+      php: .vscode/php.ini
+```
+
+**Tell Lando to use additional PHP settings**
+
+Create the custom `php.ini` file to add XDebug settings to PHP.
+
+```bash
+touch .vscode/php.ini
+code .vscode/php.ini
+```
+
+The location of this file is arbitrary.
+
+We placed it inside `.vscode/` folder simply because we find it convenient.
+
+Add your custom XDebug settings, which will vary slightly depending on which version of PHP and xdebug you're using.
+
+**PHP 7.2+ uses xdebug 3** and needs `config:` under `services:` as follow:
+
+```ini
+[PHP]
+
+; Xdebug
+xdebug.max_nesting_level = 256
+xdebug.show_exception_trace = 0
+xdebug.collect_params = 0
+; Extra custom Xdebug setting for debug to work in VSCode.
+xdebug.mode = debug
+xdebug.client_host = ${LANDO_HOST_IP}
+xdebug.client_port = 9003
+xdebug.start_with_request = trigger
+; xdebug.remote_connect_back = 1
+xdebug.log = /tmp/xdebug.log
+```
+
+**PHP 7.1 and earlier uses xdebug 2** and needs `config:` under `services:` as follow:
+
+```ini
+[PHP]
+
+; Xdebug
+xdebug.max_nesting_level = 256
+xdebug.show_exception_trace = 0
+xdebug.collect_params = 0
+; Extra custom Xdebug setting for debug to work in VSCode.
+xdebug.remote_enable = 1
+xdebug.remote_autostart = 1
+xdebug.remote_host = ${LANDO_HOST_IP}
+; xdebug.remote_connect_back = 1
+xdebug.remote_log = /tmp/xdebug.log
+```
+
+Rebuild your environment.
+
+```bash
+lando rebuild -y
+```
+
+Finally, add a custom `launch.json` file in VSCode in order to map paths so that XDebug works correctly.
+
+```bash
+touch .vscode/launch.json
+code .vscode/launch.json
+```
+
+```json
+{
+  "version": "0.2.0",
+  "configurations": [
+    {
+      "name": "Listen for XDebug",
+      "type": "php",
+      "request": "launch",
+      "port": 9003,
+      "log": false,
+      "pathMappings": {
+        "/app/": "${workspaceFolder}/",
+      }
+    }
+  ]
+}
+```
+
+**Note: PHP 7.1 and earlier uses xdebug 2** which uses port 9000, so change the port number above accordinly.
+
+
+Done!
+
+You can now click start debugging (type F5 or click on the icon in the left sidebar).
+
+## Advanced Setup
+
+Optionally for better performance you can easily toggle Xdebug on and off with some custom tooling commands.
+
+If you're using Apache, add this to your `.lando.yml`:
+
+```yaml
+services:
+  appserver:
+    overrides:
+      environment:
+        XDEBUG_MODE:
+tooling:
+  xdebug-on:
+    service: appserver
+    description: Enable xdebug for Apache.
+    cmd: docker-php-ext-enable xdebug && /etc/init.d/apache2 reload && echo "Enabling xdebug"
+    user: root
+
+  xdebug-off:
+    service: appserver
+    description: Disable xdebug for Apache.
+    cmd: rm /usr/local/etc/php/conf.d/docker-php-ext-xdebug.ini && /etc/init.d/apache2 reload && echo "Disabling xdebug"
+    user: root
+```
+
+If you're using Nginx, add this to your `.lando.yml`:
+
+```yaml
+services:
+  appserver:
+    overrides:
+      environment:
+        XDEBUG_MODE:
+tooling:
+  xdebug-on:
+    service: appserver
+    description: Enable xdebug for nginx.
+    cmd: docker-php-ext-enable xdebug && pkill -o -USR2 php-fpm && echo "Enabling xdebug"
+    user: root
+  xdebug-off:
+    service: appserver
+    description: CUSTOM Disable xdebug for nginx.
+    cmd: rm /usr/local/etc/php/conf.d/docker-php-ext-xdebug.ini && pkill -o -USR2 php-fpm && echo "Disabling xdebug"
+    user: root
+```
+
+Now you can turn Xdebug on or off with `lando xdebug-on` and `lando xdebug-off`. If you want Xdebug off by default, set `xdebug:false` in your appserver config:
+
+```yaml
+name: mywebsite
+recipe: drupal8
+services:
+  appserver:
+    webroot: web
+    xdebug: false
+    config:
+      php: .vscode/php.ini
+```
+
+## Debugging PhpUnit
+
+Debugging PhpUnit tests in VSCode requires a little more setup, but Lando helps to make it easier.
+
+First, you need to have VSCode listen for debugging on 2 separate ports, because PhpUnit runs in one process and the tests themselves in another, and VSCode's Xdebug extension currently struggles with this. You accomplish this by have a launch.json that looks like this:
+
+```json
+{
+  "version": "0.2.0",
+  "configurations": [
+    {
+      "name": "Listen for XDebug",
+      "type": "php",
+      "request": "launch",
+      "port": 9003,
+      "log": true,
+      "pathMappings": {
+        "/app/": "${workspaceFolder}/",
+      }
+    },
+    {
+      "name": "PhpUnit dummy",
+      "type": "php",
+      "request": "launch",
+      "port": 9001,
+    }
+  ],
+  "compounds": [
+    {
+        "name": "PhpUnit",
+        "configurations": ["Listen for XDebug", "PhpUnit dummy"]
+    }
+       ]
+}
+```
+
+Next add some custom tooling to your .lando.yml file, that provides a command to run PhpUnit in a way points the main PhpUnit process to the PhpUnit dummy debugger we just added. (The syntax here assumes a project-specific installation of PhpUnit, not a global one).
+
+```yml
+tooling:
+  phpunitdebug:
+    service: appserver
+    cmd: php -d xdebug.remote_port=9003 vendor/bin/phpunit
+```
+
+**Note: PHP 7.1 and earlier uses xdebug 2** which uses port 9000, so change the port number above accordinly.
+
+Now to run debug a PhpUnit test, do the following:
+
+1. Select the compound "PhpUnit" as your debugger in VSCode's UI, and start it.
+2. Make sure you untick "Everything" in the breakpoints section of the UI, or it will break every time PhpUnit throws an exception, even if it's properly caught by PhpUnit.
+3. Add a breakpoint in your code that is being tested.
+4. On your command line run PhpUnit with something like `lando phpunitdebug --filter=testMyTestMethodName` (this example is of running a single test method, actually you can add any phpunit options you like at the end).
+
+## Known issues
+
+**Xdebug session doesn't start**
+
+If Xdebug session doesn't start, dig into the log file inside the application.
+
+Enter your lando app `lando ssh` and open the debug file (`/tmp/xdebug.log`). Path to the debug file is configured in your custom `php.ini`.
+
+Now open your app in a browser and see what's being logged.
+
+```bash
+lando ssh
+tail -f /tmp/xdebug.log
+# Open your browser and refresh the app
+```
+
+**Xdebug says "timeout trying to connect to XX.XX.XX:9003**
+
+Double-check your host machine allow connection on its port 9003.
+
+This is how you can open a specific port on a Debian/Ubuntu:
+
+`sudo iptables -A INPUT -p tcp -d 0/0 -s 0/0 --dport 9003 -j ACCEPT`
+
+## Read More
+
+*   [Original Gist with settings for XDebug in VSCode](https://gist.github.com/MatthieuScarset/0c3860def9ff1f0b84e32f618c740655)
+*   [PHP programming in VSCode](https://code.visualstudio.com/docs/languages/php)
+
+<GuideFooter />
+<Newsletter />
diff --git a/docs/guides/macos-pantheon-no-proxy.md b/docs/guides/macos-pantheon-no-proxy.md
new file mode 100644
index 0000000..1d5580f
--- /dev/null
+++ b/docs/guides/macos-pantheon-no-proxy.md
@@ -0,0 +1,81 @@
+---
+date: 2019-11-05
+---
+
+# How to set up a Pantheon application without a proxy on macOS 10.12+
+
+<GuideHeader />
+
+This guide explains how to use a pantheon [lando](https://github.com/lando/lando) application without the proxy server on your local machine. Instead of using a proxy server, you will use `dnsmasq` and `pfctl` to port forward your lando application's webserver ports to 80 and 443.
+
+> **Note:** you will have to perform some manual interactions for each lando application you create. See the instructions below.
+
+1. First, install [homebrew](https://brew.sh)
+2. Then, install and setup dnsmasq with homebrew:
+
+    ```
+    brew install dnsmasq
+    echo 'address=/.lndo.site/127.0.0.1' > $(brew --prefix)/etc/dnsmasq.conf
+    echo 'listen-address=127.0.0.1' >> $(brew --prefix)/etc/dnsmasq.conf
+    echo 'port=35353' >> $(brew --prefix)/etc/dnsmasq.conf
+    brew services start dnsmasq
+    ```
+
+3. While dnsmasq is running, configure macOS to use your local host for DNS queries ending in `.lndo.site`
+
+    ```
+    sudo mkdir -v /etc/resolver
+    sudo bash -c 'echo "nameserver 127.0.0.1" > /etc/resolver/dev'
+    sudo bash -c 'echo "port 35353" >> /etc/resolver/dev'
+    ```
+
+4. Disable lando's proxy in your local config file.
+
+    ```
+    touch ~/.lando/config.yml
+    echo "proxy: OFF" >> ~/.lando/config.yml
+    ```
+
+5. [Set up your app with lando](https://docs.devwithlando.io/tutorials/basics.html). Make sure your application is stopped before proceeding.
+6. Start your application using `lando start`.
+7. In terminal, run the following command all at once:
+
+    ```
+    sudo bash -c 'export TAB=$'"'"'\t'"'"'
+    cat > /Library/LaunchDaemons/co.jakebellacera.httpdfwd.plist <<EOF
+    <?xml version="1.0" encoding="UTF-8"?>
+    <!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
+    <plist version="1.0">
+    <dict>
+    ${TAB}<key>Label</key>
+    ${TAB}<string>co.lando.httpdfwd</string>
+    ${TAB}<key>ProgramArguments</key>
+    ${TAB}<array>
+    ${TAB}${TAB}<string>sh</string>
+    ${TAB}${TAB}<string>-c</string>
+    ${TAB}${TAB}<string>echo "rdr pass proto tcp from any to any port {80,32787} -> 127.0.0.1 port 32787" | pfctl -a "com.apple/260.HttpFwdFirewall" -Ef - &amp;&amp; echo "rdr pass proto tcp from any to any port {443,32788} -> 127.0.0.1 port 32788" | pfctl -a "com.apple/261.HttpFwdFirewall" -Ef - &amp;&amp; sysctl -w net.inet.ip.forwarding=1</string>
+    ${TAB}</array>
+    ${TAB}<key>RunAtLoad</key>
+    ${TAB}<true/>
+    ${TAB}<key>UserName</key>
+    ${TAB}<string>root</string>
+    </dict>
+    </plist>
+    EOF'
+    sudo launchctl load -Fw /Library/LaunchDaemons/co.lando.httpdfwd.plist
+    ```
+
+    > **NOTE:** this assumes your pantheon app's edge servers are assigned to the following ports: 32787 (http) and 32788 (https). In testing, these seemed to be the default ports that are assigned to pantheon applications. If you see different ports, or are not using a pantheon application configuration, then you may need to adjust the ports in the code snippet above.
+
+8. In your /etc/hosts file, add an entry for your application's host name at localhost.
+
+    ```
+    127.0.0.1 example.lndo.site
+    ```
+
+    > **NOTE:** replace "example" in the hostname with the name of your application.
+
+9. Finally, you should be able to access your application by the hostname you added to your /etc/hosts file in the step above without any ports. If you are having trouble, try turning off and on your wifi or reboot your machine so that your /etc/resolver settings are applied successfully.
+
+<GuideFooter />
+<Newsletter />
diff --git a/docs/guides/offline-dev.md b/docs/guides/offline-dev.md
new file mode 100644
index 0000000..7ced396
--- /dev/null
+++ b/docs/guides/offline-dev.md
@@ -0,0 +1,75 @@
+---
+description: Learn how to use Lando for offline local development.
+date: 2019-11-05
+---
+
+# Developing offline
+
+<GuideHeader />
+
+Out of the box Lando uses an actual on-the-internet wildcard domain at `*.lndo.site` to route your domain names back to your localhost to provide convenient proxying. This method is minimally invasive and doesn't require Lando to alter your machine's DNS routing. This has the downside of requiring an internet connection to access your sites.
+
+However, you may want the freedom of hacking away on your site while scaling Everest or just to simply route your projects to a different wildcard domain, like `*.local.dev`, `*.seriously.hanshotfirst` or `*.my.test`. Note that we **DO NOT** recommend you use a _true_ top-level domain such as `*.test`. You can read more about why in our [security](./../config/security.md) documentation.
+
+To enable offline custom domain goodness, we'll use DNSMasq to route traffic to our local system and add a single config line to our global Lando config to direct lando to use that domain for our sites.
+
+That said and before we get started we **highly recommend** you consult both the [proxy](./../config/proxy.md) and [security](./../config/security.md) documentation to get a good handle on what is possible (and not possible) here.
+
+## Mac Specific Instructions
+
+1. Ensure you've installed [Homebrew](https://brew.sh/).
+2. Install DNSMasq: `brew install dnsmasq`
+3. Follow the instructions in the output of `brew info dnsmasq`
+4. Add the following line to your `/usr/local/etc/dnsmasq.conf` file:
+```
+address=/local.host/127.0.0.1
+```
+Sub in your favorite domain for 'local.host' here if you want to use something more flashy.
+
+5. Restart DNSMasq: `brew services restart dnsmasq`
+6. For macOS to resolve requests from *.local.host to localhost we need to add a resolver:
+```
+sudo mkdir -p /etc/resolver
+sudo nano /etc/resolver/local.host
+```
+7. Add the following line to the local.host file resolver in /etc/resolver/.
+```
+nameserver 127.0.0.1
+```
+8. Reboot macOS to enable the new resolver.
+9. Flush your DNS, just to be sure that your browsers use the new dns
+directives.
+```
+sudo dscacheutil -flushcache
+sudo killall -HUP mDNSResponder
+```
+10. Open your `~/.lando/config.yml` file and add the following line:
+```yaml
+domain: local.host
+```
+Again, allow your creativity to flourish and use whatever domain makes you smile.
+
+11. Power Lando down with `lando poweroff`
+12. Start up your favorite Lando app to test it out with `lando start` from within your app's root directory. You should see something like:
+
+```bash
+BOOMSHAKALAKA!!!
+
+Your app has started up correctly.
+Here are some vitals:
+
+ NAME      bestappever
+ LOCATION  /Users/McFly/timemachines/bestappever
+ SERVICES  appserver, nginx, database, cache, node
+
+ APPSERVER URLS https://localhost:32791
+                http://localhost:32792
+                http://bestappever.local.host
+                https://bestappever.local.host
+```
+13. Load it up in the browser and confirm everything is happy and working.
+
+Enjoy your signature domain while you hack away in complete wifi-less splendor.
+
+<GuideFooter />
+<Newsletter />
diff --git a/docs/guides/overriding-a-service-version.md b/docs/guides/overriding-a-service-version.md
new file mode 100644
index 0000000..915c129
--- /dev/null
+++ b/docs/guides/overriding-a-service-version.md
@@ -0,0 +1,74 @@
+---
+title: Overriding a Service Version or Image
+metaTitle: Overriding a Service Version | Lando
+description: Modify the underlying Docker images used by your Lando services so that you can custom tailor the container environment for your apps!
+summary: Modify the underling Docker images used by your Lando services so that you can custom tailor the container environment for your apps!
+date: 2020-03-19T19:59:04.806Z
+original:
+repo:
+
+author:
+  name: Dustin LeBlanc
+  pic: https://www.gravatar.com/avatar/e61caccbbfd817bc8b52c0395ba888a6
+  link: https://twitter.com/DustinLeblanc
+
+feed:
+  enable: true
+  author:
+    - name: Dustin LeBlanc
+      email: alliance@lando.dev
+      link: https://twitter.com/DustinLeblanc
+  contributor:
+    - name: Dustin LeBlanc
+      email: alliance@lando.dev
+      link: https://twitter.com/DustinLeblanc
+---
+
+# Overriding a Service Version
+
+<GuideHeader test="" name="Dustin LeBlanc" pic="https://www.gravatar.com/avatar/e61caccbbfd817bc8b52c0395ba888a6" link="https://twitter.com/DustinLeblanc" />
+
+The Docker images Lando uses for services are well optimized for local development, but occasionally you need to
+override those images with some of your own secret sauce. Lando makes this easy to do through the services `overrides`
+key:
+
+```yaml
+name: projectofdoom
+recipe: drupal8
+config:
+  via: nginx
+  webroot: web
+  php: 7.3
+  database: mariadb
+  xdebug: true
+env_file:
+  - .env
+services:
+  database:
+    overrides:
+      image: bitnami/mariadb:10.3.27
+```
+
+In the example above, we're overriding the image to use an explicit release of Bitnami's MariaDB container to bypass a
+breaking change released on Bitnami's 10.3 tag (Lando's default version).
+
+You can also use this to load your own custom images:
+
+```yaml
+name: projectofdoom
+recipe: drupal8
+config:
+  via: nginx
+  webroot: web
+  php: 7.3
+  database: mariadb
+  xdebug: true
+env_file:
+  - .env
+services:
+  appserver:
+    overrides:
+      image: myamazingorg/fancyappserver:latest
+```
+<GuideFooter test="" original="" repo=""/>
+<Newsletter />
diff --git a/docs/guides/phpmyadmin-themes.md b/docs/guides/phpmyadmin-themes.md
new file mode 100644
index 0000000..e778e5e
--- /dev/null
+++ b/docs/guides/phpmyadmin-themes.md
@@ -0,0 +1,101 @@
+---
+title: Using a custom PhpMyAdmin 4.x theme in Lando
+description: Learn how to load a custom PhpMyAdmin 4.x theme into Lando
+summary: Learn how to load a custom PhpMyAdmin 4.x theme into Lando
+date: 2020-03-30T19:23:00.720Z
+original:
+repo: https://github.com/lando/cli/tree/main/examples/pma
+
+author:
+  name: Jace Bennest
+  pic: https://avatars0.githubusercontent.com/u/6412919?s=460&u=b96d856896743523cec75bad1d9aec42a7f8a25e&v=4
+  link: https://twitter.com/thejacer87
+
+feed:
+  enable: true
+  author:
+    - name: Jace Bennest
+      email: alliance@lando.dev
+      link: https://twitter.com/thejacer87
+  contributor:
+    - name: Jace Bennest
+      email: alliance@lando.dev
+      link: https://twitter.com/thejacer87
+---
+
+# Add Themes to phpMyAdmin 4.x
+
+<GuideHeader name="Jace Bennest" pic="https://avatars0.githubusercontent.com/u/6412919?s=460&u=b96d856896743523cec75bad1d9aec42a7f8a25e&v=4" link="https://twitter.com/thejacer87" test="https://github.com/lando/cli/tree/main/examples/pma" />
+<YouTube url="" />
+
+[phpMyAdmin](https://www.phpmyadmin.net/) is a free software tool written in PHP, intended to handle the administration of MySQL over the Web. See the [lando docs](https://docs.devwithlando.io/tutorials/phpmyadmin.html) regarding phpMyAdmin for help enabling the service.
+
+:::warning Only for PhpMyAdmin 4.x
+Note that this guide is only applicable to the 4.x branch of PhpMyAdmin. You'll want to consult the docs for how to do this in 5.x
+:::
+
+This is a basic setup to help you enable extra themes.
+
+## Getting Started
+
+Add the build script to your Lando recipe where you should have the phpMyAdmin service already.
+
+```yaml
+services:
+  pma:
+    type: phpmyadmin:4.7
+    build_as_root:
+      - chmod +x /app/.lando/pma-theme.sh
+      - /app/.lando/pma-theme.sh
+```
+
+## Create script to download and install the third-party theme
+
+Create the custom `pma-theme.sh` file.
+
+```bash
+touch .lando/pma-theme.sh
+vim .lando/pma-theme.sh
+```
+
+The location of this file is arbitrary. We placed it inside `.lando/` folder simply because we find it convenient.
+
+```bash
+#!/bin/sh
+if [ ! -z $LANDO_MOUNT ]; then
+  wget https://files.phpmyadmin.net/themes/pmaterial/1.1/pmaterial-1.1.zip
+  unzip pmaterial-1.1.zip -d /www/themes/
+  rm pmaterial-1.1.zip
+fi
+```
+
+Checkout the available themes [here](https://www.phpmyadmin.net/themes/). Make sure you choose a theme compatible with your version of phpMyAdmin. Modify the script according to the theme you want.
+
+## Set new theme as the default
+
+Review the [phpMyAdmin docs](https://docs.devwithlando.io/tutorials/phpmyadmin.html#using-custom-phpmyadmin-config-file) to see how to hook up your config file.
+
+Add this line to your config:
+
+```php
+<?php
+  ...
+
+  // Set whichever theme you have available here.
+  $cfg['ThemeDefault'] = 'pmaterial';
+
+  ...
+```
+
+## Rebuild your environment
+
+```bash
+lando rebuild -y
+```
+
+Done!
+
+Check the output from lando or run `lando info` to get the url for the phpMyAdmin service.
+
+<GuideFooter test="https://github.com/lando/cli/tree/main/examples/pma" original="" repo="https://github.com/lando/cli/tree/main/examples/pma"/>
+<Newsletter />
diff --git a/docs/guides/setup-lando-on-windows-with-wsl-2.md b/docs/guides/setup-lando-on-windows-with-wsl-2.md
new file mode 100644
index 0000000..2c7df1d
--- /dev/null
+++ b/docs/guides/setup-lando-on-windows-with-wsl-2.md
@@ -0,0 +1,75 @@
+---
+title: Setup Lando on Windows with WSL2
+metaTitle: Setup Lando on Windows with WSL2 | Lando
+description: Configure Lando to run on your Windows WSL2 system for better performance when developing on Windows.
+summary: Configure Lando to run on your Windows WSL2 system for better performance when developing on Windows.
+date: 2021-01-19T14:21:27.061Z
+original: 
+repo: 
+
+author:
+  name: Dustin LeBlanc
+  pic: https://www.gravatar.com/avatar/e61caccbbfd817bc8b52c0395ba888a6
+  link: https://twitter.com/DustinLeblanc
+
+feed:
+  enable: true
+  author:
+    - name: Dustin LeBlanc
+      email: dustin@dustinleblanc.com
+      link: https://twitter.com/DustinLeblanc
+  contributor:
+    - name: Dustin LeBlanc
+      email: alliance@lando.dev
+      link: https://twitter.com/DustinLeblanc
+---
+
+# Setup Lando on Windows with WSL2
+
+<GuideHeader test="" name="Dustin LeBlanc" pic="https://www.gravatar.com/avatar/e61caccbbfd817bc8b52c0395ba888a6" link="https://twitter.com/DustinLeblanc" />
+<YouTube url="" />
+
+Developing on Windows used to cause web developers agony and pain, but with the introduction of WSL, this is no longer quite so. WSL2 provides a near-native Linux experience for developing web applications on Windows computers.
+
+Longtime Mac or Windows Lando users will be familiar with the performance difficulties associated with file system access when using Docker in a non-linux host environment. Traditionally, running Docker on Mac or Windows requires a virtual machine environment. Sharing files across the boundary between your native OS and the Linux OS running within this virtual environment creates significant performance issues.
+
+WSL2 manages to bypass the majority of this performance penalty by never mounting your source code on a non-Linux filesystem. Here is the best (highest performance) way to setup Docker (and Lando) on a Windows 10 machine in 2021:
+
+## Prerequisites
+
+**1. Uninstall Pre-existing Docker + WSL2 Backend**
+You will want to make sure that, if you have an existing Docker or WSL setup, you are **not** using the Docker + WSL2 backend. If you have this setup, [you're going to have a bad time](https://www.youtube.com/watch?v=ynxPshq8ERo). It is very sad, very frustrating, so if you are here, do yourself a favor and uninstall the Docker Desktop WSL2 backend.
+
+**2. Make Sure Your Machine Supports Virtualization**
+You also need to ensure your machine supports virtualization (Vt-d, etc.). If you're not sure, you can [check this in Task Manager](https://www.shaileshjha.com/how-to-find-out-if-intel-vt-x-or-amd-v-virtualization-technology-is-supported-in-windows-10-windows-8-windows-vista-or-windows-7-machine). You don't need to have Windows 10 Pro like the traditional Lando on Windows setup, as WSL doesn't require it.
+
+## Get WSL2 rolling
+
+The first thing we need to do is enable WSL2. To do so...
+
+1. Open the start menu and search for "Turn Windows features on or off".
+2. In the resulting window, check 'Windows Subsystem for Linux' and 'Virtual Machine Platform' and then click 'ok'. This starts the system installed for WSL and will ask us to restart after it downloads the stuff it needs. This really only gives you the WSL1 setup. To get WSL2...
+3. Download a kernel update to get WSL2 going. see the [Microsoft docs on installing the kernel update](https://docs.microsoft.com/en-us/windows/wsl/install-win10#step-4---download-the-linux-kernel-update-package).
+4. After you install the kernel update, launch a powershell and run `wsl --set-default-version 2` to default to WSL 2.
+5. Head to the Microsoft store and install a Linux distro. I am going to choose [Ubuntu 18.04 LTS](https://www.microsoft.com/en-us/p/ubuntu-1804-lts/9n9tngvndl3q), since it is the most common distro for Lando users and our handy [Hyperdrive](https://github.com/lando/hyperdrive) supports it.
+
+## Jump into Hyperspace
+
+After installing the latest LTS Ubuntu, using Hyperdrive makes the rest extremely easy. We simply launch a bash shell in the WSL instance, follow the user setup process, and then follow the Hyperdrive instructions in your terminal.
+
+## Rules to keep your setup easy and happy
+
+1. **Never** run a Lando app from within the default directory that WSL drops you into (`/mnt/c/Users/whateveruser`). This is the Windows filesystem mounted into your WSL instance, and it suffers from the filesystem performance issues that this setup avoids, therefore making going through the trouble of setting this up pointless.
+2. You have to start Docker every time you start up the WSL2 instance. Running `lando start` should automatically start Docker, but if you need to initialize Docker for non-Lando purposes, try running `sudo service docker start`. This is because the WSL2 distros have no init system, so Docker doesn't auto start.
+3. VS Code is the absolute easiest editor to use with this setup. Microsoft has some extensions that make working with your WSL filesystem very easy. Vim/Neovim also work great, but using an editor like PHPStorm currently requires some extra setup if you want decent performance.
+
+## Day to day development
+
+You'll want to do all of your shell activity from within the WSL system, and you treat it like a separate Linux development box. You can run `code .` from the directory of any project you're working on and it will lauch VS Code, properly setup to develop within WSL. If you launch the terminal within WSL, it is going to work just like you expect and open the session within the WSL system.
+
+## Some caveats
+
+Performance is generally very good with this approach, however, stability can at times leave something to be be desired. Occassional freezes under heavy load are fairly commonplace, and seem to be resolved by rebooting the system. All things considered, the reduction in CPU load, battery drain, and the accompanied increase in the speed of every single action you take (accessing site pages, running any CLI commands) more than outweighs the disruption of these occasional issues for most users. Hopefully stability will continue to increase with time.
+
+<GuideFooter test="" original="" repo=""/>
+<Newsletter />
diff --git a/docs/guides/updating-local-pantheon-environments.md b/docs/guides/updating-local-pantheon-environments.md
new file mode 100644
index 0000000..4d3184e
--- /dev/null
+++ b/docs/guides/updating-local-pantheon-environments.md
@@ -0,0 +1,62 @@
+---
+title: Updating your Pantheon site from the latest DB backup
+metaTitle: Updating your Pantheon site from the latest DB backup | Lando
+description: Add this tool to catch your local dev environment up to date.
+summary: Add this tool to catch your local dev environment up to date.
+date: 2020-03-03T21:14:32.815Z
+original: 
+repo: 
+
+author:
+  name: Jason Purdy
+  pic: https://www.gravatar.com/avatar/cb8c34b202e121d059c955433511f0b9
+  link: https://twitter.com/jason_purdy
+
+feed:
+  enable: true
+  author:
+    - name: Jason Purdy
+      email: alliance@lando.dev
+      link: https://twitter.com/jason_purdy
+  contributor:
+    - name: Jason Purdy
+      email: alliance@lando.dev
+      link: https://twitter.com/jason_purdy
+---
+
+# Updating your Pantheon site from the latest DB backup
+
+<GuideHeader test="" name="Jason Purdy" pic="https://www.gravatar.com/avatar/cb8c34b202e121d059c955433511f0b9" link="https://twitter.com/jason_purdy" />
+<YouTube url="" />
+
+I can't claim credit for this, but I wanted to share a really powerful and useful addition we add to our .lando.yml files in the tooling section. It should be said that this particular use case works for Drupal and Pantheon users.
+
+```yaml
+tooling:
+  latest:
+    service: appserver
+    description: Updates the database from the latest backup
+    cmd:
+      - mkdir -p /app/artifacts
+      - rm -f /app/artifacts/database.sql.gz
+      - terminus backup:get site.env --element=db --to=/app/artifacts/database.sql.gz
+      - database: cd /app && /helpers/sql-import.sh artifacts/database.sql.gz
+      - drush cc all && drush en devel stage_file_proxy -y && drush sql-sanitize --sanitize-password="1234" --yes
+```
+
+For Drupal 8, we setup [config split](https://www.drupal.org/project/config_split) to handle separate development configurations, so our last line looks something like this:
+
+```yaml
+- cd /app/web && drush cr && drush sql-sanitize --sanitize-password="1234" --yes && drush cr && drush config-split:import config_dev -y
+```
+
+Once you add this, then you can type `lando latest` whenever you want to refresh your local environment to bring it up to date with the latest database backup.
+
+The first time you run this, you may run into an issue where your environment cannot download the backup because you need to authenticate it with Pantheon. Basically, [create a machine token](https://dashboard.pantheon.io/machine-token/create) and then type `lando terminus auth:login --machine-token=[TOKEN]`. You may have multiple Drupal/Pantheon environments and you will need to authenticate each one, but you only need to do that once, even if you restart/rebuild the app.
+
+ You could still use this for non-Pantheon cases, but you'll have to change the terminus command to something that grabs your latest database backup and copies it into the `artifacts` folder.
+
+ You'll also want to add the `artifacts` folder to your `.gitignore` file so you don't commit any database backups.
+
+<GuideFooter test="" original="" repo=""/>
+<Newsletter />
diff --git a/docs/guides/updating-to-rc2.md b/docs/guides/updating-to-rc2.md
new file mode 100644
index 0000000..a4b6dcd
--- /dev/null
+++ b/docs/guides/updating-to-rc2.md
@@ -0,0 +1,638 @@
+---
+description: Learn how to update Lando from beta to rc and beyond.
+date: 2019-11-05
+---
+
+# Updating to 3.0.0-rc.2+
+
+<GuideHeader />
+
+Before you begin here we *highly recommend* you check out the [RC2 Release Blog Post](https://thinktandem.io/blog/2019/02/01/lando-is-ready-for-the-masses-with-rc2-release/) to get a higher level understanding on whats changed and why its changed in `3.0.0-rc.2`. After that you should be ready to get into the nitty gritty of what has changed.
+
+**This guide is for people upgrading from `3.0.0-rc.1` or lower**.
+
+Here are the various things that have changed to your [Landofiles](./../config/lando.md) syntax. We've tried to order them from the most common or most breaking config to the least. Note that this guide might not be an exhaustive list of all breaking changes and you are still *highly encouraged* to check out the other docs if you are running into an error running your older Landofiles on `3.0.0-rc.2` or higher.
+
+[[toc]]
+
+## New Images
+
+We've rebased a lot our services on [Bitnamis](https://github.com/bitnami) which means it's **highly likely** you will need to `lando destroy` your app and then `lando start` it again. It's worth trying to see if things "just work" but if you run into an error using RC2 holla at this
+
+```bash
+lando destroy
+lando start
+```
+
+Note that a `lando rebuild` is not sufficient and a `lando destroy` is needed. Also note that this will **destroy your applications perisitent storage eg your database data, solr index, etc**. If you have data you want to save, its a good idea to do something like this.
+
+```bash
+lando db-export dump.sql
+lando destroy -y
+lando start
+lando db-import dump.sql.gz
+```
+
+## Removing `~/.lando`
+
+While most updates do not require the removal of `~/.lando` there are some circumstances where this seems necessary. If you are running into any of the below known issues, or things don't seem _quite right_ we recommend a quick `rm -rf ~/.lando` and then trying again.
+
+* [Database doesn't start or reports as unhealthy](https://github.com/lando/lando/issues/1486)
+* [`lndo.site` sites are not accessible](https://github.com/lando/lando/issues/1490)
+
+If you are running into an issue that is resolved by removing `~/.lando` please [submit a ticket](https://github.com/lando/lando/issues/new/choose) so we can add it to the above list.
+
+## Overrides
+
+We've slightly changed the syntax of [service overrides](./../config/services.md#overrides) to make things more readable. All you need to do is move things up one level
+
+**old**
+
+```yaml
+services:
+  html:
+    type: apache:custom
+    overrides:
+      services:
+        environment:
+          STUFF: THINGS
+          THINGS: GUYS
+        image: pirog/myapache:2
+        volumes:
+          - ./mythings:/tmp/mythings
+```
+
+**new**
+
+```yaml
+services:
+  html:
+    type: apache:custom
+    overrides:
+      environment:
+        STUFF: THINGS
+        THINGS: GUYS
+      image: pirog/myapache:2
+      volumes:
+        - ./mythings:/tmp/mythings
+```
+
+A consequence of this is that you can no longer overrides top level `volumes` and `networks`. If you need to edit those things we recommend you look at using our [custom compose service](./../tutorials/compose.md) instead. Note the below distinction between *top level* `volumes` and `networks` and service level ones These are docker compose files not Landofiles.
+
+**top level - not supported, use a compose service**
+
+```yaml
+version: '3.6'
+services:
+  web:
+    image: nginx
+  web2:
+    image: nginx
+    ports:
+      - '80'
+volumes:
+  my-volume:
+networks:
+  my-network
+```
+
+**service level - still supported, can use a service override**
+
+```yaml
+version: '3.6'
+services:
+  web:
+    image: nginx
+  web2:
+    volumes:
+      my-volume:/tmp
+    networks:
+      - my-network
+    image: nginx
+    ports:
+      - '80'
+```
+
+Check out [this example](https://github.com/lando/cli/tree/main/examples/services) which is tested on every build for some examples of new override syntax.
+
+## Internal Service Name Changes
+
+Lando still manages some services internally such as an [nginx](./../tutorials/nginx.md) service when you use `ssl` with [varnish](./../tutorials/varnish.md) or set `via: nginx` with [php](./../tutorials/php.md) however we've changed the default names of these services so they are namespaced better.
+
+The names of these services will be the same as before except they will now be prefixed by the service that generated them. For example if you have a `php` service using `nginx` and it is named `appserver` then Lando will spin up an internal nginx service called `appserver_nginx.`
+
+Pain for this change will likely manifest if you have custom [proxy settings](./../config/proxy.md).
+
+**old**
+
+```yaml
+proxy:
+  nginx:
+    - myapp.lndo.site
+services:
+  myservice:
+    type: php
+    via: nginx
+```
+
+**new**
+
+```yaml
+proxy:
+  myservice_nginx:
+    - myapp.lndo.site
+services:
+  myservice:
+    type: php
+    via: nginx
+```
+
+This can also be an issue if you are using the service name to set a base url or config envvars.
+
+**old**
+
+```yaml
+services:
+  appserver:
+    overrides:
+      services:
+	environment:
+	  BASEURL: http://nginx
+```
+
+
+In these situations we prefer you use an option available via our [networking](./../config/networking.md).
+
+**new**
+
+```yaml
+name: myapp
+services:
+  appserver:
+    overrides:
+      environment:
+        BASEURL: https://appserver_nginx.myapp.internal
+```
+
+```yaml
+name: myapp
+proxy:
+  appserver_nginx:
+    - myapp.lndo.site
+services:
+  appserver:
+    overrides:
+      environment:
+        BASEURL: https://myapp.lndo.site
+```
+
+## Hyphens in project names
+
+If you have a `.lando.yml` that starts with
+
+```yaml
+name: site-with-hyphens
+```
+
+Then Lando generates URLs like this:
+
+**old**
+
+```
+https://sitewithhyphens.lndo.site
+```
+
+**new**
+
+```
+https://site-with-hyphens.lndo.site
+```
+
+This does not really break anything, but you may want to update the following:
+
+- If you have any browser tabs open on your Lando sites, then update the URLs after updating Lando.
+- If any of your projects have affected `.lando.yml` files, then update the URLs in related README files or other documentation.
+- If you are bothered by cruft, then see [Removing lingering Lando configuration](https://docs.devwithlando.io/installation/uninstalling.html#removing-lingering-lando-configuration). You can remove files and directories based on the old hyphenless names in the Lando configuration directory and its subdirectories.
+
+## Tooling
+
+We've altered our [tooling](./../config/tooling.md) so that it is more in line with our [events](./../config/events.md) syntax. That means you will likely want to alter two of the following scenarios.
+
+### Multi-line commands
+
+Tooling commands that are expressed as arrays now represent multiple **commands** instead of **arguments** to a single command. So you will want to change scenarios like this
+
+**old**
+
+```yaml
+tooling:
+  drush:
+    service: appserver
+    cmd:
+      - drush
+      - --root
+      - /app/PATH/TO/WEBROOT
+```
+
+**new**
+
+```yaml
+tooling:
+  drush:
+    service: appserver
+    cmd: drush --root=/app/PATH/TO/WEBROOT
+```
+
+Check out [this example](https://github.com/lando/cli/tree/main/examples/tooling) which is tested on every build for some examples of new tooling syntax.
+
+### Eventy commands
+
+If you were using [events](./../config/events.md) as a [tricky way](https://github.com/lando/lando/blob/v3.0.0-rc.1/docs/tutorials/setup-additional-tooling.md#multi-service-tooling-with-events) to run multiple commands on multiple services you can now do that [directly with tooling](./../config/tooling.md#multi-service-multi-command-tooling).
+
+**old**
+
+```yaml
+events:
+  post-update:
+    - appserver: cd $LANDO_MOUNT && composer install
+    - node: cd $LANDO_MOUNT && gulp
+    - appserver: cd $LANDO_WEBROOT && drush updb -y
+tooling:
+  update:
+    service: appserver
+    description: Builds local dependencies, compiles SASS, runs DB updates
+    cmd: 'true'
+```
+
+**new**
+
+```yaml
+tooling:
+  update:
+    description: Builds local dependencies, compiles SASS, runs DB updates
+    cmd:
+      - appserver: cd $LANDO_MOUNT && composer install
+      - node: cd $LANDO_MOUNT && gulp
+      - appserver: cd $LANDO_WEBROOT && drush updb -y
+```
+
+Check out [this example](https://github.com/lando/cli/tree/main/examples/tooling) which is tested on every build for some examples of new tooling syntax.
+
+## Build Steps
+
+While we've maintained decent backwards compatibility with previous build step names we recommend you update to the [new syntax](./../config/services.md#build-steps) and be mindful that build steps can now run **before** and **after** your application starts.
+
+**old**
+
+```yaml
+services:
+  appserver:
+    type: php
+    build_as_root:
+      - command1
+    install_dependencies_as_root:
+      - command2
+    build:
+      - command3
+    install_dependencies_as_me:
+      - command4
+    run_as_root:
+      - command5
+    extras:
+      - command6
+    run:
+      - command7
+    run_as_me
+      - command8
+```
+
+**new**
+
+```yaml
+services:
+  appserver:
+    type: php
+    build_as_root:
+      - command1
+      - command2
+    build:
+      - command3
+      - command4
+    run_as_root:
+      - command5
+      - command6
+    run:
+      - command7
+      - command8
+```
+
+If you have been using either of the following *unsupported* syntaxes then make sure you also read about [using scripty things](./../config/services.md#using-scripty-things) in your build steps.
+
+```yaml
+run:
+  - |
+    if [ ! -z $LANDO_MOUNT ]; then
+      do something
+      some other command
+    fi
+```
+
+```yaml
+run:
+  - if [ ! -z $LANDO_MOUNT ]; then do-stuff; fi
+```
+
+Check out [this example](https://github.com/lando/cli/tree/main/examples/services) which is tested on every build for some examples of new build step syntax.
+
+## Global Environment Variables
+
+Lando no longer sets its [default environment variables](./../config/env.md) on your host machine. They are now **service only**. While this usage has actually been deprecated for quite some time you may still be doing stuff like this.
+
+**old**
+
+```yaml
+events:
+  post-start:
+    - appserver: cd $LANDO_MOUNT && some-command
+services:
+  appserver:
+    build:
+      - cd $LANDO_MOUNT && some-other-command
+    overrides:
+      services:
+        volumes:
+        - $LANDO_APP_ROOT_BIND/.lando/build-sh-setup.sh:/helpers/build-sh-setup.sh
+        - $LANDO_ENGINE_CONF/.lando/build.sh:/helpers/build.sh
+```
+
+We have standardized these locations for quite some time and they **will not be changing** so you can now just do.
+
+**new**
+
+```yaml
+events:
+  post-start:
+    - appserver: some-command
+services:
+  appserver:
+    build:
+      - some-other-command
+    overrides:
+      volumes:
+        # You can use paths relative to your apps root directory
+        - ./.lando/build-sh-setup.sh:/helpers/build-sh-setup.sh
+```
+
+For `events` and `build-steps` these commands will be run from the `$LANDO_MOUNT` by default.
+
+Tooling commands will be run from the container analog of your `cwd`.
+
+If you find yourself **needing** to hard enter `$LANDO_MOUNT` you can safely just use `/app` as `$LANDO_MOUNT` will not change unless you've explicitly overridden it.
+
+```yaml
+events:
+  post-start:
+    - appserver: cd /app && command-that-def-needs-to-be-run-from-here
+```
+
+Note that in the case of something like `$LANDO_ENGINE_CONF` your application's `root` directory, the entire `~/.lando` config directory, and your user home folder are [already available inside every container](./../config/files.md) by default so you should invoke them directly instead of re-mounting them.
+
+### Accessing Environment variables in events, build-steps, tooling etc
+
+You can, however, still use the environment variables available in each service in your Landofiles by wrapping their invocation with `sh` or `bash`. This will explicitly let Lando know you want to use environment variables in the service and not the host. Note that while you **can** do this it's almost always better to just explicitly refer to things.
+
+**works but not recommended**
+
+```yaml
+events:
+  post-start:
+    - /bin/sh -c 'cd "/app/$LANDO_APP_PROJECT" && do-something'
+```
+
+**works AND recommended**
+
+```yaml
+events:
+  post-start:
+    - cd /app/landoservices && do-something
+```
+
+## Service Versions
+
+Most service versions have stayed the same but a few have changed. If you try to run a now-unsupported service version Lando will throw a nice red error. If this happens to you check out the supported version documented for each service and either choose the closest one to what you have **OR** remove the version completely and use the default.
+
+*   ### [apache](./../config/apache.md)
+*   ### [custom](./../config/compose.md)
+*   ### [dotnet](./../config/dotnet.md)
+*   ### [elasticsearch](./../config/elasticsearch.md)
+*   ### [go](./../config/go.md)
+*   ### [mailhog](./../config/mailhog.md)
+*   ### [mariadb](./../config/mariadb.md)
+*   ### [memcached](./../config/memcached.md)
+*   ### [mongo](./../config/mongo.md)
+*   ### [mssql](./../config/mssql.md)
+*   ### [mysql](./../config/mysql.md)
+*   ### [nginx](./../config/nginx.md)
+*   ### [node](./../config/node.md)
+*   ### [php](./../config/php.md)
+*   ### [phpmyadmin](./../config/phpmyadmin.md)
+*   ### [postgres](./../config/postgres.md)
+*   ### [python](./../config/python.md)
+*   ### [redis](./../config/redis.md)
+*   ### [ruby](./../config/ruby.md)
+*   ### [solr](./../tutorials/solr.md)
+*   ### [tomcat](./../config/tomcat.md)
+*   ### [varnish](./../config/varnish.md)
+
+## Environment Files
+
+You now have to explicitly set the top level [`env_file`](./../config/env.md#environment-files) if you want to load a `env` file.
+
+**old**
+
+*Had a `.env` file in Lando root directory*
+
+**new**
+
+```yaml
+env_file:
+  - .env
+```
+
+By happenstance you could previously use the following *unsupported* syntax in your `env` files.
+
+```bash
+WP_ENV=development
+WP_HOME=http://wpb4.test
+WP_SITEURL=${WP_HOME}/wp
+```
+
+Because we now directly use Docker Compose's `env_file` directive under the hood this syntax no longer works. So you will have to do something like:
+
+```bash
+WP_ENV=development
+WP_HOME=http://wpb4.test
+WP_SITEURL=http://wpb4.test/wp
+```
+
+Check out [this example](https://github.com/lando/cli/tree/main/examples/base) which is tested on every build for some examples of the new environment file syntax.
+
+## Drush Handling
+
+We've vastly simplified our [Drush handling](./../tutorials/drupal8.md#using-drush). You can now only set `drush` to a particular version for global installation. If you've installed `drush` via `composer` then Lando will use that version instead of the one in your Landofile.
+
+**old**
+
+```yaml
+recipe: drupal8
+config:
+  drush: none
+```
+
+```yaml
+recipe: drupal8
+config:
+  drush: composer
+```
+
+```yaml
+recipe: drupal8
+config:
+  drush: /path/to/my/drush
+```
+
+**new**
+
+```yaml
+recipe: drupal8
+```
+
+```yaml
+recipe: drupal8
+config:
+  drush: 8.1.15
+```
+
+## Rebuild vs. Restart
+
+If you change your Landofiles you now need to explicitly [`lando rebuild`](./../cli/rebuild.md) instead of running [`lando restart`](./../cli/rebuild.md). This helps to provide stability between restarts until you explicitly ask for things to change and vastly speeds up stops and starts.
+
+**old**
+
+*changed `.lando.yml`*
+
+```bash
+lando restart
+```
+
+**new**
+
+*changed `.lando.yml`*
+
+```bash
+lando rebuild -y
+```
+
+## Lando Init
+
+We've completely reworked [`lando init`](./../cli/init.md) to be more modular and intuitive. This means if you've got scripts relying on `lando init` you will likely need to make some changes. While there are many changes the biggest are the removal of the "init method" in favor of the `--source` option.
+
+
+**old**
+
+```bash
+lando init pantheon
+```
+
+**new**
+
+```bash
+lando init --source pantheon
+```
+
+**sources** are places where Lando can get your code and **recipes** are the kinds of applications that exists at **source**.
+
+## Global Options
+
+Lando no longer uses [`--`](https://github.com/lando/lando/blob/v3.0.0-rc.1/docs/cli/usage.md#global-options) to differentiate between its options and tooling options.
+
+**old**
+
+```bash
+# Verbose modes
+lando start -- -v
+lando start -- -vv
+lando start -- -vvv
+lando start -- -vvvv
+
+# Lando help
+lando start -- --help
+```
+
+**new**
+
+```bash
+# Verbose modes
+lando start -v
+lando start -vv
+lando start -vvv
+lando start -vvvv
+
+# Lando help
+lando start --help
+```
+
+A nice consequence of this is you can now use `--` in other tooling commands and have more predictable tooling results
+
+```bash
+# Use -- in a command
+lando terminus remote:drush "$SITE.$ENV" -- cr --all -y
+
+# Worry less about escaping crap
+lando php -r "phpinfo();"
+```
+
+## Global Envvars
+
+There is no longer a `containerGlobalEnv` option in the Lando [global config](./../config/config.md). But you can now use `appEnv` to the same effect. **Note that this is for the Lando `config.yml` and NOT for a Landofile**.
+
+**old**
+
+```yaml
+containerGlobalEnv:
+  PARTY: USA
+```
+
+**new**
+
+```yaml
+appEnv:
+  PARTY: USA
+```
+
+## App Registry
+
+There is no longer a register of apps stored at `~/.lando/cache/registry`. As a consequence you can no longer do things like `lando start MYAPP`
+
+```bash
+lando start MYAPP
+```
+
+**new**
+
+```bash
+cd /path/to/MYAPP
+lando start
+```
+
+## Plugins
+
+If you have written your own custom plugins
+
+1. Sorry!! :/
+2. Once you see the new format you'll feel better :)
+
+We've finally locked down a [Plugin System](https://docs.lando.dev/contrib/contrib-plugins.html) that uses the [Lando](./../api/lando.md) and [App](./../api/app.md) APIs and while we still don't have a great way to manage the installation and management of these plugins it is going to be the defining feature of `3.1.0`.
+
+<GuideFooter />
+<Newsletter />
diff --git a/docs/guides/using-compass-on-a-lando-node-service.md b/docs/guides/using-compass-on-a-lando-node-service.md
new file mode 100644
index 0000000..e7085ea
--- /dev/null
+++ b/docs/guides/using-compass-on-a-lando-node-service.md
@@ -0,0 +1,84 @@
+---
+title: Using Compass on a Lando Node Service
+metaTitle: Using Compass on a Lando Node Service | Lando
+description: Learn how to use legacy compass sass builds for your Lando frontend node build
+summary: Learn how to use legacy compass sass builds for your Lando frontend node build
+date: 2020-05-13T01:27:44.387Z
+original:
+repo:
+
+author:
+  name: Team Lando
+  pic: https://gravatar.com/avatar/c335f31e62b453f747f39a84240b3bbd
+  link: https://twitter.com/devwithlando
+
+feed:
+  enable: true
+  author:
+    - name: Team Lando
+      email: alliance@lando.dev
+      link: https://twitter.com/devwithlando
+  contributor:
+    - name: Team Lando
+      email: alliance@lando.dev
+      link: https://twitter.com/devwithlando
+---
+
+# Using Compass on a Lando Node Service
+
+<GuideHeader test="https://circleci.com/gh/lando/lando/tree/master" name="Team Lando" pic="https://gravatar.com/avatar/c335f31e62b453f747f39a84240b3bbd" link="https://twitter.com/devwithlando" />
+<YouTube url="" />
+
+Some older `node` based frontend build steps rely on `ruby` and `compass`. If you have such a flow we _highly recommend_ you escape dependency hell and migrate your `sass` build steps to use `node-sass` which is _way_ faster.
+
+However, if you cannot do this you may run into some issues running `compass` inside of your `node` container since this pattern is fundamentally at odds with Lando's one-thing-per-container model.
+
+You can, however, get around it by installing `ruby` and `compose` directly in the `node` service that requires them.
+
+Below is an example that installs `ruby` and `compass` using [build-steps](./../config/services.md#build-steps).
+
+```yaml
+services:
+  myservice:
+    type: node:12
+    build_as_root:
+      - apt-get update -y
+      - apt-get install ruby-full -y
+      - gem install compass
+tooling:
+  ruby:
+    service: myservice
+  compass:
+    service: myservice
+```
+
+You can verify with:
+
+```bash
+lando ruby -v
+lando compass -v
+```
+
+You should now be able to run any build steps that require `ruby` and `compass` as in this example:
+
+```yaml
+services:
+  myservice:
+    type: node:12
+    globals:
+      grunt-cli: latest
+    build_as_root:
+      - apt-get update -y
+      - apt-get install ruby-full -y
+      - gem install compass
+    build:
+      - grunt build:sass
+tooling:
+  ruby:
+    service: myservice
+  compass:
+    service: myservice
+```
+
+<GuideFooter test="https://circleci.com/gh/lando/lando/tree/master" original="" repo="https://github.com/lando/cli/tree/main/examples/node12"/>
+<Newsletter />
diff --git a/package.json b/package.json
index 4601758..9e4dd7d 100644
--- a/package.json
+++ b/package.json
@@ -50,6 +50,7 @@
     "@babel/eslint-parser": "^7.16.0",
     "@lando/leia": "^0.6.4",
     "@vuepress/plugin-docsearch": "^2.0.0-beta.27",
+    "@vuepress/plugin-register-components": "^2.0.0-beta.27",
     "chai": "^4.3.4",
     "command-line-test": "^1.0.10",
     "eslint": "^7.32.0",
diff --git a/yarn.lock b/yarn.lock
index 60c06e3..8a69599 100644
--- a/yarn.lock
+++ b/yarn.lock
@@ -991,6 +991,15 @@
     "@vuepress/core" "2.0.0-beta.27"
     prismjs "^1.25.0"
 
+"@vuepress/plugin-register-components@^2.0.0-beta.27":
+  version "2.0.0-beta.27"
+  resolved "https://registry.yarnpkg.com/@vuepress/plugin-register-components/-/plugin-register-components-2.0.0-beta.27.tgz#b57f73dfd20accc64fc4b45994dd263f1b151cc7"
+  integrity sha512-CZiEdOE5LoGb2rYcfITyPNbpK9AKKsve5amxKw28sgDw00Ssy3cgZc7G0JyqPXlylBh7KJp04+ZWQccr9lpUWw==
+  dependencies:
+    "@vuepress/core" "2.0.0-beta.27"
+    "@vuepress/utils" "2.0.0-beta.27"
+    chokidar "^3.5.2"
+
 "@vuepress/plugin-theme-data@2.0.0-beta.27":
   version "2.0.0-beta.27"
   resolved "https://registry.yarnpkg.com/@vuepress/plugin-theme-data/-/plugin-theme-data-2.0.0-beta.27.tgz#34064747fd77c27669c2c7713c956b56742fffed"

From d7a5391f4050e4cab00fde601210a9775b3e37ec Mon Sep 17 00:00:00 2001
From: John Ouellet <john@thinktandem.io>
Date: Thu, 4 Nov 2021 15:05:56 -0400
Subject: [PATCH 13/16] #130 More guide conversions

---
 docs/.vuepress/components/Newsletter.vue      |   2 +-
 docs/.vuepress/components/NewsletterLearn.vue |   2 +-
 docs/.vuepress/components/RelatedGuides.vue   |   6 +-
 docs/.vuepress/components/TeamList.vue        |   2 +-
 docs/.vuepress/theme/components/Subscribe.vue |   3 +
 .../.vuepress/theme/components/TeamMember.vue | 149 ++++++++++++++++++
 6 files changed, 159 insertions(+), 5 deletions(-)
 create mode 100644 docs/.vuepress/theme/components/TeamMember.vue

diff --git a/docs/.vuepress/components/Newsletter.vue b/docs/.vuepress/components/Newsletter.vue
index 0c1f70a..f1b16dd 100644
--- a/docs/.vuepress/components/Newsletter.vue
+++ b/docs/.vuepress/components/Newsletter.vue
@@ -14,7 +14,7 @@
 </template>
 
 <script>
-import Subscribe from '@theme/components/Subscribe.vue';
+import Subscribe from '../theme/components/Subscribe.vue';
 
 export default {
   name: 'Newsletter',
diff --git a/docs/.vuepress/components/NewsletterLearn.vue b/docs/.vuepress/components/NewsletterLearn.vue
index 80c485a..edcc77f 100644
--- a/docs/.vuepress/components/NewsletterLearn.vue
+++ b/docs/.vuepress/components/NewsletterLearn.vue
@@ -14,7 +14,7 @@
 </template>
 
 <script>
-import Subscribe from '@theme/components/Subscribe.vue';
+import Subscribe from '../theme/components/Subscribe.vue';
 
 export default {
   name: 'NewsletterLearn',
diff --git a/docs/.vuepress/components/RelatedGuides.vue b/docs/.vuepress/components/RelatedGuides.vue
index 3eb8ab5..8fc4c1b 100644
--- a/docs/.vuepress/components/RelatedGuides.vue
+++ b/docs/.vuepress/components/RelatedGuides.vue
@@ -10,7 +10,8 @@
 </template>
 
 <script>
-import {resolveSidebarItems} from '@parent-theme/util';
+import { resolveSidebarItems } from '@vuepress/theme-default/lib/client/composables/useSidebarItems.js';
+import { useThemeData } from '@vuepress/plugin-theme-data/lib/client';
 
 export default {
   name: 'RelatedGuides',
@@ -26,7 +27,8 @@ export default {
     };
   },
   mounted() {
-    const guides = resolveSidebarItems(this.$page, '/guides/', this.$site, '/');
+    const themeData = useThemeData();
+    const guides = resolveSidebarItems(this.$frontmatter, themeData);
     const section = guides.find(item => item.title.toLowerCase() === this.tag.toLowerCase());
     this.content = section.children;
   },
diff --git a/docs/.vuepress/components/TeamList.vue b/docs/.vuepress/components/TeamList.vue
index 968e405..aa4a07b 100644
--- a/docs/.vuepress/components/TeamList.vue
+++ b/docs/.vuepress/components/TeamList.vue
@@ -5,7 +5,7 @@
 </template>
 
 <script>
-import TeamMember from '@theme/components/TeamMember.vue';
+import TeamMember from '../theme/components/TeamMember.vue';
 
 export default {
   name: 'TeamList',
diff --git a/docs/.vuepress/theme/components/Subscribe.vue b/docs/.vuepress/theme/components/Subscribe.vue
index 20d0ec1..c9165c0 100644
--- a/docs/.vuepress/theme/components/Subscribe.vue
+++ b/docs/.vuepress/theme/components/Subscribe.vue
@@ -83,6 +83,9 @@ export default {
 </script>
 
 <style lang="scss">
+@import '../styles/index.scss';
+@import '../styles/palette.scss';
+@import '@vuepress/plugin-palette/palette';
 .subscribe {
   margin: auto;
   width: 90%;
diff --git a/docs/.vuepress/theme/components/TeamMember.vue b/docs/.vuepress/theme/components/TeamMember.vue
new file mode 100644
index 0000000..a8bc08f
--- /dev/null
+++ b/docs/.vuepress/theme/components/TeamMember.vue
@@ -0,0 +1,149 @@
+<template>
+  <div class="team-member">
+    <div class="team-member-pic">
+      <img :src="member.pic" :alt="member.name" />
+    </div>
+    <div class="team-member-bio">
+      <h2>{{ member.name }}</h2>
+      <div class="team-member-title">{{ member.title }}</div>
+      <p v-html="member.bio"></p>
+      <p class="team-member-helps" v-if="member.role">HELPS WITH: {{ helpText }}</p>
+    </div>
+    <div class="team-member-details">
+      <ul>
+        <li v-if="member.location">
+          <div class="social-icon">
+            <span class="detail-label">{{ member.location }}</span>
+            <svg xmlns="http://www.w3.org/2000/svg" aria-hidden="true" focusable="false" data-prefix="fas" data-icon="map-marker-alt" class="svg-inline--fa fa-map-marker-alt fa-w-12" role="img" viewBox="0 0 384 512"><path fill="currentColor" d="M172.268 501.67C26.97 291.031 0 269.413 0 192 0 85.961 85.961 0 192 0s192 85.961 192 192c0 77.413-26.97 99.031-172.268 309.67-9.535 13.774-29.93 13.773-39.464 0zM192 272c44.183 0 80-35.817 80-80s-35.817-80-80-80-80 35.817-80 80 35.817 80 80 80z"/></svg>
+          </div>
+        </li>
+        <li v-if="member.github">
+          <a class="social-icon" :href="githubUrl" target="_blank">
+            <span class="detail-label">{{ member.github }}</span>
+            <svg aria-labelledby="simpleicons-github-icon" role="img" viewBox="0 0 24 24" xmlns="http://www.w3.org/2000/svg"><title id="simpleicons-github-icon" lang="en">GitHub icon</title><path d="M12 .297c-6.63 0-12 5.373-12 12 0 5.303 3.438 9.8 8.205 11.385.6.113.82-.258.82-.577 0-.285-.01-1.04-.015-2.04-3.338.724-4.042-1.61-4.042-1.61C4.422 18.07 3.633 17.7 3.633 17.7c-1.087-.744.084-.729.084-.729 1.205.084 1.838 1.236 1.838 1.236 1.07 1.835 2.809 1.305 3.495.998.108-.776.417-1.305.76-1.605-2.665-.3-5.466-1.332-5.466-5.93 0-1.31.465-2.38 1.235-3.22-.135-.303-.54-1.523.105-3.176 0 0 1.005-.322 3.3 1.23.96-.267 1.98-.399 3-.405 1.02.006 2.04.138 3 .405 2.28-1.552 3.285-1.23 3.285-1.23.645 1.653.24 2.873.12 3.176.765.84 1.23 1.91 1.23 3.22 0 4.61-2.805 5.625-5.475 5.92.42.36.81 1.096.81 2.22 0 1.606-.015 2.896-.015 3.286 0 .315.21.69.825.57C20.565 22.092 24 17.592 24 12.297c0-6.627-5.373-12-12-12"></path></svg>
+          </a>
+        </li>
+        <li v-if="member.twitter">
+          <a class="social-icon" :href="twitterUrl" target="_blank">
+            <span class="detail-label">@{{ member.twitter }}</span>
+            <svg aria-labelledby="simpleicons-twitter-icon" role="img" viewBox="0 0 24 24" xmlns="http://www.w3.org/2000/svg"><title id="simpleicons-twitter-icon" lang="en">Twitter icon</title><path d="M23.954 4.569c-.885.389-1.83.654-2.825.775 1.014-.611 1.794-1.574 2.163-2.723-.951.555-2.005.959-3.127 1.184-.896-.959-2.173-1.559-3.591-1.559-2.717 0-4.92 2.203-4.92 4.917 0 .39.045.765.127 1.124C7.691 8.094 4.066 6.13 1.64 3.161c-.427.722-.666 1.561-.666 2.475 0 1.71.87 3.213 2.188 4.096-.807-.026-1.566-.248-2.228-.616v.061c0 2.385 1.693 4.374 3.946 4.827-.413.111-.849.171-1.296.171-.314 0-.615-.03-.916-.086.631 1.953 2.445 3.377 4.604 3.417-1.68 1.319-3.809 2.105-6.102 2.105-.39 0-.779-.023-1.17-.067 2.189 1.394 4.768 2.209 7.557 2.209 9.054 0 13.999-7.496 13.999-13.986 0-.209 0-.42-.015-.63.961-.689 1.8-1.56 2.46-2.548l-.047-.02z"></path></svg>
+          </a>
+        </li>
+      </ul>
+    </div>
+  </div>
+</template>
+
+<script>
+export default {
+  props: ['member'],
+  computed: {
+    githubUrl() {
+      return `https://github.com/${this.member.github}`;
+    },
+    twitterUrl() {
+      return `https://twitter.com/${this.member.twitter}`;
+    },
+    helpText() {
+      const lowered = this.member.role.map(item => item.toLowerCase());
+      let ender = '.';
+      if (lowered.length > 1) {
+        ender = ` and ${lowered[lowered.length - 1]}.`;
+        lowered.pop();
+      }
+      return `${lowered.join(', ')}${ender}`;
+    },
+  },
+};
+</script>
+
+<style lang="scss">
+@import '../styles/index.scss';
+@import '../styles/palette.scss';
+@import '@vuepress/plugin-palette/palette';
+.team-member {
+  padding-bottom: 2rem;
+  padding-top: 2rem;
+  border-bottom: 1px dotted #ddd;
+  display: flex;
+  margin: auto;
+  &:last-child {
+    border: none;
+  }
+  .team-member-pic,
+  .team-member-bio,
+  .team-member-details {
+    display: inline-block;
+  }
+  .team-member-pic {
+    width: 15%;
+    img {
+      border-radius: 100%;
+    }
+  }
+  .team-member-bio {
+    width: 55%;
+    h2 {
+      font-size: 1.4rem;
+      border: 0;
+      margin: 0;
+    }
+  }
+  .team-member-details {
+    text-align: right;
+    width: 30%;
+    ul {
+      margin: .25em;
+      list-style: none;
+    }
+    .detail-label {
+      text-transform: uppercase;
+      font-weight: 800;
+      font-size: 0.75rem;
+      color: $landoGrey;
+      position: relative;
+      top: -7px;
+      right: 4px;
+    }
+  }
+  .team-member-title,
+  .team-member-helps {
+    text-transform: uppercase;
+    font-weight: 800;
+    font-size: 0.75rem;
+    color: $landoPink;
+  }
+  .team-member-helps {
+    color: lighten($landoGrey, 25%);
+  }
+  .social-icon {
+    svg {
+      width: 24px;
+      height: 24px;
+      color: $landoPink;
+      fill: $landoPink;
+    }
+  }
+}
+
+@media (max-width: $MQMobile) {
+  .team-member {
+    display: block;
+    text-align: center;
+    .team-member-pic,
+    .team-member-bio,
+    .team-member-details {
+      display: block;
+      width: 100%;
+    }
+    .team-member-details {
+      width: 100%;
+      margin: auto;
+      ul {
+        text-align: center;
+      }
+    }
+  }
+}
+
+</style>

From 0e517776bb5b727cc1a6f23a3ebb45aa35551781 Mon Sep 17 00:00:00 2001
From: John Ouellet <john@thinktandem.io>
Date: Thu, 4 Nov 2021 15:18:08 -0400
Subject: [PATCH 14/16] #130 Remove guides we dont need

---
 docs/.vuepress/components/RelatedGuides.vue   |   1 +
 docs/guides/access-by-other-devices.md        |  47 --
 docs/guides/db-export.md                      |  73 --
 docs/guides/db-import.md                      |  84 ---
 .../guides/drupal-7-landoize-an-extant-app.md | 109 ---
 docs/guides/drupal-multisite-on-lando.md      | 150 ----
 docs/guides/external-access.md                | 138 ----
 docs/guides/frontend.md                       |  76 ---
 ...pull-sync-my-database-on-lamp-y-recipes.md | 159 -----
 .../how-do-i-configure-a-lando-recipe.md      |  80 ---
 ...o-i-set-the-timezone-of-a-lando-service.md |  63 --
 ...up-browsersync-and-gulp-in-my-lando-app.md | 186 -----
 ...stalling-node-in-your-lando-php-service.md | 110 ---
 .../installing-php-extensions-on-lando.md     | 111 ---
 docs/guides/lando-101/lando-config.md         |  65 --
 docs/guides/lando-101/lando-init.md           | 117 ----
 docs/guides/lando-101/lando-overview.md       |  48 --
 docs/guides/lando-101/lando-proxy.md          |  69 --
 docs/guides/lando-101/lando-services.md       |  75 --
 docs/guides/lando-101/lando-start.md          |  72 --
 docs/guides/lando-101/lando-tooling.md        |  77 ---
 docs/guides/lando-info.md                     |  45 --
 docs/guides/lando-phpstorm.md                 |  43 --
 docs/guides/lando-with-vscode.md              | 277 --------
 docs/guides/macos-pantheon-no-proxy.md        |  81 ---
 docs/guides/offline-dev.md                    |  75 --
 docs/guides/overriding-a-service-version.md   |  74 --
 docs/guides/phpmyadmin-themes.md              | 101 ---
 .../setup-lando-on-windows-with-wsl-2.md      |  75 --
 .../updating-local-pantheon-environments.md   |  62 --
 docs/guides/updating-to-rc2.md                | 638 ------------------
 .../using-compass-on-a-lando-node-service.md  |  84 ---
 32 files changed, 1 insertion(+), 3464 deletions(-)
 delete mode 100644 docs/guides/access-by-other-devices.md
 delete mode 100644 docs/guides/db-export.md
 delete mode 100644 docs/guides/db-import.md
 delete mode 100644 docs/guides/drupal-7-landoize-an-extant-app.md
 delete mode 100644 docs/guides/drupal-multisite-on-lando.md
 delete mode 100644 docs/guides/external-access.md
 delete mode 100644 docs/guides/frontend.md
 delete mode 100644 docs/guides/how-can-i-pull-sync-my-database-on-lamp-y-recipes.md
 delete mode 100644 docs/guides/how-do-i-configure-a-lando-recipe.md
 delete mode 100644 docs/guides/how-do-i-set-the-timezone-of-a-lando-service.md
 delete mode 100644 docs/guides/how-to-wire-up-browsersync-and-gulp-in-my-lando-app.md
 delete mode 100644 docs/guides/installing-node-in-your-lando-php-service.md
 delete mode 100644 docs/guides/installing-php-extensions-on-lando.md
 delete mode 100644 docs/guides/lando-101/lando-config.md
 delete mode 100644 docs/guides/lando-101/lando-init.md
 delete mode 100644 docs/guides/lando-101/lando-overview.md
 delete mode 100644 docs/guides/lando-101/lando-proxy.md
 delete mode 100644 docs/guides/lando-101/lando-services.md
 delete mode 100644 docs/guides/lando-101/lando-start.md
 delete mode 100644 docs/guides/lando-101/lando-tooling.md
 delete mode 100644 docs/guides/lando-info.md
 delete mode 100644 docs/guides/lando-phpstorm.md
 delete mode 100644 docs/guides/lando-with-vscode.md
 delete mode 100644 docs/guides/macos-pantheon-no-proxy.md
 delete mode 100644 docs/guides/offline-dev.md
 delete mode 100644 docs/guides/overriding-a-service-version.md
 delete mode 100644 docs/guides/phpmyadmin-themes.md
 delete mode 100644 docs/guides/setup-lando-on-windows-with-wsl-2.md
 delete mode 100644 docs/guides/updating-local-pantheon-environments.md
 delete mode 100644 docs/guides/updating-to-rc2.md
 delete mode 100644 docs/guides/using-compass-on-a-lando-node-service.md

diff --git a/docs/.vuepress/components/RelatedGuides.vue b/docs/.vuepress/components/RelatedGuides.vue
index 8fc4c1b..130d8eb 100644
--- a/docs/.vuepress/components/RelatedGuides.vue
+++ b/docs/.vuepress/components/RelatedGuides.vue
@@ -29,6 +29,7 @@ export default {
   mounted() {
     const themeData = useThemeData();
     const guides = resolveSidebarItems(this.$frontmatter, themeData);
+    console.log(guides);
     const section = guides.find(item => item.title.toLowerCase() === this.tag.toLowerCase());
     this.content = section.children;
   },
diff --git a/docs/guides/access-by-other-devices.md b/docs/guides/access-by-other-devices.md
deleted file mode 100644
index 90afd07..0000000
--- a/docs/guides/access-by-other-devices.md
+++ /dev/null
@@ -1,47 +0,0 @@
----
-description: Learn how to access your Lando sites from other devices on your network like mobile phones or tablets.
-author:
-  name: Team Lando
-  twitter: devwithlando
-date: 2019-11-05
----
-
-# Accessing Lando from Other Devices on Your Local Network
-
-<GuideHeader />
-<YouTube url="" />
-
-You may want to use another device (e.g., a smartphone or tablet) to test your Lando app.  You can access your lando app easily from another device as follows.
-
-## lando share (Testing over the Internet)
-
-The fastest way to do this is to use the [lando share](./../basics/share.html) command.  This will provide you with a URL that you can use to access your app via the Internet.  You can close the connection at any time by pressing a key in the terminal on your local machine.
-
-## Changing the Bind
-
-If you would rather test only on your local network and not over the Internet, you first need to change the `bindAddress` to expose your services on the LAN. Note that there are security implications to this and it is not recommended. Please consult the [Security Docs](./../config/security.md).
-
-Once you've done that you can ...
-
-### 1. First, get the IP address of the machine running lando.
-
-#### Windows
-
-Open a command prompt and enter the command `ipconfig /all` and look for the "IPv4 Address" for the network adapter you use to connect to the Internet.  Make sure NOT to use the IP address of the Docker network adapter.  It should be a number like `192.168.0.123`.
-
-#### macOS
-
-Open System Preferences, Network, and then choose the network adapter you are using to connect to the Internet (Ethernet or Wireless).  The local IP address will then be displayed.
-
-#### Linux
-
-Open a command prompt and enter the command `hostname -I | cut -d' ' -f1`.
-
-### 2. Next, get the port of your lando app.
-
-You can do this by running `lando info` from a command prompt and looking for the URL to your site, which should look something like this: `http://localhost:33333`.  In this case, `33333` is the port number.
-
-You can now visit your lando app from other devices by going to `IP address: Port number`.  (Example: `http://192.168.0.123:33333`)
-
-<GuideFooter />
-<Newsletter />
diff --git a/docs/guides/db-export.md b/docs/guides/db-export.md
deleted file mode 100644
index 4e3b837..0000000
--- a/docs/guides/db-export.md
+++ /dev/null
@@ -1,73 +0,0 @@
----
-metaTitle: Exporting SQL Databases | Lando
-description: Learn how to export your MySQL, MariaDB or Postgres databases from Lando.
-date: 2019-11-05
----
-
-# SQL Export
-
-<GuideHeader test="https://circleci.com/gh/lando/lando/tree/master"/>
-
-Lando ships with a helper `db-export` script that is available in all our `LAMP` and `LEMP` based recipes. Used in the recipe context it should export a database dump `DATABASE.TIMESTAMP.gz` into the `/app` directory.
-
-You can also export databases from other services.
-
-## Usage
-
-At the command line execute:
-
-```bash
-lando db-export
-```
-
-### Examples
-
-```bash
-# Export to a file named `DATABASE.TIMESTAMP.gz`
-lando db-export
-
-# Export to a file called dump.sql.gz
-lando db-export dump.sql
-
-# Export from a secondary database
-lando db-export --host db2
-
-# Dump the result to stdout
-lando db-export --stdout
-
-# Dump to an absolute path
-# NOTE: this is an absolute path in the target container, not on you host
-lando db-export /db/dump.zip
-```
-
-### Options
-
-```bash
-Options:
-  --host, -h      The database service to use                  [default: "database"]
-  --stdout        Dump database to stdout
-```
-
-## Adding the `db-export` command
-
-If you are not using one of our LAMPy [recipes](./../config/recipes.md) you can add the `db-export` command and default options to the ['tooling'](./../config/tooling.md) section of your [Landofile](./../config/lando.md).
-
-```yaml
-tooling:
-  'db-export [file]':
-    service: :host
-    description: Exports database from a database service to a file
-    cmd: /helpers/sql-export.sh
-    user: root
-    options:
-      host:
-        description: The database service to use
-        default: database
-        alias:
-          - h
-      stdout:
-        description: Dump database to stdout
-```
-
-<GuideFooter test="https://circleci.com/gh/lando/lando/tree/master" repo="https://github.com/lando/cli/tree/main/examples/sql-export" />
-<Newsletter />
diff --git a/docs/guides/db-import.md b/docs/guides/db-import.md
deleted file mode 100644
index 115a98f..0000000
--- a/docs/guides/db-import.md
+++ /dev/null
@@ -1,84 +0,0 @@
----
-metaTitle: Importing SQL Databases | Lando
-description: Learn how to import your MySQL, MariaDB or Postgres databases to Lando.
-date: 2019-11-05
----
-
-# SQL Import
-
-<GuideHeader test="https://circleci.com/gh/lando/lando/tree/master"/>
-
-Lando ships with a helper `db-import` script that is available in all our `LAMP` and `LEMP` based recipes. Used in the recipe context it should import a database dump into the recipe-provided database by default but can be used on additional database services as well.
-
-You can also import databases into other hosts and databases. It will currently handle uncompressed, gzipped or zipped dump files.
-
-**This command will wipe out the target database before it runs the import unless you use the `--no-wipe` flag!**
-
-## Usage
-
-```bash
-lando db-import somedumpfile.sql.gz
-```
-
-::: warning DB dump must reside within app directory!
-Due to restrictions in how Docker handles file sharing your database dump **MUST** exist somewhere inside of your app directory. This means that **IT IS A VERY GOOD IDEA** to make sure you add SQL dumps to your `.gitignore` file.
-:::
-
-### Examples
-
-```bash
-# Import a file into the recipe-provided db
-lando db-import dump.sql
-
-# Import a file into an auxiliary second database called 'db2'
-# with a db called `dataz`
-lando db-import dump.zip --host db2
-
-# Import without destroying the target database
-lando db-import dump.zip --no-wipe
-
-# Import using an absolute path
-# NOTE: this is an absolute path in the target container, not on you host
-lando db-import /db/dump.zip
-
-# Import from a subdirectory
-lando db-import subdir/test.sql
-
-# Pipe stdout into db-import
-# NOTE: this is a bit finicky right now
-cat dump.sql | lando db-import
-```
-
-### Options
-
-```bash
-Options:
-  --host, -h      The database service to use                  [default: "database"]
-  --no-wipe       Do not destroy the existing database before an import
-```
-
-## Adding the `db-import` command
-
-If you are not using one of our LAMPy [recipes](./../config/recipes.md) you can add the `db-import` command and default options to the ['tooling'](./../config/tooling.md) section of your [Landofile](./../config/lando.md).
-
-```yaml
-tooling:
-  'db-import <file>':
-    service: :host
-    description: Imports a dump file into a database service
-    cmd: /helpers/sql-import.sh
-    user: root
-    options:
-      host:
-        description: The database service to use
-        default: database
-        alias:
-          - h
-      no-wipe:
-        description: Do not destroy the existing database before an import
-        boolean: true
-```
-
-<GuideFooter test="https://circleci.com/gh/lando/lando/tree/master" repo="https://github.com/lando/cli/tree/main/examples/sql-import" />
-<Newsletter />
-
diff --git a/docs/guides/drupal-7-landoize-an-extant-app.md b/docs/guides/drupal-7-landoize-an-extant-app.md
deleted file mode 100644
index 4857b65..0000000
--- a/docs/guides/drupal-7-landoize-an-extant-app.md
+++ /dev/null
@@ -1,109 +0,0 @@
----
-title: Drupal 7 Landoize an Extant App
-metaTitle: Drupal 7 Landoize an Extant App | Lando
-description: Use Lando as local development environment for an existing Drupal 7 app.
-date: 2020-01-21T17:34:56.556Z
-original: 
-repo: 
-
-author:
-  name: Geoff St. Pierre
-  pic: https://www.gravatar.com/avatar/e103c2a2a8f8caf5848b38b80422cdd9
-  link: https://twitter.com/serundeputy
-
-feed:
-  enable: true
-  author:
-    - name: Geoff St. Pierre
-      email: alliance@lando.dev
-      link: https://twitter.com/serundeputy
-  contributor:
-    - name: Geoff St. Pierre
-      email: alliance@lando.dev
-      link: https://twitter.com/serundeputy
----
-
-# Drupal 7 Landoize an Extant App
-
-<GuideHeader name="Geoff St. Pierre" pic="https://www.gravatar.com/avatar/e103c2a2a8f8caf5848b38b80422cdd9" link="https://twitter.com/serundeputy" />
-
-If you and your team have an existing Drupal 7 application that you would like to use Lando for local development you just need to add a `.lando.yml` configuration file
-to the project and commit it to git.
-
-First in a terminal move to the directory that contains your Drupal 7 project:
-
-```bash
-cd PATH/TO/YOUR/DRUPAL7/APP
-```
-
-## Lando Init
-
-
-Then use the `lando init` command to build your `.lando.yml` file:
-
-```bash
-lando init
-```
-
-Lando will ask you `From where should we get your app's codebase?` select `current working directory`.
-
-<img src="/images/drupal7-extant/landoInit.jpg" />
-
-Then Lando will ask you `What recipe do you want to use?` select `drupal7`.
-
-<img src="/images/drupal7-extant/landoCodeBase.jpg" />
-
-Then Lando needs to know what directory has the Drupal code it asks `Where is your webroot relative to the init destination?` If your
-code is in the current directory you can just hit enter.
-
-
-<img src="/images/drupal7-extant/landoWebroot.jpg" />
-
-::: tip Nested Web Root
-If you are using a nested web root then you should
-specify the path to the Drupal code here like: `web`
-:::
-
-Then Lando prompts for the app name: ` What do you want to call this app?` you can type anything you like, i.e. MyApp.
-
-<img src="/images/drupal7-extant/landoAppName.jpg" />
-
-The `lando init` command will create the `.lando.yml` config file for you. If you chose the `drupal7` recipe your config file should look like this:
-
-```yaml
-name: myapp
-recipe: drupal7
-config:
-  webroot: .
-```
-
-## Lando Start
-
-
-Now you are ready to start your app.
-
-```bash
-lando start
-```
-
-This will build out the containers necessary for your Drupal 7 app. You'll end up with a screen like this once the app is started:
-
-<img src="/images/drupal7-extant/landoStart.jpg" />
-
-Now you can copy any one of the resulting URLs and paste it into a browser to visit your Drupal 7 app running in Lando!
-
-## Pro Tips
-
-If you issue additional terminal commands or clear the screen you can get the URLs and other info about your app anytime by using the `lando info` command:
-
-```bash
-lando info
-```
-
-The info command will give you lots of useful information about your app:
-
-<img src="/images/drupal7-extant/landoInfo.jpg" />
-
-
-<GuideFooter />
-<Newsletter />
diff --git a/docs/guides/drupal-multisite-on-lando.md b/docs/guides/drupal-multisite-on-lando.md
deleted file mode 100644
index 34c5158..0000000
--- a/docs/guides/drupal-multisite-on-lando.md
+++ /dev/null
@@ -1,150 +0,0 @@
----
-title: Running Drupal Multisite on Lando
-metaTitle: How to run Drupal Multisite on Lando | Lando
-description: How to run multisite Drupal installs on Lando.
-summary: How to run multisite Drupal installs on Lando.
-date: 2021-03-17T14:05:33.088Z
-original:
-repo:
-
-author:
-  name: Brook Heaton
-  pic: https://avatars.githubusercontent.com/u/19474864
-  link: https://github.com/brooke-heaton
-
-feed:
-  enable: true
-  author:
-    - name: Brook Heaton
-      email: alliance@lando.dev
-      link: https://github.com/brooke-heaton
-  contributor:
-    - name: Brook Heaton
-      email: alliance@lando.dev
-      link: https://github.com/brooke-heaton
----
-
-# How to Run Drupal Multisite on Lando
-
-<GuideHeader test="" name="Brook Heaton" pic="https://avatars.githubusercontent.com/u/19474864" link="https://github.com/brooke-heaton" />
-<YouTube url="" />
-
-[Drupal multisite](https://www.drupal.org/docs/multisite-drupal) is a feature of Drupal that allows you to run multiple Drupal installs off of a common codebase.
-It's common in universities and other settings where you might want to share themes and modules between a collection of many websites.
-
-## Configuring Lando
-
-To run Drupal multisite you need to do several things:
-
-1. Your `.lando.yml` will need proxies for each multisite in the appserver array
-2. The `settings.local.php` file within your subsite directory (ex: `docroot/sites/site1/`) needs settings to connect to the appropriate Lando-hosted database.
-3. You need Drush aliases pointing to your local. If you use Drupal console, you'll need to specify your uri (ex: `drupal --uri=http://site1.lndo.site cr all`).
-
-## 1. Configure .lando.yml
-
-Create proxies for each multisite in the appserver array in your `.lando.yml` file. Ex:
-
-```yaml
-proxy:
-  appserver:
-    - site1.lndo.site
-    - site2.lndo.s
-services:
-  site1:
-    type: mysql:5.7
-    portforward: 33068
-    config:
-      confd: lando/mysql/conf.d
-  site2:
-    type: mysql:5.7
-    portforward: 33069
-    config:
-      confd: .lando/mysql/conf.d
-```
-
-## 2. Configure each subsite's local.settings.php
-
-Configure each subsite to include the default Lando config to connect to the database, along with specifying the appserver name you defined in `.lando.yml`. For example, in `docroot/sites/site1/settings/local.settings.php` you would include...
-
-```php
-/**
- * Database configuration.
- */
-$databases['default'] = array (
-  'default' => array (
-    'driver' => 'mysql',
-    'database' => 'database',
-    'username' => 'mysql',
-    'password' => 'password',
-    'prefix' => '',
-    'port' => 3306,
-  )
-);
-// The only thing to add from the out-of-the-box Lando db is the special host for each subsite
-$databases['default']['default']['host'] = 'site1';
-```
-
-::: warning If you're on Acquia...
-You must specify $_Server['PWD']=DRUPAL_ROOT if you use Drush 9 on Acquia (this may apply to some other hosts as well). Update your main `sites/default/settings.php` to tell our local Drupal to use the `/settings/local.settings.php` within each subsite:
-
-```php
-if (!key_exists('AH_SITE_ENVIRONMENT', $_ENV)) {
-  $environment_settings = __DIR__  . '/settings/local.settings.php';
-  if (file_exists($environment_settings)) {
-    include $environment_settings;
-  }
-}
-// Temporary fix because drush9 blocks superglobals
-$_SERVER['PWD']=DRUPAL_ROOT;
-```
-:::
-
-## 3. Define Drush aliases for each subsite
-
-Finally you'll need some Drush aliases so Drush can find your subsite installs. Here `docroot` is where our Drupal root is. For example, in `site_root/drush/sites/site-aliases/site1.site.yml` we would define...
-
-```yaml
-local:
-  uri: 'https://site1.lndo.site'
-  paths:
-  - files: /path_to_your_local_site/site_root/docroot'
-dev:
-  host: 'site1dev.ssh.prod.acquia-sites.com'
-  user: 'site1.dev'
-  root: '/var/www/html/site1.dev/docroot'
-  uri: 'site1dev.prod.acquia-sites.com'
-  ac-site: 'site1'
-  ac-env: 'dev'
-  ac-realm: 'prod'
-  paths:
-    drush-script: 'drush8'
-test:
-  root: '/var/www/html/site1.test/docroot'
-  ac-site: 'site1'
-  ac-env: 'test'
-  ac-realm: 'prod'
-  uri: 'site1stg.prod.acquia-sites.com'
-  host: 'site1stg.ssh.prod.acquia-sites.com'
-  user: 'site1.test'
-  paths:
-    drush-script: 'drush8'
-prod:
-  root: '/var/www/html/site1.prod/docroot'
-  ac-site: 'site1'
-  ac-env: 'prod'
-  ac-realm: 'prod'
-  uri: 'site1.prod.acquia-sites.com'
-  host: 'site1.ssh.prod.acquia-sites.com'
-  user: 'site1.prod'
-  paths:
-    drush-script: 'drush8'
-```
-
-I'm using drush8 against the cloud here by specifying that in the drush-script, since I've had issues trying to use drush9 and have no defined drush9 aliases, but that's purely a concern of working with Acquia Cloud.
-
-
-
-
-
-<GuideFooter test="" original="" repo=""/>
-<Newsletter />
diff --git a/docs/guides/external-access.md b/docs/guides/external-access.md
deleted file mode 100644
index 4726cdf..0000000
--- a/docs/guides/external-access.md
+++ /dev/null
@@ -1,138 +0,0 @@
----
-description: Learn how to access your Lando services externally from your host machine.
-date: 2019-11-05
----
-
-# Accessing Your Services Externally
-
-<GuideHeader />
-
-It is often desirable to interact with your services on the host machine level. Common examples of this are accessing a SQL database through a GUI client like SequelPro, or running unit tests through an IDE like PhpStorm.
-
-Lando makes this process relatively painless.
-
-## Checking Connection Info
-
-If you've spun up a Lando app using one of our [recipes](./../config/recipes.md) then its likely relevant services are already exposed and ready for access.
-
-```bash
-# Get info about it
-lando info
-
-{
-  "appserver": {
-    "type": "php",
-    "version": "7.0",
-    "via": "apache",
-    "webroot": "www",
-    "urls": [
-      "https://localhost:32785",
-      "http://localhost:32786",
-      "http://backdrop.lndo.site",
-      "https://backdrop.lndo.site"
-    ]
-  },
-  "database": {
-    "type": "mariadb",
-    "version": "latest",
-    "creds": {
-      "user": "backdrop",
-      "password": "backdrop",
-      "database": "backdrop"
-    },
-    "internal_connection": {
-      "host": "database",
-      "port": 3306
-    },
-    "external_connection": {
-      "host": "localhost",
-      "port": "32787"
-    }
-  }
-}
-```
-
-In the example above you can access the `mariadb` database from your host at `localhost:32787`. Note that this port is automatically assigned by Docker itself and will change every time you restart your app.
-
-That said, Lando provides a way to "lock down" these ports so they are more predictable.
-
-## Locking Down Ports
-
-Say you've spun up an app using our Backdrop recipe but you are frustrated by the external database port always changing. You can modify your `.lando.yml` with some recipe overrides to assign a static port.
-
-::: warning THE PORT YOU FORWARD MUST BE AVAILABLE ON YOUR HOST!
-You are going to need to select a port that is actually available on your host machine. If you don't, then this will fail. It's a good idea to avoid common ports like `3306` which likely are in use already. To that end it's good practice to use a port CLOSE TO the default eg `3307` for `3306` or `5433` for `5432`.
-:::
-
-```yml
-name: myapp
-recipe: backdrop
-services:
-  database:
-    portforward: 3307
-```
-
-```bash
-# rebuild from app directory
-lando rebuild --yes
-
-# Check to see the locked down port
-lando info
-
-{
-  "appserver": {
-    "type": "php",
-    "version": "7.0",
-    "via": "apache",
-    "webroot": "www",
-    "urls": [
-      "https://localhost:32785",
-      "http://localhost:32786",
-      "http://backdrop.lndo.site",
-      "https://backdrop.lndo.site"
-    ]
-  },
-  "database": {
-    "type": "mariadb",
-    "version": "latest",
-    "creds": {
-      "user": "backdrop",
-      "password": "backdrop",
-      "database": "backdrop"
-    },
-    "internal_connection": {
-      "host": "database",
-      "port": 3306
-    },
-    "external_connection": {
-      "host": "localhost",
-      "port": "3307"
-    }
-  }
-}
-```
-
-## Mapping to The Lando Network
-
-Some IDEs, such as PhpStorm, will spin up a separate container to run their appserver for services like built-in unit testing.  This means that it is separate from the Lando network and cannot communicate with Lando's other containers, such as the database.  In order to allow them to communicate, you need to tell your interpreter which network to listen on.
-
-::: warning If you got this message...
-`php_network_getaddresses: getaddrinfo failed: Name or service not known` while PHPUnit testing in PHPStorm and use a MySQL test database, you're in the right place!
-:::
-
-First, find your Lando network name by going to the terminal, and _outside of Lando_ run `$ docker network ls`.  You should find a record matching your Lando project.  For example, if your Lando project is named `d7dev`, then you should see something like:
-
-```
-    NETWORK ID          NAME                                        DRIVER              SCOPE
-    d9526b32d92c        d7dev_default                               bridge              local
-
-```
-
-Next, ensure your framework (PHP) interpreter is configured to use a Docker container matching your project's appserver configuration.  For example, if your running PHP 7.1 on Apache, this would look like `devwithlando/php:7.1-apache`.
-
-Finally, when configuring your framework, edit the Docker Container settings and change the Network Mode to the name of your Lando docker network.
-
-Now your IDE should be able to communicate with Lando.
-
-<GuideFooter />
-<Newsletter />
diff --git a/docs/guides/frontend.md b/docs/guides/frontend.md
deleted file mode 100644
index fe79308..0000000
--- a/docs/guides/frontend.md
+++ /dev/null
@@ -1,76 +0,0 @@
----
-description: Learn how to add node services to your Lando app so you can use yarn, npm, grunt, gulp, webpack, etc for all the frontend magic.
-date: 2019-11-05
----
-
-# Frontend Tooling
-
-<GuideHeader />
-
-Most modern frontend tooling relies upon the NPM package manager. In this tutorial we'll show you how to add Node to your app, download tools like Gulp/Grunt/Webpack, and run them in your Lando app.
-
-When you're done, you should be able to distribute your Lando app with a full set of frontend tools that are standardized to work the same on every team member's computer.
-
-## Add Node Service
-
-Assuming you're starting with a "Lando-ized" app, open the `.lando.yml` file in the root of your app directory. In this example we'll assume you're using a very basic [LAMP](./../config/lamp.md) recipe.
-
-To install our frontend tooling we need to be able to run Node. Fortunately it's very easy for us to add a basic Node service to our app:
-
-```yml
-name: myapp
-recipe: lamp
-
-services:
-  node:
-    type: node
-    build:
-      - npm install
-```
-
-Note the `build` section. This bash command will automatically run when we start our app, installing any Node packages specified in our package.json file.
-
-## Adding Grunt/Gulp/Etc.
-
-While we're now able to install Node packages for our project, we still need to be able to install global tooling like Grunt, Gulp, or other task runners that form the backbone of our frontend tooling. Fortunately, Lando makes this easy through the `globals` tag:
-
-
-```yml
-services:
-  node:
-    type: node
-    build:
-      - npm install
-      - gulp
-    globals:
-      gulp-cli: latest
-```
-
-You can do the same thing for any NPM project; for example Grunt would be `grunt-cli: "latest"`. This is the equivalent to installing a package with `npm install -g project-name`.
-
-Note we've now added a another command to `build` to automatically run `gulp` every time we start the app. This, of course, assumes that the default `gulp` task is defined otherwise you should expect your build step to fail.
-
-::: tip Package Versions Are Fully Armed and Customizable
-You can lock your app tooling to whatever package version you like. Don't use node:6.10? Change to one of the other available versions in the [service documentation](./../config/node.md). And you're free to download whatever version of a global service your heart desires. For example, if you want to lock your team to something more stable than the latest gulp-cli, change that entry in `globals` to `gulp-cli:1.3.0`.
-:::
-
-## Making Tooling Available on the CLI
-
-Almost there! All our services are installed, but how do we run a command on the fly, say starting a watch task or running `lando npm install hot-new-thing` to start experimenting with a new package? We could SSH into our node container, but that's SO 2016. Instead, we'll expose our new tooling via the CLI by adding this [`tooling`](./../config/tooling.md) section to our `.lando.yml` file:
-
-```yml
-tooling:
-  npm:
-    service: node
-  node:
-    service: node
-  gulp:
-    service: node
-  yarn:
-    service: node
-```
-
-After restarting your app, you should be able to run `lando node`, `lando gulp` or `lando npm` and have the corresponding commands run. This is particularly useful if you want to kickoff a watch task you might have configured, say `lando gulp watch`.
-
-<GuideFooter />
-<Newsletter />
diff --git a/docs/guides/how-can-i-pull-sync-my-database-on-lamp-y-recipes.md b/docs/guides/how-can-i-pull-sync-my-database-on-lamp-y-recipes.md
deleted file mode 100644
index c9a8cc0..0000000
--- a/docs/guides/how-can-i-pull-sync-my-database-on-lamp-y-recipes.md
+++ /dev/null
@@ -1,159 +0,0 @@
----
-title: Importing a remote database and files into Lando using Laravel Envoy
-description: Add a pull command for LAMP, LEMP, Drupal, Backdrop, Laravel, PHP apps hosted on metal.
-summary: Add a pull command for LAMP, LEMP, Drupal, Backdrop, Laravel, PHP apps hosted on metal.
-date: 2020-03-30T19:23:00.720Z
-original:
-repo:
-
-author:
-  name: Geoff St. Pierre
-  pic: https://www.gravatar.com/avatar/e103c2a2a8f8caf5848b38b80422cdd9
-  link: https://twitter.com/serundeputy
-
-feed:
-  enable: true
-  author:
-    - name: Geoff St. Pierre
-      email: alliance@lando.dev
-      link: https://twitter.com/serundeputy
-  contributor:
-    - name: Geoff St. Pierre
-      email: alliance@lando.dev
-      link: https://twitter.com/serundeputy
----
-
-# Importing a remote database and files into Lando using Laravel Envoy
-
-<GuideHeader name="Geoff St. Pierre" pic="https://www.gravatar.com/avatar/e103c2a2a8f8caf5848b38b80422cdd9" link="https://twitter.com/serundeputy" />
-<YouTube url="" />
-
-If you are hosted on a server like Linode, Digital Ocean, AWS or the like you can still cook up a `lando pull` command to pull your database and/or file assets down from production using Laravel Envoy.
-
-This will work for all Lando apps that extend from `laempy` recipes like: LAMP, LEMP, Dupal 6/7/8, Backdrop, Joomla, WordPress and Laravel.
-
-## Requirements
-
-We'll need a few things to get this set up for our `laempy` apps. We need to require the `laravel/envoy` composer package in our app, configure a `.env` file, configure an `Envoy.blade.php` file to define our tasks, and configure some `tooling` in our `.lando.yml` file. Let's jump in.
-
-## laravel/envoy
-
-To get the `laravel/envoy` package just use `composer`:
-
-```bash
-lando composer require laravel/envoy
-```
-
-## .env
-
-If you don't have a `.env` file create one and add this to it, if you already have on just add this:
-
-```bash
-LP_DB_PWD=<your_db_password>
-LP_DB=<your_db_name>
-LP_PROJECT_ROOT=<path/to/project/root/on/your/server> # like: /var/www/myapp
-LP_SITE_ROOT=<path/to/site/root> # like for nested web root /var/www/myapp/web
-LP_DB_BACK_PATH=<path/to/db/backups> # like /home/me/backups/appname/dbs
-LP_FILES_BACK_PATH=<path/to/files/backups/f.tgz # like /home/me/backups/appname/files/f.tgz
-LP_SSH_CMD=<user>@<server_ip> # like me@server_ip
-```
-after creating or updating your `.env` file you'll need to rebuild the app.
-
-```bash
-lando rebuild -y
-```
-
-## Envoy.blade.php
-
-Create a file in the root of your app called `Envoy.blade.php` and add this to it:
-
-```php
-@setup
-  $ssh = getenv('LP_SSH_CMD');
-@endsetup
-
-@servers(['web' => $ssh, 'localhost' => '127.0.0.1'])
-
-@story('pull')
-  dump
-  getdb
-  cleandb
-  backupfiles
-  getfiles
-  cleanfiles
-@endstory
-
-@task('dump', ['on' => 'web'])
-  mysqldump -u root -p{{ getenv('LP_DB_PWD') }} {{ getenv('LP_DB') }} > {{ getenv('LP_DB_BACK_PATH') }}
-@endtask
-
-@task('getdb', ['on' => 'localhost'])
-  scp {{ getenv('LP_SSH_CMD') }}:{{ getenv('LP_DB_BACK_PATH') }} db.sql
-@endtask
-
-@task('cleandb', ['on' => 'web'])
-  rm {{ getenv('LP_DB_BACK_PATH') }}
-@endtask
-
-@task('backupfiles', ['on' => 'web'])
-  cd {{ getenv('LP_SITE_ROOT') }}
-  tar czf {{ getenv('LP_FILES_BACK_PATH') }} files
-@endtask
-
-@task('getfiles', ['on' => 'localhost'])
-  scp {{ getenv('LP_SSH_CMD') }}:{{ getenv('LP_FILES_BACK_PATH') }} /app/f.tgz
-@endtask
-
-@task('cleanfiles', ['on' => 'web'])
-  rm {{ getenv('LP_FILES_BACK_PATH') }}
-@endtask
-```
-
-## .lando.yml
-
-In your `.lando.yml` file tell Lando about your `.env` file and add tooling for the `pull` command.
-
-If you don't have an `env_file` section add one.
-
-```yaml
-env_file:
-  - .env
-```
-
-If you just added this your app will require a rebuild.
-
-```bash
-lando rebuild -y
-```
-
-In your `tooling` section add.
-
-```yaml
-tooling:
-  envoy:
-    service: appserver
-  pull:
-    service: appserver
-    description: Pull and import the database from production.
-    cmd:
-      - appserver: envoy run pull
-      - database: /helpers/sql-import.sh db.sql
-      - appserver: rm db.sql
-      - appserver: rm -rf /app/web/files # change this to the /path/to/file/assets for your app.
-      - appserver: tar xvzf f.tgz -C /app/web
-      - appserver: rm f.tgz
-```
-
-## Using the pull command
-
-Now to use your pull command you'll need to configure the `backups` directories as specified in `LP_DB_BACK_PATH` and `LP_FILES_BACK_PATH`
-to exist on your server. Then just run:
-
-```bash
-lando pull
-```
-
-and that will backup your db and file assets and pull them down for you! Happy Lando travels folks.
-
-<GuideFooter test="" original="" repo=""/>
-<Newsletter />
diff --git a/docs/guides/how-do-i-configure-a-lando-recipe.md b/docs/guides/how-do-i-configure-a-lando-recipe.md
deleted file mode 100644
index ed9da3d..0000000
--- a/docs/guides/how-do-i-configure-a-lando-recipe.md
+++ /dev/null
@@ -1,80 +0,0 @@
----
-title: How do I configure a Lando Recipe?
-metaTitle: How do I configure a Lando Recipe? | Lando
-description: Using the lando config key to configure your recipe.
-date: 2020-02-04T18:00:18.702Z
-original: 
-repo: 
-
-author:
-  name: Team Lando
-  pic: https://gravatar.com/avatar/c335f31e62b453f747f39a84240b3bbd
-  link: https://twitter.com/devwithlando
-
-feed:
-  enable: true
-  author:
-    - name: Team Lando
-      email: alliance@lando.dev
-      link: https://twitter.com/devwithlando
-  contributor:
-    - name: Team Lando
-      email: alliance@lando.dev
-      link: https://twitter.com/devwithlando
----
-
-# How do I configure a Lando Recipe?
-
-<GuideHeader name="Team Lando" pic="https://gravatar.com/avatar/c335f31e62b453f747f39a84240b3bbd" link="https://twitter.com/devwithlando" test="https://github.com/lando/cli/tree/main/examples/lamp"/>
-
-When you first initialize a lando app (`lando init`) you get a very simple `.lando.yml` configuration file. Here is the `.lando.yml` file for the LAMP recipe.
-
-```yaml
-name: mylamp
-recipe: lamp
-config:
-  webroot: .
-```
-
-By using the `config` key in the `lando.yml` file you can configure aspects of your app to say match the production instance. For example say your production server
-is using PHP 5.6; you can set that under the `config` key like so:
-
-```yaml
-name: mylamp
-recipe: lamp
-config:
-  webroot: .
-  php: 5.6
-```
-
-Now be sure to `rebuild` your app so that the new changes take effect:
-
-```bash
-lando rebuild -y
-```
-
-You can check that the change took by using `lando php -v`:
-
-```bash
-└─ $ ∴ lando php -v
-PHP 5.6.40 (cli) (built: Jan 23 2019 00:10:05) 
-Copyright (c) 1997-2016 The PHP Group
-Zend Engine v2.6.0, Copyright (c) 1998-2016 Zend Technologies
-    with Zend OPcache v7.0.6-dev, Copyright (c) 1999-2016, by Zend Technologies
-```
-
-Similarly you can pin down the database backend and version of your app. Say you want MariaDB 10.3:
-
-```yaml
-name: mylamp
-recipe: lamp
-config:
-  webroot: .
-  php: 5.6
-  database: mariadb:10.3
-```
-
-Again rebuild for the changes: `lando rebuild -y` and 💥 you now have PHP 5.6 and MariaDB 10.3!
-
-<GuideFooter original="" repo=""/>
-<Newsletter />
diff --git a/docs/guides/how-do-i-set-the-timezone-of-a-lando-service.md b/docs/guides/how-do-i-set-the-timezone-of-a-lando-service.md
deleted file mode 100644
index cf2f6d5..0000000
--- a/docs/guides/how-do-i-set-the-timezone-of-a-lando-service.md
+++ /dev/null
@@ -1,63 +0,0 @@
----
-title: How do I set the timezone of a Lando service?
-metaTitle: How do I set the timezone of a Lando service? | Lando
-description: Set the timezone of a Lando service for testing time sensitive operations
-summary: Set the timezone of a Lando service for testing time sensitive operations
-date: 2020-03-27T22:30:09.777Z
-original:
-repo:
-
-author:
-  name: Team Lando
-  pic: https://gravatar.com/avatar/c335f31e62b453f747f39a84240b3bbd
-  link: https://twitter.com/devwithlando
-
-feed:
-  enable: true
-  author:
-    - name: Team Lando
-      email: alliance@lando.dev
-      link: https://twitter.com/devwithlando
-  contributor:
-    - name: Team Lando
-      email: alliance@lando.dev
-      link: https://twitter.com/devwithlando
----
-
-# How do I set the timezone of a Lando service?
-
-<GuideHeader test="https://github.com/lando/cli/tree/main/examples/services" name="Team Lando" pic="https://gravatar.com/avatar/c335f31e62b453f747f39a84240b3bbd" link="https://twitter.com/devwithlando" />
-
-<YouTube url="https://www.youtube.com/embed/P8n2z4m0_s0" />
-
-If you need to set the timezone of a Lando service here is how! Just symlink the appropriate timezone you need in a `run_as_root` build step. Here is an example `.lando.yml` file.
-
-```yaml
-name: timezone
-recipe: lemp
-config:
-  webroot: .
-
-services:
-  appserver:
-    run_as_root:
-      - ln -snf /usr/share/zoneinfo/America/New_York /etc/localtime
-      - echo "America/New_York" > /etc/timezone
-```
-
-Just copy the `run_as_root` section into your `services` key for any service you need it for, i.e. `appserver`, `database`, or whatever service you need to set. Be sure to swap out `America/New_York` to the timezone that you need.
-
-::: warning Tested on Debian only
-Note that we test this on Debian flavored services so these instructions might differ slightly or be unapplicable for non-Debian services.
-:::
-
-Then run a rebuild:
-
-```bash
-lando rebuild -y
-```
-
-and you'll have the timezone set in those services.
-
-<GuideFooter original="" repo=""/>
-<Newsletter />
diff --git a/docs/guides/how-to-wire-up-browsersync-and-gulp-in-my-lando-app.md b/docs/guides/how-to-wire-up-browsersync-and-gulp-in-my-lando-app.md
deleted file mode 100644
index 5eee2f3..0000000
--- a/docs/guides/how-to-wire-up-browsersync-and-gulp-in-my-lando-app.md
+++ /dev/null
@@ -1,186 +0,0 @@
----
-title: How do I wire up Browsersync and Gulp in my Lando app?
-metaTitle: How to wire up Browsersync and Gulp in my Lando app | Lando
-description: How to setup Lando with Browsersync & Gulp so that edits to scss files are reflected immediately in your browser.
-summary: How to setup Lando with Browsersync & Gulp so that edits to scss files are reflected immediately in your browser.
-date: 2020-04-07T14:05:33.088Z
-original:
-repo:
-
-author:
-  name: Jonathan Shaw
-  pic: https://www.gravatar.com/avatar/ba46283b2033d3a0201f2042746f81e7
-  link: https://github.com/jonathanjfshaw
-
-feed:
-  enable: true
-  author:
-    - name: Jonathan Shaw
-      email: alliance@lando.dev
-      link: https://github.com/jonathanjfshaw
-  contributor:
-    - name: Jonathan Shaw
-      email: alliance@lando.dev
-      link: https://github.com/jonathanjfshaw
----
-
-# How do I wire up Browsersync and Gulp in my Lando app?
-
-<GuideHeader test="" name="Jonathan Shaw" pic="https://www.gravatar.com/avatar/ba46283b2033d3a0201f2042746f81e7" link="https://github.com/jonathanjfshaw" />
-<YouTube url="" />
-
-[Browsersync](https://www.browsersync.io) is a nodejs package that synchronizes website changes to the browser.
-While it can be used for many things, this guide shows how to use it to push changes made to css files to the browser.
-
-This guide also assumes you're using Gulp to automate your theming tasks, and are editing SASS/SCSS files that need compiling
-into css before they can be previewed in your browser.
-
-## Configuring Lando for Browsersync
-
-### Create the proxy
-
-First you must create a proxy domain for browsersync to use. Changes you make to your scss files will only show up when
-you are looking at this `https://bs.myproject.lndo.site`, not at the usual domain `https://myproject.lndo.site`.
-Add your equivalent of this to your .lando.yml file:
-
-```yaml
-proxy:
-  node:
-    - bs.myproject.lndo.site:3000
-```
-
-### Stream changes whenever Lando is running
-It's most convenient if Browsersync is running in the background whenever your Lando site is up.
-One simple way to achieve this is to fire off a gulp task whenever Lando starts up.
-If you had a gulp task called 'watch' then you'd put this in .lando.yml:
-
-```yaml
-services:
-  node:
-    type: node
-    ssl: true
-    command: cd /app/path/to/gulpfile && node_modules/.bin/gulp watch
-```
-
-## Configuring Gulp to push scss
-
-### Compiling scss
-
-Here's an example of a `gulpfile.js` that defines a task that compiles scss into css.
-Note the addition of `browserSync.stream()` at the end of the pipeline.
-This will send the compiled css to the browser, if browsersync is running.
-
-```js
-// Live CSS reload & browser Syncing.
-var browserSync = require('browser-sync').create();
-
-// Gulp plugin for showing scss file in browser inspect tools rather than the compiled css file.
-var sourcemaps = require('gulp-sourcemaps');
-
-// Gulp plugin for sass.
-var sass = require('gulp-sass');
-
-// Allows you to use glob syntax in imports (i.e. @import "dir/*.sass"). Use as a custom importer for node-sass.
-var importer = require('node-sass-globbing');
-
-// Default configuration.
-var config = {
-  scss: './scss/*.scss', // The top level scss files that include all other scss.
-  watch: './scss/**', // All scss files that should trigger a recompile.
-  css: './css', // The path to the generated css files.
-  node_modules: './node_modules', // The path to the node modules directory.
-};
-
-// A gulp task that compiles scss into css. Execute with 'gulp scss-compile'
-gulp.task('scss-compile', function () {
- return gulp.src(config.scss)
-  .pipe(plumber())
-   // Start making a source map, so that the browser can show a developer which scss file is responsible for a css rule.
-  .pipe(sourcemaps.init({loadMaps: true})) //Not sure if loadMaps is a good idea.
-   // Compile the scss to css.
-  .pipe(sass({
-    importer: importer,
-    // Include some useful scss from external node packages.
-    includePaths: [
-      config.node_modules + '/breakpoint-sass/stylesheets/',
-      config.node_modules + '/compass-mixins/lib/'
-    ],
-    // Tweak output styling to make things easier for developers.
-    outputStyle: 'expanded',
-    sourceComments: true,
-    indentWidth: 2
-  }).on('error', sass.logError))
-  .pipe(sourcemaps.write('maps'))
-   // Write out the generated css.
-  .pipe(gulp.dest(config.css))
-   // Push the css to the browser.
-  .pipe(browserSync.stream());
-});
-```
-
-### Recompiling whenever the scss changes
-
-```js
-// Watch the scss files and push changes automatically.
-gulp.task('watch', function () {
-  // Setup a browsersync server.
-  browserSync.init({
-    proxy: 'http://appserver_nginx', // Could be 'http://appserver' if you're running apache.
-    socket: {
-      domain: 'https://bs.myproject.lndo.site', // The node proxy domain you defined in .lando.yaml. Must be https?
-      port: 80 // NOT the 3000 you might expect.
-    },
-    open: false,
-    logLevel: "debug",
-    logConnections: true,
-  });
-  // Trigger the scss-compile task whenever any file in the defined location changes.
-  gulp.watch(config.watch, gulp.series('scss-compile'));
-});
-```
-
-## Trying it out
-
-* Run `lando rebuild -y` so your new proxy domain is exposed.
-* Verify that the output includes under `NODE URLS` your new proxy `https://bs.myproject.lndo.site`, and it is green.
-* Run `lando logs -s node -f` to continuously stream the logs of the node service. You should see something like:
-
-```bash
-Using gulpfile /app/path/to/my/theme/gulpfile.js
-Starting 'watch'...
-...
-[Browsersync] Proxying: http://appserver_nginx
-[Browsersync] Access URLs:
-  Local: http://localhost:3000
-  External: http://172.20.0.6:3000
-```
-
-* Visit your browsersync url `https://bs.myproject.lndo.site` in your browser. It should load normally.
-* In the source of this page search for "browser-sync". You should see the browser-sync-client script has been injected into the page.
-* Look again at the streaming node logs; something like this should have appeared
-
-```bash
-[Browsersync] Browser Connected: Chrome, version: 80.0.3987.149
-```
-
-* In your IDE edit a style rule in an scss file, save if necessary, and wait a few seconds.
-* Look again at the logs; something like this should have appeared:
-
-```bash
-Starting 'scss-compile'...
-[Browsersync] 2 files changed (style.css.map, style.css)
-Finished 'scss-compile' after 1.88 s
-```
-
-* Look at your open browser window again (without refreshing). You should see the impact of your scss edit.
-* Feel very excited!
-
-## Known issues
-
-* When submitting a form on `https://bs.myproject.lndo.site` you will be redirected to `https://appserver_nginx` (which is not a working url).
-If you know a solution for this problem, please update this guide.
-* So to use the forms on a site use the non-browsersync URL, i.e. `https://myproject.lndo.site`.
-
-
-<GuideFooter test="" original="" repo=""/>
-<Newsletter />
diff --git a/docs/guides/installing-node-in-your-lando-php-service.md b/docs/guides/installing-node-in-your-lando-php-service.md
deleted file mode 100644
index 0d2079c..0000000
--- a/docs/guides/installing-node-in-your-lando-php-service.md
+++ /dev/null
@@ -1,110 +0,0 @@
----
-title: Installing node in your Lando PHP service
-metaTitle: Installing node in your Lando PHP service | Lando
-description: Learn how to install node in a Lando PHP service for things like Pattern Lab or Emulsify
-summary: Learn how to install node in a Lando PHP service for things like Pattern Lab or Emulsify
-date: 2020-05-12T18:06:56.254Z
-original:
-repo:
-
-author:
-  name: Team Lando
-  pic: https://gravatar.com/avatar/c335f31e62b453f747f39a84240b3bbd
-  link: https://twitter.com/devwithlando
-
-feed:
-  enable: true
-  author:
-    - name: Team Lando
-      email: alliance@lando.dev
-      link: https://twitter.com/devwithlando
-  contributor:
-    - name: Team Lando
-      email: alliance@lando.dev
-      link: https://twitter.com/devwithlando
----
-
-# Installing node in your Lando PHP service
-
-<GuideHeader test="https://circleci.com/gh/lando/lando/tree/master" name="Team Lando" pic="https://gravatar.com/avatar/c335f31e62b453f747f39a84240b3bbd" link="https://twitter.com/devwithlando" />
-<YouTube url="" />
-
-Some frontend tooling kits like [Emulsify](https://www.drupal.org/project/emulsify_drupal) or [Pattern Lab](https://patternlab.io/) _may_ assume that `composer/php` can invoke `yarn/npm/node` and vice-versa. This pattern, sadly, is fundamentally at odds with Lando's one-thing-per-container model.
-
-You can, however, get around it by installing the needed dependencies directly in the service that requires them.
-
-We've found installing `node` inside a Lando PHP service to generally be the path of least resistance.
-
-## 1. Using build steps
-
-Below is an example that installs `node12` using [build-steps](./../config/services.md#build-steps).
-
-```yaml
-services:
-  myservice:
-    type: php
-    build_as_root:
-      # Note that you will want to use the script for the major version of node you want to install
-      # See: https://github.com/nodesource/distributions/blob/master/README.md#installation-instructions
-      - curl -sL https://deb.nodesource.com/setup_12.x | bash -
-      - apt-get install -y nodejs
-tooling:
-  node:
-    service: myservice
-  npm:
-    service: myservice
-```
-
-You can verify with:
-
-```bash
-lando node -v
-lando npm -v
-```
-
-## 2. Extending a Dockerfile
-
-If you are planning to extend your service with _additional_ build steps or would like to cache the build steps for a faster `lando rebuild` you should instead consider [extending with a Dockerfile](./../config/services.md#using-dockerfiles) as in the example below:
-
-**.lando.yml**
-
-```yaml
-services:
-  myservice:
-    type: php:custom
-    via: cli
-    overrides:
-      image: lando/php:7.4-with-node12
-      build:
-        context: ./
-        dockerfile: Dockerfile.node
-tooling:
-  node:
-    service: myservice
-  npm:
-    service: myservice
-```
-
-**Dockerfile.node**
-
-```docker
-FROM devwithlando/php:7.4-apache-2
-
-# Choose the major node version
-ENV NODE_VERSION=12
-
-# Install node
-RUN curl -sL "https://deb.nodesource.com/setup_${NODE_VERSION}.x" | bash - \
-  && apt-get install -y nodejs
-```
-
-Again, you can verify with:
-
-```bash
-lando node -v
-lando npm -v
-```
-
-
-<GuideFooter test="https://circleci.com/gh/lando/lando/tree/master" original="" repo="https://github.com/lando/cli/tree/main/examples/php"/>
-<Newsletter />
diff --git a/docs/guides/installing-php-extensions-on-lando.md b/docs/guides/installing-php-extensions-on-lando.md
deleted file mode 100644
index 85d0bc1..0000000
--- a/docs/guides/installing-php-extensions-on-lando.md
+++ /dev/null
@@ -1,111 +0,0 @@
----
-title: Installing PHP Extensions on Lando
-metaTitle: Installing PHP Extensions on Lando | Lando
-description: Learn a few ways you can install extra php extensions to your Lando PHP service
-summary: Learn a few ways you can install extra php extensions to your Lando PHP service
-date: 2020-05-12T16:52:31.824Z
-original:
-repo:
-
-author:
-  name: Team Lando
-  pic: https://gravatar.com/avatar/c335f31e62b453f747f39a84240b3bbd
-  link: https://twitter.com/devwithlando
-
-feed:
-  enable: true
-  author:
-    - name: Team Lando
-      email: alliance@lando.dev
-      link: https://twitter.com/devwithlando
-  contributor:
-    - name: Team Lando
-      email: alliance@lando.dev
-      link: https://twitter.com/devwithlando
----
-
-# Installing PHP Extensions on Lando
-
-<GuideHeader test="https://circleci.com/gh/lando/lando/tree/master" name="Team Lando" pic="https://gravatar.com/avatar/c335f31e62b453f747f39a84240b3bbd" link="https://twitter.com/devwithlando" />
-<YouTube url="" />
-
-You may wish to add additional PHP extensions to your Lando [PHP service](./../config/php.md). There are a few different ways you can do this:
-
-[[toc]]
-
-Note that both of these strategies make use of underlying utilities provided by the [Official Docker PHP Image]() which is the base image used by Lando's PHP service. We recommend you read more about them [over on their docs](https://hub.docker.com/_/php).
-
-Also note that you may need to adapt these slightly depending on the PHP version you are using.
-
-## 1. Using build steps
-
-If installing your PHP extension is fairly trivial and not a long-running operation you may wish to simply use Lando [build-steps](./../config/services.md#build-steps)
-
-Here is an example that uses build-steps to install the `xsl` and `stats` extensions.
-
-```yaml
-services:
-  myservice:
-    type: php
-    build_as_root:
-      - apt-get update -y
-      - apt install libxslt1-dev -y
-      - pecl install stats-2.0.3
-      - docker-php-ext-install xsl
-      - docker-php-ext-enable stats
-```
-
-You can verify the extension was enabled by running:
-
-```bash
-lando ssh -s myservice -c "php -m"
-```
-
-A downside of this approach is these steps till run _EVERY TIME_ you do a `lando rebuild`.
-
-## 2. Using Dockerfiles
-
-If you have complex, lengthy or long running build steps you may wish to create a `Dockerfile` in your repo that directly extends one of [Lando's PHP images](https://hub.docker.com/r/devwithlando/php/tags).
-
-This approach is great if you care about rebuild speed. Docker will cache the resultant image and only rebuild if the Dockerfile changes. By extension this means your `lando rebuild` will be pretty fast as well.
-
-It also ensures your Landofile does not get unruly.
-
-Here is an example that installs the `oci8` and `pdo_sqlsrv` extension.
-
-**.lando.yml**
-
-```yaml
-services:
-  myservice:
-    type: php:custom
-    overrides:
-      image: lando/php:7.3-custom
-      build:
-        context: ./
-        dockerfile: Dockerfile.custom
-      ports:
-        - "80"
-```
-
-**Dockerfile.custom**
-
-```docker
-FROM devwithlando/php:7.3-apache-2
-
-# Add php extension helper
-ADD https://github.com/mlocati/docker-php-extension-installer/releases/latest/download/install-php-extensions /usr/local/bin/
-
-# Install Oracle Instantclient, OCI8 and Microsoft SQL Server extensions
-RUN chmod +x /usr/local/bin/install-php-extensions && sync && \
-  install-php-extensions oci8-2.2.0 sqlsrv pdo_sqlsrv
-```
-
-You can verify the extension was enabled by running
-
-```bash
-lando ssh -s myservice -c "php -m"
-```
-
-<GuideFooter test="https://circleci.com/gh/lando/lando/tree/master" original="" repo="https://github.com/lando/cli/tree/main/examples/php-extensions"/>
-<Newsletter />
diff --git a/docs/guides/lando-101/lando-config.md b/docs/guides/lando-101/lando-config.md
deleted file mode 100644
index 8746a24..0000000
--- a/docs/guides/lando-101/lando-config.md
+++ /dev/null
@@ -1,65 +0,0 @@
----
-title: Lando Configure
-metaTitle: Lando Configure | Lando
-description: An example using the config key to configure a Lando recipe.
-summary: An example of extending a Lando recipe using the config key.
-date: 2020-08-12T14:38:22.169Z
-original: 
-repo: 
-
-author:
-  name: Team Lando
-  pic: https://gravatar.com/avatar/c335f31e62b453f747f39a84240b3bbd
-  link: https://twitter.com/devwithlando
-
-feed:
-  enable: true
-  author:
-    - name: Team Lando
-      email: alliance@lando.dev
-      link: https://twitter.com/devwithlando
-  contributor:
-    - name: Team Lando
-      email: alliance@lando.dev
-      link: https://twitter.com/devwithlando
----
-
-# Lando Configuration
-
-<GuideHeader test="https://github.com/lando/lando/blob/master/examples/lando-101/README.md" name="Team Lando" pic="https://gravatar.com/avatar/c335f31e62b453f747f39a84240b3bbd" link="https://twitter.com/devwithlando" />
-<YouTube url="" />
-
-As we've seen Lando recipes are very useful and dead simple. So far our `.lando.yml` file for the LAMP recipe is just two lines:
-
-```yaml
-name: lando-101
-recipe: lamp
-```
-
-The power of Lando is our ability to configure and change it to meet our needs. We can configure it to match production for instance. Let's add a PHP file to our `lando-101` app just so we have something to view in our app. Open a file in your favorite text editor and add a call to `phpinfo()` and save it as `index.php`.
-
-```php
-<?php
-phpinfo();
-```
-
-Now if we visit our Lando provide URL for the `lando-101` app `https://lando-101.lndo.site` we will see:
-
-<img src="/images/lando-101/lando-101-index.jpg" />
-
-We can see that this reports the PHP version as `7.3`. Enter the `config` key. Say our production server for the `lando-101` app is running PHP 7.4 and we want to match that in our Lando development environment. We can do that by using the [config](/config/lamp.html#configuration) key in our `.lando.yml` file to configure how the recipe is built. In this case we want PHP 7.4. Edit your `.lando.yml` file like this:
-
-```yaml
-name: lando-101
-recipe: lamp
-config:
-  php: 7.4
-```
-
-Now let's rebuild our app with the `lando rebuild -y` command. Now if we visit our app in a browser we will see the the PHP version is reported as `7.4`. Simple! Just like that we've configured our app to use a different version of PHP.
-
-You can read the details about the `config` key in the docs: [config](/config/recipes.html#config).
-
-
-<GuideFooter test="" original="" repo=""/>
-<Newsletter />
diff --git a/docs/guides/lando-101/lando-init.md b/docs/guides/lando-101/lando-init.md
deleted file mode 100644
index 1744bac..0000000
--- a/docs/guides/lando-101/lando-init.md
+++ /dev/null
@@ -1,117 +0,0 @@
----
-title: Lando Init
-metaTitle: Lando Init | Lando
-description: Introduction to Lando ~ Using lando init command.
-summary: Introduction to Lando ~ Using lando init command.
-date: 2020-06-16T13:44:13.109Z
-original: 
-repo: 
-
-author:
-  name: Team Lando
-  pic: https://gravatar.com/avatar/c335f31e62b453f747f39a84240b3bbd
-  link: https://twitter.com/devwithlando
-
-feed:
-  enable: true
-  author:
-    - name: Team Lando
-      email: alliance@lando.dev
-      link: https://twitter.com/devwithlando
-  contributor:
-    - name: Team Lando
-      email: alliance@lando.dev
-      link: https://twitter.com/devwithlando
----
-
-# Lando Init
-
-<GuideHeader test="https://github.com/lando/lando/blob/master/examples/lando-101/README.md" name="Team Lando" pic="https://gravatar.com/avatar/c335f31e62b453f747f39a84240b3bbd" link="https://twitter.com/devwithlando" />
-<YouTube url="" />
-
-The `lando init` command follows the pattern of `git init` or `npm init`. Where `lando init` will prompt you with some questions and prepares a `.lando.yml` configuration file for you. You can run `lando init` from an empty directory or from an extant codebase.
-
-Let's step through the questions that `lando init` prompts us with:
-
-```bash
-gff ~/code/lando-ops/guides-example-code/introduction-to-lando/lando-init 
-() └─ ∴ lando init
-? From where should we get your app's codebase? 
-  current working directory 
-  github 
-  pantheon 
-  platformsh 
-❯ remote git repo or archive 
-```
-
-The first question is `? From where should we get your app's codebase?` and it wants to know where the application code lives, i.e. if you are in an application that you want to initialize for use with Lando you would choose `current working directory`.
-
-The next question is `? What recipe do you want to use?`. Recipes are pre-configured start states that Lando knows about. For this course we'll choose the LAMP recipe.
-
-```bash
-? What recipe do you want to use? (Use arrow keys)
-❯ lamp 
-  laravel 
-  lemp 
-  mean 
-  pantheon 
-  platformsh 
-  wordpress 
-(Move up and down to reveal more choices)
-```
-
-Next up Lando prompts us for the webroot of the application: `? Where is your webroot relative to the init destination?` The webroot can be nested or it can be in the same location as the `.lando.yml` file the project root. For this course we'll leave the default `.` for the current working directory.
-
-```bash
-? Where is your webroot relative to the init destination? (.)
-```
-
-Then Lando needs to know a name for our application:
-
-```bash
-? What do you want to call this app? Lando 101
-```
-
-We'll name this app `Lando 101`.
-
-That's it!
-
-We've successfully initialized our first Lando app. We should see a message similar to:
-
-```bash
-? What do you want to call this app? lando-101
-
-   _  __                       _         
-  / |/ /__ _    __  _    _____( )_______ 
- /    / _ \ |/|/ / | |/|/ / -_)// __/ -_)
-/_/|_/\___/__,__/  |__,__/\__/ /_/  \__/ 
-                                         
-  _________  ____  __ _______  _______  _      ______________ __  ___________  ______
- / ___/ __ \/ __ \/ //_/  _/ |/ / ___/ | | /| / /  _/_  __/ // / / __/  _/ _ \/ __/ /
-/ /__/ /_/ / /_/ / ,< _/ //    / (_ /  | |/ |/ // /  / / / _  / / _/_/ // , _/ _//_/ 
-\___/\____/\____/_/|_/___/_/|_/\___/   |__/|__/___/ /_/ /_//_/ /_/ /___/_/|_/___(_)  
-                                                                                     
-Your app has been initialized!
-
-Go to the directory where your app was initialized and run lando start to get rolling.
-Check the LOCATION printed below if you are unsure where to go.
-
-Oh... and here are some vitals:
-
- NAME      lando-101                                                                     
- LOCATION  /home/gff/code/lando-ops/guides-example-code/introduction-to-lando/lando-init 
- RECIPE    lamp                                                                          
- DOCS      https://docs.lando.dev/config/lamp.html   
-```
-
-And the result is that Lando has written a `.lando.yml` configuration file for us in the project root. If you are following along that file should look like this:
-
-```yaml
-name: lando-101
-recipe: lamp
-```
-The `.lando.yml` file gives Lando the information it needs to spin up your application. In this case just two lines! The `name` of the app and the `recipe` to use. We recommend that you commit the `.lando.yml` file to version control so that everyone on your team can have the exact same configuration for development.
-
-You can see the full documentation for [lando init](/basics/init.html).
-<GuideFooter test="" original="" repo=""/>
-<Newsletter />
diff --git a/docs/guides/lando-101/lando-overview.md b/docs/guides/lando-101/lando-overview.md
deleted file mode 100644
index 671a501..0000000
--- a/docs/guides/lando-101/lando-overview.md
+++ /dev/null
@@ -1,48 +0,0 @@
----
-title: Lando Overview
-metaTitle: Lando Overview | Lando
-description: Overview of Lando ecosystem ~ install, init, configure, services, tooling, build steps, and events.
-summary: Overview of Lando ecosystem install, init, configure, services, tooling, build steps, and events.
-date: 2020-07-10T14:38:22.169Z
-original: 
-repo: 
-
-author:
-  name: Team Lando
-  pic: https://gravatar.com/avatar/c335f31e62b453f747f39a84240b3bbd
-  link: https://twitter.com/devwithlando
-
-feed:
-  enable: true
-  author:
-    - name: Team Lando
-      email: alliance@lando.dev
-      link: https://twitter.com/devwithlando
-  contributor:
-    - name: Team Lando
-      email: alliance@lando.dev
-      link: https://twitter.com/devwithlando
----
-
-# Lando Overview
-
-<GuideHeader test="https://github.com/lando/lando/blob/master/examples/lando-101/README.md" name="Team Lando" pic="https://gravatar.com/avatar/c335f31e62b453f747f39a84240b3bbd" link="https://twitter.com/devwithlando" />
-<YouTube url="" />
-
-Lando can isolate all your dev needs on a per app basis. This course will walk you through some examples of what can be accomplished with Lando development environments. If you have not installed Lando yet head over to [installing](/basics/installation.html) first.
-
-Here is the outline of content the Lando 101 course will cover:
-
-* [Init](/guides/lando-101/lando-init.html)
-* [Start](/guides/lando-101/lando-start.html)
-* [Configure](/guides/lando-101/lando-config.html)
-* [Add a Service](/guides/lando-101/lando-services.html)
-* [Add a Proxy URL](/guides/lando-101/lando-proxy.html)
-* [Add Tooling](/guides/lando-101/lando-tooling.html)
-* Add a Build step
-* Add an Event
-
-Throughout the Lando 101 course you'll see a number of hyperlinks in the text. These usually link to the full documentation or deep dives on a topic. We'd recommend that for your first read through that you simply ignore those links and go back to them after to deepen your understanding of Lando once you have the basics down.
-
-<GuideFooter test="" original="" repo=""/>
-<Newsletter />
diff --git a/docs/guides/lando-101/lando-proxy.md b/docs/guides/lando-101/lando-proxy.md
deleted file mode 100644
index c521224..0000000
--- a/docs/guides/lando-101/lando-proxy.md
+++ /dev/null
@@ -1,69 +0,0 @@
----
-title: Lando Proxy
-metaTitle: Lando Proxy | Lando
-description: An example of using the Lando proxy key. 
-summary: An example of adding the a proxy URL to a Lando service.
-date: 2020-09-04T14:38:22.169Z
-original: 
-repo: 
-
-author:
-  name: Team Lando
-  pic: https://gravatar.com/avatar/c335f31e62b453f747f39a84240b3bbd
-  link: https://twitter.com/devwithlando
-
-feed:
-  enable: true
-  author:
-    - name: Team Lando
-      email: alliance@lando.dev
-      link: https://twitter.com/devwithlando
-  contributor:
-    - name: Team Lando
-      email: alliance@lando.dev
-      link: https://twitter.com/devwithlando
----
-
-# Lando Proxy
-
-<GuideHeader test="https://github.com/lando/lando/blob/master/examples/lando-101/README.md" name="Team Lando" pic="https://gravatar.com/avatar/c335f31e62b453f747f39a84240b3bbd" link="https://twitter.com/devwithlando" />
-<YouTube url="" />
-
-Some `services` like `mailhog` provide an admin interface via a browser. In such cases it is convenient to assign a URL to the service container. We do so via the `proxy` key in our `.lando.yml` file.
-
-Let's add a URL to our `mailhog` service so we can access the MailHog dashboard. Open up your Lando 101 `.lando.yml` file and add a proxy section like so:
-
-```yaml
-name: lando-101
-recipe: lamp
-config:
-  php: 7.4
-services:
-  mailhog:
-    type: mailhog:v1.0.0
-    portforward: true
-    hogfrom:
-      - appserver
-proxy:
-  mailhog:
-    - mail.lando-101.lndo.site
-```
-
-The new config being the `proxy` key which takes a `service` and the `service` gets an array of URLs in this case `- mail.lando-101.lndo.site`. You can add a URL to any service you like.
-
-::: warning Rebuild Required
-After adding a `proxy` make sure to `rebuild` the Lando 101 app.
-
-```bash
-lando rebuild -y
-```
-:::
-
-After rebuilding we can now access the new `mail.lando-101.lndo.site` URL to view the MailHog dashboard.
-
-<img src="/images/lando-101/mh.jpg" />
-
-Using the `proxy` key in our `.lando.yml` file we can add a URL to any `service` in a Lando app! If you need to dig deeper you can find the read the [full proxy documentatioin](/config/proxy.html).
-
-<GuideFooter test="" original="" repo=""/>
-<Newsletter />
diff --git a/docs/guides/lando-101/lando-services.md b/docs/guides/lando-101/lando-services.md
deleted file mode 100644
index 6749acd..0000000
--- a/docs/guides/lando-101/lando-services.md
+++ /dev/null
@@ -1,75 +0,0 @@
----
-title: Lando Services
-metaTitle: Lando Services | Lando
-description: An example adding the mailhog service to a Lando recipe.
-summary: An example of adding the mailhog service to a Lando recipe using the services key.
-date: 2020-08-28T14:38:22.169Z
-original: 
-repo: 
-
-author:
-  name: Team Lando
-  pic: https://gravatar.com/avatar/c335f31e62b453f747f39a84240b3bbd
-  link: https://twitter.com/devwithlando
-
-feed:
-  enable: true
-  author:
-    - name: Team Lando
-      email: alliance@lando.dev
-      link: https://twitter.com/devwithlando
-  contributor:
-    - name: Team Lando
-      email: alliance@lando.dev
-      link: https://twitter.com/devwithlando
----
-
-# Lando Services
-
-<GuideHeader test="https://github.com/lando/lando/blob/master/examples/lando-101/README.md" name="Team Lando" pic="https://gravatar.com/avatar/c335f31e62b453f747f39a84240b3bbd" link="https://twitter.com/devwithlando" />
-<YouTube url="" />
-
-Another way you can extend Lando recipes is by adding additional [services](/config/services.html). If you need to add a second database to your app, a node container for theming, or any number of use cases you can handle them by adding the appropriate service to your app. In this example we'll add a [mailhog](/config/mailhog.html) service to our Lando 101 app!
-
-Open up your `.lando.yml` configuration file in your favorite text editor. If you are following along with Lando 101 that file currently looks like this:
-
-```yaml
-name: lando-101
-recipe: lamp
-config:
-  php: 7.4
-```
-
-We'll now add the `services` key to our `.lando.yml` file and add in our `mailhog` service:
-
-```yaml
-name: lando-101
-recipe: lamp
-config:
-  php: 7.4
-services:
-  mailhog:
-    type: mailhog:v1.0.0
-    portforward: true
-    hogfrom:
-      - appserver
-```
-
-The new configuration for our `mailhog` service is under the `services` key in our `.lando.yml` file. The service name can be anything. We've named it `mailhog` after the service it provides, but you can name it anything you like. The `type` tells lando what `service` to use (what image to initially fetch and subsequently use). Then the `portforward` key will automatically set a port for the new service, and finally the `hogfrom` key is specific to the the `mailhog` service and tells mailhog where it should be grabbing the mail from for the Lando 101 app that is the appserver.
-
-After adding or changing a `service` in our app a rebuild is required.
-
-```bash
-lando rebuild -y
-```
-
-After rebuilding the Lando 101 app the new `mailhog` service will be available to our app! You can verify that by running: `docker ps` and you should see a line similar to this:
-
-```bash
-00daf795ccd0        mailhog/mailhog:v1.0.0               "/lando-entrypoint.s…"   25 seconds ago      Up 24 seconds       8025/tcp, 127.0.0.1:32780->80/tcp, 127.0.0.1:32778->1025/tcp              lando101_mailhog_1
-```
-
-You can see that our `lando101_mailhog_1` container is up and running and ready for us to use! Some services, like the `mailhog` service, will need to have a URL exposed in order to make use of them. In the next section we'll demonstrate how to add a proxy URL for the `mailhog` service.
-
-<GuideFooter test="" original="" repo=""/>
-<Newsletter />
diff --git a/docs/guides/lando-101/lando-start.md b/docs/guides/lando-101/lando-start.md
deleted file mode 100644
index 0f0a1ae..0000000
--- a/docs/guides/lando-101/lando-start.md
+++ /dev/null
@@ -1,72 +0,0 @@
----
-title: Lando Start
-metaTitle: Lando Start | Lando
-description: Start a Lando app and some vocabulary to help us talk about Lando.
-summary: Lando start command and some vocabulary to help us understand the Lando ecosystem.
-date: 2020-07-27T14:38:22.169Z
-original: 
-repo: 
-
-author:
-  name: Team Lando
-  pic: https://gravatar.com/avatar/c335f31e62b453f747f39a84240b3bbd
-  link: https://twitter.com/devwithlando
-
-feed:
-  enable: true
-  author:
-    - name: Team Lando
-      email: alliance@lando.dev
-      link: https://twitter.com/devwithlando
-  contributor:
-    - name: Team Lando
-      email: alliance@lando.dev
-      link: https://twitter.com/devwithlando
----
-
-# Lando Start
-
-<GuideHeader test="https://github.com/lando/lando/blob/master/examples/lando-101/README.md" name="Team Lando" pic="https://gravatar.com/avatar/c335f31e62b453f747f39a84240b3bbd" link="https://twitter.com/devwithlando" />
-<YouTube url="" />
-
-This lesson is primarily about vocabulary to help us understand the Lando ecosystem. A `recipe` in Lando is a pre-configured start state for an application. Lando comes [with more than 12 recipes](/config/recipes.html) out of the box. In the Lando 101 course we are using the [LAMP](/config/lamp.html#getting-started) recipe. This tells Lando that we'll need an application container with Apache and PHP and a MySQL container.
-
-So, if we `lando start` our `Lando 101` app we'll see those corresponding containers. Here is some of the output from `lando start`:
-
-```bash
-Scanning to determine which services are ready... Please standby...
-
-   ___                      __        __        __     __        ______
-  / _ )___  ___  __ _  ___ / /  ___ _/ /_____ _/ /__ _/ /_____ _/ / / /
- / _  / _ \/ _ \/  ' \(_-</ _ \/ _ `/  '_/ _ `/ / _ `/  '_/ _ `/_/_/_/ 
-/____/\___/\___/_/_/_/___/_//_/\_,_/_/\_\\_,_/_/\_,_/_/\_\\_,_(_|_|_)  
-                                                                       
-
-Your app has started up correctly.
-Here are some vitals:
-
- NAME            lando-101                                                                     
- LOCATION        /home/gff/code/lando-ops/guides-example-code/introduction-to-lando/lando-init 
- SERVICES        appserver, database                                                           
- APPSERVER URLS  https://localhost:32952                                                       
-                 http://localhost:32953                                                        
-                 http://lando-101.lndo.site/                                                   
-                 https://lando-101.lndo.site/                                                  
-```
-
-And if you run the docker command: `docker ps` you can see the containers for the Lando 101 app:
-
-```bash
-gff ~/code/lando-ops/guides-example-code/introduction-to-lando/lando-init 
-() └─ ∴ docker ps
-CONTAINER ID        IMAGE                                COMMAND                  CREATED             STATUS              PORTS                                                                     NAMES
-c92d36534d66        devwithlando/php:7.3-apache-2        "/lando-entrypoint.s…"   25 seconds ago      Up 23 seconds       127.0.0.1:32953->80/tcp, 127.0.0.1:32952->443/tcp                         lando101_appserver_1
-a5d7060a15be        bitnami/mysql:5.7.29-debian-10-r51   "/lando-entrypoint.s…"   25 seconds ago      Up 23 seconds       127.0.0.1:32951->3306/tcp                                                 lando101_database_1
-7f64e8add1fd        traefik:2.2.0                        "/lando-entrypoint.s…"   30 hours ago        Up 25 seconds       127.0.0.1:80->80/tcp, 127.0.0.1:443->443/tcp, 127.0.0.1:32950->8080/tcp   landoproxyhyperion5000gandalfedition_proxy_1
-
-```
-
-So you can see that Lando has started up `lando101_appserver_1`, `lando101_database_1`, and `landoproxyhyperion5000gandalfedition_proxy_1` containers. Behind the scenes Lando is managing the containers, persistent storage, and the networking for the containers to communication with each other. We don't need to worry about that Lando handles it for us. If later we want to take a deep dive you can see how Lando leverages docker-compose to get that all done for us, but for now just know Lando takes care of the right configurations for the recipe we choose.
-
-<GuideFooter test="" original="" repo=""/>
-<Newsletter />
diff --git a/docs/guides/lando-101/lando-tooling.md b/docs/guides/lando-101/lando-tooling.md
deleted file mode 100644
index 4a09042..0000000
--- a/docs/guides/lando-101/lando-tooling.md
+++ /dev/null
@@ -1,77 +0,0 @@
----
-title: Lando Tooling
-metaTitle: Lando Proxy | Lando
-description: An example of adding tooling to a Lando app.
-summary: An example of adding tooling to your Lando app. 
-date: 2020-09-05T14:38:22.169Z
-original: 
-repo: 
-
-author:
-  name: Team Lando
-  pic: https://gravatar.com/avatar/c335f31e62b453f747f39a84240b3bbd
-  link: https://twitter.com/devwithlando
-
-feed:
-  enable: true
-  author:
-    - name: Team Lando
-      email: alliance@lando.dev
-      link: https://twitter.com/devwithlando
-  contributor:
-    - name: Team Lando
-      email: alliance@lando.dev
-      link: https://twitter.com/devwithlando
----
-
-# Lando Tooling
-
-<GuideHeader test="https://github.com/lando/lando/blob/master/examples/lando-101/README.md" name="Team Lando" pic="https://gravatar.com/avatar/c335f31e62b453f747f39a84240b3bbd" link="https://twitter.com/devwithlando" />
-<YouTube url="" />
-
-Lando provides context specific tooling for the provided recipes, for example, the `lando-101` app is using the `lamp` recipe and out of the box provides us with tooling commands for `php` cli, `composer`, and a `mysql` shell among others. You can see the available commands for any given Lando app by typing `lando` at your command prompt.
-
-Sometimes we might need or want to add our own tooling to a Lando app to simplify workflows, use in CI, and reduce documentation. Let's add a `phpcs` tooling command to our Lando 101 app.
-
-First lets use the Lando provided `composer` tooling to add `phpcs` to our Lando 101 app:
-
-```bash
-lando composer require squizlabs/php_codesniffer
-```
-
-That will place the `phpcs` binary in `/app/vendor/bin/phpcs` and we'll use that path to expose the tooling to our Lando 101 app.
-
-Open up your `.lando.yml` config file in your favorite text editor:
-
-```yaml
-name: lando-101
-recipe: lamp
-config:
-  php: 7.4
-services:
-  mailhog:
-    type: mailhog:v1.0.0
-    portforward: true
-    hogfrom:
-      - appserver
-proxy:
-  mailhog:
-    - mail.lando-101.lndo.site
-tooling:
-  phpcs:
-    service: appserver
-    cmd: /app/vendor/bin/phpcs
-```
-
-The new part of our config is the `tooling` key under which we have nested the command we want to expose, `phpcs` in this case. Told Lando which service to run the tooling command against with `service: appserver`. Provided the `cmd: /app/vendor/bin/phpcs` to tell Lando what command to run under the hood.
-
-Now all the developers on our team for the Lando 101 app can code sniff their code to provide uniform standards across the project. For example, if you want to check the syntax of the `index.php` file; you do so like this:
-
-```bash
-lando phpcs index.php
-```
-
-Adding the `phpcs` command is simple, but just one example of the types of tooling you can add to your apps. To take a deep dive and learn more about Lando tooling read the [tooling docs page](/config/tooling.html).
-
-<GuideFooter test="" original="" repo=""/>
-<Newsletter />
diff --git a/docs/guides/lando-info.md b/docs/guides/lando-info.md
deleted file mode 100644
index a911ea8..0000000
--- a/docs/guides/lando-info.md
+++ /dev/null
@@ -1,45 +0,0 @@
----
-description: Learn how to use Lando's default environment variables inside you application.
-date: 2019-11-05
----
-
-# Using $LANDO_INFO
-
-<GuideHeader />
-
-Lando will inject an environment variable called `$LANDO_INFO` into each service. This is a `JSON` string representation of the `lando info` command and you can use it to see valuable information about other services such as service hostnames and database connection information and credentials.
-
-This is helpful if you want to set application configuration in a way that is portable and dynamic between many lando apps.
-
-::: warning Use `internal_connection` information!
-For services with both `external_connection` and `internal_connection` information. ALWAYS use the `internal_connection` information inside of your application.
-:::
-
-Here are some examples of code on how to parse `$LANDO_INFO`.
-
-## Using PHP
-
-```php
-$info = json_decode(getenv('LANDO_INFO'), TRUE);
-print_r($info);
-```
-
-## Using Javascript/NodeJS
-
-```js
-'use strict';
-
-var info = JSON.parse(process.env.LANDO_INFO);
-
-console.log(info);
-```
-
-## Using Other
-
-More examples coming soon but in the meantime consult the documentation for your language on how to:
-
-* Grab an environment variable
-* Decode a JSON string to an object
-
-<GuideFooter />
-<Newsletter />
diff --git a/docs/guides/lando-phpstorm.md b/docs/guides/lando-phpstorm.md
deleted file mode 100644
index 4a75374..0000000
--- a/docs/guides/lando-phpstorm.md
+++ /dev/null
@@ -1,43 +0,0 @@
----
-description: Learn how to configure xdebug in Lando using PhpStorm.
-date: 2019-11-05
----
-
-# Lando + PhpStorm + Xdebug
-
-<GuideHeader />
-<YouTube url="https://www.youtube.com/embed/sHNJxx0L9r0" />
-
-[PhpStorm](https://www.jetbrains.com/phpstorm/) is a popular code IDE for PHP
-and Drupal development. This video tutorial shows you how to set up PhpStorm with Xdebug.
-
-If you’ve a local php installation (for example php 7.1 installed with homebrew on macOS) that listens on port 9000 you may need to change the containers php.ini port specification to another port (i.e. `xdebug.remote_port=9001`) and tell phpstorm to listen on that port. See also [Debugging Drupal 8 with PHPstorm and Lando on your Mac](https://www.isovera.com/2020/11/24/debugging-drupal-8-with-phpstorm-and-lando-on-your-mac/).
-
-### PHP 7.3 and later
-With PHP 7.3, the setting `xdebug.remote_port` has been deprecated, and the setting `xdebug.client_port` should be used instead.
-Also the default xdebug port changed from `9000` to `9003`.
-
-https://xdebug.org/docs/upgrade_guide#changed-xdebug.remote_port
-
-## Debugging Drush Commands
-
-By default our Drupal recipes come with Drush out of the box. In order to debug any Drush command using Xdebug using
-PhpStorm or a similar IDE, you will need to set an additional environment variable `PHP_IDE_CONFIG` and configure the
-path mapping in your IDE accordingly.
-
-```yaml
-services:
-  appserver:
-    overrides:
-      environment:
-        # Support debugging Drush with XDEBUG.
-        PHP_IDE_CONFIG: "serverName=appserver"
-```
-
-You are free to assign any name to "serverName" as long as it matches the server you define in the IDE settings.
-In the example above we set the variable to `appserver` and created a path mapping for the server accordingly:
-
-![screenshot](/images/drush-xdebug-phpstorm.png)
-
-<GuideFooter />
-<Newsletter />
diff --git a/docs/guides/lando-with-vscode.md b/docs/guides/lando-with-vscode.md
deleted file mode 100644
index 34f6f4a..0000000
--- a/docs/guides/lando-with-vscode.md
+++ /dev/null
@@ -1,277 +0,0 @@
----
-description: Learn how to configure xdebug in Lando using VSCode.
-date: 2019-11-05
----
-
-# Using Lando with VSCode
-
-<GuideHeader />
-
-[Visual Studio Code](https://github.com/Microsoft/vscode/) is a great open source editor for programming. Debugging PHP applications with it can be easy too.
-
-This is a basic setup to help you in this task.
-
-[[toc]]
-
-## Getting Started
-
-Enable Xdebug by adding some lines to your Lando recipe.
-
-**Lando beta versions and rc.1** need `conf:` at file root as follow:
-
-```yaml
-name: mywebsite
-recipe: drupal8
-config:
-  webroot: docroot
-  xdebug: true
-  conf:
-    php: .vscode/php.ini
-```
-
-**Lando rc.2+** needs `config:` under `services:` as follow:
-
-```yaml
-name: mywebsite
-recipe: drupal8
-services:
-  appserver:
-    webroot: web
-    xdebug: true
-    config:
-      php: .vscode/php.ini
-```
-
-**Tell Lando to use additional PHP settings**
-
-Create the custom `php.ini` file to add XDebug settings to PHP.
-
-```bash
-touch .vscode/php.ini
-code .vscode/php.ini
-```
-
-The location of this file is arbitrary.
-
-We placed it inside `.vscode/` folder simply because we find it convenient.
-
-Add your custom XDebug settings, which will vary slightly depending on which version of PHP and xdebug you're using.
-
-**PHP 7.2+ uses xdebug 3** and needs `config:` under `services:` as follow:
-
-```ini
-[PHP]
-
-; Xdebug
-xdebug.max_nesting_level = 256
-xdebug.show_exception_trace = 0
-xdebug.collect_params = 0
-; Extra custom Xdebug setting for debug to work in VSCode.
-xdebug.mode = debug
-xdebug.client_host = ${LANDO_HOST_IP}
-xdebug.client_port = 9003
-xdebug.start_with_request = trigger
-; xdebug.remote_connect_back = 1
-xdebug.log = /tmp/xdebug.log
-```
-
-**PHP 7.1 and earlier uses xdebug 2** and needs `config:` under `services:` as follow:
-
-```ini
-[PHP]
-
-; Xdebug
-xdebug.max_nesting_level = 256
-xdebug.show_exception_trace = 0
-xdebug.collect_params = 0
-; Extra custom Xdebug setting for debug to work in VSCode.
-xdebug.remote_enable = 1
-xdebug.remote_autostart = 1
-xdebug.remote_host = ${LANDO_HOST_IP}
-; xdebug.remote_connect_back = 1
-xdebug.remote_log = /tmp/xdebug.log
-```
-
-Rebuild your environment.
-
-```bash
-lando rebuild -y
-```
-
-Finally, add a custom `launch.json` file in VSCode in order to map paths so that XDebug works correctly.
-
-```bash
-touch .vscode/launch.json
-code .vscode/launch.json
-```
-
-```json
-{
-  "version": "0.2.0",
-  "configurations": [
-    {
-      "name": "Listen for XDebug",
-      "type": "php",
-      "request": "launch",
-      "port": 9003,
-      "log": false,
-      "pathMappings": {
-        "/app/": "${workspaceFolder}/",
-      }
-    }
-  ]
-}
-```
-
-**Note: PHP 7.1 and earlier uses xdebug 2** which uses port 9000, so change the port number above accordinly.
-
-
-Done!
-
-You can now click start debugging (type F5 or click on the icon in the left sidebar).
-
-## Advanced Setup
-
-Optionally for better performance you can easily toggle Xdebug on and off with some custom tooling commands.
-
-If you're using Apache, add this to your `.lando.yml`:
-
-```yaml
-services:
-  appserver:
-    overrides:
-      environment:
-        XDEBUG_MODE:
-tooling:
-  xdebug-on:
-    service: appserver
-    description: Enable xdebug for Apache.
-    cmd: docker-php-ext-enable xdebug && /etc/init.d/apache2 reload && echo "Enabling xdebug"
-    user: root
-
-  xdebug-off:
-    service: appserver
-    description: Disable xdebug for Apache.
-    cmd: rm /usr/local/etc/php/conf.d/docker-php-ext-xdebug.ini && /etc/init.d/apache2 reload && echo "Disabling xdebug"
-    user: root
-```
-
-If you're using Nginx, add this to your `.lando.yml`:
-
-```yaml
-services:
-  appserver:
-    overrides:
-      environment:
-        XDEBUG_MODE:
-tooling:
-  xdebug-on:
-    service: appserver
-    description: Enable xdebug for nginx.
-    cmd: docker-php-ext-enable xdebug && pkill -o -USR2 php-fpm && echo "Enabling xdebug"
-    user: root
-  xdebug-off:
-    service: appserver
-    description: CUSTOM Disable xdebug for nginx.
-    cmd: rm /usr/local/etc/php/conf.d/docker-php-ext-xdebug.ini && pkill -o -USR2 php-fpm && echo "Disabling xdebug"
-    user: root
-```
-
-Now you can turn Xdebug on or off with `lando xdebug-on` and `lando xdebug-off`. If you want Xdebug off by default, set `xdebug:false` in your appserver config:
-
-```yaml
-name: mywebsite
-recipe: drupal8
-services:
-  appserver:
-    webroot: web
-    xdebug: false
-    config:
-      php: .vscode/php.ini
-```
-
-## Debugging PhpUnit
-
-Debugging PhpUnit tests in VSCode requires a little more setup, but Lando helps to make it easier.
-
-First, you need to have VSCode listen for debugging on 2 separate ports, because PhpUnit runs in one process and the tests themselves in another, and VSCode's Xdebug extension currently struggles with this. You accomplish this by have a launch.json that looks like this:
-
-```json
-{
-  "version": "0.2.0",
-  "configurations": [
-    {
-      "name": "Listen for XDebug",
-      "type": "php",
-      "request": "launch",
-      "port": 9003,
-      "log": true,
-      "pathMappings": {
-        "/app/": "${workspaceFolder}/",
-      }
-    },
-    {
-      "name": "PhpUnit dummy",
-      "type": "php",
-      "request": "launch",
-      "port": 9001,
-    }
-  ],
-  "compounds": [
-    {
-        "name": "PhpUnit",
-        "configurations": ["Listen for XDebug", "PhpUnit dummy"]
-    }
-       ]
-}
-```
-
-Next add some custom tooling to your .lando.yml file, that provides a command to run PhpUnit in a way points the main PhpUnit process to the PhpUnit dummy debugger we just added. (The syntax here assumes a project-specific installation of PhpUnit, not a global one).
-
-```yml
-tooling:
-  phpunitdebug:
-    service: appserver
-    cmd: php -d xdebug.remote_port=9003 vendor/bin/phpunit
-```
-
-**Note: PHP 7.1 and earlier uses xdebug 2** which uses port 9000, so change the port number above accordinly.
-
-Now to run debug a PhpUnit test, do the following:
-
-1. Select the compound "PhpUnit" as your debugger in VSCode's UI, and start it.
-2. Make sure you untick "Everything" in the breakpoints section of the UI, or it will break every time PhpUnit throws an exception, even if it's properly caught by PhpUnit.
-3. Add a breakpoint in your code that is being tested.
-4. On your command line run PhpUnit with something like `lando phpunitdebug --filter=testMyTestMethodName` (this example is of running a single test method, actually you can add any phpunit options you like at the end).
-
-## Known issues
-
-**Xdebug session doesn't start**
-
-If Xdebug session doesn't start, dig into the log file inside the application.
-
-Enter your lando app `lando ssh` and open the debug file (`/tmp/xdebug.log`). Path to the debug file is configured in your custom `php.ini`.
-
-Now open your app in a browser and see what's being logged.
-
-```bash
-lando ssh
-tail -f /tmp/xdebug.log
-# Open your browser and refresh the app
-```
-
-**Xdebug says "timeout trying to connect to XX.XX.XX:9003**
-
-Double-check your host machine allow connection on its port 9003.
-
-This is how you can open a specific port on a Debian/Ubuntu:
-
-`sudo iptables -A INPUT -p tcp -d 0/0 -s 0/0 --dport 9003 -j ACCEPT`
-
-## Read More
-
-*   [Original Gist with settings for XDebug in VSCode](https://gist.github.com/MatthieuScarset/0c3860def9ff1f0b84e32f618c740655)
-*   [PHP programming in VSCode](https://code.visualstudio.com/docs/languages/php)
-
-<GuideFooter />
-<Newsletter />
diff --git a/docs/guides/macos-pantheon-no-proxy.md b/docs/guides/macos-pantheon-no-proxy.md
deleted file mode 100644
index 1d5580f..0000000
--- a/docs/guides/macos-pantheon-no-proxy.md
+++ /dev/null
@@ -1,81 +0,0 @@
----
-date: 2019-11-05
----
-
-# How to set up a Pantheon application without a proxy on macOS 10.12+
-
-<GuideHeader />
-
-This guide explains how to use a pantheon [lando](https://github.com/lando/lando) application without the proxy server on your local machine. Instead of using a proxy server, you will use `dnsmasq` and `pfctl` to port forward your lando application's webserver ports to 80 and 443.
-
-> **Note:** you will have to perform some manual interactions for each lando application you create. See the instructions below.
-
-1. First, install [homebrew](https://brew.sh)
-2. Then, install and setup dnsmasq with homebrew:
-
-    ```
-    brew install dnsmasq
-    echo 'address=/.lndo.site/127.0.0.1' > $(brew --prefix)/etc/dnsmasq.conf
-    echo 'listen-address=127.0.0.1' >> $(brew --prefix)/etc/dnsmasq.conf
-    echo 'port=35353' >> $(brew --prefix)/etc/dnsmasq.conf
-    brew services start dnsmasq
-    ```
-
-3. While dnsmasq is running, configure macOS to use your local host for DNS queries ending in `.lndo.site`
-
-    ```
-    sudo mkdir -v /etc/resolver
-    sudo bash -c 'echo "nameserver 127.0.0.1" > /etc/resolver/dev'
-    sudo bash -c 'echo "port 35353" >> /etc/resolver/dev'
-    ```
-
-4. Disable lando's proxy in your local config file.
-
-    ```
-    touch ~/.lando/config.yml
-    echo "proxy: OFF" >> ~/.lando/config.yml
-    ```
-
-5. [Set up your app with lando](https://docs.devwithlando.io/tutorials/basics.html). Make sure your application is stopped before proceeding.
-6. Start your application using `lando start`.
-7. In terminal, run the following command all at once:
-
-    ```
-    sudo bash -c 'export TAB=$'"'"'\t'"'"'
-    cat > /Library/LaunchDaemons/co.jakebellacera.httpdfwd.plist <<EOF
-    <?xml version="1.0" encoding="UTF-8"?>
-    <!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
-    <plist version="1.0">
-    <dict>
-    ${TAB}<key>Label</key>
-    ${TAB}<string>co.lando.httpdfwd</string>
-    ${TAB}<key>ProgramArguments</key>
-    ${TAB}<array>
-    ${TAB}${TAB}<string>sh</string>
-    ${TAB}${TAB}<string>-c</string>
-    ${TAB}${TAB}<string>echo "rdr pass proto tcp from any to any port {80,32787} -> 127.0.0.1 port 32787" | pfctl -a "com.apple/260.HttpFwdFirewall" -Ef - &amp;&amp; echo "rdr pass proto tcp from any to any port {443,32788} -> 127.0.0.1 port 32788" | pfctl -a "com.apple/261.HttpFwdFirewall" -Ef - &amp;&amp; sysctl -w net.inet.ip.forwarding=1</string>
-    ${TAB}</array>
-    ${TAB}<key>RunAtLoad</key>
-    ${TAB}<true/>
-    ${TAB}<key>UserName</key>
-    ${TAB}<string>root</string>
-    </dict>
-    </plist>
-    EOF'
-    sudo launchctl load -Fw /Library/LaunchDaemons/co.lando.httpdfwd.plist
-    ```
-
-    > **NOTE:** this assumes your pantheon app's edge servers are assigned to the following ports: 32787 (http) and 32788 (https). In testing, these seemed to be the default ports that are assigned to pantheon applications. If you see different ports, or are not using a pantheon application configuration, then you may need to adjust the ports in the code snippet above.
-
-8. In your /etc/hosts file, add an entry for your application's host name at localhost.
-
-    ```
-    127.0.0.1 example.lndo.site
-    ```
-
-    > **NOTE:** replace "example" in the hostname with the name of your application.
-
-9. Finally, you should be able to access your application by the hostname you added to your /etc/hosts file in the step above without any ports. If you are having trouble, try turning off and on your wifi or reboot your machine so that your /etc/resolver settings are applied successfully.
-
-<GuideFooter />
-<Newsletter />
diff --git a/docs/guides/offline-dev.md b/docs/guides/offline-dev.md
deleted file mode 100644
index 7ced396..0000000
--- a/docs/guides/offline-dev.md
+++ /dev/null
@@ -1,75 +0,0 @@
----
-description: Learn how to use Lando for offline local development.
-date: 2019-11-05
----
-
-# Developing offline
-
-<GuideHeader />
-
-Out of the box Lando uses an actual on-the-internet wildcard domain at `*.lndo.site` to route your domain names back to your localhost to provide convenient proxying. This method is minimally invasive and doesn't require Lando to alter your machine's DNS routing. This has the downside of requiring an internet connection to access your sites.
-
-However, you may want the freedom of hacking away on your site while scaling Everest or just to simply route your projects to a different wildcard domain, like `*.local.dev`, `*.seriously.hanshotfirst` or `*.my.test`. Note that we **DO NOT** recommend you use a _true_ top-level domain such as `*.test`. You can read more about why in our [security](./../config/security.md) documentation.
-
-To enable offline custom domain goodness, we'll use DNSMasq to route traffic to our local system and add a single config line to our global Lando config to direct lando to use that domain for our sites.
-
-That said and before we get started we **highly recommend** you consult both the [proxy](./../config/proxy.md) and [security](./../config/security.md) documentation to get a good handle on what is possible (and not possible) here.
-
-## Mac Specific Instructions
-
-1. Ensure you've installed [Homebrew](https://brew.sh/).
-2. Install DNSMasq: `brew install dnsmasq`
-3. Follow the instructions in the output of `brew info dnsmasq`
-4. Add the following line to your `/usr/local/etc/dnsmasq.conf` file:
-```
-address=/local.host/127.0.0.1
-```
-Sub in your favorite domain for 'local.host' here if you want to use something more flashy.
-
-5. Restart DNSMasq: `brew services restart dnsmasq`
-6. For macOS to resolve requests from *.local.host to localhost we need to add a resolver:
-```
-sudo mkdir -p /etc/resolver
-sudo nano /etc/resolver/local.host
-```
-7. Add the following line to the local.host file resolver in /etc/resolver/.
-```
-nameserver 127.0.0.1
-```
-8. Reboot macOS to enable the new resolver.
-9. Flush your DNS, just to be sure that your browsers use the new dns
-directives.
-```
-sudo dscacheutil -flushcache
-sudo killall -HUP mDNSResponder
-```
-10. Open your `~/.lando/config.yml` file and add the following line:
-```yaml
-domain: local.host
-```
-Again, allow your creativity to flourish and use whatever domain makes you smile.
-
-11. Power Lando down with `lando poweroff`
-12. Start up your favorite Lando app to test it out with `lando start` from within your app's root directory. You should see something like:
-
-```bash
-BOOMSHAKALAKA!!!
-
-Your app has started up correctly.
-Here are some vitals:
-
- NAME      bestappever
- LOCATION  /Users/McFly/timemachines/bestappever
- SERVICES  appserver, nginx, database, cache, node
-
- APPSERVER URLS https://localhost:32791
-                http://localhost:32792
-                http://bestappever.local.host
-                https://bestappever.local.host
-```
-13. Load it up in the browser and confirm everything is happy and working.
-
-Enjoy your signature domain while you hack away in complete wifi-less splendor.
-
-<GuideFooter />
-<Newsletter />
diff --git a/docs/guides/overriding-a-service-version.md b/docs/guides/overriding-a-service-version.md
deleted file mode 100644
index 915c129..0000000
--- a/docs/guides/overriding-a-service-version.md
+++ /dev/null
@@ -1,74 +0,0 @@
----
-title: Overriding a Service Version or Image
-metaTitle: Overriding a Service Version | Lando
-description: Modify the underlying Docker images used by your Lando services so that you can custom tailor the container environment for your apps!
-summary: Modify the underling Docker images used by your Lando services so that you can custom tailor the container environment for your apps!
-date: 2020-03-19T19:59:04.806Z
-original:
-repo:
-
-author:
-  name: Dustin LeBlanc
-  pic: https://www.gravatar.com/avatar/e61caccbbfd817bc8b52c0395ba888a6
-  link: https://twitter.com/DustinLeblanc
-
-feed:
-  enable: true
-  author:
-    - name: Dustin LeBlanc
-      email: alliance@lando.dev
-      link: https://twitter.com/DustinLeblanc
-  contributor:
-    - name: Dustin LeBlanc
-      email: alliance@lando.dev
-      link: https://twitter.com/DustinLeblanc
----
-
-# Overriding a Service Version
-
-<GuideHeader test="" name="Dustin LeBlanc" pic="https://www.gravatar.com/avatar/e61caccbbfd817bc8b52c0395ba888a6" link="https://twitter.com/DustinLeblanc" />
-
-The Docker images Lando uses for services are well optimized for local development, but occasionally you need to
-override those images with some of your own secret sauce. Lando makes this easy to do through the services `overrides`
-key:
-
-```yaml
-name: projectofdoom
-recipe: drupal8
-config:
-  via: nginx
-  webroot: web
-  php: 7.3
-  database: mariadb
-  xdebug: true
-env_file:
-  - .env
-services:
-  database:
-    overrides:
-      image: bitnami/mariadb:10.3.27
-```
-
-In the example above, we're overriding the image to use an explicit release of Bitnami's MariaDB container to bypass a
-breaking change released on Bitnami's 10.3 tag (Lando's default version).
-
-You can also use this to load your own custom images:
-
-```yaml
-name: projectofdoom
-recipe: drupal8
-config:
-  via: nginx
-  webroot: web
-  php: 7.3
-  database: mariadb
-  xdebug: true
-env_file:
-  - .env
-services:
-  appserver:
-    overrides:
-      image: myamazingorg/fancyappserver:latest
-```
-<GuideFooter test="" original="" repo=""/>
-<Newsletter />
diff --git a/docs/guides/phpmyadmin-themes.md b/docs/guides/phpmyadmin-themes.md
deleted file mode 100644
index e778e5e..0000000
--- a/docs/guides/phpmyadmin-themes.md
+++ /dev/null
@@ -1,101 +0,0 @@
----
-title: Using a custom PhpMyAdmin 4.x theme in Lando
-description: Learn how to load a custom PhpMyAdmin 4.x theme into Lando
-summary: Learn how to load a custom PhpMyAdmin 4.x theme into Lando
-date: 2020-03-30T19:23:00.720Z
-original:
-repo: https://github.com/lando/cli/tree/main/examples/pma
-
-author:
-  name: Jace Bennest
-  pic: https://avatars0.githubusercontent.com/u/6412919?s=460&u=b96d856896743523cec75bad1d9aec42a7f8a25e&v=4
-  link: https://twitter.com/thejacer87
-
-feed:
-  enable: true
-  author:
-    - name: Jace Bennest
-      email: alliance@lando.dev
-      link: https://twitter.com/thejacer87
-  contributor:
-    - name: Jace Bennest
-      email: alliance@lando.dev
-      link: https://twitter.com/thejacer87
----
-
-# Add Themes to phpMyAdmin 4.x
-
-<GuideHeader name="Jace Bennest" pic="https://avatars0.githubusercontent.com/u/6412919?s=460&u=b96d856896743523cec75bad1d9aec42a7f8a25e&v=4" link="https://twitter.com/thejacer87" test="https://github.com/lando/cli/tree/main/examples/pma" />
-<YouTube url="" />
-
-[phpMyAdmin](https://www.phpmyadmin.net/) is a free software tool written in PHP, intended to handle the administration of MySQL over the Web. See the [lando docs](https://docs.devwithlando.io/tutorials/phpmyadmin.html) regarding phpMyAdmin for help enabling the service.
-
-:::warning Only for PhpMyAdmin 4.x
-Note that this guide is only applicable to the 4.x branch of PhpMyAdmin. You'll want to consult the docs for how to do this in 5.x
-:::
-
-This is a basic setup to help you enable extra themes.
-
-## Getting Started
-
-Add the build script to your Lando recipe where you should have the phpMyAdmin service already.
-
-```yaml
-services:
-  pma:
-    type: phpmyadmin:4.7
-    build_as_root:
-      - chmod +x /app/.lando/pma-theme.sh
-      - /app/.lando/pma-theme.sh
-```
-
-## Create script to download and install the third-party theme
-
-Create the custom `pma-theme.sh` file.
-
-```bash
-touch .lando/pma-theme.sh
-vim .lando/pma-theme.sh
-```
-
-The location of this file is arbitrary. We placed it inside `.lando/` folder simply because we find it convenient.
-
-```bash
-#!/bin/sh
-if [ ! -z $LANDO_MOUNT ]; then
-  wget https://files.phpmyadmin.net/themes/pmaterial/1.1/pmaterial-1.1.zip
-  unzip pmaterial-1.1.zip -d /www/themes/
-  rm pmaterial-1.1.zip
-fi
-```
-
-Checkout the available themes [here](https://www.phpmyadmin.net/themes/). Make sure you choose a theme compatible with your version of phpMyAdmin. Modify the script according to the theme you want.
-
-## Set new theme as the default
-
-Review the [phpMyAdmin docs](https://docs.devwithlando.io/tutorials/phpmyadmin.html#using-custom-phpmyadmin-config-file) to see how to hook up your config file.
-
-Add this line to your config:
-
-```php
-<?php
-  ...
-
-  // Set whichever theme you have available here.
-  $cfg['ThemeDefault'] = 'pmaterial';
-
-  ...
-```
-
-## Rebuild your environment
-
-```bash
-lando rebuild -y
-```
-
-Done!
-
-Check the output from lando or run `lando info` to get the url for the phpMyAdmin service.
-
-<GuideFooter test="https://github.com/lando/cli/tree/main/examples/pma" original="" repo="https://github.com/lando/cli/tree/main/examples/pma"/>
-<Newsletter />
diff --git a/docs/guides/setup-lando-on-windows-with-wsl-2.md b/docs/guides/setup-lando-on-windows-with-wsl-2.md
deleted file mode 100644
index 2c7df1d..0000000
--- a/docs/guides/setup-lando-on-windows-with-wsl-2.md
+++ /dev/null
@@ -1,75 +0,0 @@
----
-title: Setup Lando on Windows with WSL2
-metaTitle: Setup Lando on Windows with WSL2 | Lando
-description: Configure Lando to run on your Windows WSL2 system for better performance when developing on Windows.
-summary: Configure Lando to run on your Windows WSL2 system for better performance when developing on Windows.
-date: 2021-01-19T14:21:27.061Z
-original: 
-repo: 
-
-author:
-  name: Dustin LeBlanc
-  pic: https://www.gravatar.com/avatar/e61caccbbfd817bc8b52c0395ba888a6
-  link: https://twitter.com/DustinLeblanc
-
-feed:
-  enable: true
-  author:
-    - name: Dustin LeBlanc
-      email: dustin@dustinleblanc.com
-      link: https://twitter.com/DustinLeblanc
-  contributor:
-    - name: Dustin LeBlanc
-      email: alliance@lando.dev
-      link: https://twitter.com/DustinLeblanc
----
-
-# Setup Lando on Windows with WSL2
-
-<GuideHeader test="" name="Dustin LeBlanc" pic="https://www.gravatar.com/avatar/e61caccbbfd817bc8b52c0395ba888a6" link="https://twitter.com/DustinLeblanc" />
-<YouTube url="" />
-
-Developing on Windows used to cause web developers agony and pain, but with the introduction of WSL, this is no longer quite so. WSL2 provides a near-native Linux experience for developing web applications on Windows computers.
-
-Longtime Mac or Windows Lando users will be familiar with the performance difficulties associated with file system access when using Docker in a non-linux host environment. Traditionally, running Docker on Mac or Windows requires a virtual machine environment. Sharing files across the boundary between your native OS and the Linux OS running within this virtual environment creates significant performance issues.
-
-WSL2 manages to bypass the majority of this performance penalty by never mounting your source code on a non-Linux filesystem. Here is the best (highest performance) way to setup Docker (and Lando) on a Windows 10 machine in 2021:
-
-## Prerequisites
-
-**1. Uninstall Pre-existing Docker + WSL2 Backend**
-You will want to make sure that, if you have an existing Docker or WSL setup, you are **not** using the Docker + WSL2 backend. If you have this setup, [you're going to have a bad time](https://www.youtube.com/watch?v=ynxPshq8ERo). It is very sad, very frustrating, so if you are here, do yourself a favor and uninstall the Docker Desktop WSL2 backend.
-
-**2. Make Sure Your Machine Supports Virtualization**
-You also need to ensure your machine supports virtualization (Vt-d, etc.). If you're not sure, you can [check this in Task Manager](https://www.shaileshjha.com/how-to-find-out-if-intel-vt-x-or-amd-v-virtualization-technology-is-supported-in-windows-10-windows-8-windows-vista-or-windows-7-machine). You don't need to have Windows 10 Pro like the traditional Lando on Windows setup, as WSL doesn't require it.
-
-## Get WSL2 rolling
-
-The first thing we need to do is enable WSL2. To do so...
-
-1. Open the start menu and search for "Turn Windows features on or off".
-2. In the resulting window, check 'Windows Subsystem for Linux' and 'Virtual Machine Platform' and then click 'ok'. This starts the system installed for WSL and will ask us to restart after it downloads the stuff it needs. This really only gives you the WSL1 setup. To get WSL2...
-3. Download a kernel update to get WSL2 going. see the [Microsoft docs on installing the kernel update](https://docs.microsoft.com/en-us/windows/wsl/install-win10#step-4---download-the-linux-kernel-update-package).
-4. After you install the kernel update, launch a powershell and run `wsl --set-default-version 2` to default to WSL 2.
-5. Head to the Microsoft store and install a Linux distro. I am going to choose [Ubuntu 18.04 LTS](https://www.microsoft.com/en-us/p/ubuntu-1804-lts/9n9tngvndl3q), since it is the most common distro for Lando users and our handy [Hyperdrive](https://github.com/lando/hyperdrive) supports it.
-
-## Jump into Hyperspace
-
-After installing the latest LTS Ubuntu, using Hyperdrive makes the rest extremely easy. We simply launch a bash shell in the WSL instance, follow the user setup process, and then follow the Hyperdrive instructions in your terminal.
-
-## Rules to keep your setup easy and happy
-
-1. **Never** run a Lando app from within the default directory that WSL drops you into (`/mnt/c/Users/whateveruser`). This is the Windows filesystem mounted into your WSL instance, and it suffers from the filesystem performance issues that this setup avoids, therefore making going through the trouble of setting this up pointless.
-2. You have to start Docker every time you start up the WSL2 instance. Running `lando start` should automatically start Docker, but if you need to initialize Docker for non-Lando purposes, try running `sudo service docker start`. This is because the WSL2 distros have no init system, so Docker doesn't auto start.
-3. VS Code is the absolute easiest editor to use with this setup. Microsoft has some extensions that make working with your WSL filesystem very easy. Vim/Neovim also work great, but using an editor like PHPStorm currently requires some extra setup if you want decent performance.
-
-## Day to day development
-
-You'll want to do all of your shell activity from within the WSL system, and you treat it like a separate Linux development box. You can run `code .` from the directory of any project you're working on and it will lauch VS Code, properly setup to develop within WSL. If you launch the terminal within WSL, it is going to work just like you expect and open the session within the WSL system.
-
-## Some caveats
-
-Performance is generally very good with this approach, however, stability can at times leave something to be be desired. Occassional freezes under heavy load are fairly commonplace, and seem to be resolved by rebooting the system. All things considered, the reduction in CPU load, battery drain, and the accompanied increase in the speed of every single action you take (accessing site pages, running any CLI commands) more than outweighs the disruption of these occasional issues for most users. Hopefully stability will continue to increase with time.
-
-<GuideFooter test="" original="" repo=""/>
-<Newsletter />
diff --git a/docs/guides/updating-local-pantheon-environments.md b/docs/guides/updating-local-pantheon-environments.md
deleted file mode 100644
index 4d3184e..0000000
--- a/docs/guides/updating-local-pantheon-environments.md
+++ /dev/null
@@ -1,62 +0,0 @@
----
-title: Updating your Pantheon site from the latest DB backup
-metaTitle: Updating your Pantheon site from the latest DB backup | Lando
-description: Add this tool to catch your local dev environment up to date.
-summary: Add this tool to catch your local dev environment up to date.
-date: 2020-03-03T21:14:32.815Z
-original: 
-repo: 
-
-author:
-  name: Jason Purdy
-  pic: https://www.gravatar.com/avatar/cb8c34b202e121d059c955433511f0b9
-  link: https://twitter.com/jason_purdy
-
-feed:
-  enable: true
-  author:
-    - name: Jason Purdy
-      email: alliance@lando.dev
-      link: https://twitter.com/jason_purdy
-  contributor:
-    - name: Jason Purdy
-      email: alliance@lando.dev
-      link: https://twitter.com/jason_purdy
----
-
-# Updating your Pantheon site from the latest DB backup
-
-<GuideHeader test="" name="Jason Purdy" pic="https://www.gravatar.com/avatar/cb8c34b202e121d059c955433511f0b9" link="https://twitter.com/jason_purdy" />
-<YouTube url="" />
-
-I can't claim credit for this, but I wanted to share a really powerful and useful addition we add to our .lando.yml files in the tooling section. It should be said that this particular use case works for Drupal and Pantheon users.
-
-```yaml
-tooling:
-  latest:
-    service: appserver
-    description: Updates the database from the latest backup
-    cmd:
-      - mkdir -p /app/artifacts
-      - rm -f /app/artifacts/database.sql.gz
-      - terminus backup:get site.env --element=db --to=/app/artifacts/database.sql.gz
-      - database: cd /app && /helpers/sql-import.sh artifacts/database.sql.gz
-      - drush cc all && drush en devel stage_file_proxy -y && drush sql-sanitize --sanitize-password="1234" --yes
-```
-
-For Drupal 8, we setup [config split](https://www.drupal.org/project/config_split) to handle separate development configurations, so our last line looks something like this:
-
-```yaml
-- cd /app/web && drush cr && drush sql-sanitize --sanitize-password="1234" --yes && drush cr && drush config-split:import config_dev -y
-```
-
-Once you add this, then you can type `lando latest` whenever you want to refresh your local environment to bring it up to date with the latest database backup.
-
-The first time you run this, you may run into an issue where your environment cannot download the backup because you need to authenticate it with Pantheon. Basically, [create a machine token](https://dashboard.pantheon.io/machine-token/create) and then type `lando terminus auth:login --machine-token=[TOKEN]`. You may have multiple Drupal/Pantheon environments and you will need to authenticate each one, but you only need to do that once, even if you restart/rebuild the app.
-
- You could still use this for non-Pantheon cases, but you'll have to change the terminus command to something that grabs your latest database backup and copies it into the `artifacts` folder.
-
- You'll also want to add the `artifacts` folder to your `.gitignore` file so you don't commit any database backups.
-
-<GuideFooter test="" original="" repo=""/>
-<Newsletter />
diff --git a/docs/guides/updating-to-rc2.md b/docs/guides/updating-to-rc2.md
deleted file mode 100644
index a4b6dcd..0000000
--- a/docs/guides/updating-to-rc2.md
+++ /dev/null
@@ -1,638 +0,0 @@
----
-description: Learn how to update Lando from beta to rc and beyond.
-date: 2019-11-05
----
-
-# Updating to 3.0.0-rc.2+
-
-<GuideHeader />
-
-Before you begin here we *highly recommend* you check out the [RC2 Release Blog Post](https://thinktandem.io/blog/2019/02/01/lando-is-ready-for-the-masses-with-rc2-release/) to get a higher level understanding on whats changed and why its changed in `3.0.0-rc.2`. After that you should be ready to get into the nitty gritty of what has changed.
-
-**This guide is for people upgrading from `3.0.0-rc.1` or lower**.
-
-Here are the various things that have changed to your [Landofiles](./../config/lando.md) syntax. We've tried to order them from the most common or most breaking config to the least. Note that this guide might not be an exhaustive list of all breaking changes and you are still *highly encouraged* to check out the other docs if you are running into an error running your older Landofiles on `3.0.0-rc.2` or higher.
-
-[[toc]]
-
-## New Images
-
-We've rebased a lot our services on [Bitnamis](https://github.com/bitnami) which means it's **highly likely** you will need to `lando destroy` your app and then `lando start` it again. It's worth trying to see if things "just work" but if you run into an error using RC2 holla at this
-
-```bash
-lando destroy
-lando start
-```
-
-Note that a `lando rebuild` is not sufficient and a `lando destroy` is needed. Also note that this will **destroy your applications perisitent storage eg your database data, solr index, etc**. If you have data you want to save, its a good idea to do something like this.
-
-```bash
-lando db-export dump.sql
-lando destroy -y
-lando start
-lando db-import dump.sql.gz
-```
-
-## Removing `~/.lando`
-
-While most updates do not require the removal of `~/.lando` there are some circumstances where this seems necessary. If you are running into any of the below known issues, or things don't seem _quite right_ we recommend a quick `rm -rf ~/.lando` and then trying again.
-
-* [Database doesn't start or reports as unhealthy](https://github.com/lando/lando/issues/1486)
-* [`lndo.site` sites are not accessible](https://github.com/lando/lando/issues/1490)
-
-If you are running into an issue that is resolved by removing `~/.lando` please [submit a ticket](https://github.com/lando/lando/issues/new/choose) so we can add it to the above list.
-
-## Overrides
-
-We've slightly changed the syntax of [service overrides](./../config/services.md#overrides) to make things more readable. All you need to do is move things up one level
-
-**old**
-
-```yaml
-services:
-  html:
-    type: apache:custom
-    overrides:
-      services:
-        environment:
-          STUFF: THINGS
-          THINGS: GUYS
-        image: pirog/myapache:2
-        volumes:
-          - ./mythings:/tmp/mythings
-```
-
-**new**
-
-```yaml
-services:
-  html:
-    type: apache:custom
-    overrides:
-      environment:
-        STUFF: THINGS
-        THINGS: GUYS
-      image: pirog/myapache:2
-      volumes:
-        - ./mythings:/tmp/mythings
-```
-
-A consequence of this is that you can no longer overrides top level `volumes` and `networks`. If you need to edit those things we recommend you look at using our [custom compose service](./../tutorials/compose.md) instead. Note the below distinction between *top level* `volumes` and `networks` and service level ones These are docker compose files not Landofiles.
-
-**top level - not supported, use a compose service**
-
-```yaml
-version: '3.6'
-services:
-  web:
-    image: nginx
-  web2:
-    image: nginx
-    ports:
-      - '80'
-volumes:
-  my-volume:
-networks:
-  my-network
-```
-
-**service level - still supported, can use a service override**
-
-```yaml
-version: '3.6'
-services:
-  web:
-    image: nginx
-  web2:
-    volumes:
-      my-volume:/tmp
-    networks:
-      - my-network
-    image: nginx
-    ports:
-      - '80'
-```
-
-Check out [this example](https://github.com/lando/cli/tree/main/examples/services) which is tested on every build for some examples of new override syntax.
-
-## Internal Service Name Changes
-
-Lando still manages some services internally such as an [nginx](./../tutorials/nginx.md) service when you use `ssl` with [varnish](./../tutorials/varnish.md) or set `via: nginx` with [php](./../tutorials/php.md) however we've changed the default names of these services so they are namespaced better.
-
-The names of these services will be the same as before except they will now be prefixed by the service that generated them. For example if you have a `php` service using `nginx` and it is named `appserver` then Lando will spin up an internal nginx service called `appserver_nginx.`
-
-Pain for this change will likely manifest if you have custom [proxy settings](./../config/proxy.md).
-
-**old**
-
-```yaml
-proxy:
-  nginx:
-    - myapp.lndo.site
-services:
-  myservice:
-    type: php
-    via: nginx
-```
-
-**new**
-
-```yaml
-proxy:
-  myservice_nginx:
-    - myapp.lndo.site
-services:
-  myservice:
-    type: php
-    via: nginx
-```
-
-This can also be an issue if you are using the service name to set a base url or config envvars.
-
-**old**
-
-```yaml
-services:
-  appserver:
-    overrides:
-      services:
-	environment:
-	  BASEURL: http://nginx
-```
-
-
-In these situations we prefer you use an option available via our [networking](./../config/networking.md).
-
-**new**
-
-```yaml
-name: myapp
-services:
-  appserver:
-    overrides:
-      environment:
-        BASEURL: https://appserver_nginx.myapp.internal
-```
-
-```yaml
-name: myapp
-proxy:
-  appserver_nginx:
-    - myapp.lndo.site
-services:
-  appserver:
-    overrides:
-      environment:
-        BASEURL: https://myapp.lndo.site
-```
-
-## Hyphens in project names
-
-If you have a `.lando.yml` that starts with
-
-```yaml
-name: site-with-hyphens
-```
-
-Then Lando generates URLs like this:
-
-**old**
-
-```
-https://sitewithhyphens.lndo.site
-```
-
-**new**
-
-```
-https://site-with-hyphens.lndo.site
-```
-
-This does not really break anything, but you may want to update the following:
-
-- If you have any browser tabs open on your Lando sites, then update the URLs after updating Lando.
-- If any of your projects have affected `.lando.yml` files, then update the URLs in related README files or other documentation.
-- If you are bothered by cruft, then see [Removing lingering Lando configuration](https://docs.devwithlando.io/installation/uninstalling.html#removing-lingering-lando-configuration). You can remove files and directories based on the old hyphenless names in the Lando configuration directory and its subdirectories.
-
-## Tooling
-
-We've altered our [tooling](./../config/tooling.md) so that it is more in line with our [events](./../config/events.md) syntax. That means you will likely want to alter two of the following scenarios.
-
-### Multi-line commands
-
-Tooling commands that are expressed as arrays now represent multiple **commands** instead of **arguments** to a single command. So you will want to change scenarios like this
-
-**old**
-
-```yaml
-tooling:
-  drush:
-    service: appserver
-    cmd:
-      - drush
-      - --root
-      - /app/PATH/TO/WEBROOT
-```
-
-**new**
-
-```yaml
-tooling:
-  drush:
-    service: appserver
-    cmd: drush --root=/app/PATH/TO/WEBROOT
-```
-
-Check out [this example](https://github.com/lando/cli/tree/main/examples/tooling) which is tested on every build for some examples of new tooling syntax.
-
-### Eventy commands
-
-If you were using [events](./../config/events.md) as a [tricky way](https://github.com/lando/lando/blob/v3.0.0-rc.1/docs/tutorials/setup-additional-tooling.md#multi-service-tooling-with-events) to run multiple commands on multiple services you can now do that [directly with tooling](./../config/tooling.md#multi-service-multi-command-tooling).
-
-**old**
-
-```yaml
-events:
-  post-update:
-    - appserver: cd $LANDO_MOUNT && composer install
-    - node: cd $LANDO_MOUNT && gulp
-    - appserver: cd $LANDO_WEBROOT && drush updb -y
-tooling:
-  update:
-    service: appserver
-    description: Builds local dependencies, compiles SASS, runs DB updates
-    cmd: 'true'
-```
-
-**new**
-
-```yaml
-tooling:
-  update:
-    description: Builds local dependencies, compiles SASS, runs DB updates
-    cmd:
-      - appserver: cd $LANDO_MOUNT && composer install
-      - node: cd $LANDO_MOUNT && gulp
-      - appserver: cd $LANDO_WEBROOT && drush updb -y
-```
-
-Check out [this example](https://github.com/lando/cli/tree/main/examples/tooling) which is tested on every build for some examples of new tooling syntax.
-
-## Build Steps
-
-While we've maintained decent backwards compatibility with previous build step names we recommend you update to the [new syntax](./../config/services.md#build-steps) and be mindful that build steps can now run **before** and **after** your application starts.
-
-**old**
-
-```yaml
-services:
-  appserver:
-    type: php
-    build_as_root:
-      - command1
-    install_dependencies_as_root:
-      - command2
-    build:
-      - command3
-    install_dependencies_as_me:
-      - command4
-    run_as_root:
-      - command5
-    extras:
-      - command6
-    run:
-      - command7
-    run_as_me
-      - command8
-```
-
-**new**
-
-```yaml
-services:
-  appserver:
-    type: php
-    build_as_root:
-      - command1
-      - command2
-    build:
-      - command3
-      - command4
-    run_as_root:
-      - command5
-      - command6
-    run:
-      - command7
-      - command8
-```
-
-If you have been using either of the following *unsupported* syntaxes then make sure you also read about [using scripty things](./../config/services.md#using-scripty-things) in your build steps.
-
-```yaml
-run:
-  - |
-    if [ ! -z $LANDO_MOUNT ]; then
-      do something
-      some other command
-    fi
-```
-
-```yaml
-run:
-  - if [ ! -z $LANDO_MOUNT ]; then do-stuff; fi
-```
-
-Check out [this example](https://github.com/lando/cli/tree/main/examples/services) which is tested on every build for some examples of new build step syntax.
-
-## Global Environment Variables
-
-Lando no longer sets its [default environment variables](./../config/env.md) on your host machine. They are now **service only**. While this usage has actually been deprecated for quite some time you may still be doing stuff like this.
-
-**old**
-
-```yaml
-events:
-  post-start:
-    - appserver: cd $LANDO_MOUNT && some-command
-services:
-  appserver:
-    build:
-      - cd $LANDO_MOUNT && some-other-command
-    overrides:
-      services:
-        volumes:
-        - $LANDO_APP_ROOT_BIND/.lando/build-sh-setup.sh:/helpers/build-sh-setup.sh
-        - $LANDO_ENGINE_CONF/.lando/build.sh:/helpers/build.sh
-```
-
-We have standardized these locations for quite some time and they **will not be changing** so you can now just do.
-
-**new**
-
-```yaml
-events:
-  post-start:
-    - appserver: some-command
-services:
-  appserver:
-    build:
-      - some-other-command
-    overrides:
-      volumes:
-        # You can use paths relative to your apps root directory
-        - ./.lando/build-sh-setup.sh:/helpers/build-sh-setup.sh
-```
-
-For `events` and `build-steps` these commands will be run from the `$LANDO_MOUNT` by default.
-
-Tooling commands will be run from the container analog of your `cwd`.
-
-If you find yourself **needing** to hard enter `$LANDO_MOUNT` you can safely just use `/app` as `$LANDO_MOUNT` will not change unless you've explicitly overridden it.
-
-```yaml
-events:
-  post-start:
-    - appserver: cd /app && command-that-def-needs-to-be-run-from-here
-```
-
-Note that in the case of something like `$LANDO_ENGINE_CONF` your application's `root` directory, the entire `~/.lando` config directory, and your user home folder are [already available inside every container](./../config/files.md) by default so you should invoke them directly instead of re-mounting them.
-
-### Accessing Environment variables in events, build-steps, tooling etc
-
-You can, however, still use the environment variables available in each service in your Landofiles by wrapping their invocation with `sh` or `bash`. This will explicitly let Lando know you want to use environment variables in the service and not the host. Note that while you **can** do this it's almost always better to just explicitly refer to things.
-
-**works but not recommended**
-
-```yaml
-events:
-  post-start:
-    - /bin/sh -c 'cd "/app/$LANDO_APP_PROJECT" && do-something'
-```
-
-**works AND recommended**
-
-```yaml
-events:
-  post-start:
-    - cd /app/landoservices && do-something
-```
-
-## Service Versions
-
-Most service versions have stayed the same but a few have changed. If you try to run a now-unsupported service version Lando will throw a nice red error. If this happens to you check out the supported version documented for each service and either choose the closest one to what you have **OR** remove the version completely and use the default.
-
-*   ### [apache](./../config/apache.md)
-*   ### [custom](./../config/compose.md)
-*   ### [dotnet](./../config/dotnet.md)
-*   ### [elasticsearch](./../config/elasticsearch.md)
-*   ### [go](./../config/go.md)
-*   ### [mailhog](./../config/mailhog.md)
-*   ### [mariadb](./../config/mariadb.md)
-*   ### [memcached](./../config/memcached.md)
-*   ### [mongo](./../config/mongo.md)
-*   ### [mssql](./../config/mssql.md)
-*   ### [mysql](./../config/mysql.md)
-*   ### [nginx](./../config/nginx.md)
-*   ### [node](./../config/node.md)
-*   ### [php](./../config/php.md)
-*   ### [phpmyadmin](./../config/phpmyadmin.md)
-*   ### [postgres](./../config/postgres.md)
-*   ### [python](./../config/python.md)
-*   ### [redis](./../config/redis.md)
-*   ### [ruby](./../config/ruby.md)
-*   ### [solr](./../tutorials/solr.md)
-*   ### [tomcat](./../config/tomcat.md)
-*   ### [varnish](./../config/varnish.md)
-
-## Environment Files
-
-You now have to explicitly set the top level [`env_file`](./../config/env.md#environment-files) if you want to load a `env` file.
-
-**old**
-
-*Had a `.env` file in Lando root directory*
-
-**new**
-
-```yaml
-env_file:
-  - .env
-```
-
-By happenstance you could previously use the following *unsupported* syntax in your `env` files.
-
-```bash
-WP_ENV=development
-WP_HOME=http://wpb4.test
-WP_SITEURL=${WP_HOME}/wp
-```
-
-Because we now directly use Docker Compose's `env_file` directive under the hood this syntax no longer works. So you will have to do something like:
-
-```bash
-WP_ENV=development
-WP_HOME=http://wpb4.test
-WP_SITEURL=http://wpb4.test/wp
-```
-
-Check out [this example](https://github.com/lando/cli/tree/main/examples/base) which is tested on every build for some examples of the new environment file syntax.
-
-## Drush Handling
-
-We've vastly simplified our [Drush handling](./../tutorials/drupal8.md#using-drush). You can now only set `drush` to a particular version for global installation. If you've installed `drush` via `composer` then Lando will use that version instead of the one in your Landofile.
-
-**old**
-
-```yaml
-recipe: drupal8
-config:
-  drush: none
-```
-
-```yaml
-recipe: drupal8
-config:
-  drush: composer
-```
-
-```yaml
-recipe: drupal8
-config:
-  drush: /path/to/my/drush
-```
-
-**new**
-
-```yaml
-recipe: drupal8
-```
-
-```yaml
-recipe: drupal8
-config:
-  drush: 8.1.15
-```
-
-## Rebuild vs. Restart
-
-If you change your Landofiles you now need to explicitly [`lando rebuild`](./../cli/rebuild.md) instead of running [`lando restart`](./../cli/rebuild.md). This helps to provide stability between restarts until you explicitly ask for things to change and vastly speeds up stops and starts.
-
-**old**
-
-*changed `.lando.yml`*
-
-```bash
-lando restart
-```
-
-**new**
-
-*changed `.lando.yml`*
-
-```bash
-lando rebuild -y
-```
-
-## Lando Init
-
-We've completely reworked [`lando init`](./../cli/init.md) to be more modular and intuitive. This means if you've got scripts relying on `lando init` you will likely need to make some changes. While there are many changes the biggest are the removal of the "init method" in favor of the `--source` option.
-
-
-**old**
-
-```bash
-lando init pantheon
-```
-
-**new**
-
-```bash
-lando init --source pantheon
-```
-
-**sources** are places where Lando can get your code and **recipes** are the kinds of applications that exists at **source**.
-
-## Global Options
-
-Lando no longer uses [`--`](https://github.com/lando/lando/blob/v3.0.0-rc.1/docs/cli/usage.md#global-options) to differentiate between its options and tooling options.
-
-**old**
-
-```bash
-# Verbose modes
-lando start -- -v
-lando start -- -vv
-lando start -- -vvv
-lando start -- -vvvv
-
-# Lando help
-lando start -- --help
-```
-
-**new**
-
-```bash
-# Verbose modes
-lando start -v
-lando start -vv
-lando start -vvv
-lando start -vvvv
-
-# Lando help
-lando start --help
-```
-
-A nice consequence of this is you can now use `--` in other tooling commands and have more predictable tooling results
-
-```bash
-# Use -- in a command
-lando terminus remote:drush "$SITE.$ENV" -- cr --all -y
-
-# Worry less about escaping crap
-lando php -r "phpinfo();"
-```
-
-## Global Envvars
-
-There is no longer a `containerGlobalEnv` option in the Lando [global config](./../config/config.md). But you can now use `appEnv` to the same effect. **Note that this is for the Lando `config.yml` and NOT for a Landofile**.
-
-**old**
-
-```yaml
-containerGlobalEnv:
-  PARTY: USA
-```
-
-**new**
-
-```yaml
-appEnv:
-  PARTY: USA
-```
-
-## App Registry
-
-There is no longer a register of apps stored at `~/.lando/cache/registry`. As a consequence you can no longer do things like `lando start MYAPP`
-
-```bash
-lando start MYAPP
-```
-
-**new**
-
-```bash
-cd /path/to/MYAPP
-lando start
-```
-
-## Plugins
-
-If you have written your own custom plugins
-
-1. Sorry!! :/
-2. Once you see the new format you'll feel better :)
-
-We've finally locked down a [Plugin System](https://docs.lando.dev/contrib/contrib-plugins.html) that uses the [Lando](./../api/lando.md) and [App](./../api/app.md) APIs and while we still don't have a great way to manage the installation and management of these plugins it is going to be the defining feature of `3.1.0`.
-
-<GuideFooter />
-<Newsletter />
diff --git a/docs/guides/using-compass-on-a-lando-node-service.md b/docs/guides/using-compass-on-a-lando-node-service.md
deleted file mode 100644
index e7085ea..0000000
--- a/docs/guides/using-compass-on-a-lando-node-service.md
+++ /dev/null
@@ -1,84 +0,0 @@
----
-title: Using Compass on a Lando Node Service
-metaTitle: Using Compass on a Lando Node Service | Lando
-description: Learn how to use legacy compass sass builds for your Lando frontend node build
-summary: Learn how to use legacy compass sass builds for your Lando frontend node build
-date: 2020-05-13T01:27:44.387Z
-original:
-repo:
-
-author:
-  name: Team Lando
-  pic: https://gravatar.com/avatar/c335f31e62b453f747f39a84240b3bbd
-  link: https://twitter.com/devwithlando
-
-feed:
-  enable: true
-  author:
-    - name: Team Lando
-      email: alliance@lando.dev
-      link: https://twitter.com/devwithlando
-  contributor:
-    - name: Team Lando
-      email: alliance@lando.dev
-      link: https://twitter.com/devwithlando
----
-
-# Using Compass on a Lando Node Service
-
-<GuideHeader test="https://circleci.com/gh/lando/lando/tree/master" name="Team Lando" pic="https://gravatar.com/avatar/c335f31e62b453f747f39a84240b3bbd" link="https://twitter.com/devwithlando" />
-<YouTube url="" />
-
-Some older `node` based frontend build steps rely on `ruby` and `compass`. If you have such a flow we _highly recommend_ you escape dependency hell and migrate your `sass` build steps to use `node-sass` which is _way_ faster.
-
-However, if you cannot do this you may run into some issues running `compass` inside of your `node` container since this pattern is fundamentally at odds with Lando's one-thing-per-container model.
-
-You can, however, get around it by installing `ruby` and `compose` directly in the `node` service that requires them.
-
-Below is an example that installs `ruby` and `compass` using [build-steps](./../config/services.md#build-steps).
-
-```yaml
-services:
-  myservice:
-    type: node:12
-    build_as_root:
-      - apt-get update -y
-      - apt-get install ruby-full -y
-      - gem install compass
-tooling:
-  ruby:
-    service: myservice
-  compass:
-    service: myservice
-```
-
-You can verify with:
-
-```bash
-lando ruby -v
-lando compass -v
-```
-
-You should now be able to run any build steps that require `ruby` and `compass` as in this example:
-
-```yaml
-services:
-  myservice:
-    type: node:12
-    globals:
-      grunt-cli: latest
-    build_as_root:
-      - apt-get update -y
-      - apt-get install ruby-full -y
-      - gem install compass
-    build:
-      - grunt build:sass
-tooling:
-  ruby:
-    service: myservice
-  compass:
-    service: myservice
-```
-
-<GuideFooter test="https://circleci.com/gh/lando/lando/tree/master" original="" repo="https://github.com/lando/cli/tree/main/examples/node12"/>
-<Newsletter />

From ab8649df8686399ef38980cf29be8a79b8b96975 Mon Sep 17 00:00:00 2001
From: John Ouellet <john@thinktandem.io>
Date: Mon, 8 Nov 2021 10:07:09 -0500
Subject: [PATCH 15/16] Add in npm version of theme

---
 docs/.vuepress/components/GuideFooter.vue     |  69 ------
 docs/.vuepress/components/GuideHeader.vue     |  65 ------
 docs/.vuepress/components/Newsletter.vue      | 130 -----------
 docs/.vuepress/components/NewsletterLearn.vue | 134 ------------
 docs/.vuepress/components/RelatedGuides.vue   |  53 -----
 docs/.vuepress/components/TeamList.vue        |  49 -----
 docs/.vuepress/components/YouTube.vue         |  38 ----
 docs/.vuepress/config.js                      |  18 +-
 docs/.vuepress/theme/components/CarbonAds.vue |  80 -------
 docs/.vuepress/theme/components/Sponsors.vue  |  97 ---------
 docs/.vuepress/theme/components/Subscribe.vue | 201 ------------------
 .../.vuepress/theme/components/TeamMember.vue | 149 -------------
 docs/.vuepress/theme/index.js                 |  42 ----
 docs/.vuepress/theme/layouts/404.vue          |  16 --
 docs/.vuepress/theme/layouts/Layout.vue       |  31 ---
 docs/.vuepress/theme/styles/index.scss        | 175 ---------------
 docs/.vuepress/theme/styles/palette.scss      |  17 --
 package.json                                  |   1 +
 yarn.lock                                     |   8 +
 19 files changed, 10 insertions(+), 1363 deletions(-)
 delete mode 100644 docs/.vuepress/components/GuideFooter.vue
 delete mode 100644 docs/.vuepress/components/GuideHeader.vue
 delete mode 100644 docs/.vuepress/components/Newsletter.vue
 delete mode 100644 docs/.vuepress/components/NewsletterLearn.vue
 delete mode 100644 docs/.vuepress/components/RelatedGuides.vue
 delete mode 100644 docs/.vuepress/components/TeamList.vue
 delete mode 100644 docs/.vuepress/components/YouTube.vue
 delete mode 100644 docs/.vuepress/theme/components/CarbonAds.vue
 delete mode 100644 docs/.vuepress/theme/components/Sponsors.vue
 delete mode 100644 docs/.vuepress/theme/components/Subscribe.vue
 delete mode 100644 docs/.vuepress/theme/components/TeamMember.vue
 delete mode 100644 docs/.vuepress/theme/index.js
 delete mode 100644 docs/.vuepress/theme/layouts/404.vue
 delete mode 100644 docs/.vuepress/theme/layouts/Layout.vue
 delete mode 100644 docs/.vuepress/theme/styles/index.scss
 delete mode 100644 docs/.vuepress/theme/styles/palette.scss

diff --git a/docs/.vuepress/components/GuideFooter.vue b/docs/.vuepress/components/GuideFooter.vue
deleted file mode 100644
index 8d0d288..0000000
--- a/docs/.vuepress/components/GuideFooter.vue
+++ /dev/null
@@ -1,69 +0,0 @@
-<template>
-  <div class="originally-appeared">
-    <div v-if="repo" class="tip custom-block">
-      <h3>FULL CODE EXAMPLE!</h3>
-      <p>If you are interested in checking out the fully-armed and operational source code for this guide then check out <a target="_blank" :href="repo">this repo here</a>.</p>
-    </div>
-    <div class="original-rule"></div>
-    <div class="original-article" v-if="original">
-      This guide is adapted from other content. If you are interested in the original then <a target="_blank" :href="original">check it out here</a>.
-    </div>
-    <div class="original-article">
-      Have a Lando question you'd like to see as a guide? <a target="_blank" href="https://github.com/lando/lando/issues/new/choose"> Suggest one!</a>
-    </div>
-    <div class="original-article">
-      Want to write a Lando guide? <a href="./../theme/contrib/guides-intro.html"> Learn how!</a>
-    </div>
-  </div>
-</template>
-
-<script>
-export default {
-  name: 'GuideFooter',
-  props: {
-    original: {
-      type: String,
-      default: '',
-    },
-    repo: {
-      type: String,
-      default: '',
-    },
-    test: {
-      type: String,
-    },
-  },
-};
-</script>
-
-<style lang="scss">
-@import '../theme/styles/index.scss';
-@import '../theme/styles/palette.scss';
-@import '@vuepress/plugin-palette/palette';
-
-.originally-appeared {
-  margin-top: 2rem;
-  padding-top: 1rem;
-  img {
-    width: 24px;
-    border-radius: 100%;
-    float: right;
-    position: relative;
-    bottom: 6px;
-  }
-  .original-article {
-    font-size: 0.85em;
-    font-style: italic;
-  }
-  .original-rule {
-    border-bottom: 1px dotted #ddd;
-    padding-top: 1em;
-    margin-bottom: 1em;
-  }
-  .custom-block {
-    &.tip {
-      border-color: $landoGreen;
-    }
-  }
-}
-</style>
diff --git a/docs/.vuepress/components/GuideHeader.vue b/docs/.vuepress/components/GuideHeader.vue
deleted file mode 100644
index 114d6bb..0000000
--- a/docs/.vuepress/components/GuideHeader.vue
+++ /dev/null
@@ -1,65 +0,0 @@
-<template>
-  <div class="written-by">
-    Written by:
-    <a :href="link" target="_blank">{{ name }}</a>
-    <a :href="link" target="_blank"><img :src="pic" :alt="name" /></a>
-    <div v-if="test" class="tested-by">
-      Guide Tested: <a :href="test" target="_blank">Yes</a>
-    </div>
-    <div v-else>
-      Guide Tested: <span class="not-tested">No</span>
-    </div>
-  </div>
-
-</template>
-
-<script>
-export default {
-  name: 'GuideHeader',
-  props: {
-    name: {
-      type: String,
-      default: 'Team Lando',
-    },
-    pic: {
-      type: String,
-      default: 'https://www.gravatar.com/avatar/db2470075fb67c330c155cab9698826f',
-    },
-    link: {
-      type: String,
-      default: 'https://twitter.com/devwithlando',
-    },
-    test: {
-      type: String,
-      default: null,
-    },
-  },
-};
-</script>
-
-<style lang="scss">
-@import '../theme/styles/index.scss';
-@import '../theme/styles/palette.scss';
-@import '@vuepress/plugin-palette/palette';
-
-.written-by {
-  font-size: 0.85em;
-  padding-bottom: 1rem;
-  border-bottom: 1px dotted #ddd;
-  img {
-    width: 24px;
-    border-radius: 100%;
-    float: right;
-    position: relative;
-    bottom: 6px;
-  }
-  .tested-by {
-    a {
-      color: #2ecc71;
-    }
-  }
-  .not-tested {
-    color: #f00;
-  }
-}
-</style>
diff --git a/docs/.vuepress/components/Newsletter.vue b/docs/.vuepress/components/Newsletter.vue
deleted file mode 100644
index f1b16dd..0000000
--- a/docs/.vuepress/components/Newsletter.vue
+++ /dev/null
@@ -1,130 +0,0 @@
-<template>
-  <div class="newsletter post-subscribe">
-    <div class="newsletter__wrap">
-      <div class="newsletter__title">Want new guide content?</div>
-      <div class="newsletter__content">Sign up and we'll send you the latest and greatest!</div>
-      <Subscribe
-        successMessage="More awesome guide material will be heading your way!"
-        :customStyles="stylez"
-        :interests="interests"
-        title=""
-      />
-    </div>
-  </div>
-</template>
-
-<script>
-import Subscribe from '../theme/components/Subscribe.vue';
-
-export default {
-  name: 'Newsletter',
-  components: {Subscribe}, // eslint-disable-line
-  data() {
-    return {
-      stylez: {
-        width: '100%',
-      },
-      interests: [{
-        id: 1,
-        group: 37781,
-        checked: true,
-        hidden: true,
-        label: 'Updates',
-      }],
-    };
-  },
-};
-</script>
-
-<style lang="scss">
-@import '../theme/styles/index.scss';
-@import '../theme/styles/palette.scss';
-@import '@vuepress/plugin-palette/palette';
-
-.newsletter {
-  text-align: center;
-  width: 100%;
-  font-size: 1rem;
-  color: var(--c-text);
-}
-.newsletter__wrap {
-  margin: 1.5rem auto;
-  padding: 1.8rem 2.3rem;
-  border-radius: 3px;
-  box-sizing: border-box;
-  width: auto;
-  background-color: #f8f8f8;
-}
-.newsletter__title {
-  font-size: 1.7rem;
-}
-.newsletter__content {
-  margin-top: 1.5rem;
-  margin-bottom: 1.5rem;
-  line-height: 1.7rem;
-}
-.newsletter__input {
-  font-size: inherit;
-  border: 1px solid var(  --c-border);
-  width: 100%;
-  padding: 0.6rem 1.2rem;
-  box-sizing: border-box;
-  border-radius: 3px;
-  margin-bottom: 0.8rem;
-  outline: none;
-}
-.newsletter__button {
-  font-size: inherit;
-  border: none;
-  cursor: pointer;
-  background: var(  --c-text-accent);
-  color: #fff;
-  padding: 0.6rem 1.8rem;
-  box-sizing: border-box;
-  border-radius: 3px;
-  width: 100%;
-  outline: none;
-}
-.post-subscribe {
-  .subscribe {
-    width: 100%;
-    padding: 0;
-    .button {
-      font-size: inherit;
-      border: none;
-      cursor: pointer;
-      background: #ed3f7a;
-      color: #fff;
-      padding: 0.6rem 1.2rem;
-      box-sizing: border-box;
-      border-radius: 3px;
-      width: 100%;
-      outline: none;
-      text-transform: none;
-      font-weight: 400;
-      height: auto;
-    }
-  }
-  .subscribe-input {
-    background-color: #fff;
-    font-size: inherit;
-    border: 1px solid #ddd;
-    width: 100%;
-    padding: 0.6rem 1.2rem;
-    box-sizing: border-box;
-    border-radius: 3px;
-    margin-bottom: 0.8rem;
-    outline: none;
-    height: auto;
-    margin: 1em 0;
-  }
-  .newsletter__wrap {
-    background-color: #f8f8f8;
-  }
-  @media (max-width: $MQMobile) {
-    .post-subscribe .subscribe-form {
-      display: block;
-    }
-  }
-}
-</style>
diff --git a/docs/.vuepress/components/NewsletterLearn.vue b/docs/.vuepress/components/NewsletterLearn.vue
deleted file mode 100644
index edcc77f..0000000
--- a/docs/.vuepress/components/NewsletterLearn.vue
+++ /dev/null
@@ -1,134 +0,0 @@
-<template>
-  <div class="newsletter post-subscribe">
-    <div class="newsletter__wrap">
-      <div class="newsletter__title">Want more helpful onboarding content?</div>
-      <div class="newsletter__content">Sign up and we'll send you a new and helpful guide every week!</div>
-      <Subscribe
-        successMessage="Soon you will be the master!"
-        :customStyles="stylez"
-        :groups="groups"
-        title=""
-      />
-    </div>
-  </div>
-</template>
-
-<script>
-import Subscribe from '../theme/components/Subscribe.vue';
-
-export default {
-  name: 'NewsletterLearn',
-  components: {Subscribe}, // eslint-disable-line
-  data() {
-    return {
-      stylez: {
-        width: '100%',
-      },
-      groups: ['NEWSLETTER', 'NEWUSER'],
-    };
-  },
-};
-</script>
-
-<style lang="scss">
-@import '../theme/styles/index.scss';
-@import '../theme/styles/palette.scss';
-@import '@vuepress/plugin-palette/palette';
-
-.newsletter {
-	text-align: center;
-	width: 100%;
-	font-size: 1rem;
-	color: var(--c-text);
-}
-.newsletter__wrap {
-	margin: 1.5rem auto;
-	padding: 1.8rem 2.3rem;
-	border-radius: 3px;
-	box-sizing: border-box;
-	width: auto;
-	background-color: #f8f8f8;
-}
-.newsletter__title {
-	font-size: 1.7rem;
-}
-.newsletter__content {
-	margin-top: 1.5rem;
-	margin-bottom: 1.5rem;
-	line-height: 1.7rem;
-}
-.newsletter__input {
-	font-size: inherit;
-	border: 1px solid var(  --c-border);
-	width: 100%;
-	padding: 0.6rem 1.2rem;
-	box-sizing: border-box;
-	border-radius: 3px;
-	margin-bottom: 0.8rem;
-	outline: none;
-}
-.newsletter__button {
-	font-size: inherit;
-	border: none;
-	cursor: pointer;
-	background: var(  --c-text-accent);
-	color: #fff;
-	padding: 0.6rem 1.8rem;
-	box-sizing: border-box;
-	border-radius: 3px;
-	width: 100%;
-	outline: none;
-}
-.post-subscribe {
-	.subscribe {
-		width: 100%;
-		padding: 0;
-		.button {
-			font-size: inherit;
-			border: none;
-			cursor: pointer;
-			background: #ed3f7a;
-			color: #fff;
-			padding: 0.6rem 1.2rem;
-			box-sizing: border-box;
-			border-radius: 3px;
-			width: 100%;
-			outline: none;
-			text-transform: none;
-			font-weight: 400;
-			height: auto;
-		}
-	}
-	.subscribe-form {
-		display: grid;
-		grid-template-columns: 1fr 1fr;
-		grid-gap: 10px;
-	}
-	.subscribe-input {
-		background-color: #fff;
-		font-size: inherit;
-		border: 1px solid #ddd;
-		width: 100%;
-		padding: 0.6rem 1.2rem;
-		box-sizing: border-box;
-		border-radius: 3px;
-		margin-bottom: 0.8rem;
-		outline: none;
-		height: auto;
-		margin: 1em 0;
-		&:focus {
-			outline: none;
-			border: 0;
-			border-color: transparent;
-		}
-	}
-  @media (max-width: $MQMobile) {
-    .subscribe-form {
-      display: block;
-    }
-    .newsletter__wrap {
-      background-color: #f8f8f8;
-    }
-  }
-}
-</style>
diff --git a/docs/.vuepress/components/RelatedGuides.vue b/docs/.vuepress/components/RelatedGuides.vue
deleted file mode 100644
index 130d8eb..0000000
--- a/docs/.vuepress/components/RelatedGuides.vue
+++ /dev/null
@@ -1,53 +0,0 @@
-<template>
-  <div v-if="tag && content.length > 0" class="related-guides">
-    <h2>Related Guides and Tutorials</h2>
-    <ul>
-      <li v-for="page in content" :key="page.key">
-        <a :href="page.path">{{ page.title }}</a>
-      </li>
-    </ul>
-  </div>
-</template>
-
-<script>
-import { resolveSidebarItems } from '@vuepress/theme-default/lib/client/composables/useSidebarItems.js';
-import { useThemeData } from '@vuepress/plugin-theme-data/lib/client';
-
-export default {
-  name: 'RelatedGuides',
-  props: {
-    tag: {
-      type: String,
-      default: '',
-    },
-  },
-  data() {
-    return {
-      content: [],
-    };
-  },
-  mounted() {
-    const themeData = useThemeData();
-    const guides = resolveSidebarItems(this.$frontmatter, themeData);
-    console.log(guides);
-    const section = guides.find(item => item.title.toLowerCase() === this.tag.toLowerCase());
-    this.content = section.children;
-  },
-};
-</script>
-
-<style lang="scss">
-@import '../theme/styles/index.scss';
-@import '../theme/styles/palette.scss';
-@import '@vuepress/plugin-palette/palette';
-
-.related-guides {
-	margin-top: 2rem;
-	padding-top: 1rem;
-	a {
-		display: block;
-		padding-bottom: 0.3em;
-	}
-}
-
-</style>
diff --git a/docs/.vuepress/components/TeamList.vue b/docs/.vuepress/components/TeamList.vue
deleted file mode 100644
index aa4a07b..0000000
--- a/docs/.vuepress/components/TeamList.vue
+++ /dev/null
@@ -1,49 +0,0 @@
-<template>
-  <div id="current-team" class="current-team-wrapper">
-    <TeamMember v-for="(member, index) in members" :key="index" :member="member" />
-  </div>
-</template>
-
-<script>
-import TeamMember from '../theme/components/TeamMember.vue';
-
-export default {
-  name: 'TeamList',
-  components: {TeamMember},
-  data() {
-    return {
-      members: [],
-    };
-  },
-  mounted() {
-    this.members = this.$contributors;
-  },
-};
-</script>
-
-<style lang="scss">
-@import '../theme/styles/index.scss';
-@import '../theme/styles/palette.scss';
-@import '@vuepress/plugin-palette/palette';
-
-.current-team {
-	.current-team-wrapper {
-		max-width: 740px;
-		margin: 0 auto;
-		padding: 0rem 2.5rem;
-		padding-top: 3.75rem;
-		padding-bottom: 1rem;
-	}
-	.theme-default-content {
-		max-width: 740px;
-		margin: 0 auto;
-		padding: 0rem 2.5rem;
-		&:not(.custom) {
-			& > *:first-child {
-				margin-top: 0px;
-			}
-		}
-	}
-}
-
-</style>
diff --git a/docs/.vuepress/components/YouTube.vue b/docs/.vuepress/components/YouTube.vue
deleted file mode 100644
index 947e8b2..0000000
--- a/docs/.vuepress/components/YouTube.vue
+++ /dev/null
@@ -1,38 +0,0 @@
-<template>
-  <div v-if="url" class="video-responsive">
-    <iframe width="100%" height="400" :src="url" frameborder="0" allow="accelerometer; autoplay; encrypted-media; gyroscope; picture-in-picture" allowfullscreen></iframe>
-  </div>
-</template>
-
-<script>
-
-export default {
-  name: 'YouTube',
-  props: {
-    url: {
-      type: String,
-    },
-  },
-};
-</script>
-
-<style lang="scss">
-@import '../theme/styles/index.scss';
-@import '../theme/styles/palette.scss';
-@import '@vuepress/plugin-palette/palette';
-
-.video-responsive {
-	margin-top: 1em;
-	overflow: hidden;
-	padding-bottom: 56.25%;
-	position: relative;
-	height: 0;
-	iframe {
-		left: 0;
-		top: 0;
-		height: 100%;
-		width: 100%;
-		position: absolute;
-	}
-}
-</style>
diff --git a/docs/.vuepress/config.js b/docs/.vuepress/config.js
index 6855c09..5c8d4dc 100644
--- a/docs/.vuepress/config.js
+++ b/docs/.vuepress/config.js
@@ -10,7 +10,7 @@ module.exports = {
     ['link', {rel: 'icon', href: '/favicon.ico'}],
     ['link', {rel: 'stylesheet', href: '//fonts.googleapis.com/css?family=Poppins:700|Source+Sans+Pro&display=swap'}],
   ],
-  theme: path.resolve(__dirname, 'theme'),
+  theme: '@lando/vuepress-docs-theme',
   themeConfig: {
     logo: '/images/logo-pink-small.png',
     repo: 'lando/platformsh',
@@ -27,20 +27,4 @@ module.exports = {
       {text: 'Help and Support', link: '/help/logs/'},
     ],
   },
-  plugins: [
-    [
-      '@vuepress/docsearch',
-      {
-        apiKey: '15e332850128e9ec96929f44c62f6c88',
-        indexName: 'lando',
-      },
-    ],
-    [
-      '@vuepress/register-components',
-      {
-        componentsDir: path.resolve(__dirname, './components'),
-        componentsPatterns: ['*.vue', '**/*.vue']
-      },
-    ],
-  ]
 };
diff --git a/docs/.vuepress/theme/components/CarbonAds.vue b/docs/.vuepress/theme/components/CarbonAds.vue
deleted file mode 100644
index 587961f..0000000
--- a/docs/.vuepress/theme/components/CarbonAds.vue
+++ /dev/null
@@ -1,80 +0,0 @@
-<script>
-import { h } from 'vue';
-
-export default {
-  render() {
-    return h('div', {class: 'carbon-ads'});
-  },
-  mounted() {
-    this.load();
-  },
-  watch: {
-    '$route'(to, from) {
-      if (
-        to.path !== from.path
-        // Only reload if the ad has been loaded
-        // otherwise it's possible that the script is appended but
-        // the ads are not loaded yet. This would result in duplicated ads.
-        && this.$el.querySelector('#carbonads')
-      ) {
-        this.$el.innerHTML = '';
-        this.load();
-      }
-    },
-  },
-  methods: {
-    load() {
-      const s = document.createElement('script');
-      s.id = '_carbonads_js';
-      s.src = `//cdn.carbonads.com/carbon.js?serve=CE7DCKJU&placement=landodev`;
-      this.$el.appendChild(s);
-    },
-  },
-};
-</script>
-
-<style lang="scss">
-@import '../styles/palette.scss';
-.sidebar {
-	.carbon-ads {
-		a {
-			display: block;
-		}
-	}
-}
-.carbon-ads {
-	min-height: 102px;
-	padding: 1.5rem 1.5rem 0;
-	margin-bottom: -0.5rem;
-	font-size: 0.75rem;
-	a {
-		color: #444;
-		font-weight: normal;
-		display: inline;
-	}
-	.carbon-img {
-		float: left;
-		margin-right: 1rem;
-		border: 1px solid var(--c-border);
-		img {
-			display: block;
-		}
-	}
-	.carbon-poweredby {
-		color: #999;
-		display: block;
-		margin-top: 0.5em;
-	}
-}
-.dark {
-  a.carbon-text {
-    color: var(--c-text-light);
-  }
-}
-@media (max-width: $MQMobile) {
-  .carbon-ads .carbon-img img {
-    width: 100px;
-    height: 77px;
-	}
-}
-</style>
diff --git a/docs/.vuepress/theme/components/Sponsors.vue b/docs/.vuepress/theme/components/Sponsors.vue
deleted file mode 100644
index e640fc9..0000000
--- a/docs/.vuepress/theme/components/Sponsors.vue
+++ /dev/null
@@ -1,97 +0,0 @@
-<template>
-  <div id="special_sponsors">
-    <h4>special sponsors</h4>
-    <div class="sponsor-wrapper">
-      <div class="special-sponsor-block" v-for="(sponsor, index) in sponsorList" :key="index">
-        <a :href="sponsor.url" target="_blank">
-          <div class="special-sponsor-image"><img :src="sponsor.logo" :alt="sponsor.name"></div>
-        </a>
-      </div>
-    </div>
-
-    <div class="special-sponsor-footer">
-      <a href="https://lando.dev/sponsor" target="_blank">become a sponsor</a>
-    </div>
-  </div>
-</template>
-
-
-<script>
-import { filter } from 'lodash';
-import { useThemeData } from '@vuepress/plugin-theme-data/lib/client';
-
-export default {
-  data() {
-    return {
-      sponsorList: [],
-    };
-  },
-  setup() {
-    // Get theme data
-    const themeData = useThemeData();
-    // Get the config from themedata
-    const {showSponsors = true} = themeData.value;
-    const {sponsors = []} = themeData.value;
-
-    return {
-      showSponsors,
-      sponsors
-    }
-  },
-  mounted() {
-    this.sponsorList = !Array.isArray(this.showSponsors) 
-      ? this.sponsors
-      : filter(this.sponsors, sponsor => {
-          return this.showSponsors.includes(sponsor.id);
-      });
-  },
-};
-</script>
-
-<style lang="scss">
-  #special_sponsors {
-    padding: 3em;
-    position: absolute;
-    right: 2em;
-    top: 6em;
-    width: 150px;
-    background: transparent;
-    opacity: .75;
-    text-align: center;
-    font-size: .8em;
-  }
-  .special-sponsor-block {
-    img {
-      width: 100px;
-      padding-bottom: 2em;
-    }
-  }
-  @media (max-width: 1300px) {
-    #special_sponsors {
-      position: initial;
-      padding: 1em;
-      right: initial;
-      top: initial;
-      width: initial;
-      .sponsor-wrapper {
-        display: flex;
-        justify-content: center;
-        .special-sponsor-block {
-          margin-top: auto;
-          margin-bottom: auto;
-          padding-right: 1em;
-          &:last-of-type {
-            padding-right: 0;
-          }
-          img {
-            height: auto;
-            padding: 0;
-          }
-        }
-      }
-      .special-sponsor-footer {
-        padding-top: 2em;
-      }
-    }
-  }
-</style>
\ No newline at end of file
diff --git a/docs/.vuepress/theme/components/Subscribe.vue b/docs/.vuepress/theme/components/Subscribe.vue
deleted file mode 100644
index c9165c0..0000000
--- a/docs/.vuepress/theme/components/Subscribe.vue
+++ /dev/null
@@ -1,201 +0,0 @@
-<template>
-  <div :class="{ subscribe: true, 'subscribe-dark': theme === 'dark' }" :style="customStyles">
-    <h3>{{ title }}</h3>
-    <div id="mc_embed_signup">
-      <form action="https://dev.us12.list-manage.com/subscribe/post?u=59874b4d6910fa65e724a4648&amp;id=613837077f" method="post" id="mc-embedded-subscribe-form" name="mc-embedded-subscribe-form" class="validate subscribe-form" target="_blank" novalidate>
-        <input
-          id="mce-EMAIL"
-          type="email"
-          v-model="email"
-          placeholder="Email address"
-          name="EMAIL"
-          class="subscribe-input" />
-
-        <ul style="display: none;" v-if="interests.length > 0">
-          <li v-for="(interest, index) in interests" :key="index">
-            <input
-              type="checkbox"
-              :checked="interest.checked"
-              :value="interest.id"
-              :name="`group[${interest.group}][${interest.id}]`"
-              :id="`mce-group[${interest.group}]-${interest.group}-${index}`">
-            <label :for="`mce-group[${interest.group}]-${interest.group}-${index}`">{{ interest.label }}</label>
-          </li>
-        </ul>
-
-        <div id="mce-responses" class="clear">
-          <div class="response" id="mce-error-response" style="display:none"></div>
-          <div class="response" id="mce-success-response" style="display:none"></div>
-        </div>
-        <div style="position: absolute; left: -5000px;" aria-hidden="true">
-          <input type="text" name="b_59874b4d6910fa65e724a4648_613837077f" tabindex="-1" value="">
-        </div>
-
-        <input
-          id="mc-embedded-subscribe"
-          :class="{ button: true, disabled: !email }"
-          :disabled="!email"
-          type="submit"
-          :value="buttonLabel"
-          name="subscribe" />
-      </form>
-    </div>
-  </div>
-</template>
-
-<script>
-
-export default {
-  props: {
-    buttonLabel: {
-      type: String,
-      default: 'Subscribe',
-    },
-    customStyles: {
-      type: Object,
-      default: () => ({
-        width: '90%',
-      }),
-    },
-    interests: {
-      type: Array,
-      default: () => ([]),
-    },
-    hideInterests: {
-      type: Boolean,
-      default: true,
-    },
-    title: {
-      type: String,
-      default: 'Get the latest updates',
-    },
-    theme: {
-      type: String,
-      default: 'light',
-    },
-  },
-  data() {
-    return {
-      email: '',
-    };
-  },
-};
-</script>
-
-<style lang="scss">
-@import '../styles/index.scss';
-@import '../styles/palette.scss';
-@import '@vuepress/plugin-palette/palette';
-.subscribe {
-  margin: auto;
-  width: 90%;
-  padding: 2em 0;
-  text-align: center;
-  h3 {
-    color: $landoPink;
-  }
-  &.subscribe-dark {
-    background-color: darken($landoBlue, 12%);
-    h3 {
-      color: lighten($landoBlue, 90%);
-    }
-  }
-  .button {
-    text-transform: uppercase;
-    background-color: $landoPink;
-    margin: 1em 0;
-    font-size: 1.2em;
-    font-weight: 500;
-    letter-spacing: .05em;
-    min-width: 8em;
-    text-align: center;
-    &:not(:last-child) {
-      margin-right: 1%;
-    }
-    &.disabled {
-      opacity: .5;
-    }
-  }
-  .hidden-field {
-    visibility: hidden;
-  }
-  .subscribe-alliance,
-  .subscribe-devnetwork,
-  .subscribe-sponsors {
-    padding-top: 2em;
-    padding-bottom: 2em;
-    p {
-      color: lighten($landoBlue, 90%);
-      font-size: 1.2em;
-    }
-    .subscribe-alliance-wrapper,
-    .subscribe-devnetwork-checkbox,
-    .subscribe-sponsors-wrapper {
-      padding-top: 1em;
-      padding-bottom: 1em;
-      input.subscribe-alliance-checkbox {
-        font-size: 16px;
-      }
-      label {
-        cursor: pointer;
-        color: lighten($landoBlue, 90%);
-        font-size: 2em;
-        font-weight: 800;
-      }
-      small {
-        font-family: "Source Sans Pro", "Helvetica Neue", Arial, sans-serif;
-        color: lighten($landoBlue, 90%);
-        text-align: center;
-        font-size: 1.4em;
-        letter-spacing: 0;
-      }
-    }
-    .subscribe-devnetwork-checkbox {
-      padding-top: .5em;
-      padding-bottom: .5em;
-      label {
-        font-size: 1em;
-      }
-    }
-  }
-  .subscribe-input {
-    width: 100%;
-    box-sizing: border-box;
-    padding: 10px 80px 10px 20px;
-    margin-bottom: 1em;
-    height: 50px;
-    border-radius: 50px;
-    border: 1px solid #ccc;
-    font-size: 16px;
-    background-color: lighten($landoBlue, 96%);
-    &:focus {
-      outline: none;
-      border-color: lighten($landoPink, 18%);
-    }
-    &.disabled {
-      opacity: .5;
-    }
-  }
-
-  .subscribe-error,
-  .subscribe-success {
-    padding: 1em;
-    color: red;
-    text-transform: uppercase;
-    font-weight: 800;
-    font-size: 0.75rem;
-    .subscribe-success {
-      color: $landoPink
-    }
-  }
-}
-
-@media (max-width: $MQMobile) {
-  .subscribe {
-    .subscribe-input {
-      width: 90%;
-    }
-  }
-}
-
-</style>
diff --git a/docs/.vuepress/theme/components/TeamMember.vue b/docs/.vuepress/theme/components/TeamMember.vue
deleted file mode 100644
index a8bc08f..0000000
--- a/docs/.vuepress/theme/components/TeamMember.vue
+++ /dev/null
@@ -1,149 +0,0 @@
-<template>
-  <div class="team-member">
-    <div class="team-member-pic">
-      <img :src="member.pic" :alt="member.name" />
-    </div>
-    <div class="team-member-bio">
-      <h2>{{ member.name }}</h2>
-      <div class="team-member-title">{{ member.title }}</div>
-      <p v-html="member.bio"></p>
-      <p class="team-member-helps" v-if="member.role">HELPS WITH: {{ helpText }}</p>
-    </div>
-    <div class="team-member-details">
-      <ul>
-        <li v-if="member.location">
-          <div class="social-icon">
-            <span class="detail-label">{{ member.location }}</span>
-            <svg xmlns="http://www.w3.org/2000/svg" aria-hidden="true" focusable="false" data-prefix="fas" data-icon="map-marker-alt" class="svg-inline--fa fa-map-marker-alt fa-w-12" role="img" viewBox="0 0 384 512"><path fill="currentColor" d="M172.268 501.67C26.97 291.031 0 269.413 0 192 0 85.961 85.961 0 192 0s192 85.961 192 192c0 77.413-26.97 99.031-172.268 309.67-9.535 13.774-29.93 13.773-39.464 0zM192 272c44.183 0 80-35.817 80-80s-35.817-80-80-80-80 35.817-80 80 35.817 80 80 80z"/></svg>
-          </div>
-        </li>
-        <li v-if="member.github">
-          <a class="social-icon" :href="githubUrl" target="_blank">
-            <span class="detail-label">{{ member.github }}</span>
-            <svg aria-labelledby="simpleicons-github-icon" role="img" viewBox="0 0 24 24" xmlns="http://www.w3.org/2000/svg"><title id="simpleicons-github-icon" lang="en">GitHub icon</title><path d="M12 .297c-6.63 0-12 5.373-12 12 0 5.303 3.438 9.8 8.205 11.385.6.113.82-.258.82-.577 0-.285-.01-1.04-.015-2.04-3.338.724-4.042-1.61-4.042-1.61C4.422 18.07 3.633 17.7 3.633 17.7c-1.087-.744.084-.729.084-.729 1.205.084 1.838 1.236 1.838 1.236 1.07 1.835 2.809 1.305 3.495.998.108-.776.417-1.305.76-1.605-2.665-.3-5.466-1.332-5.466-5.93 0-1.31.465-2.38 1.235-3.22-.135-.303-.54-1.523.105-3.176 0 0 1.005-.322 3.3 1.23.96-.267 1.98-.399 3-.405 1.02.006 2.04.138 3 .405 2.28-1.552 3.285-1.23 3.285-1.23.645 1.653.24 2.873.12 3.176.765.84 1.23 1.91 1.23 3.22 0 4.61-2.805 5.625-5.475 5.92.42.36.81 1.096.81 2.22 0 1.606-.015 2.896-.015 3.286 0 .315.21.69.825.57C20.565 22.092 24 17.592 24 12.297c0-6.627-5.373-12-12-12"></path></svg>
-          </a>
-        </li>
-        <li v-if="member.twitter">
-          <a class="social-icon" :href="twitterUrl" target="_blank">
-            <span class="detail-label">@{{ member.twitter }}</span>
-            <svg aria-labelledby="simpleicons-twitter-icon" role="img" viewBox="0 0 24 24" xmlns="http://www.w3.org/2000/svg"><title id="simpleicons-twitter-icon" lang="en">Twitter icon</title><path d="M23.954 4.569c-.885.389-1.83.654-2.825.775 1.014-.611 1.794-1.574 2.163-2.723-.951.555-2.005.959-3.127 1.184-.896-.959-2.173-1.559-3.591-1.559-2.717 0-4.92 2.203-4.92 4.917 0 .39.045.765.127 1.124C7.691 8.094 4.066 6.13 1.64 3.161c-.427.722-.666 1.561-.666 2.475 0 1.71.87 3.213 2.188 4.096-.807-.026-1.566-.248-2.228-.616v.061c0 2.385 1.693 4.374 3.946 4.827-.413.111-.849.171-1.296.171-.314 0-.615-.03-.916-.086.631 1.953 2.445 3.377 4.604 3.417-1.68 1.319-3.809 2.105-6.102 2.105-.39 0-.779-.023-1.17-.067 2.189 1.394 4.768 2.209 7.557 2.209 9.054 0 13.999-7.496 13.999-13.986 0-.209 0-.42-.015-.63.961-.689 1.8-1.56 2.46-2.548l-.047-.02z"></path></svg>
-          </a>
-        </li>
-      </ul>
-    </div>
-  </div>
-</template>
-
-<script>
-export default {
-  props: ['member'],
-  computed: {
-    githubUrl() {
-      return `https://github.com/${this.member.github}`;
-    },
-    twitterUrl() {
-      return `https://twitter.com/${this.member.twitter}`;
-    },
-    helpText() {
-      const lowered = this.member.role.map(item => item.toLowerCase());
-      let ender = '.';
-      if (lowered.length > 1) {
-        ender = ` and ${lowered[lowered.length - 1]}.`;
-        lowered.pop();
-      }
-      return `${lowered.join(', ')}${ender}`;
-    },
-  },
-};
-</script>
-
-<style lang="scss">
-@import '../styles/index.scss';
-@import '../styles/palette.scss';
-@import '@vuepress/plugin-palette/palette';
-.team-member {
-  padding-bottom: 2rem;
-  padding-top: 2rem;
-  border-bottom: 1px dotted #ddd;
-  display: flex;
-  margin: auto;
-  &:last-child {
-    border: none;
-  }
-  .team-member-pic,
-  .team-member-bio,
-  .team-member-details {
-    display: inline-block;
-  }
-  .team-member-pic {
-    width: 15%;
-    img {
-      border-radius: 100%;
-    }
-  }
-  .team-member-bio {
-    width: 55%;
-    h2 {
-      font-size: 1.4rem;
-      border: 0;
-      margin: 0;
-    }
-  }
-  .team-member-details {
-    text-align: right;
-    width: 30%;
-    ul {
-      margin: .25em;
-      list-style: none;
-    }
-    .detail-label {
-      text-transform: uppercase;
-      font-weight: 800;
-      font-size: 0.75rem;
-      color: $landoGrey;
-      position: relative;
-      top: -7px;
-      right: 4px;
-    }
-  }
-  .team-member-title,
-  .team-member-helps {
-    text-transform: uppercase;
-    font-weight: 800;
-    font-size: 0.75rem;
-    color: $landoPink;
-  }
-  .team-member-helps {
-    color: lighten($landoGrey, 25%);
-  }
-  .social-icon {
-    svg {
-      width: 24px;
-      height: 24px;
-      color: $landoPink;
-      fill: $landoPink;
-    }
-  }
-}
-
-@media (max-width: $MQMobile) {
-  .team-member {
-    display: block;
-    text-align: center;
-    .team-member-pic,
-    .team-member-bio,
-    .team-member-details {
-      display: block;
-      width: 100%;
-    }
-    .team-member-details {
-      width: 100%;
-      margin: auto;
-      ul {
-        text-align: center;
-      }
-    }
-  }
-}
-
-</style>
diff --git a/docs/.vuepress/theme/index.js b/docs/.vuepress/theme/index.js
deleted file mode 100644
index f60b6a6..0000000
--- a/docs/.vuepress/theme/index.js
+++ /dev/null
@@ -1,42 +0,0 @@
-const {path} = require('@vuepress/utils');
-
-module.exports = (options, app) => {
-  // console.log(options);
-
-  // Define default options
-  const defaultOptions = {
-    // Shows the CarbonAds in the top sidebar
-    showCarbonAds: true,
-    // Shows the special sponsors on the right
-    // Can be true|false|or a list of sponsors to show
-    showSponsors: true,
-    // Metadata for our sponsors
-    // sponsors:
-  };
-
-  // Merge together
-  options = {...defaultOptions, ...options};
-  console.log(options);
-
-  return {
-    name: '@lando/vuepress-docs-theme',
-    extends: '@vuepress/theme-default',
-    layouts: path.resolve(__dirname, 'layouts'),
-    // alias: {
-    //   // replace the Navbar component
-    //   '@theme/Navbar.vue': path.resolve(__dirname, 'components/CustomNavbar.vue'),
-    // },
-    // extendsMarkdown: md => {
-    //   console.log('hi');
-    //   console.log(md.renderer);
-    // },
-    // extendsPageData: page => {
-    // },
-    plugins: [
-      [
-        '@vuepress/plugin-palette',
-        {preset: 'sass'},
-      ],
-    ],
-  };
-};
diff --git a/docs/.vuepress/theme/layouts/404.vue b/docs/.vuepress/theme/layouts/404.vue
deleted file mode 100644
index 52547f2..0000000
--- a/docs/.vuepress/theme/layouts/404.vue
+++ /dev/null
@@ -1,16 +0,0 @@
-<template>
-  <ParentLayout></ParentLayout>
-</template>
-
-<script>
-import ParentLayout from '@vuepress/theme-default/lib/client/layouts/404.vue'
-
-export default {
-  components: {ParentLayout},
-};
-</script>
-
-<style lang="scss">
-@import '../styles/index.scss';
-@import '@vuepress/plugin-palette/palette';
-</style>
diff --git a/docs/.vuepress/theme/layouts/Layout.vue b/docs/.vuepress/theme/layouts/Layout.vue
deleted file mode 100644
index 18c6259..0000000
--- a/docs/.vuepress/theme/layouts/Layout.vue
+++ /dev/null
@@ -1,31 +0,0 @@
-<template>
-  <ParentLayout>
-    <template #sidebar-top>
-      <CarbonAds v-if="showCarbonAds" />
-    </template>
-    <template #page-top>
-      <Sponsors v-if="showSponsors" />
-    </template>
-  </ParentLayout>
-</template>
-
-<script setup>
-import { computed } from 'vue'
-import ParentLayout from '@vuepress/theme-default/lib/client/layouts/Layout.vue'
-import CarbonAds from '../components/CarbonAds.vue';
-import Sponsors from '../components/Sponsors.vue';
-import { useThemeData } from '@vuepress/plugin-theme-data/lib/client'
-
-// Get theme data
-const themeData = useThemeData();
-// Get the config from themedata
-const {showCarbonAds = true} = themeData.value;
-const {showSponsors = true} = themeData.value;
-
-</script>
-
-<style lang="scss">
-@import '../styles/index.scss';
-@import '../styles/palette.scss';
-@import '@vuepress/plugin-palette/palette';
-</style>
diff --git a/docs/.vuepress/theme/styles/index.scss b/docs/.vuepress/theme/styles/index.scss
deleted file mode 100644
index 527837c..0000000
--- a/docs/.vuepress/theme/styles/index.scss
+++ /dev/null
@@ -1,175 +0,0 @@
-:root {
-  // brand colors
-  --c-brand: #ed3f7a;
-  --c-brand-light: #f26f9b;
-
-  // background colors
-  --c-bg: #ffffff;
-  --c-bg-light: #f3f4f5;
-  --c-bg-lighter: #eeeeee;
-  --c-bg-navbar: var(--c-bg);
-  --c-bg-sidebar: var(--c-bg);
-  --c-bg-arrow: #cccccc;
-
-  // text colors
-  --c-text: #2c3e50;
-  --c-text-accent: var(--c-brand);
-  --c-text-light: #3a5169;
-  --c-text-lighter: #4e6e8e;
-  --c-text-lightest: #6a8bad;
-  --c-text-quote: #999999;
-
-  // border colors
-  --c-border: #eaecef;
-  --c-border-dark: #dfe2e5;
-
-  // custom container colors
-  --c-tip: #42b983;
-  --c-tip-bg: var(--c-bg-light);
-  --c-tip-title: var(--c-text);
-  --c-tip-text: var(--c-text);
-  --c-tip-text-accent: var(--c-text-accent);
-  --c-warning: #e7c000;
-  --c-warning-bg: #fffae3;
-  --c-warning-title: #ad9000;
-  --c-warning-text: #746000;
-  --c-warning-text-accent: var(--c-text);
-  --c-danger: #cc0000;
-  --c-danger-bg: #ffe0e0;
-  --c-danger-title: #990000;
-  --c-danger-text: #660000;
-  --c-danger-text-accent: var(--c-text);
-  --c-details-bg: #eeeeee;
-
-  // badge component colors
-  --c-badge-tip: var(--c-tip);
-  --c-badge-warning: var(--c-warning);
-  --c-badge-danger: var(--c-danger);
-
-  // transition vars
-  --t-color: 0.3s ease;
-  --t-transform: 0.3s ease;
-
-  // code blocks vars
-  --code-bg-color: #282c34;
-  --code-hl-bg-color: rgba(0, 0, 0, 0.66);
-  --code-ln-color: #9e9e9e;
-  --code-ln-wrapper-width: 3.5rem;
-
-  // font vars
-  --font-family: -apple-system, BlinkMacSystemFont, 'Segoe UI', Roboto, Oxygen,
-    Ubuntu, Cantarell, 'Fira Sans', 'Droid Sans', 'Helvetica Neue', sans-serif;
-  --font-family-code: Consolas, Monaco, 'Andale Mono', 'Ubuntu Mono', monospace;
-
-  // layout vars
-  --navbar-height: 3.6rem;
-  --navbar-padding-v: 0.7rem;
-  --navbar-padding-h: 1.5rem;
-  --sidebar-width: 20rem;
-  --sidebar-width-mobile: calc(var(--sidebar-width) * 0.82);
-  --content-width: 740px;
-  --homepage-width: 960px;
-}
-
-// plugin-back-to-top
-.back-to-top {
-  --back-to-top-color: var(--c-brand);
-  --back-to-top-color-hover: var(--c-brand-light);
-}
-
-// plugin-docsearch
-.DocSearch {
-  --docsearch-primary-color: var(--c-brand);
-  --docsearch-text-color: var(--c-text);
-  --docsearch-highlight-color: var(--c-brand);
-  --docsearch-muted-color: var(--c-text-quote);
-  --docsearch-container-background: rgba(9, 10, 17, 0.8);
-  --docsearch-modal-background: var(--c-bg-light);
-  --docsearch-searchbox-background: var(--c-bg-lighter);
-  --docsearch-searchbox-focus-background: var(--c-bg);
-  --docsearch-searchbox-shadow: inset 0 0 0 2px var(--c-brand);
-  --docsearch-hit-color: var(--c-text-light);
-  --docsearch-hit-active-color: var(--c-bg);
-  --docsearch-hit-background: var(--c-bg);
-  --docsearch-hit-shadow: 0 1px 3px 0 var(--c-border-dark);
-  --docsearch-footer-background: var(--c-bg);
-}
-
-// plugin-medium-zoom
-.medium-zoom-overlay {
-  --medium-zoom-bg-color: var(--c-bg);
-}
-
-// plugin-nprogress
-#nprogress {
-  --nprogress-color: var(--c-brand);
-}
-
-// plugin-pwa-popup
-.pwa-popup {
-  --pwa-popup-text-color: var(--c-text);
-  --pwa-popup-bg-color: var(--c-bg);
-  --pwa-popup-border-color: var(--c-brand);
-  --pwa-popup-shadow: 0 4px 16px var(--c-brand);
-  --pwa-popup-btn-text-color: var(--c-bg);
-  --pwa-popup-btn-bg-color: var(--c-brand);
-  --pwa-popup-btn-hover-bg-color: var(--c-brand-light);
-}
-
-// plugin-search
-.search-box {
-  --search-bg-color: var(--c-bg);
-  --search-accent-color: var(--c-brand);
-  --search-text-color: var(--c-text);
-  --search-border-color: var(--c-border);
-
-  --search-item-text-color: var(--c-text-lighter);
-  --search-item-focus-bg-color: var(--c-bg-light);
-}
-
-html.dark {
-  // brand colors
-  --c-brand: #ed3f7a;
-  --c-brand-light: #f26f9b;
-
-  // background colors
-  --c-bg: #22272e;
-  --c-bg-light: #2b313a;
-  --c-bg-lighter: #262c34;
-
-  // text colors
-  --c-text: #adbac7;
-  --c-text-light: #96a7b7;
-  --c-text-lighter: #8b9eb0;
-  --c-text-lightest: #8094a8;
-
-  // border colors
-  --c-border: #3e4c5a;
-  --c-border-dark: #34404c;
-
-  // custom container colors
-  --c-tip: #318a62;
-  --c-warning: #ceab00;
-  --c-warning-bg: #7e755b;
-  --c-warning-title: #ceac03;
-  --c-warning-text: #362e00;
-  --c-danger: #940000;
-  --c-danger-bg: #806161;
-  --c-danger-title: #610000;
-  --c-danger-text: #3a0000;
-  --c-details-bg: #323843;
-
-  // code blocks vars
-  --code-hl-bg-color: #363b46;
-}
-
-// plugin-docsearch
-html.dark .DocSearch {
-  --docsearch-logo-color: var(--c-text);
-  --docsearch-modal-shadow: inset 1px 1px 0 0 #2c2e40, 0 3px 8px 0 #000309;
-  --docsearch-key-shadow: inset 0 -2px 0 0 #282d55, inset 0 0 1px 1px #51577d,
-    0 2px 2px 0 rgba(3, 4, 9, 0.3);
-  --docsearch-key-gradient: linear-gradient(-225deg, #444950, #1c1e21);
-  --docsearch-footer-shadow: inset 0 1px 0 0 rgba(73, 76, 106, 0.5),
-    0 -4px 8px 0 rgba(0, 0, 0, 0.2);
-}
diff --git a/docs/.vuepress/theme/styles/palette.scss b/docs/.vuepress/theme/styles/palette.scss
deleted file mode 100644
index f50b3a9..0000000
--- a/docs/.vuepress/theme/styles/palette.scss
+++ /dev/null
@@ -1,17 +0,0 @@
-// More things
-$landoPink: #ed3f7a;
-$landoGrey: #47474A;
-$landoBlue: #035785;
-$landoOrange: #FF7042;
-$landoGreen: #00A38F;
-$landoGrey: #2c3e50;
-
-// responsive breakpoints
-$MQNarrow: 959px !default;
-$MQMobile: 719px !default;
-$MQMobileNarrow: 419px !default;
-
-// code languages
-$codeLang: 'c' 'cpp' 'cs' 'css' 'dart' 'docker' 'fs' 'go' 'html' 'java' 'js'
-  'json' 'kt' 'less' 'makefile' 'md' 'php' 'py' 'rb' 'rs' 'sass' 'scss' 'sh'
-  'styl' 'ts' 'toml' 'vue' 'yml' !default;
diff --git a/package.json b/package.json
index 9e4dd7d..0284ccd 100644
--- a/package.json
+++ b/package.json
@@ -49,6 +49,7 @@
   "devDependencies": {
     "@babel/eslint-parser": "^7.16.0",
     "@lando/leia": "^0.6.4",
+    "@lando/vuepress-docs-theme": "^0.1.2",
     "@vuepress/plugin-docsearch": "^2.0.0-beta.27",
     "@vuepress/plugin-register-components": "^2.0.0-beta.27",
     "chai": "^4.3.4",
diff --git a/yarn.lock b/yarn.lock
index 8a69599..17c0686 100644
--- a/yarn.lock
+++ b/yarn.lock
@@ -448,6 +448,14 @@
     mocha "^5.2.0"
     object-hash "^2.2.0"
 
+"@lando/vuepress-docs-theme@^0.1.2":
+  version "0.1.2"
+  resolved "https://registry.yarnpkg.com/@lando/vuepress-docs-theme/-/vuepress-docs-theme-0.1.2.tgz#16a0e9f8f8cb98bd7874ad95202922567db6e737"
+  integrity sha512-7GyjQXtJ9wbf0I3EKeIliWJC2i8aOss30pl+BrLrfI00Ut5tuWaZv8IqSCM2beZci+WRqqKGeGzFDMq51b+dBg==
+  dependencies:
+    js-yaml "^3.4.6"
+    lodash "^4.17.21"
+
 "@nodelib/fs.scandir@2.1.5":
   version "2.1.5"
   resolved "https://registry.yarnpkg.com/@nodelib/fs.scandir/-/fs.scandir-2.1.5.tgz#7619c2eb21b25483f6d167548b4cfd5a7488c3d5"

From 0d9fee524b31c832a6bb5cf0f22b872fc6e66421 Mon Sep 17 00:00:00 2001
From: John Ouellet <john@thinktandem.io>
Date: Mon, 8 Nov 2021 10:40:58 -0500
Subject: [PATCH 16/16] #130 Add in new repo for theme

---
 docs/.vuepress/config.js | 2 +-
 package.json             | 2 +-
 yarn.lock                | 8 ++++----
 3 files changed, 6 insertions(+), 6 deletions(-)

diff --git a/docs/.vuepress/config.js b/docs/.vuepress/config.js
index 5c8d4dc..868e8f5 100644
--- a/docs/.vuepress/config.js
+++ b/docs/.vuepress/config.js
@@ -10,7 +10,7 @@ module.exports = {
     ['link', {rel: 'icon', href: '/favicon.ico'}],
     ['link', {rel: 'stylesheet', href: '//fonts.googleapis.com/css?family=Poppins:700|Source+Sans+Pro&display=swap'}],
   ],
-  theme: '@lando/vuepress-docs-theme',
+  theme: '@lando/vuepress-theme-lando-docs',
   themeConfig: {
     logo: '/images/logo-pink-small.png',
     repo: 'lando/platformsh',
diff --git a/package.json b/package.json
index 0284ccd..476fdd0 100644
--- a/package.json
+++ b/package.json
@@ -49,7 +49,7 @@
   "devDependencies": {
     "@babel/eslint-parser": "^7.16.0",
     "@lando/leia": "^0.6.4",
-    "@lando/vuepress-docs-theme": "^0.1.2",
+    "@lando/vuepress-theme-lando-docs": "^0.2.0",
     "@vuepress/plugin-docsearch": "^2.0.0-beta.27",
     "@vuepress/plugin-register-components": "^2.0.0-beta.27",
     "chai": "^4.3.4",
diff --git a/yarn.lock b/yarn.lock
index 17c0686..9ea6dfc 100644
--- a/yarn.lock
+++ b/yarn.lock
@@ -448,10 +448,10 @@
     mocha "^5.2.0"
     object-hash "^2.2.0"
 
-"@lando/vuepress-docs-theme@^0.1.2":
-  version "0.1.2"
-  resolved "https://registry.yarnpkg.com/@lando/vuepress-docs-theme/-/vuepress-docs-theme-0.1.2.tgz#16a0e9f8f8cb98bd7874ad95202922567db6e737"
-  integrity sha512-7GyjQXtJ9wbf0I3EKeIliWJC2i8aOss30pl+BrLrfI00Ut5tuWaZv8IqSCM2beZci+WRqqKGeGzFDMq51b+dBg==
+"@lando/vuepress-theme-lando-docs@^0.2.0":
+  version "0.2.0"
+  resolved "https://registry.yarnpkg.com/@lando/vuepress-theme-lando-docs/-/vuepress-theme-lando-docs-0.2.0.tgz#5d09c07896acbe6a31eb76270237e01c9a5456da"
+  integrity sha512-zE1yOpMMHeBEaDvXoi60VpAhqRyDmOTvzEWzD7Reg1gXTXXE3Xu1OI6PexhWgMY2+gqFRG7l6hxXo40AbQJ4qA==
   dependencies:
     js-yaml "^3.4.6"
     lodash "^4.17.21"