DOCS-2772: Rename use cases to how tos (#3258)

Author: sguequierre

assets/use-cases/base-control.png assets/how-tos/base-control.png

@@ -30,42 +30,42 @@ carouselscript: true
       </a>
 </div>
 <div class="col hover-card link-with-icon">
-  <a href="use-cases/configure/" class="noanchor"><div>
+  <a href="how-tos/configure/" class="noanchor"><div>
     <picture><img src="icons/build.svg" alt="Build" loading="lazy"></picture>
     <p>Build simple smart machines</p></div>
       </a>
 </div>
 <div class="col hover-card link-with-icon">
-  <a href="use-cases/image-data/" class="noanchor"><div>
+  <a href="how-tos/image-data/" class="noanchor"><div>
     <picture><img src="icons/data.svg" alt="Data Management" loading="lazy"></picture>
     <p>Capture and sync image data</p></div>
       </a>
 </div>
 <div class="col hover-card link-with-icon">
-  <a href="use-cases/collect-sensor-data/" class="noanchor"><div>
+  <a href="how-tos/collect-sensor-data/" class="noanchor"><div>
     <picture><img src="icons/data-analytics.svg" alt="Data Analytics" loading="lazy"></picture>
     <p>Capture and sync sensor data</p></div>
       </a>
 </div>
 <div class="col hover-card link-with-icon">
-  <a href="use-cases/create-module/" class="noanchor"><div>
+  <a href="how-tos/create-module/" class="noanchor"><div>
     <picture><img src="icons/code-deployment.svg" alt="Code deployment" loading="lazy"></picture>
     <p>Manage and deploy code versions</p></div>
       </a>
 </div>
 <div class="col hover-card link-with-icon">
-  <a href="use-cases/deploy-ml/" class="noanchor"><div>
+  <a href="how-tos/deploy-ml/" class="noanchor"><div>
     <picture><img src="icons/ml.svg" alt="Machine Learning" loading="lazy"></picture>
     <p>Train and deploy classification models</p></div>
       </a>
 </div>
 <div class="col hover-card link-with-icon">
-  <a href="use-cases/navigate/" class="noanchor"><div>
+  <a href="how-tos/navigate/" class="noanchor"><div>
     <picture><img src="icons/mobility.svg" alt="Mobility" loading="lazy"></picture>
     <p>Teleoperate and navigate with rovers</p></div></a>
   </div>
   <div class="col hover-card link-with-icon">
-    <a href="use-cases/manage-fleet/" class="noanchor"><div>
+    <a href="how-tos/manage-fleet/" class="noanchor"><div>
     <picture><img src="icons/fleet.svg" alt="Fleet" loading="lazy"></picture>
     <p>Manage a fleet of machines</p></div></a>
   </div>
@@ -88,7 +88,7 @@ carouselscript: true
 <div class="cards max-page use-cases">
   <div class="row">
 <div class="col hover-card link-with-icon">
-  <a href="use-cases/" class="noanchor"><div>
+  <a href="how-tos/" class="noanchor"><div>
     <picture><img src="icons/rover.svg" alt="Rover" loading="lazy"></picture>
     <p>How-to Guides</p></div>
   </a>

assets/use-cases/last-online.png assets/how-tos/last-online.png

@@ -196,7 +196,7 @@ Viam has added a [sensor-controlled base](/components/base/sensor-controlled/) c
 
 {{% changelog date="2024-01-31" color="added" title="Visualize captured data" %}}
 
-You can now [visualize your data](/use-cases/sensor-data-visualize/) using many popular third-party visualization tools, including Grafana, Tableau, Google’s Looker Studio, and more.
+You can now [visualize your data](/how-tos/sensor-data-visualize/) using many popular third-party visualization tools, including Grafana, Tableau, Google’s Looker Studio, and more.
 You can visualize any data, such as sensor readings, that you have [synced](/services/data/cloud-sync/) to the Viam app from your machine.
 
 See [Visualize data with Grafana](/tutorials/services/visualize-data-grafana/) for a full walkthrough focused on Grafana specifically.
@@ -242,7 +242,7 @@ Location secrets, the previous method of authentication, is deprecated and will
 
 Once you have added the data management service and synced data, such as sensor readings, to the Viam app, you can now run queries against both captured data as well as its metadata using either SQL or MQL.
 
-For more information, see [Query Data with SQL or MQL](/use-cases/sensor-data-query-with-third-party-tools/).
+For more information, see [Query Data with SQL or MQL](/how-tos/sensor-data-query-with-third-party-tools/).
 
 {{% /changelog %}}
 

assets/use-cases/ml-cycle.svg assets/how-tos/ml-cycle.svg

@@ -1,11 +1,11 @@
 ---
 title: Model Namespace Triplet
 id: model-namespace-triplet
-full_link: /use-cases/create-module/#name-your-new-resource-model
+full_link: /how-tos/create-module/#name-your-new-resource-model
 short_description: namespace:repo-name:name or rdk:builtin:name
 ---
 
 {{< glossary_tooltip term_id="model" text="Models" >}} are uniquely namespaced as colon-delimited-triplets.
 Modular resource model names have the form `namespace:repo-name:name`.
 Built-in model names have the form `rdk:builtin:name`.
-See [Name your new resource model](/use-cases/create-module/#name-your-new-resource-model) for more information.
+See [Name your new resource model](/how-tos/create-module/#name-your-new-resource-model) for more information.

assets/use-cases/ml-vision-diagram.png assets/how-tos/ml-vision-diagram.png

@@ -16,4 +16,4 @@ Models are either included with [`viam-server`](/installation/), provided in {{<
 All models are uniquely namespaced as colon-delimited-triplets.
 Built-in model names have the form `rdk:builtin:name`.
 Modular resource model names have the form `namespace:repo-name:name`.
-See [Name your new resource model](/use-cases/create-module/#name-your-new-resource-model) for more information.
+See [Name your new resource model](/how-tos/create-module/#name-your-new-resource-model) for more information.

assets/use-cases/navigation-card.png assets/how-tos/navigation-card.png

@@ -8,6 +8,6 @@ short_description: A module provides one or more modular resources, which add re
 A _module_ provides one or more {{< glossary_tooltip term_id="modular-resource" text="modular resources" >}}, which add {{< glossary_tooltip term_id="resource" text="resource" >}} {{< glossary_tooltip term_id="type" text="types" >}} or {{< glossary_tooltip term_id="model" text="models" >}} that are not built into Viam.
 Modules run alongside `viam-server` as separate process, communicating with `viam-server` over UNIX sockets.
 
-You can [create your own module](/use-cases/create-module/) or [add existing modules from the Viam registry](/registry/configure/).
+You can [create your own module](/how-tos/create-module/) or [add existing modules from the Viam registry](/registry/configure/).
 
 For more information see the [modular resource documentation](/registry/).

assets/use-cases/new-machine.png assets/how-tos/new-machine.png

@@ -336,8 +336,8 @@ done
 | Command option | Description | Positional arguments |
 | -------------- | ----------- | -------------------- |
 | `export` | Export data in a specified format to a specified location | - |
-| `database configure` | Create a new database user for the Viam organization's MongoDB Atlas Data Federation instance, or change the password of an existing user. See [Configure data query](/use-cases/sensor-data-query-with-third-party-tools/#configure-data-query) | - |
-| `database hostname` | Get the MongoDB Atlas Data Federation instance hostname and connection URI. See [Configure data query](/use-cases/sensor-data-query-with-third-party-tools/#configure-data-query) | - |
+| `database configure` | Create a new database user for the Viam organization's MongoDB Atlas Data Federation instance, or change the password of an existing user. See [Configure data query](/how-tos/sensor-data-query-with-third-party-tools/#configure-data-query) | - |
+| `database hostname` | Get the MongoDB Atlas Data Federation instance hostname and connection URI. See [Configure data query](/how-tos/sensor-data-query-with-third-party-tools/#configure-data-query) | - |
 | `dataset add` | Add a new image to an existing dataset by its file id, or add a group of images by specifying a filter | `filter` |
 | `dataset remove` | Remove an existing image from a dataset by its file id, or remove a group of images by specifying a filter | `filter` |
 | `delete binary` | Delete binary data | - |
@@ -528,10 +528,10 @@ viam module update
 viam module upload --version "1.0.0" --platform "darwin/arm64" packaged-module.tar.gz
 ```
 
-See [Upload a custom module](/use-cases/create-module/#upload-your-module-to-the-modular-resource-registry) and [Update an existing module](/use-cases/manage-modules/#update-an-existing-module) for a detailed walkthrough of the `viam module` commands.
+See [Upload a custom module](/how-tos/create-module/#upload-your-module-to-the-modular-resource-registry) and [Update an existing module](/how-tos/manage-modules/#update-an-existing-module) for a detailed walkthrough of the `viam module` commands.
 
 If you update and release your module as part of a continuous integration (CI) workflow, you can also
-[automatically upload new versions of your module on release](/use-cases/manage-modules/#update-an-existing-module-using-a-github-action) using a GitHub Action.
+[automatically upload new versions of your module on release](/how-tos/manage-modules/#update-an-existing-module-using-a-github-action) using a GitHub Action.
 
 #### Command options
 
@@ -701,12 +701,12 @@ For example, the following represents the configuration of an example `my-module
 ```
 
 {{% alert title="Important" color="note" %}}
-If you are publishing a public module (`"visibility": "public"`), the [namespace of your model](/use-cases/create-module/#name-your-new-resource-model) must match the [namespace of your organization](/cloud/organizations/#create-a-namespace-for-your-organization).
+If you are publishing a public module (`"visibility": "public"`), the [namespace of your model](/how-tos/create-module/#name-your-new-resource-model) must match the [namespace of your organization](/cloud/organizations/#create-a-namespace-for-your-organization).
 In the example above, the model namespace is set to `acme` to match the owning organization's namespace.
 If the two namespaces do not match, the command will return an error.
 {{% /alert %}}
 
-See [Upload a custom module](/use-cases/create-module/#upload-your-module-to-the-modular-resource-registry) and [Update an existing module](/use-cases/manage-modules/#update-an-existing-module) for a detailed walkthrough of the `viam module` commands.
+See [Upload a custom module](/how-tos/create-module/#upload-your-module-to-the-modular-resource-registry) and [Update an existing module](/how-tos/manage-modules/#update-an-existing-module) for a detailed walkthrough of the `viam module` commands.
 
 See [Modular resources](/registry/) for a conceptual overview of modules and the modular resource system at Viam.
 

assets/use-cases/one-to-many/config.png assets/how-tos/one-to-many/config.png

@@ -5,7 +5,7 @@ weight: 40
 type: "docs"
 description: Use fragments to configure many machines at the same time.
 tags: ["fleet management", "cloud", "app"]
-images: ["/use-cases/one-to-many/new-fragment.png"]
+images: ["/how-tos/one-to-many/new-fragment.png"]
 aliases:
   - /fleet/configure-a-fleet/
 ---
@@ -39,7 +39,7 @@ You can add multiple fragments to a single machine, and you can add additional r
 Get started with this how-to guide:
 
 {{< cards >}}
-{{% card link="/use-cases/one-to-many/" %}}
+{{% card link="/how-tos/one-to-many/" %}}
 {{< /cards >}}
 
 ## Modify the config of a machine that uses a fragment

assets/use-cases/one-to-many/delete.png assets/how-tos/one-to-many/delete.png

@@ -246,10 +246,10 @@ Now that you have captured data, you could use this data to train you own Machin
 
 This concludes our guided path for getting to know the Viam platform.
 
-To learn more about the viam platform, dive into the [How-to Guides](/use-cases/) which provide instructions for common tasks and workflows, check out [Tutorials](/tutorials/) for projects, or learn more in the [Platform Reference](/platform/) documentation:
+To learn more about the viam platform, dive into the [How-to Guides](/how-tos/) which provide instructions for common tasks and workflows, check out [Tutorials](/tutorials/) for projects, or learn more in the [Platform Reference](/platform/) documentation:
 
 {{< cards >}}
-{{% card link="/use-cases/" %}}
+{{% card link="/how-tos/" %}}
 {{% card link="/tutorials/" %}}
 {{% card link="/platform/" %}}
 {{< /cards >}}

assets/use-cases/one-to-many/new-fragment.png assets/how-tos/one-to-many/new-fragment.png

@@ -0,0 +1,31 @@
+---
+title: "How-to Guides"
+linkTitle: "How-to Guides"
+weight: 200
+type: "docs"
+images: ["/registry/module-puzzle-piece.svg"]
+description: "Follow instructions for common tasks and workflows."
+no_list: true
+aliases:
+  - /use-cases/
+---
+
+Click on one of the following guides that provide solutions for common tasks and workflows:
+
+{{< cards >}}
+{{% card link="/how-tos/configure/" class="fit-contain" %}}
+{{% card link="/how-tos/develop-app/" class="fit-contain" %}}
+{{% card link="/how-tos/image-data/" class="fit-contain" %}}
+{{% card link="/how-tos/deploy-ml/" class="fit-contain" %}}
+{{% card link="/how-tos/collect-sensor-data/" %}}
+{{% card link="/how-tos/sensor-data-query-with-third-party-tools/" %}}
+{{% card link="/how-tos/sensor-data-query-sdk/" %}}
+{{% card link="/how-tos/sensor-data-visualize/" %}}
+{{% card link="/how-tos/create-module/" class="fit-contain" %}}
+{{% card link="/how-tos/manage-modules/" class="fit-contain" %}}
+{{% card link="/how-tos/navigate/" %}}
+{{% card link="/how-tos/one-to-many/" class="fit-contain" %}}
+{{% card link="/how-tos/manage-fleet/" class="fit-contain" %}}
+{{< /cards >}}
+
+If you're looking for examples of how Viam is being used in the world, have a look at [customer stories](https://www.viam.com/customers), follow our [step-by-step tutorials](/tutorials/), or browse our [blog posts](https://www.viam.com/blog?categories=Tutorials).

assets/use-cases/one-to-many/raw-json.png assets/how-tos/one-to-many/raw-json.png

@@ -6,6 +6,8 @@ type: "docs"
 images: ["/services/icons/data-capture.svg"]
 description: "Gather sensor data, sync it to the cloud, and view it in the Viam app."
 modulescript: true
+aliases:
+  - /use-cases/collect-sensor-data/
 # SME: Devin Hilly
 ---
 
@@ -113,12 +115,12 @@ Confirm that you are seeing data appear.
 
 ## Next steps
 
-Now that you have collected sensor data, you can [query it](/use-cases/sensor-data-query-with-third-party-tools/), [access it programmatically](/use-cases/sensor-data-query-sdk/) or [visualize it](/use-cases/sensor-data-visualize/) with third-party tools.
+Now that you have collected sensor data, you can [query it](/how-tos/sensor-data-query-with-third-party-tools/), [access it programmatically](/how-tos/sensor-data-query-sdk/) or [visualize it](/how-tos/sensor-data-visualize/) with third-party tools.
 
 {{< cards >}}
-{{% card link="/use-cases/sensor-data-query-with-third-party-tools/" %}}
-{{% card link="/use-cases/sensor-data-query-sdk/" %}}
-{{% card link="/use-cases/sensor-data-visualize/" %}}
+{{% card link="/how-tos/sensor-data-query-with-third-party-tools/" %}}
+{{% card link="/how-tos/sensor-data-query-sdk/" %}}
+{{% card link="/how-tos/sensor-data-visualize/" %}}
 {{< /cards >}}
 
 To see sensor data in action, check out this tutorial:

assets/use-cases/one-to-many/repeat.svg assets/how-tos/one-to-many/repeat.svg

@@ -6,6 +6,9 @@ type: "docs"
 description: "Build a simple smart machine in a few steps using Viam's modular system of components and services without writing much or any code."
 images: ["/platform/build.svg", "/services/ml/configure.svg"]
 tags: ["components", "configuration"]
+aliases:
+  - /use-cases/configure/
+  - use-cases/configure/
 ---
 
 You can get a smart machine running with Viam in just a few steps.
@@ -58,7 +61,7 @@ For each component that makes up your machine:
 3. Click on the **Test** area of the configuration panel to test your component.
 4. If any problems occur check the [logs](/cloud/machines/#logs) or review or roll back the [configuration history](/cloud/machines/#configure).
 
-If a component you want to use for your project is not natively supported, you can [build your own modular resource](/use-cases/create-module/).
+If a component you want to use for your project is not natively supported, you can [build your own modular resource](/how-tos/create-module/).
 
 You need to [_configure_](/configure/) your machine so that `viam-server` can interact with its hardware.
 Use the configuration builder tool in the Viam app to create a file that describes what hardware you are using and how it is connected.
@@ -101,7 +104,7 @@ For more information, see the [configuration documentation](/configure/).
 Once you have configured your machine, continue to develop an application:
 
 {{< cards >}}
-{{% card link="/use-cases/develop-app/" %}}
+{{% card link="/how-tos/develop-app/" %}}
 {{< /cards >}}
 
 To see full sample projects, that configure and control machines, check out these tutorials: