add lando to path guide

docs/.vitepress/config.mjs

@@ -83,6 +83,7 @@ function sidebar() {
         {text: 'Contact Us', link: '/support'},
       ],
     },
+    {text: 'Guides', link: '/guides'},
     {text: 'Examples', link: 'https://github.com/lando/cli/tree/main/examples'},
   ];
 };

docs/guides.md

@@ -0,0 +1,25 @@
+---
+description: Home helpful generic tutorial and guide content for Lando CLI
+layout: page
+title: Guides
+sidebar: false
+---
+<VPLCollectionPage>
+  <VPLCollectionPageTitle>
+    <template #title>
+      Guides
+    </template>
+    <template #lead>
+      Some Lando CLI tutorials and guides
+    </template>
+  </VPLCollectionPageTitle>
+  <VPLCollectionPageTags v-model="tags" />
+  <VPLCollectionItems :tags="tags" :items="pages"/>
+</VPLCollectionPage>
+
+<script setup>
+import {VPLCollectionPage, VPLCollectionPageTags, VPLCollectionPageTitle, VPLCollectionItems} from '@lando/vitepress-theme-default-plus';
+import {useCollection} from '@lando/vitepress-theme-default-plus';
+
+const {pages, tags} = useCollection('guide');
+</script>

docs/guides/adding-lando-2-path.md

@@ -0,0 +1,88 @@
+---
+title: Adding Lando to PATH
+description: Learn how to add Lando to PATH in the event that hasn't been automatically done for you.
+guide: true
+
+authors:
+  - name: Team Lando
+    pic: https://gravatar.com/avatar/c335f31e62b453f747f39a84240b3bbd
+    link: https://twitter.com/devwithlando
+updated:
+  timestamp: 1709049201359
+
+mailchimp:
+  # action is required
+  action: https://dev.us12.list-manage.com/subscribe/post?u=59874b4d6910fa65e724a4648&id=613837077f
+  # everything else is optional
+  title: Want similar content?
+  byline: Signup and we will send you a weekly blog digest of similar content to keep you satiated.
+  button: Sign me up!
+---
+
+# Adding Lando to PATH
+
+Lando _should_ be added to your `PATH` environment variable when you install or update it. When an executable is in `PATH` you can invoke it by name instead of by its path as in this example:
+
+```sh
+# lando is in PATH
+lando start
+
+# lando is not in PATH
+/my/weird/place/for/stuff/lando start
+```
+
+However, there are some situations where Lando may not be automatically added to `PATH`. For those situations you can use [`lando shellenv`](../shellenv.md) and do the below:
+
+## Checking if Lando is in `PATH`
+
+The most straightforward way to check is to simply run `lando` from a terminal and see if it returns the `lando` command list.
+
+You can also do things like:
+
+::: code-group
+```sh [sh]
+which lando
+```
+
+```bat [cmd.exe]
+where lando
+```
+
+```powershell [powershell]
+Get-Command lando
+```
+:::
+
+If any of them fail or return nothing then congrats :tada: because `lando` is not in your `PATH`! :(
+
+## Adding Lando to `PATH`
+
+To add `lando` to `PATH` you first need to figure out the absolute path to the Lando binary. For the purposes of this we will assume the user has directly downloaded the Lando CLI to a special directory they created called `/all/my/bin`.
+
+Here are a few ways you can use `lando shellenv` to add `lando` to `PATH`. Note that because `lando` is not in `PATH` you must invoke it using its absolute path.
+
+```sh
+# print the shellenv i need so i can copy/paste it to the relevant rc file
+/all/my/bin/lando shellenv
+
+# have lando attempt to add the shellenv to a shell rc file it thinks make sense
+/all/my/bin/lando shellenv --add
+
+# have lando add the shellenv to a file you want
+/all/my/bin/lando shellenv --add ~/.specialrc
+
+# directly append the output of shellenv to a file
+/all/my/bin/lando shellenv >> ~/.anotherrc
+```
+
+Note that after any of the above commands you must either directly `source` the shell rc file that was edited or open a new terminal for the changes to apply. An example for most `macOS` users would be something like
+
+```sh
+source ~/.zshrc
+```
+
+You can then verify all is good with:
+
+```sh
+lando shellenv --check
+```