chore: Added more aliases

Signed-off-by: Steven Gettys <steven.gettys@gmail.com>

Author: sgettys

docs/content/docs/operations/_index.md

@@ -2,6 +2,8 @@
 title: "Operations"
 description: ""
 weight: 5
+aliases:
+  - /operations/
 ---
 
 **Get Started with Porter**

docs/content/docs/operations/connect-to-docker.md

@@ -2,6 +2,8 @@
 title: Connect to Docker
 description: Configure Porter to authenticate and connect to a Docker engine
 weight: 5
+aliases:
+  - /operations/connect-to-docker/
 ---
 
 Some Porter commands connect to a Docker engine in order to build, push, and pull the bundle image.

docs/content/docs/operations/connect-to-registry.md

@@ -2,6 +2,8 @@
 title: Connect to a Registry
 description: Configure Porter to authenticate and connect to a registry
 weight: 6
+aliases:
+  - /operations/connect-to-registry/
 ---
 
 Porter stores bundles in OCI (Docker) registries.

docs/content/docs/operations/create-porter-config.md

@@ -2,6 +2,8 @@
 title: Create a Porter Config File
 description: Learn how to customize Porter's default behavior through configuration file
 weight: 4
+aliases:
+  - /operations/create-porter-config/
 ---
 
 Porter's default behavior, such as log level and default plugins, can be modified through its config file.

docs/content/docs/operations/examine-bundles.md

@@ -4,6 +4,7 @@ description: Figure out how to use a bundle
 weight: 2
 aliases:
   - /examining-bundles/
+  - /operations/examine-bundles/
 ---
 
 Once a bundle has been built, how do users of the bundle figure out how to actually _use_ it? A user could read the `porter.yaml` or the `bundle.json` if they have the bundle locally, but this won't work for a bundle that has been published to an OCI registry. Even when you have them locally, the `bundle.json` and `porter.yaml` aren't the best way to figure out how to use a bundle. How should a user examine the bundle then? Porter has a command called `explain` to help with this!

docs/content/docs/operations/manage-installations.md

@@ -2,6 +2,8 @@
 title: Manage Installations
 description: Manage bundle installations with Porter
 weight: 1
+aliases:
+  - /operations/manage-installations/
 ---
 
 When a bundle is installed, an **installation** is created.

docs/content/docs/operations/view-logs.md

@@ -4,6 +4,7 @@ description: View logs from previous runs of Porter
 weight: 3
 aliases:
   - operators/logs/
+  - /operations/view-logs/
 ---
 
 You can view the logs from the most recent execution of a bundle with the

docs/content/docs/quickstart/_index.md

@@ -2,6 +2,8 @@
 title: "Quickstart"
 description: ""
 weight: 2
+aliases:
+  - /quickstart/
 ---
 
 {{< cards >}}

docs/content/docs/quickstart/bundles.md

@@ -1,6 +1,8 @@
 ---
 title: "Bundles"
 descriptions: Learn about bundles and how to install them with Porter
+aliases:
+  - /quickstart/bundles/
 ---
 
 So you're interested in learning more about Porter? Great! This guide will walk you through key concepts of managing bundles. You will use the porter CLI to install, upgrade, and uninstall the bundle.

docs/content/docs/quickstart/configuration.md

@@ -2,6 +2,8 @@
 title: "Configuration"
 descriptions: Control Porter's behavior with its config file
 layout: single
+aliases:
+  - /quickstart/configuration/
 ---
 
 You now know how to install a bundle, passing in a credential or parameter set

docs/content/docs/quickstart/credentials.md

@@ -2,6 +2,8 @@
 title: "Credentials"
 descriptions: Learn how to use a bundle with credentials
 layout: single
+aliases:
+  - /quickstart/credentials/
 ---
 
 Now that you know how to customize a bundle installation with parameters, let's look at how your bundle can authenticate with **credentials**.

docs/content/docs/quickstart/desired-state.md

@@ -2,6 +2,8 @@
 title: "Desired State"
 descriptions: Manage an installation by defining its desired state in a file
 layout: single
+aliases:
+  - /quickstart/desired-state/
 ---
 
 You now know how to install a bundle, passing in a credential or parameter set.

docs/content/docs/quickstart/parameters.md

@@ -1,6 +1,8 @@
 ---
 title: "Parameters"
 descriptions: Learn how to use a bundle with parameters
+aliases:
+  - /quickstart/parameters/
 ---
 
 Now that you know how to install a bundle, let's look at how to specify parameters to customize how that bundle is installed.