fixup! Docs: update introduction

Author: hannahlanzrath

…ser_guide/figures/RDM-output-commits.png …e/_static/figures/RDM-output-commits.pngdocs/source/user_guide/figures/RDM-output-commits.png renamed to docs/source/_static/figures/RDM-output-commits.png docs/source/user_guide/figures/RDM-output-commits.png renamed to docs/source/_static/figures/RDM-output-commits.png

@@ -1,6 +1,4 @@
 ```{include} ./user_guide/introduction.md
-:relative-images:
-:relative-docs:
 ```
 
 ```{toctree}

…er_guide/figures/RDM-project-commits.png …/_static/figures/RDM-project-commits.pngdocs/source/user_guide/figures/RDM-project-commits.png renamed to docs/source/_static/figures/RDM-project-commits.png docs/source/user_guide/figures/RDM-project-commits.png renamed to docs/source/_static/figures/RDM-project-commits.png

@@ -29,7 +29,7 @@ CADET-RDM projects are structured into two distinct repositories.
 1. The **project repository** that contains the input data, code, software and configurations to execute the computations. The output repository is a directory within the project repository.
 2. The **output repository** that contains the results of these computations, including all calculations, models and figures created by running the project code. Also stored in the output directory is the metadata used to create the specific result. This includes e.g. the software versions and requirements.
 
-:::{figure} user_guide/figures/RDM_wide.png
+:::{figure} /_static/figures/RDM_wide.png
 :width: 700
 :alt: RDM structure
 
@@ -47,11 +47,11 @@ Every run of the project code creates a new output branch (*result branch*) in t
    :gap: 8px
    :subcaptions: below
 
-   .. image:: user_guide/figures/RDM-project-commits.png
+   .. image:: /_static/figures/RDM-project-commits.png
       :alt: Project Repository
       :width: 300px
 
-   .. image:: user_guide/figures/RDM-output-commits.png
+   .. image:: /_static/figures/RDM-output-commits.png
       :alt: Output Repository
       :width: 420px