Adjust some md file name (#561)

* adjust some md file name

* update bed url

* rename of md file

* rename some docs

* prepare docs version 1.3.1

* update bad url

* update bad url

Author: casionone

blog/2022-02-21-linkis-deploy.md

@@ -420,7 +420,7 @@ normal as follows
 
 
 Check whether the material record of the engine exists (if there is an update, check whether the update time is correct).  
-If it does not exist or is not updated, first try to manually refresh the material resource (for details, see [Engine Material Resource Refresh](docs/latest/deployment/engine-conn-plugin-installation#23-Engine Refresh)). Check the `log/linkis-cg-engineplugin.log` log to check the specific reasons for the failure of the material. In many cases, it may be caused by the lack of permissions in the hdfs directory. Check whether the gateway address configuration is correct `conf/linkis.properties:wds.linkis.gateway.url`
+If it does not exist or is not updated, first try to manually refresh the material resource (for details, see [Engine Material Resource Refresh](docs/latest/deployment/install-engineconn#23-Engine Refresh)). Check the `log/linkis-cg-engineplugin.log` log to check the specific reasons for the failure of the material. In many cases, it may be caused by the lack of permissions in the hdfs directory. Check whether the gateway address configuration is correct `conf/linkis.properties:wds.linkis.gateway.url`
 
 The material resources of the engine are uploaded to the hdfs directory by default as `/apps-data/${deployUser}/bml`
 ```shell script

blog/2022-04-15-how-to-download-engineconn-plugin.md

@@ -47,4 +47,4 @@ cd 1.0.3-engineconn-plugin
 
 Copy the engine material package to be used to the engine plug-in directory of linkis, and then refresh the engine material.
 
-For the detailed process, refer to [Installing the EngineConnPlugin Engine](https://linkis.apache.org/zh-CN/docs/latest/deployment/engine-conn-plugin-installation).
+For the detailed process, refer to [Installing the EngineConnPlugin Engine](https://linkis.apache.org/zh-CN/docs/latest/deployment/install-engineconn).

docs/deployment/cluster-deployment.md renamed to docs/deployment/deploy-cluster.md

@@ -1,6 +1,6 @@
 ---
 title: Cluster Deployment
-sidebar_position: 2
+sidebar_position: 1.1
 ---
 
 Linkis's stand-alone deployment is simple, but it cannot be used in a production environment, because too many processes on the same server will make the server too stressful. The choice of deployment plan is related to the company's user scale, user habits, and the number of simultaneous users of the cluster. Generally speaking, we will choose the deployment method based on the number of simultaneous users using Linkis and the user's preference for the execution engine.

docs/deployment/web-install.md renamed to docs/deployment/deploy-console.md

@@ -1,12 +1,12 @@
 ---
 title: Console Deployment
-sidebar_position: 3
+sidebar_position: 1.2
 ---
 ```
 The linkis web service uses nginx as a static resource server. The access request process is as follows :
 Linkis Management Console request -> Nginx ip:port-> Linkis-gateway ip:port-> Other services
 ```
-Linkis 1.0 provides a Linkis Console, which provides functions such as displaying Linkis' global history, modifying user parameters, managing ECM and microservices, etc. Before deploying the front-end management console, you need to deploy the Linkis back-end. Linkis deployment manual See: [Linkis Deployment Manual](quick-deploy.md)
+Linkis 1.0 provides a Linkis Console, which provides functions such as displaying Linkis' global history, modifying user parameters, managing ECM and microservices, etc. Before deploying the front-end management console, you need to deploy the Linkis back-end. Linkis deployment manual See: [Linkis Deployment Manual](deploy-quick.md)
 
 ## 1. Preparation
 

docs/deployment/quick-deploy.md renamed to docs/deployment/deploy-quick.md

@@ -44,7 +44,7 @@ hadoop ALL=(ALL) NOPASSWD: NOPASSWD: ALL
 
 - Method 1: From the official website [download address](https://linkis.apache.org/zh-CN/download/main): https://linkis.apache.org/zh-CN/download/main
 , download the corresponding The installation package (project installation package and management console installation package)
-- Method 2: Compile the project installation package and management console according to [Linkis Compile and Package](../development/linkis-compile-and-package) and [Front-end Management Console Compile](../development/web-build) Installation package
+- Method 2: Compile the project installation package and management console according to [Linkis Compile and Package](../development/build) and [Front-end Management Console Compile](../development/build-console) Installation package
 
 After uploading the installation package `apache-linkis-x.x.x-incubating-bin.tar.gz`, decompress the installation package
 
@@ -412,13 +412,13 @@ If the verification fails, please refer to [Step 8] for troubleshooting
 ## 6 Installation of development tool IDE (Scriptis) (optional)
 >After installing the Scripti tool, it can support writing SQL, Pyspark, HiveQL and other scripts online on the web page
 
-For detailed instructions, see [Installation and Deployment of Tool Scriptis](./linkis-scriptis-install)
+For detailed instructions, see [Installation and Deployment of Tool Scriptis](./install-scriptis)
 
 ## 7. Supported Engines
 
 ### 7.1 Engine Adaptation List
 
-Please note: The separate installation package of Linkis only contains four engines by default: Python/Shell/Hive/Spark. If there are other engines (such as jdbc/flink/sqoop and other engines) usage scenarios, you can install them manually. For details, please refer to [ EngineConnPlugin Engine Plugin Installation Documentation](engine-conn-plugin-installation).
+Please note: The separate installation package of Linkis only contains four engines by default: Python/Shell/Hive/Spark. If there are other engines (such as jdbc/flink/sqoop and other engines) usage scenarios, you can install them manually. For details, please refer to [ EngineConnPlugin Engine Plugin Installation Documentation](install-engineconn).
 
 The list of supported engines that have been adapted in this version is as follows:
 
@@ -526,7 +526,7 @@ The normal is as follows:
 
 Check whether the material record of the engine exists (if there is an update, check whether the update time is correct).
 
-- If it does not exist or is not updated, first try to manually refresh the material resource (for details, see [Engine Material Resource Refresh](engine-conn-plugin-installation#23-Engine Refresh)).
+- If it does not exist or is not updated, first try to manually refresh the material resource (for details, see [Engine Material Resource Refresh](install-engineconn#23-Engine Refresh)).
 - Check the specific reasons for material failure through `log/linkis-cg-engineplugin.log` log. In many cases, it may be caused by the lack of permissions in the hdfs directory
 - Check whether the gateway address configuration is correct. The configuration item `wds.linkis.gateway.url` of `conf/linkis.properties`
 

docs/deployment/deploy-linkis-to-kbernetes.md renamed to docs/deployment/deploy-to-kubernetes.md

@@ -1,22 +1,24 @@
 ---
-title: linkis Container deployment
-sidebar_position: 12
+title: Kubernetes Deployment
+sidebar_position: 1.4
 ---
+
 This article describes how to deploy a Linkis service in a Kind Kubernetes environment for easier learning and debugging.
 
 ## 1. Dependencies and versions
+
 kind github：https://github.com/kubernetes-sigs/kind   
 kind web site：[kind.sigs.k8s.io/](https://kind.sigs.k8s.io/)
 
-### versions:
-kind 0.14.0  
-docker 20.10.17  
-centos 7.6  
-helm 3.x  
+### Versions
+- kind 0.14.0  
+- docker 20.10.17  
+- centos 7.6  
+- helm 3.x  
 
-### notice：
-1. Ensure that the component depends on the version  
-2.kind means that the machine simulating node with docker container is restarted and the container has changed and the scheduler is not working anymore. This is a kind limitation and there is a detailed explanation in the official document.
+### Notice
+- 1. Ensure that the component depends on the version  
+- 2. kind means that the machine simulating node with docker container is restarted and the container has changed and the scheduler is not working anymore. This is a kind limitation and there is a detailed explanation in the official document.
 
 ## 2.Install the docker
 ### 2.1 Install the tutorial
@@ -41,60 +43,60 @@ vi /etc/docker/daemon.json
 
 ## 3. Install the kind
 
-### （1）Manually download the kind binary
+### Step1 Manually download the kind binary
 ```
 https://github.com/kubernetes-sigs/kind/releases
 ```
-### （2）Install kind Binary
+### Step2 Install kind Binary
 ```
 chmod +x ./kind
 mv kind-linux-amd64 /usr/bin/kind
 ```
 ## 4. Install linkis
-### 0.Download linkis1.3.0 deployment package
+### Step1 Download linkis1.3.0 deployment package
 ```
 apache-linkis-1.3.0-incubating-bin.tar.gz
 ```
-### 1.Build directory
+### Step2 Build directory
 ```
 mkdir -p /opt/data/common/extendlib
 ```
-### 2.Copy driver to /opt/data/common/extendlib
+### Step3 Copy driver to /opt/data/common/extendlib
 ```
 curl https://repo1.maven.org/maven2/mysql/mysql-connector-java/8.0.28/mysql-connector-java-8.0.28.jar -o /opt/data/common/extendlib/[mysql-connector-java-8.0.28.jar](https://repo1.maven.org/maven2/mysql/mysql-connector-java/8.0.28/mysql-connector-java-8.0.28.jar)
 ```
-### 3.Reset kind (not necessary)
+### Step3 Reset kind (not necessary)
 ```
 ./bin/install-linkis-to-kubernetes.sh reset
 ```
-### 4.Pull the image
+### Step5 Pull the image
 ```
 ./bin/install-linkis-to-kubernetes.sh pull -mghcr.dockerproxy.com
 ```
-### 5.Install linkis to kind
+### Step6 Install linkis to kind
 ```
 ./bin/install-linkis-to-kubernetes.sh install -l -mghcr.dockerproxy.com
 ```
-### 6.Run commands to view services and wait until all services are successfully started
+### Step7 Run commands to view services and wait until all services are successfully started
 ```
 kubectl get pods -A
 ```
 ![](/Images/deployment/kubernetes/pods.jpg)
 
-### 7.Copy the ldh environment to linkis
+### Step8 Copy the ldh environment to linkis
 ```
 ./helm/scripts/prepare-for-spark.sh
 ```
-### 8.Enabling Port Mapping
+### Step9 Enabling Port Mapping
 ```
 ./helm/scripts/remote-proxy.sh start
 ```
-### 9.Access to the system
+### Step10 Access to the system
 ```
 linkis-web: http://10.0.2.101:8088/
 eureka: http://10.0.2.101:20303/
 ```
-### 10.Into the container
+### Step11 Into the container
 ```
 ./helm/scripts/login-pod.sh cg-engineconnmanager
 Executing shell tests

docs/deployment/deploy-linkis-without-hdfs.md renamed to docs/deployment/deploy-without-hdfs.md

@@ -1,6 +1,6 @@
 ---
 title: Deploy without HDFS
-sidebar_position: 8
+sidebar_position: 1.3
 ---
 
 This article describes how to deploy Linkis services in an environment where HDFS is not deployed to facilitate more lightweight learning, use and debugging.

docs/deployment/installation-hierarchical-structure.md renamed to docs/deployment/directory-of-deployed.md

@@ -1,6 +1,6 @@
 ---
-title: After Installation Directory Structure
-sidebar_position: 6.2
+title: After Installation Directory
+sidebar_position: 3.2
 ---
 
 > The directory structure of Linkis 1.0 is very different from the 0.X version. Each microservice in 0.X has a root directory that exists independently. The main advantage of this directory structure is that it is easy to distinguish microservices and facilitate individual Microservices are managed, but there are some obvious problems:

docs/deployment/sourcecode-hierarchical-structure.md renamed to docs/deployment/directory-of-sourcecode.md

@@ -1,6 +1,6 @@
 ---
-title:  Source Code Directory Structure
-sidebar_position: 6
+title:  Source Code Directory
+sidebar_position: 3.0
 ---
 
 > Linkis source code hierarchical directory structure description, if you want to learn more about Linkis modules, please check [Linkis related architecture design](architecture/overview.md)

docs/deployment/unpack-hierarchical-structure.md renamed to docs/deployment/directory-of-unpack.md

@@ -1,6 +1,6 @@
 ---
-title: Installation Package Directory Structure
-sidebar_position: 6.1
+title: Installation Package Directory
+sidebar_position: 3.1
 ---
 
 Download the officially released [Compilation Complete Package](https://linkis.apache.org/zh-CN/download/main), and the decompressed directory structure is as follows: