diff --git a/assets/scss/_styles_project.scss b/assets/scss/_styles_project.scss
index 2ae37c88f8..fea87afe1c 100644
--- a/assets/scss/_styles_project.scss
+++ b/assets/scss/_styles_project.scss
@@ -539,7 +539,7 @@ details[open] > .expand-label {
   border-bottom-left-radius: 4px;
   border-bottom-right-radius: 4px;
   padding: 1rem 1rem;
-  overflow: hidden;
+  overflow: auto;
 }
 
 // First child is the anchor link
@@ -553,8 +553,9 @@ details > div.expand-content > *:last-child {
 }
 
 .expand {
-  padding-bottom: 0.75rem;
   clear: both;
+  margin-bottom: 0.75rem;
+  margin-top: 0.75rem;
 }
 
 .expand i {
@@ -619,6 +620,11 @@ details summary::-webkit-details-marker {
 
 /* START CSS for how-to paths */
 
+.expand.howtoexpand {
+  margin-bottom: 0.5rem;
+  margin-top: 0.5rem;
+}
+
 .expand.howtoexpand summary, .expand.howtoexpand .expand-content {
   background-color: #eaf9fb;
 }
@@ -1112,12 +1118,13 @@ td > ul, td > ol {
 
 /* TAB CSS consistency START */
 
-.nav-tabs {
+.nav.nav-tabs {
   border-bottom: none; // unset from inherited styles
   gap: 1px;
   display: flex;
   flex-direction: row;
   border-bottom: 1px solid #E4E4E6;
+  margin-left: 0rem;
 }
 
 .horizontalheaders > .nav-tabs, .horizontalheaders * .nav-tabs {
@@ -1174,6 +1181,7 @@ td > ul, td > ol {
 
 .horizontalheaders * .nav-tabs > .nav-item, .horizontalheaders > .nav-tabs > .nav-item {
   margin-bottom: 0rem;
+  margin-left: 0rem;
 }
 
 .horizontalheaders > .nav-tabs .nav-item > a {
@@ -1187,12 +1195,14 @@ td > ul, td > ol {
 
 .td-content ol li.nav-item {
   margin-bottom: 0 !important;
+  margin-left: 0 !important;
 }
 
 .tab-content {
   padding: .7rem 0;
   background-color: white;
   border-bottom: 1px solid rgb(215, 215, 217);
+  max-width: 1000px;
 }
 
 .horizontalheaders * .tab-content, .horizontalheaders > .tab-content {
@@ -2080,8 +2090,8 @@ a.ais-Pagination-link:hover {
 
   #sideSearchBar {
     display: unset;
-    margin-right: 0.5rem;
-    margin-left: 0rem;
+    margin-right: 0rem;
+    margin-left: 1rem;
     margin-top: 0.5rem;
   }
 
@@ -2098,30 +2108,23 @@ a.ais-Pagination-link:hover {
 }
 
 #mobile-search {
-  margin-left: 0.5rem;
-  margin-right: 1rem;
+  margin-left: auto;
+  margin-right: auto;
 }
 
 @media (max-width: 768px) {
 
-  #sideSearchBar {
-    padding-right: 0.25rem;
-    margin-left: 1rem;
-  }
 
 
   #mobile-search {
     margin-left: 0rem;
     margin-right: 0rem;
   }
-}
-
-
-@media (max-width: 768px) {
 
   #sideSearchBar {
-    margin-right: 1.0rem;
-    margin-left: 0.75rem;
+    padding-right: 0rem;
+    margin-right: 0.75rem;
+    margin-left: 1.5rem;
   }
 
   .td-sidebar-nav > .td-sidebar-nav__section {
@@ -3262,17 +3265,30 @@ li.active-path.tutorial-heading > a {
   list-style: none;
   counter-reset: item;
   padding-inline-start: 0px;
-  display: table;
   list-style-position: outside;
   margin-bottom: 1rem;
-  width: 100%;
+  width: calc(100% - 2.5rem);;
   margin-left: 2.5rem;
 }
 
 .td-content > ol > li, .td-content > .table * ol > li {
   counter-increment: item;
   margin-bottom: 5px;
-  display: table-row;
+  display: block;
+}
+
+.td-content > ol > li > ul {
+  margin-left: 1rem;
+  margin-bottom: 0.5rem;
+}
+
+.td-content * ul {
+  margin-left: 1rem;
+  padding-left: 0rem;
+}
+
+.td-content * ol * ul > li, .td-content > ol * ul > li {
+  margin-left: 1.5rem;
 }
 
 div.tablestep {
@@ -3334,6 +3350,11 @@ div.tablestep > table td, div.tablestep table td {
   margin-bottom: 0rem;
 }
 
+.td-content > ul li, .td-content > ol li {
+  list-style-position: outside;
+  margin-left: 1.0rem;
+}
+
 .td-content > ul {
   padding-left: 1rem;
 }
diff --git a/docs/data-ai/capture-data/conditional-sync.md b/docs/data-ai/capture-data/conditional-sync.md
index 41097cae9e..6654b109ff 100644
--- a/docs/data-ai/capture-data/conditional-sync.md
+++ b/docs/data-ai/capture-data/conditional-sync.md
@@ -236,7 +236,7 @@ On your machine's **CONFIGURE** tab, switch to **JSON** mode and add a `selectiv
 
 {{% expand "Click to view a full configuration example" %}}
 
-```json {class="line-numbers linkable-line-numbers" data-line="12-22,25-37,40-45"}
+```json {class="line-numbers linkable-line-numbers" data-line="12-21,25-37,40-45"}
 {
   "components": [
     {
diff --git a/docs/manage/fleet/provision/setup.md b/docs/manage/fleet/provision/setup.md
index 0483388850..973c1c6e69 100644
--- a/docs/manage/fleet/provision/setup.md
+++ b/docs/manage/fleet/provision/setup.md
@@ -479,7 +479,7 @@ For a guide you can give to end users for setting up their machine, see [Setup m
 {{< tabs >}}
 {{% tab name="Mobile app" min-height="703px" %}}
 
-{{<video webm_src="/platform/provisioning-demo.webm" mp4_src="/platform/provisioning-demo.mp4" alt="Using the Viam mobile app to provision a new machine with viam-agent." poster="/platform/provisioning-demo.jpg" class="alignright" max-width="400px" style="margin-left: 2rem">}}
+{{<video webm_src="/platform/provisioning-demo.webm" mp4_src="/platform/provisioning-demo.mp4" alt="Using the Viam mobile app to provision a new machine with viam-agent." poster="/platform/provisioning-demo.jpg" class="" max-width="400px" style="margin-left: 2rem">}}
 
 1. Open the app and follow any instructions there until the app directs you to turn on the machine.
 
diff --git a/docs/operate/control/web-app.md b/docs/operate/control/web-app.md
index 6c17a3cf73..602a588420 100644
--- a/docs/operate/control/web-app.md
+++ b/docs/operate/control/web-app.md
@@ -38,7 +38,7 @@ Refer to the [Viam TypeScript SDK](https://ts.viam.dev/) documentation for avail
 
 The following files create an example TypeScript web app that connects to a machine and displays the latest image from the machine's camera, and the latest sensor readings.
 
-{{<imgproc src="/operate/ts-dashboard.png" resize="x1100" declaredimensions=true alt="A web browser displaying a dashboard with a camera feed and sensor readings." style="max-width:450px" class="imgzoom" >}}
+{{<imgproc src="/operate/ts-dashboard.png" resize="x1100" declaredimensions=true alt="A web browser displaying a dashboard with a camera feed and sensor readings." style="width:450px" class="imgzoom" >}}
 
 {{< tabs >}}
 {{% tab name="main.ts" %}}
diff --git a/docs/operate/get-started/other-hardware/_index.md b/docs/operate/get-started/other-hardware/_index.md
index 06d848288f..24d72f7fe3 100644
--- a/docs/operate/get-started/other-hardware/_index.md
+++ b/docs/operate/get-started/other-hardware/_index.md
@@ -180,21 +180,31 @@ Edit the generated files to add your logic:
 {{< tabs >}}
 {{% tab name="Python" %}}
 
-1. Open <file>/src/models/&lt;model-name&gt;.py</file> and add any necessary imports.
-1. **Edit the `validate_config` function** to do the following:
+{{< table >}}
+{{< tablestep number=1 >}}
+Open <file>/src/models/&lt;model-name&gt;.py</file> and add any necessary imports.
+{{% /tablestep %}}
+{{< tablestep number=2 >}}
+**Edit the `validate_config` function** to do the following:
+
+- Check that the user has configured required attributes and return errors if they are missing.
+- Return a map of any dependencies.
 
-   - Check that the user has configured required attributes and return errors if they are missing.
-   - Return a map of any dependencies.
-     - For more information, see [Module dependencies](/operate/get-started/other-hardware/dependencies/).
+For more information, see [Module dependencies](/operate/get-started/other-hardware/dependencies/).
 
-1. **Edit the `reconfigure` function**, which gets called when the user changes the configuration.
-   This function should do the following:
+{{% /tablestep %}}
+{{< tablestep number=3 >}}
+
+**Edit the `reconfigure` function**, which gets called when the user changes the configuration.
+This function should do the following:
 
-   - If you assigned any configuration attributes to global variables, get the values from the latest `config` object and update the values of the global variables.
-   - Assign default values as necessary to any optional attributes if the user hasn't configured them.
-   - If your module has dependencies, get the dependencies from the `dependencies` map and cast each resource according to which API it implements, as in [this <file>ackermann.py</file> example](https://github.com/mcvella/viam-ackermann-base/blob/main/src/ackermann.py).
+- If you assigned any configuration attributes to global variables, get the values from the latest `config` object and update the values of the global variables.
+- Assign default values as necessary to any optional attributes if the user hasn't configured them.
+- If your module has dependencies, get the dependencies from the `dependencies` map and cast each resource according to which API it implements, as in [this <file>ackermann.py</file> example](https://github.com/mcvella/viam-ackermann-base/blob/main/src/ackermann.py).
+  {{% /tablestep %}}
+  {{< tablestep number=4 >}}
 
-<ol><li style="counter-reset: item 3"><strong>Edit the methods you want to implement</strong>:
+**Edit the methods you want to implement**:
 
 For each method you want to implement, replace the body of the method with your relevant logic.
 Make sure you return the correct type in accordance with the function's return signature.
@@ -323,10 +333,11 @@ if __name__ == "__main__":
 
 You can find more examples by looking at the source code GitHub repos linked from each module in the [Viam Registry](https://app.viam.com/registry).
 
-</li></ol>
+{{% /tablestep %}}
+{{< tablestep number=5 >}}
 
-<ol><li style="counter-reset: item 4"><strong>Add logging</strong> messages as desired.
-   The following log severity levels are available for resource logs:
+**Add logging** messages as desired.
+The following log severity levels are available for resource logs:
 
 ```python {class="line-numbers linkable-line-numbers"}
 # Within some method, log information:
@@ -367,12 +378,14 @@ LOGGER.critical("critical info")
 
 {{< /expand >}}
 
-</li></ol>
+{{% /tablestep %}}
+{{< tablestep number=6 >}}
 
-<ol><li style="counter-reset: item 5"><strong>Edit the generated <file>requirements.txt</file> file</strong> to include any packages that must be installed for the module to run.
-   Depending on your use case, you may not need to add anything here beyond <code>viam-sdk</code> which is auto-populated.
+**Edit the generated <file>requirements.txt</file> file** to include any packages that must be installed for the module to run.
+Depending on your use case, you may not need to add anything here beyond <code>viam-sdk</code> which is auto-populated.
 
-</li></ol>
+{{% /tablestep %}}
+{{< /table >}}
 
 {{% /tab %}}
 {{% tab name="Go" %}}
@@ -382,35 +395,48 @@ LOGGER.critical("critical info")
 This error doesn't exist in the other SDKs, so `AlwaysRebuild` is not supported in those SDKs.
 {{% /hiddencontent %}}
 
-1. Open <file>module.go</file> and add necessary imports.
+{{< table >}}
+{{< tablestep number=1 >}}
+Open <file>module.go</file> and add necessary imports.
+{{% /tablestep %}}
+{{< tablestep number=2 >}}
+**Add any configurable attributes to the `Config` struct.**
+{{% /tablestep %}}
+{{< tablestep number=3 >}}
+**Edit the `Validate` function** to do the following:
 
-1. **Add any configurable attributes to the `Config` struct.**
+- Check that the user has configured required attributes and return errors if they are missing.
+- Return any dependencies.
 
-1. **Edit the `Validate` function** to do the following:
+For more information, see [Module dependencies](/operate/get-started/other-hardware/dependencies/).
+{{% /tablestep %}}
+{{< tablestep number=4 >}}
+
+**(Optional) Create and edit a `Reconfigure` function**:
 
-   - Check that the user has configured required attributes and return errors if they are missing.
-   - Return any dependencies.
-     - For more information, see [Module dependencies](/operate/get-started/other-hardware/dependencies/).<br><br>
+In most cases, you can omit this function and leave `resource.AlwaysRebuild` in the `Config` struct.
+This will cause `viam-server` to fully rebuild the resource each time the user changes the configuration.
 
-1. **(Optional) Create and edit a `Reconfigure` function**:
+If you need to maintain the state of the resource, for example if you are implementing a board and need to keep the software PWM loops running, you should implement this function so that `viam-server` updates the configuration without rebuilding the resource from scratch.
+In this case, your `Reconfigure` function should do the following:
 
-   In most cases, you can omit this function and leave `resource.AlwaysRebuild` in the `Config` struct.
-   This will cause `viam-server` to fully rebuild the resource each time the user changes the configuration.
+- If you assigned any configuration attributes to global variables, get the values from the latest `config` object and update the values of the global variables.
+- Assign default values as necessary to any optional attributes if the user hasn't configured them.
 
-   If you need to maintain the state of the resource, for example if you are implementing a board and need to keep the software PWM loops running, you should implement this function so that `viam-server` updates the configuration without rebuilding the resource from scratch.
-   In this case, your `Reconfigure` function should do the following:
+For an example that implements the `Reconfigure` method, see [<file>mybase.go</file> on GitHub](https://github.com/viamrobotics/rdk/blob/main/examples/customresources/models/mybase/mybase.go).
 
-   - If you assigned any configuration attributes to global variables, get the values from the latest `config` object and update the values of the global variables.
-   - Assign default values as necessary to any optional attributes if the user hasn't configured them.<br><br>
+{{% /tablestep %}}
+{{< tablestep number=5 >}}
 
-   For an example that implements the `Reconfigure` method, see [<file>mybase.go</file> on GitHub](https://github.com/viamrobotics/rdk/blob/main/examples/customresources/models/mybase/mybase.go).
+**Edit the constructor** to do the following:
 
-1. **Edit the constructor** to do the following:
+- If you didn't create a `Reconfigure` function, use the constructor to assign default values as necessary to any optional attributes if the user hasn't configured them.
+- If you created a `Reconfigure` function, make your constructor call `Reconfigure`.
 
-   - If you didn't create a `Reconfigure` function, use the constructor to assign default values as necessary to any optional attributes if the user hasn't configured them.
-   - If you created a `Reconfigure` function, make your constructor call `Reconfigure`.<br><br>
+{{% /tablestep %}}
+{{< tablestep number=6 >}}
 
-<ol><li style="counter-reset: item 4"><strong>Edit the methods you want to implement</strong>:
+**Edit the methods you want to implement**:
 
 For each method you want to implement, replace the body of the method with your relevant logic.
 Make sure you return the correct type in accordance with the function's return signature.
@@ -553,10 +579,9 @@ func (s *helloWorldHelloCamera) Close(context.Context) error {
 {{< /expand >}}
 
 You can find more examples by looking at the source code GitHub repos linked from each module in the [Viam Registry](https://app.viam.com/registry).
-
-</li></ol>
-
-<ol><li style="counter-reset: item 5"><strong>Add logging</strong> messages as desired.
+{{% /tablestep %}}
+{{< tablestep number=7 >}}
+**Add logging** messages as desired.
 
 You can add log messages with various levels of severity:
 
@@ -573,7 +598,8 @@ fn (c *component) someFunction(ctx context.Context, a int) {
 }
 ```
 
-</li></ol>
+{{% /tablestep %}}
+{{< /table >}}
 
 {{% alert title="Note" color="note" %}}
 In order to see debug logs when using your modular resource, you'll need to run `viam-server` with the `-debug` option.
@@ -738,7 +764,7 @@ viam module build local
 Then restart it in your machine's **CONFIGURE** tab in the Viam app.
 In upper right corner of the module's card, click the **...** menu, then click **Restart**.
 
-{{<imgproc src="/registry/restart-module.png" resize="x600" declaredimensions=true alt="Module menu." style="max-width:300px" class="shadow" >}}
+{{<imgproc src="/registry/restart-module.png" resize="x600" declaredimensions=true alt="Module menu." style="width:300px" class="shadow" >}}
 
 {{< /expand >}}
 
@@ -792,7 +818,7 @@ Configure any required attributes using proper JSON syntax.
 Click the **TEST** bar at the bottom of your modular component configuration, and check whether it works as expected.
 For example, if you created a sensor component, check whether readings are displayed.
 
-{{<imgproc src="/how-tos/sensor-test.png" resize="x1100" declaredimensions=true alt="The test section of an example modular sensor, with readings displayed." style="max-width:600px" class="shadow" >}}
+{{<imgproc src="/how-tos/sensor-test.png" resize="x1100" declaredimensions=true alt="The test section of an example modular sensor, with readings displayed." style="width:600px" class="shadow" >}}
 
 {{% /tablestep %}}
 {{% tablestep number=5 %}}
@@ -825,7 +851,7 @@ viam module build local
 Then restart it in your machine's **CONFIGURE** tab in the Viam app.
 In upper right corner of the module's card, click **...** menu, then click **Restart**.
 
-{{<imgproc src="/registry/restart-module.png" resize="x600" declaredimensions=true alt="Module menu." style="max-width:300px" class="shadow" >}}
+{{<imgproc src="/registry/restart-module.png" resize="x600" declaredimensions=true alt="Module menu." style="width:300px" class="shadow" >}}
 
 {{% /tab %}}
 {{% tab name="Go" %}}
diff --git a/docs/operate/get-started/other-hardware/hello-world-module.md b/docs/operate/get-started/other-hardware/hello-world-module.md
index b4daab3a96..456f223bf9 100644
--- a/docs/operate/get-started/other-hardware/hello-world-module.md
+++ b/docs/operate/get-started/other-hardware/hello-world-module.md
@@ -296,70 +296,95 @@ Edit the stub files to add the logic from your test script in a way that works w
 
 First, implement the camera API methods by editing the camera class definition:
 
-1. Add the following to the list of imports at the top of <file>hello-world/src/models/hello_camera.py</file>:
+{{< table >}}
+{{< tablestep number=1 >}}
 
-   ```python {class="line-numbers linkable-line-numbers"}
-   from viam.media.utils.pil import pil_to_viam_image
-   from viam.media.video import CameraMimeType
-   from viam.utils import struct_to_dict
-   from PIL import Image
-   ```
+Add the following to the list of imports at the top of <file>hello-world/src/models/hello_camera.py</file>:
 
-1. In the test script you hard-coded the path to the image.
-   For the module, let's make the path a configurable attribute so you or other users of the module can set the path from which to get the image.
-   Add the following lines to the camera's `reconfigure()` function definition.
-   These lines set the `image_path` based on the configuration when the resource is configured or reconfigured.
+```python {class="line-numbers linkable-line-numbers"}
+from viam.media.utils.pil import pil_to_viam_image
+from viam.media.video import CameraMimeType
+from viam.utils import struct_to_dict
+from PIL import Image
+```
 
-   ```python {class="line-numbers" data-start="59"}
-   attrs = struct_to_dict(config.attributes)
-   self.image_path = str(attrs.get("image_path"))
-   ```
+{{% /tablestep %}}
+{{< tablestep number=2 >}}
 
-1. We are not providing a default image but rely on the end user to supply a valid path to an image when configuring the resource.
-   This means `image_path` is a required attribute.
-   Add the following code to the `validate()` function to throw an error if `image_path` isn't configured:
-
-   ```python {class="line-numbers linkable-line-numbers" data-start="46"}
-   # Check that a path to get an image was configured
-   fields = config.attributes.fields
-   if not "image_path" in fields:
-       raise Exception("Missing image_path attribute.")
-   elif not fields["image_path"].HasField("string_value"):
-       raise Exception("image_path must be a string.")
-   ```
+In the test script you hard-coded the path to the image.
+For the module, let's make the path a configurable attribute so you or other users of the module can set the path from which to get the image.
+Add the following lines to the camera's `reconfigure()` function definition.
+These lines set the `image_path` based on the configuration when the resource is configured or reconfigured.
 
-1. The module generator created a stub for the `get_image()` function we want to implement:
+```python {class="line-numbers" data-start="59"}
+attrs = struct_to_dict(config.attributes)
+self.image_path = str(attrs.get("image_path"))
+```
 
-   ```python {class="line-numbers linkable-line-numbers" data-start="79" }
-    async def get_image(
-        self,
-        mime_type: str = "",
-        *,
-        extra: Optional[Dict[str, Any]] = None,
-        timeout: Optional[float] = None,
-        **kwargs
-    ) -> ViamImage:
-        raise NotImplementedError()
-   ```
+{{% /tablestep %}}
+{{< tablestep number=3 >}}
+
+We are not providing a default image but rely on the end user to supply a valid path to an image when configuring the resource.
+This means `image_path` is a required attribute.
+Add the following code to the `validate()` function to throw an error if `image_path` isn't configured:
+
+```python {class="line-numbers linkable-line-numbers" data-start="46"}
+# Check that a path to get an image was configured
+fields = config.attributes.fields
+if "image_path" not in fields:
+    raise Exception("Missing image_path attribute.")
+elif not fields["image_path"].HasField("string_value"):
+    raise Exception("image_path must be a string.")
+```
 
-   You need to replace `raise NotImplementedError()` with code to actually implement the method:
+{{% /tablestep %}}
+{{< tablestep number=4 >}}
+
+The module generator created a stub for the `get_image()` function we want to implement:
+
+```python {class="line-numbers linkable-line-numbers" data-start="79" }
+async def get_image(
+    self,
+    mime_type: str = "",
+    *,
+    extra: Optional[Dict[str, Any]] = None,
+    timeout: Optional[float] = None,
+    **kwargs
+) -> ViamImage:
+    raise NotImplementedError()
+```
 
-   ```python {class="line-numbers linkable-line-numbers" data-start="86" }
-   ) -> ViamImage:
-       img = Image.open(self.image_path)
-       return pil_to_viam_image(img, CameraMimeType.JPEG)
-   ```
+You need to replace `raise NotImplementedError()` with code to actually implement the method:
+
+```python {class="line-numbers linkable-line-numbers" data-start="79" }
+async def get_image(
+    self,
+    mime_type: str = "",
+    *,
+    extra: Optional[Dict[str, Any]] = None,
+    timeout: Optional[float] = None,
+    **kwargs
+) -> ViamImage:
+    img = Image.open(self.image_path)
+    return pil_to_viam_image(img, CameraMimeType.JPEG)
+```
 
-   Leave the rest of the functions not implemented, because this module is not meant to return a point cloud (`get_point_cloud()`), and does not need to return multiple images simultaneously (`get_images()`).
+Leave the rest of the functions not implemented, because this module is not meant to return a point cloud (`get_point_cloud()`), and does not need to return multiple images simultaneously (`get_images()`).
 
-   Save the file.
+Save the file.
 
-1. Open <file>requirements.txt</file>.
-   Add the following line:
+{{% /tablestep %}}
+{{< tablestep number=5 >}}
 
-   ```text
-   Pillow
-   ```
+Open <file>requirements.txt</file>.
+Add the following line:
+
+```text
+Pillow
+```
+
+{{% /tablestep %}}
+{{< /table >}}
 
 ### Implement the sensor API
 
@@ -571,7 +596,7 @@ You can view the complete example code in the [hello-world-module repository on
 With the implementation written, it's time to test your module locally:
 
 {{< table >}}
-{{% tablestep number=1 %}}
+{{< tablestep number=1 >}}
 
 {{< tabs >}}
 {{% tab name="Python" %}}
@@ -600,13 +625,19 @@ viam module build local
 
 {{% /tablestep %}}
 {{% tablestep number=2 %}}
+
 Make sure your machine's instance of `viam-server` is live and connected to the [Viam app](https://app.viam.com).
+
 {{% /tablestep %}}
 {{% tablestep number=3 %}}
+
 In the Viam app, navigate to your machine's **CONFIGURE** page.
+
 {{% /tablestep %}}
 {{% tablestep number=4 %}}
+
 Click the **+** button, select **Local module**, then again select **Local module**.
+
 {{% /tablestep %}}
 {{% tablestep number=5 %}}
 
@@ -652,7 +683,7 @@ Replace the path with the path to your image, for example `"/Users/jessamyt/Down
 {{% tablestep number=8 %}}
 Save the config, then click the **TEST** section of the camera's configuration card.
 
-{{<imgproc src="/how-tos/hello-camera.png" resize="x1100" declaredimensions=true alt="The Viam app configuration interface with the Test section of the camera card open, showing a hello world image." style="max-width:800px" class="shadow aligncenter" >}}
+{{<imgproc src="/how-tos/hello-camera.png" resize="x1100" declaredimensions=true alt="The Viam app configuration interface with the Test section of the camera card open, showing a hello world image." style="width:800px" class="shadow aligncenter" >}}
 
 You should see your image displayed.
 If not, check the **LOGS** tab for errors.
@@ -729,7 +760,7 @@ Now, if you look at the [Viam Registry page](https://app.viam.com/registry) whil
 With the module now in the registry, you can configure the hello-sensor and hello-camera on your machines just as you would configure other components and services.
 There's no more need for local module configuration; local modules are primarily used for testing.
 
-{{<imgproc src="/how-tos/hello-config.png" resize="x1100" declaredimensions=true alt="The create a component menu open, searching for hello. The hello-camera and hello-sensor components are shown in the search results." style="max-width:500px" class="shadow aligncenter" >}}
+{{<imgproc src="/how-tos/hello-config.png" resize="x1100" declaredimensions=true alt="The create a component menu open, searching for hello. The hello-camera and hello-sensor components are shown in the search results." style="width:500px" class="shadow aligncenter" >}}
 
 For more information about uploading modules, see [Update and manage modules you created](/operate/get-started/other-hardware/manage-modules/).
 
diff --git a/docs/operate/mobility/define-geometry.md b/docs/operate/mobility/define-geometry.md
index 6abd8427e3..2e9e48de5b 100644
--- a/docs/operate/mobility/define-geometry.md
+++ b/docs/operate/mobility/define-geometry.md
@@ -17,7 +17,7 @@ You can also [define static obstacles](/operate/mobility/define-obstacles/) for
 For complex kinematic chain configuration, useful when creating a module to support an unsupported arm model, see [Configure Complex Kinematic Chains](/operate/reference/kinematic-chain-config/).
 {{% /alert %}}
 
-{{<imgproc src="/services/frame-system/frame_system_wheeled_base.png" resize="x1100" declaredimensions=true alt="Visualization of a wheeled base configured with motors and a mounted camera in the frame system tab of the Viam app UI" style="max-width:600px" class="imgzoom shadow" >}}
+{{<imgproc src="/services/frame-system/frame_system_wheeled_base.png" resize="x1100" declaredimensions=true alt="Visualization of a wheeled base configured with motors and a mounted camera in the frame system tab of the Viam app UI" style="width:600px" class="imgzoom shadow" >}}
 
 ## Configure a reference frame
 
diff --git a/docs/operate/reference/components/camera/webcam.md b/docs/operate/reference/components/camera/webcam.md
index abf71ffabd..87b27f6f2f 100644
--- a/docs/operate/reference/components/camera/webcam.md
+++ b/docs/operate/reference/components/camera/webcam.md
@@ -117,7 +117,7 @@ To add and use the service:
 1. Click the **Copy attributes** button for the camera you want to use.
 1. Click the **{}** icon in the upper right corner of the camera component configuration.
 
-   {{<imgproc src="/components/camera/advanced-config.png" resize="x1100" declaredimensions=true alt="The switch to advanced button in the Viam app." style="max-width:200px" class="shadow" >}}
+   {{<imgproc src="/components/camera/advanced-config.png" resize="x1100" declaredimensions=true alt="The switch to advanced button in the Viam app." style="width:200px" class="shadow" >}}
 
 1. Paste the copied attributes.
 1. Click **Save**.
diff --git a/docs/tutorials/services/navigate-with-rover-base.md b/docs/tutorials/services/navigate-with-rover-base.md
index 240b88e193..ce75ab5a20 100644
--- a/docs/tutorials/services/navigate-with-rover-base.md
+++ b/docs/tutorials/services/navigate-with-rover-base.md
@@ -101,7 +101,7 @@ We used a [`jetson` board](https://github.com/viam-modules/nvidia/tree/main/jets
 
 1. Configure a board named `local` as shown below:
 
-{{<imgproc src="/tutorials/navigate-with-rover-base/board-config-builder.png" resize="1200x" declaredimensions=true alt="Configuration of a jetson board with digital interrupts in the Viam app config builder." style="max-width:650px" class="shadow imgzoom" >}}
+{{<imgproc src="/tutorials/navigate-with-rover-base/board-config-builder.png" resize="1200x" declaredimensions=true alt="Configuration of a jetson board with digital interrupts in the Viam app config builder." style="width:650px" class="shadow imgzoom" >}}
 
 2. Configure [digital interrupts](https://github.com/viam-modules/nvidia/blob/main/README.md#digital-interrupt-configuration) on your board to signal precise GPIO state changes to the [encoders](/operate/reference/components/encoder/) on your rover base.
    Find your board on the **CONFIGURE** tab in **Builder** mode.
@@ -322,21 +322,21 @@ In the **JSON** mode in your machine's **CONFIGURE** tab, add the following JSON
 1.  Configure a GPS movement sensor so the robot knows where it is while navigating.
     We configured ours as a `gps-nmea-rtk-serial` movement sensor:
 
-    {{<imgproc src="/tutorials/navigate-with-rover-base/gps-movement-sensor-config-builder.png" resize="1100x" declaredimensions=true alt="An example configuration for a GPS movement sensor in the Viam app Config Builder." style="max-width:550px" class="shadow imgzoom" >}}
+    {{<imgproc src="/tutorials/navigate-with-rover-base/gps-movement-sensor-config-builder.png" resize="1100x" declaredimensions=true alt="An example configuration for a GPS movement sensor in the Viam app Config Builder." style="width:550px" class="shadow imgzoom" >}}
 
     We named ours `gps`.
     Refer to [the `gps-nmea-rtk-serial` movement sensor documentation](https://github.com/viam-modules/gps/blob/main/README.md#configure-your-rtk-serial-movement_sensor) for attribute information.
 
 2.  Configure a wheeled odometry movement sensor to provide angular and linear velocity measurements from the encoded motors on our base.
 
-    {{<imgproc src="/tutorials/navigate-with-rover-base/wheeled-odometry-movement-sensor-config-builder.png" resize="1100x" declaredimensions=true alt="An example configuration for a wheeled-odometry movement sensor in the Viam app Config Builder." style="max-width:550px" class="shadow imgzoom" >}}
+    {{<imgproc src="/tutorials/navigate-with-rover-base/wheeled-odometry-movement-sensor-config-builder.png" resize="1100x" declaredimensions=true alt="An example configuration for a wheeled-odometry movement sensor in the Viam app Config Builder." style="width:550px" class="shadow imgzoom" >}}
 
     We named ours `enc-linear`.
     Refer to [the `wheeled-odometry` movement sensor documentation](/operate/reference/components/movement-sensor/wheeled-odometry/) for attribute information.
 
 3.  Now that you've got movement sensors which can give you GPS position and linear and angular velocity readings, configure a `merged` movement sensor to aggregate the readings from our other movement sensors into a singular sensor:
 
-    {{<imgproc src="/tutorials/navigate-with-rover-base/merged-movement-sensor-config-builder.png" resize="1100x" declaredimensions=true alt="An example configuration for a merged movement sensor in the Viam app Config Builder." style="max-width:550px" class="shadow imgzoom" >}}
+    {{<imgproc src="/tutorials/navigate-with-rover-base/merged-movement-sensor-config-builder.png" resize="1100x" declaredimensions=true alt="An example configuration for a merged movement sensor in the Viam app Config Builder." style="width:550px" class="shadow imgzoom" >}}
 
     We named ours `merged`.
     Refer to [the `merged` movement sensor documentation](/operate/reference/components/movement-sensor/merged/) for attribute information.
@@ -348,7 +348,7 @@ In the **JSON** mode in your machine's **CONFIGURE** tab, add the following JSON
         If your movement sensor is mounted on top of the rover like ours is, set **Orientation**'s third input field, Z, to `1`.
       - Select the `base` as the parent frame.
 
-        {{<imgproc src="/tutorials/navigate-with-rover-base/merged-movement-sensor-frame-system.png" resize="1100x" declaredimensions=true alt="An example configuration for a merged movement sensor in the Viam app Frame System." style="max-width:460px" class="shadow imgzoom" >}}
+        {{<imgproc src="/tutorials/navigate-with-rover-base/merged-movement-sensor-frame-system.png" resize="1100x" declaredimensions=true alt="An example configuration for a merged movement sensor in the Viam app Frame System." style="width:460px" class="shadow imgzoom" >}}
 
 {{% /tab %}}
 {{% tab name="JSON" %}}
@@ -465,7 +465,7 @@ To add the navigation service to your robot, do the following:
 
 Your navigation service should now appear in your machine's **CONFIGURE** tab as a card with a map like the following:
 
-{{<imgproc src="/tutorials/navigate-with-rover-base/navigation-config-builder.png" resize="1200x" declaredimensions=true alt="Navigation Card" style="max-width:650px" class="shadow imgzoom" >}}
+{{<imgproc src="/tutorials/navigate-with-rover-base/navigation-config-builder.png" resize="1200x" declaredimensions=true alt="Navigation Card" style="width:650px" class="shadow imgzoom" >}}
 
 For more detailed information see [the navigation service](/operate/reference/services/navigation/#configuration).
 
@@ -516,12 +516,12 @@ From there, ensure that **Navigation mode** is selected as **Manual**, so your r
 Select **Waypoints** on the upper-left corner menu of the navigation card.
 Zoom in on your current location and click on the map to add a waypoint.
 
-{{<imgproc src="/tutorials/navigate-with-rover-base/add-first-waypoint.png" resize="1200x" declaredimensions=true alt="Waypoint 0 being added in the Viam app config builder on a New York City street" style="max-width:650px" class="shadow imgzoom" >}}
+{{<imgproc src="/tutorials/navigate-with-rover-base/add-first-waypoint.png" resize="1200x" declaredimensions=true alt="Waypoint 0 being added in the Viam app config builder on a New York City street" style="width:650px" class="shadow imgzoom" >}}
 
 Add as many waypoints as you desire.
 Hover over a waypoint in the left-hand menu and click the trash icon to delete a waypoint.
 
-{{<imgproc src="/tutorials/navigate-with-rover-base/add-second-waypoint.png" resize="1200x" declaredimensions=true alt="Waypoint 1 being added in the Viam app config builder, further down the street" style="max-width:650px" class="shadow imgzoom" >}}
+{{<imgproc src="/tutorials/navigate-with-rover-base/add-second-waypoint.png" resize="1200x" declaredimensions=true alt="Waypoint 1 being added in the Viam app config builder, further down the street" style="width:650px" class="shadow imgzoom" >}}
 
 #### (Optional) Add obstacles
 
@@ -610,7 +610,7 @@ First, configure a depth [camera](/operate/reference/components/camera/) that yo
 
 We configured ours as an Intel RealSense Camera, which is available as a {{< glossary_tooltip term_id="modular-resource" text="modular resource" >}} [in the Viam Registry](https://app.viam.com/module/viam/realsense):
 
-{{<imgproc src="/tutorials/navigate-with-rover-base/realsense-camera-config-builder.png" resize="1200x" declaredimensions=true alt="An example configuration for an Intel RealSense camera in the Viam app Config Builder." style="max-width:650px" class="shadow imgzoom" >}}
+{{<imgproc src="/tutorials/navigate-with-rover-base/realsense-camera-config-builder.png" resize="1200x" declaredimensions=true alt="An example configuration for an Intel RealSense camera in the Viam app Config Builder." style="width:650px" class="shadow imgzoom" >}}
 
 {{< alert title="Tip" color="tip" >}}