chore: organize pictures (#1003)

Author: Chasen-Zhang

docs/cn/guides/00-overview/00-editions/02-dc/01-platforms.md

@@ -4,10 +4,10 @@ title: 云平台和地域
 
 Databend Cloud 是一款完全基于云基础架构的解决方案，目前已支持[阿里云](https://cn.aliyun.com/)、[腾讯云](https://cloud.tencent.com/)和 [Amazon S3](https://aws.amazon.com/cn/s3/) 的对象存储服务。各平台已开通的地理地域如下图所示：
 
-![alt text](../../../../../public/img/cloud/dc-platform.png)
+![alt text](/img/cloud/dc-platform.png)
 
 :::note
 Databend Cloud 计划扩展其支持的云厂商和地域范围。如果您的项目需要特定的云厂商或地域支持，请点击 [Databend Cloud 中国官网](https://www.databend.cn/)首页右上角的“联系销售”与 Databend Cloud 团队取得联系。
 :::
 
-您在开通 Databend Cloud 账号时需要选定一个云厂商及地域。开通成功后，选定的云厂商及地域暂不支持修改。
+您在开通 Databend Cloud 账号时需要选定一个云厂商及地域。开通成功后，选定的云厂商及地域暂不支持修改。

docs/en/guides/00-overview/00-editions/02-dc/01-platforms.md

@@ -4,10 +4,10 @@ title: Platforms & Regions
 
 Databend Cloud is a cloud-native solution that currently supports [Amazon S3](https://aws.amazon.com/s3/) in the following regions:
 
-![alt text](../../../../../public/img/cloud/dc-platform-en.png)
+![alt text](/img/cloud/dc-platform-en.png)
 
 :::note
 Databend Cloud plans to expand its support for additional cloud platforms and regions. If your project requires support for a specific cloud platform or region, please click the **Contact Sales** button on the top right corner of the Databend Cloud homepage to get in touch with the Databend Cloud team.
 :::
 
-When you sign up for a Databend Cloud account, you will need to select a cloud platform and region. Once the account is successfully created, the selected cloud platform and region cannot be changed.
+When you sign up for a Databend Cloud account, you will need to select a cloud platform and region. Once the account is successfully created, the selected cloud platform and region cannot be changed.

docs/en/guides/00-overview/02-faq.md

@@ -6,7 +6,7 @@ title: FAQ
 
 The diagram illustrates the hierarchical structure of Databend objects across two levels. Fine-grained privileges and ownership are designed for each type of object, providing flexibility. For more information, see [Access Control](../56-security/access-control/index.md).
 
-![Alt text](@site/docs/public/img/guides/faq1.png)
+![Alt text](/img/guides/faq1.png)
 
 ### Q2: How do I create a table in Databend?
 
@@ -28,31 +28,31 @@ CREATE TABLE example (
 
 This table provides an outline of the mapping of data types between Databend, MySQL, and Oracle.
 
-| Databend      | MySQL     | Oracle       |
-|---------------|-----------|--------------|
-| TINYINT       | TINYINT   | NUMBER(3,0)  |
-| SMALLINT      | SMALLINT  | NUMBER(5,0)  |
-| INT           | INT       | NUMBER(10,0) |
-| BIGINT        | BIGINT    | NUMBER(19,0) |
-| FLOAT         | FLOAT     | FLOAT        |
-| DOUBLE        | DOUBLE    | FLOAT(24)    |
-| DECIMAL       | DECIMAL   | NUMBER       |
-| DATE          | DATE      | DATE         |
-| TIMESTAMP     | TIMESTAMP | NUMBER       |
-| DATETIME      | DATETIME  | DATE         |
-| YEAR          | INT       | NUMBER       |
-| VARCHAR       | VARCHAR   | VARCHAR2     |
-| VARCHAR       | CHAR      | CHAR         |
-| BINARY        | VARBINARY | RAW, BLOB    |
-| VARCHAR       | TEXT      | VARCHAR2     |
-| VARCHAR       | LONGTEXT  | RAW, CBLOB   |
-| VARCHAR       | MEDIUMTEXT| RAW, CBLOB   |
-| VARCHAR       | ENUM      | VARCHAR2     |
-| VARCHAR       | SET       | VARCHAR2     |
-| VARCHAR       | bit       | CHAR         |
-| ARRAY         | N/A       | N/A          |
-| BOOLEAN       | N/A       | N/A          |
-| TUPLE         | N/A       | N/A          |
-| MAP           | N/A       | N/A          |
-| JSON, VARIANT | JSON      | JSON         |
-| BITMAP        | N/A       | N/A          |
+| Databend      | MySQL      | Oracle       |
+| ------------- | ---------- | ------------ |
+| TINYINT       | TINYINT    | NUMBER(3,0)  |
+| SMALLINT      | SMALLINT   | NUMBER(5,0)  |
+| INT           | INT        | NUMBER(10,0) |
+| BIGINT        | BIGINT     | NUMBER(19,0) |
+| FLOAT         | FLOAT      | FLOAT        |
+| DOUBLE        | DOUBLE     | FLOAT(24)    |
+| DECIMAL       | DECIMAL    | NUMBER       |
+| DATE          | DATE       | DATE         |
+| TIMESTAMP     | TIMESTAMP  | NUMBER       |
+| DATETIME      | DATETIME   | DATE         |
+| YEAR          | INT        | NUMBER       |
+| VARCHAR       | VARCHAR    | VARCHAR2     |
+| VARCHAR       | CHAR       | CHAR         |
+| BINARY        | VARBINARY  | RAW, BLOB    |
+| VARCHAR       | TEXT       | VARCHAR2     |
+| VARCHAR       | LONGTEXT   | RAW, CBLOB   |
+| VARCHAR       | MEDIUMTEXT | RAW, CBLOB   |
+| VARCHAR       | ENUM       | VARCHAR2     |
+| VARCHAR       | SET        | VARCHAR2     |
+| VARCHAR       | bit        | CHAR         |
+| ARRAY         | N/A        | N/A          |
+| BOOLEAN       | N/A        | N/A          |
+| TUPLE         | N/A        | N/A          |
+| MAP           | N/A        | N/A          |
+| JSON, VARIANT | JSON       | JSON         |
+| BITMAP        | N/A        | N/A          |

docs/en/guides/10-deploy/01-deploy/00-understanding-deployment-modes.md

@@ -1,8 +1,7 @@
 ---
 title: Understanding Databend Deployments
 sidebar_label: Understanding Deployments
-description:
-  Describes Databend deployment modes
+description: Describes Databend deployment modes
 ---
 
 ## Databend Node Types
@@ -17,7 +16,7 @@ Please note that, when we mention "nodes," it refers to individual servers that
 
 ## Deployment Modes
 
-Databend deployment provides two modes: standalone and cluster, each with different application scenarios and node configurations. 
+Databend deployment provides two modes: standalone and cluster, each with different application scenarios and node configurations.
 
 ### Standalone Deployment
 
@@ -46,11 +45,11 @@ The primary goal of a Query cluster is to ensure that the query processing speed
 
 #### Tenant Management
 
-A tenant refers to an entity or organization that utilizes the services or resources provided by a system. In Databend, a tenant is associated with a unique tenant ID, which serves as an identifier to differentiate and manage their data, users, and resources within Databend. 
+A tenant refers to an entity or organization that utilizes the services or resources provided by a system. In Databend, a tenant is associated with a unique tenant ID, which serves as an identifier to differentiate and manage their data, users, and resources within Databend.
 
 In the case of a query cluster, when a SQL request is received by a query node, the computational workload is efficiently distributed among query nodes that share the same tenant ID and cluster ID. Please note that query nodes with the same tenant ID but different cluster IDs provide a mechanism for workload isolation while still sharing the same data and user lists.
 
-![Alt text](@site/docs/public/img/deploy/tenantid.PNG)
+![Alt text](/img/deploy/tenantid.PNG)
 
 ## Deployment Environments
 
@@ -60,12 +59,12 @@ This topic provides information on the recommended hardware specifications for D
 
 Databend nodes can be deployed either on-premises servers or in the cloud. Databend is compatible with various public cloud platforms, such as Amazon EC2, Azure VMs, Tencent Cloud, and Alibaba Cloud. The table below outlines the recommended hardware specifications for servers running Databend nodes:
 
-| Hardware Specification  	| Standalone Mode  	| Cluster Mode (Meta Node) 	| Cluster Mode (Query Node) 	|
-|-------------------------	|------------------	|--------------------------	|---------------------------	|
-| CPU                     	| 16-cores or above	| 4-cores or above         	| 16-cores or above          	|
-| Memory                  	| 32 GB or above   	| 16 GB or above           	| 32 GB or above            	|
-| Data Disk (SSD)           | 200-600 GB       	| 100-200 GB               	| 100-200 GB                	|
-| Network Interface Card  	| 10 Gbps or above 	| 10 Gbps or above         	| 10 Gbps or above          	|
+| Hardware Specification | Standalone Mode   | Cluster Mode (Meta Node) | Cluster Mode (Query Node) |
+| ---------------------- | ----------------- | ------------------------ | ------------------------- |
+| CPU                    | 16-cores or above | 4-cores or above         | 16-cores or above         |
+| Memory                 | 32 GB or above    | 16 GB or above           | 32 GB or above            |
+| Data Disk (SSD)        | 200-600 GB        | 100-200 GB               | 100-200 GB                |
+| Network Interface Card | 10 Gbps or above  | 10 Gbps or above         | 10 Gbps or above          |
 
 ### Supported Object Storage
 

docs/en/guides/10-deploy/01-deploy/01-non-production/00-deploying-local.md

@@ -23,7 +23,7 @@ To quickly access Databend features and gain practical expertise, you have the f
 
 In this guide, you will deploy Databend along with [MinIO](https://min.io/) using [Docker](https://www.docker.com/) for a containerized setup on an [Amazon EC2](https://aws.amazon.com/ec2/) Ubuntu virtual machine.
 
-![Alt text](@site/docs/public/img/deploy/docker-deploy.png)
+![Alt text](/img/deploy/docker-deploy.png)
 
 <StepsWrap>
 <StepContent number="1">
@@ -34,11 +34,11 @@ Before you start, launch an instance on Amazon EC2 and install the Docker engine
 
 1. Log into the [Amazon EC2 console](https://console.aws.amazon.com/ec2/), and launch an Ubuntu instance with a memory capacity of at least 8 GiB. Once the instance is up, you can find the public IP address and the private IP address assigned to the instance on the instance details page.
 
-![Alt text](@site/docs/public/img/deploy/docker-instance.png)
+![Alt text](/img/deploy/docker-instance.png)
 
 2. Create a security group, and add an inbound rule to allow access to your instance through port `9001`, then add the security group to the instance.
 
-![Alt text](@site/docs/public/img/deploy/docker-create-sg.png)
+![Alt text](/img/deploy/docker-create-sg.png)
 
 3. Connect to your instance. There are many ways to connect to your instance from a local machine. For more information, see https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/connect-to-linux-instance.html.
 
@@ -95,11 +95,11 @@ STARTUP WARNINGS:
 
 3. Open your web browser on your local machine and visit the MinIO console using the WebUI address shown in the logs above (replace the IP address with your instance's public IP address). For example, if your instance's public IP address is `3.142.131.212`, then your MinIO console address would be `http://3.142.131.212:9001`.
 
-![Alt text](@site/docs/public/img/deploy/docker-minio.png)
+![Alt text](/img/deploy/docker-minio.png)
 
 4. Log into the MinIO console with the credentials `ROOTUSER`/`CHANGEME123`, and create a bucket named `databend`.
 
-![Alt text](@site/docs/public/img/deploy/docker-bucket.png)
+![Alt text](/img/deploy/docker-bucket.png)
 
 </StepContent>
 

docs/en/guides/10-deploy/01-deploy/02-production/02-deploying-databend-on-kubernetes.md

@@ -8,7 +8,7 @@ This topic explains how to install and configure the Databend cluster on Kuberne
 
 ## Deployment Architecture
 
-![Deployment Architecture](@site/docs/public/img/deploy/k8s-deployment-arch.jpg)
+![Deployment Architecture](/img/deploy/k8s-deployment-arch.jpg)
 
 **Scenario Description**
 
@@ -605,17 +605,17 @@ Note the `serviceMonitor` should be enabled when deploying meta and query cluste
 
 - Select `+` on the upper right corner to expand the menu, click on "Import dashboard" to import the dashboard, and upload the two downloaded JSON files.
 
-  ![Alt text](@site/docs/public/img/deploy/import-dashboard.png)
+  ![Alt text](/img/deploy/import-dashboard.png)
 
 - Then you should see the two dashboard:
 
   - Databend Meta Runtime
 
-    ![Alt text](@site/docs/public/img/deploy/databend-meta-runtime.png)
+    ![Alt text](/img/deploy/databend-meta-runtime.png)
 
   - Databend Query Runtime
 
-    ![Alt text](@site/docs/public/img/deploy/databend-query-runtime.png)
+    ![Alt text](/img/deploy/databend-query-runtime.png)
 
 ## Next Steps
 

docs/en/guides/10-deploy/03-monitor/tools/prometheus-and-grafana.md

@@ -68,7 +68,7 @@ The steps below describe how to install and deploy Prometheus using Docker.
 
    Check the value on the right of each instance. `1` means the instance is healthy, and `0` means that the scrape failed.
 
-   ![Prometheus up](@site/docs/public/img/tracing/prometheus-up.png)
+   ![Prometheus up](/img/tracing/prometheus-up.png)
 
 ### Step 3. Deploy Grafana
 
@@ -95,12 +95,12 @@ The steps below describe how to install and deploy Grafana using Docker.
 
    Please note that set the URL to `http://host.docker.internal:9090` for the data source.
 
-   ![Grafana data source](@site/docs/public/img/tracing/grafana-datasource.png)
+   ![Grafana data source](/img/tracing/grafana-datasource.png)
 
 4. Create dashboards.
 
    Databend recommend import the files in [datafuselabs/helm-charts - dashboards](https://github.com/datafuselabs/helm-charts/tree/main/dashboards) to create your dashboards. To do so, download the files first, then go to `http://0.0.0.0:3000/dashboard/import` to import the downloaded files one by one and select the `Prometheus` data source for each dashboard.
 
-   ![Grafana import query json](@site/docs/public/img/tracing/grafana-query-json.png)
+   ![Grafana import query json](/img/tracing/grafana-query-json.png)
 
-   ![Grafana query dashboard](@site/docs/public/img/tracing/grafana-query-dashboard.png)
+   ![Grafana query dashboard](/img/tracing/grafana-query-dashboard.png)

docs/en/guides/20-cloud/10-using-databend-cloud/03-monitor.md

@@ -38,25 +38,25 @@ Query Profile refers to the graphical representation or visual breakdown of how
 
 Here is an example of a query profile, comprising a set of three operator nodes in a hierarchical structure. When executing the SQL statement, Databend Cloud processes the nodes in a bottom-to-top sequence. The quantity and types of operator nodes a query profile contains depend on the specifics of your SQL statement. For the common operators and their statistical fields, see [Common Operators and Fields](/sql/sql-commands/explain-cmds/explain#common-operators-and-fields).
 
-![alt text](../../../../public/img/cloud/query-profile-1.png)
+![alt text](/img/cloud/query-profile-1.png)
 
 *Please note that the bracketed number in each node's title represents the node ID and does *not* indicate the execution step.*
 
 A query profile comes with a set of information panes that offer more details. The example above includes two information panes:
 
 | Pane                 | Description                                                                                                                                                                                            |
-|----------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| -------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
 | Most Expensive Nodes | Lists the nodes with the longest execution times.                                                                                                                                                      |
 | Profile Overview     | Displays the percentage of time spent on CPU and I/O. Please note that if you select a node, this information pane shows the information specific to the node you select, rather than the whole query. |
 
 If you click on the `TableScan [4]` node, you will notice that two additional information panes have been added to the right:
 
-![alt text](../../../../public/img/cloud/query-profile-2.png)
+![alt text](/img/cloud/query-profile-2.png)
 
-| Pane       | Description                                                                                                                         |
-|------------|-------------------------------------------------------------------------------------------------------------------------------------|
+| Pane       | Description                                                                                                        |
+| ---------- | ------------------------------------------------------------------------------------------------------------------ |
 | Statistics | Includes information such as scan progress, bytes scanned, percentage scanned from cache, partitions scanned, etc. |
-| Attributes | Displays details specific to the node. The shown fields vary based on the functionality of the node.                                |
+| Attributes | Displays details specific to the node. The shown fields vary based on the functionality of the node.               |
 
 ## Audit