fix(docs): Move all images to the static folder (#2359)

* fix(devx): Moved all doc images to docs/static/img and all homepage images to docs/site/static/img. Deleted unused images.

* fix(devx): fix img path and typo indexer-functions.mdx

* fix(devx): fix index images

* fix(devx): img url

crates/iota-indexer/README.md

@@ -2,7 +2,7 @@ IOTA Indexer is an off-fullnode service to serve data from the IOTA protocol, in
 
 ## Architecture
 
-![enhanced_FN](../../docs/content/operator/images/indexer-arch.png)
+![enhanced_FN](../../docs/site/static/img/operator/indexer-functions/indexer-arch.png)
 
 > [!NOTE]
 >

docs/content/developer/cryptography/transaction-auth/multisig.mdx

@@ -27,7 +27,7 @@ different weights for each key (which is complex in threshold cryptography), mul
 transaction. On the other hand, threshold signatures provide the benefits of hiding the threshold policy, but also
 resulting in a single signature payload, making it indistinguishable from a single-key account.
 
-![Supported structures in IOTA multisig](images/iota_multisig_structures.png 'Supported structures in IOTA multisig')
+![Supported structures in IOTA multisig](/img/developer/cryptography/transaction-auth/iota_multisig_structures.png 'Supported structures in IOTA multisig')
 _Multisig structures supported in IOTA._
 
 ## Example workflow

docs/content/operator/data-management.mdx

@@ -12,7 +12,7 @@ Managing the data on your IOTA Full node is critical to ensuring a healthy IOTA
 
 The minimal version of an IOTA Full node executes all of the transactions IOTA validators commit. IOTA Full nodes also orchestrate the submitting of new transactions to the system:
 
-![Basic IOTA Full node functionality](images/fn-basic-functionality.png "A diagram that shows the operations of a basic IOTA Full node.")
+![Basic IOTA Full node functionality](/img/operator/data-management/fn-basic-functionality.png "A diagram that shows the operations of a basic IOTA Full node.")
 
 The preceding image shows how data flows through a Full node:
 

docs/content/operator/indexer-functions.mdx

@@ -5,12 +5,12 @@ description: IOTA Indexer is a node data service that serves data from the IOTA
 
 The IOTA Indexer is a node data service that serves data from the IOTA protocol, including both data directly generated from chain and derivative data.
 
-![Indexer architecture](./images/indexer-arch.png)
+![Indexer architecture](/img/operator/indexer-functions/indexer-arch.png)
 
 ## Functions 
 
 The IOTA Indexer provides three main functionalities:
-- Ingest data from a Full node to a relational database. Data on Full nodes is stored as BCS bytes in an embedded RocksDB database, thus the query capabilities are very limited. The indexer pulls chekpoint blob data, schematizing them into various tables like objects, transactions, and so on, with proper indices.
+- Ingest data from a Full node to a relational database. Data on Full nodes is stored as BCS bytes in an embedded RocksDB database, thus the query capabilities are very limited. The indexer pulls checkpoint blob data, schematizing them into various tables like objects, transactions, and so on, with proper indices.
 - Serve online transaction processing (OLTP) RPC requests. With data in relational databases, IOTA indexer spins a stateless reader binary as JSON RPC server with an [interface](/references/iota-api).
 - Other than OLTP data ingestion and requests, the Indexer also supports some analytical data ingestion like transactions per second (TPS) and daily active user (DAU) metrics.
 

docs/content/operator/snapshots.mdx

@@ -135,7 +135,7 @@ Mainnet: `s3://iota-mainnet-snapshots/`,  `s3://iota-mainnet-formal/`
 Testnet: `gs://iota-testnet-snapshots/`, `gs://iota-testnet-formal/`
 Mainnet: `gs://iota-mainnet-snapshots/`,  `gs://iota-mainnet-formal/`
 
-![IOTA Managed Snapshots](images/iota-cloud-snapshots.png "A diagram that shows the current architecture of iota snapshot availability")
+![IOTA Managed Snapshots](/img/operator/snapshots/iota-cloud-snapshots.png "A diagram that shows the current architecture of iota snapshot availability")
 
 ## Enabling snapshots
 

docs/site/src/pages/index.js

@@ -7,9 +7,9 @@ import React from "react";
 import Layout from "@theme/Layout";
 import Link from "@docusaurus/Link";
 import styles from "./index.module.css";
-import heroCardBg from "@site/static/img/heroCardBg.png";
-import heroCardBg1 from "@site/static/img/heroCardBg1.png";
-import heroCardBg2 from "@site/static/img/heroCardBg2.png";
+import heroCardBg from "@site/static/img/index/heroCardBg.png";
+import heroCardBg1 from "@site/static/img/index/heroCardBg1.png";
+import heroCardBg2 from "@site/static/img/index/heroCardBg2.png";
 export default function Home() {
   const HomeCard = (props) => {
     const { title, children, heroCardBg } = props;
@@ -119,7 +119,7 @@ export default function Home() {
               to="./operator/iota-full-node"
             >
               Run a IOTA Full node
-              <span className="block bg-auto bg-[url(../static/img/index/right-arrow.svg)]"></span>
+              <span className="block bg-auto bg-[url(/img/index/right-arrow.svg)]"></span>
             </Link>
           </HomeCard>
           <HomeCard title="References" aux heroCardBg={heroCardBg1}>
@@ -192,7 +192,7 @@ export default function Home() {
         </div>
         <div className={styles.why}>
           <div className={styles.whyImgCard}>
-            <img height={"90%"} src="/img/blocks.png" alt="Decorative visual" />
+            <img height={"90%"} src="/img/index/blocks.png" alt="Decorative visual" />
           </div>
           <div className={styles.cardsB}>
             <div className={styles.cardB}>

docs/site/src/pages/index.module.css

@@ -19,7 +19,7 @@
   width: 400px;
 }
 .backgroundImage {
-  background: black url(../../static/img/heroTextBg.svg);
+  background: black url(../../static/img/index/heroTextBg.svg);
   height: 27rem;
   margin-top: -10rem;
   background-position: right;