Revert "feat: make docs versioning compatible by relocating assets"

This reverts commit 305d64a.

docs/docs/10-overview.md

@@ -13,7 +13,7 @@ technologies, like [Argo CD](https://argoproj.github.io/cd/), to streamline and
 automate the progressive rollout of changes across the many stages of an
 application's lifecycle.
 
-![Screenshot](./assets/kargo-dashboard.png)
+![Screenshot](../static/img/kargo-dashboard.png)
 
 Kargo's goal is to provide an intuitive and flexible layer "above" existing GitOps tooling, wherein you can describe the relationships between various application instances deployed to different environments as well as procedures for progressing changes from one application instance's source of truth to the next.
 

docs/docs/20-quickstart.md

@@ -227,7 +227,7 @@ all three Argo CD `Application`s have not yet synced because they're not
 configured to do so automatically, and in fact, the branches referenced by their
 `targetRevision` fields do not even exist yet.
 
-![Argo-dashboard-screenshot](./assets/argo-dashboard.png)
+![Argo-dashboard-screenshot](../static/img/argo-dashboard.png)
 
 ## Your First Kargo Project
 
@@ -787,7 +787,7 @@ the previous section.
       This will take you to a list of `Project`s.  It currently includes only
       the one created in the previous step.
 
-      ![Kargo-dashboard](./assets/kargo-projects.png)
+      ![Kargo-dashboard](../static/img/kargo-projects.png)
 
    1. Select <Hlt>kargo-demo</Hlt>:
 
@@ -801,13 +801,13 @@ the previous section.
         * Three `Stage`s representing distinct instances of our demo
           application.
 
-        ![Kargo-dashboard-screenshot](./assets/kargo-dashboard-projects.png)
+        ![Kargo-dashboard-screenshot](../static/img/kargo-dashboard-projects.png)
 
       * An interactive <Hlt>Freight Timeline</Hlt> with `Freight` ordered
         chronologically, with newer `Freight` to the left and older `Freight` to
         the right.
 
-        ![Kargo-Freight-Timeline](./assets/kargo-frieght-timeline.png)
+        ![Kargo-Freight-Timeline](../static/img/kargo-frieght-timeline.png)
 
 1. After a few seconds, a piece of `Freight` should appear in the <Hlt>Freight
    Timeline</Hlt>, if it isn't there already.
@@ -838,17 +838,17 @@ the previous section.
 1. To promote `Freight` to the `test` `Stage`, select the target icon on the
    left border of <Hlt>test</Hlt>:
 
-    ![Kargo-Promote](./assets/kargo-promote-option.png)
+    ![Kargo-Promote](../static/img/kargo-promote-option.png)
 
     Next, select the `Freight` from the <Hlt>Freight Timeline</Hlt> and confirm
     the promotion by selecting <Hlt>Yes</Hlt>:
 
-    ![Kargo-Promote](./assets/kargo-promote-option-2.png)
+    ![Kargo-Promote](../static/img/kargo-promote-option-2.png)
 
     When promotion process is complete, you'll see a check mark next to
     <Hlt>test</Hlt>, indicating that the promotion was successful.
 
-    ![Kargo-dashboard-screenshot](./assets/kargo-dashboard-promotion.png)
+    ![Kargo-dashboard-screenshot](../static/img/kargo-dashboard-promotion.png)
 
     Following the promotion, health checks will run periodically. When a `Stage`
     is in a healthy state, this will be reflected with a heart icon. You can
@@ -868,7 +868,7 @@ the previous section.
    `test`, which designates it as eligible for promotion to the next `Stage` --
    in our case, `uat`.
 
-   ![Kargo-Freight-Verified](./assets/kargo-freight-verified.png)
+   ![Kargo-Freight-Verified](../static/img/kargo-freight-verified.png)
 
     :::note
     Although this example does not demonstrate it, it is also possible to verify

docs/docs/30-how-to-guides/14-working-with-stages.md

@@ -436,20 +436,20 @@ Users with credentials for and sufficient permissions within the Kargo control p
 
 1. Navigate to your Project in the Kargo UI and locate the action menu in the upper right corner of the pipeline:
 
-   ![create-stage](../assets/create-stage.png)
+   ![create-stage](../../static/img/create-stage.png)
 
 1. Click the magic wand icon to open the dropdown, then select <Hlt>Create Stage</Hlt>.
 
    A form will appear to input details for a new `Stage`:
 
-   ![create-stage](../assets/create-stage-2.png)
+   ![create-stage](../../static/img/create-stage-2.png)
 
 1. Complete the form with the necessary details and submit it.
 
    The new `Stage` will be added to the pipeline, connected to other
    `Stage`s based on your configuration:
 
-   ![create-stage](../assets/create-stage-3.png)
+   ![create-stage](../../static/img/create-stage-3.png)
 
 </TabItem>
 
@@ -497,7 +497,7 @@ For comprehensive guidance on promoting `Freight` to a `Stage`, refer to [Workin
 
 1. Click <Hlt>Delete</Hlt> in the upper right corner of the pop-up window:
 
-   ![delete-stage](../assets/delete-stage.png)
+   ![delete-stage](../../static/img/delete-stage.png)
 
 </TabItem>
 
@@ -526,7 +526,7 @@ any applicable health check processes.
 
 1. Click <Hlt>Refresh</Hlt> in the top-right corner of the pop-up window:
 
-   ![refresh-stage](../assets/refresh-stage.png)
+   ![refresh-stage](../../static/img/refresh-stage.png)
 
 </TabItem>
 
@@ -553,7 +553,7 @@ as desired.
 
 1. Select the `Stage` you want to reverify and click <Hlt>Reverify</Hlt> at the top of the menu:
 
-    ![verify-stage](../assets/reverify-freight.png)
+    ![verify-stage](../../static/img/reverify-freight.png)
 
     :::note
     If you wish to stop the in-progress verification, you can click <Hlt>Abort Verification</Hlt>.
@@ -562,7 +562,7 @@ as desired.
 1. To check the `Stage`s where the `Freight` has been successfully verified, return to 
     the <Hlt>Freight Timeline</Hlt> and select the `Freight`. Verified `Stage` names will appear under <Hlt>VERIFIED IN</Hlt>:
 
-    ![verify-stage](../assets/verified-in.png)
+    ![verify-stage](../../static/img/verified-in.png)
 
 </TabItem>
 

docs/docusaurus.config.js

@@ -31,7 +31,7 @@ const config = {
         docs: {
           sidebarPath: require.resolve('./sidebars.js'),
           sidebarCollapsible: false,
-          routeBasePath: '/', // Serve the docs at the site's root
+          routeBasePath: '/', // Serve the docs at the site's roo
         },
         blog: false,
         pages: false,