Change URL structure of how-to/get-started (pingcap#1046)

Changed URL structure of how-to/get-started.
Fixed s/sample/example/ bug introduced in DITA
fixed categories

Author: morgo

TOC.md

@@ -26,14 +26,14 @@
 + How-to
   + Get Started
     + Start a Local Cluster
-      - [From Binary](op-guide/binary-local-deployment.md)
+      - [From Binary](dev/how-to/get-started/local-cluster/install-from-binary.md)
       - [From Homebrew](dev/how-to/get-started/local-cluster/install-from-homebrew.md)
       - [From DBdeployer](dev/how-to/get-started/local-cluster/install-from-dbdeployer.md)
-      - [In Kubernetes](op-guide/kubernetes-local.md)
-      - [In Docker Compose](op-guide/docker-compose.md)
-    - [Explore SQL with TiDB](try-tidb.md)
-    - [Import Sample Database](bikeshare-example-database.md)
-    - [Read Historical Data](op-guide/history-read.md)
+      - [In Kubernetes](dev/how-to/get-started/local-cluster/install-from-kubernetes.md)
+      - [In Docker Compose](dev/how-to/get-started/local-cluster/install-from-docker-compose.md)
+    - [Explore SQL with TiDB](dev/how-to/get-started/explore-sql.md)
+    - [Import Example Database](dev/how-to/get-started/import-example-database.md)
+    - [Read Historical Data](dev/how-to/get-started/read-historical-data.md)
   - Deploy
     - [Hardware Recommendations](op-guide/recommendation.md)
     + From Binary Tarball

try-tidb.md dev/how-to/get-started/explore-sql.md

@@ -1,12 +1,13 @@
 ---
-title: Try TiDB
+title: Explore SQL with TiDB 
 summary: Learn about the basic SQL statements for the TiDB database.
-category: try tidb
+category: how-to
+aliases: ['/docs/try-tidb'] 
 ---
 
-# Try TiDB
+# Explore SQL with TiDB
 
-After you successfully deploy a TiDB cluster, you can run SQL statements in TiDB. Because TiDB is compatible with MySQL, you can use THE MySQL client to connect to TiDB and run MySQL statements directly in most of the cases. For more information, see [Compatibility with MySQL](sql/mysql-compatibility.md).
+After you successfully deploy a TiDB cluster, you can run SQL statements in TiDB. Because TiDB is compatible with MySQL, you can use THE MySQL client to connect to TiDB and run MySQL statements directly in most of the cases. For more information, see [Compatibility with MySQL](/sql/mysql-compatibility.md).
 
 This page includes some basic SQL statements such as CRUD operations. For a complete list of the statements, see [TiDB SQL Syntax Diagram](https://pingcap.github.io/sqlgram/).
 

bikeshare-example-database.md dev/how-to/get-started/import-example-database.md

@@ -1,10 +1,11 @@
 ---
-title: Bikeshare Example Database
+title: Import Example Database
 summary: Install the Bikeshare example database.
-category: user guide
+category: how-to 
+aliases: ['/docs/bikeshare-example-database/']
 ---
 
-# Bikeshare Example Database
+# Import Example Database
 
 Examples used in the TiDB manual use [System Data](https://www.capitalbikeshare.com/system-data) from Capital Bikeshare, released under the [Capital Bikeshare Data License Agreement](https://www.capitalbikeshare.com/data-license-agreement).
 

op-guide/binary-local-deployment.md dev/how-to/get-started/local-cluster/install-from-binary.md

@@ -1,14 +1,15 @@
 ---
 title: Local Deployment from Binary Tarball
 summary: Use the binary to deploy a TiDB cluster.
-category: operations
+category: how-to
+aliases: ['/docs/op-guide/binary-local-deployment/']
 ---
 
 # Local Deployment from Binary Tarball
 
 This guide provides installation instructions for all TiDB components on a single developer machine. It is intended for evaluation purposes, and does not match the recommended usage for production systems.
 
-See also [testing environment](../op-guide/binary-testing-deployment.md) and [production enviroment](../op-guide/binary-deployment.md) deployment.
+See also [testing environment](/op-guide/binary-testing-deployment.md) and [production enviroment](/op-guide/binary-deployment.md) deployment.
 
 The following local TCP ports will be used:
 
@@ -36,7 +37,7 @@ EOF
 sudo cp /tmp/tidb.conf /etc/security/limits.d/
 sudo sysctl -w fs.file-max=1000000
 ```
-See the [production deployment](../op-guide/binary-deployment.md) optional kernel tuning parameters.
+See the [production deployment](/op-guide/binary-deployment.md) optional kernel tuning parameters.
 
 ### Create a database running user account
 

dev/how-to/get-started/local-cluster/install-from-dbdeployer.md

@@ -8,7 +8,7 @@ category: how-to
 
 DBdeployer is designed to allow multiple versions of TiDB deployed concurrently. It is recommended for advanced users who are testing out new builds of TiDB, or testing compatibility across releases.
 
-Similar to [Homebrew](install-from-homebrew.md), the DBdeployer installation method installs the tidb-server **without** the tikv-server or pd-server. This is useful for development environments, since you can test your application's compatibility with TiDB without needing to deploy a full TiDB platform.
+Similar to [Homebrew](./install-from-homebrew.md), the DBdeployer installation method installs the tidb-server **without** the tikv-server or pd-server. This is useful for development environments, since you can test your application's compatibility with TiDB without needing to deploy a full TiDB platform.
 
 > **Note**: Internally this installation uses goleveldb as the storage engine. It is much slower than TiKV, and any benchmarks will be unreliable.
 
@@ -25,9 +25,7 @@ Similar to [Homebrew](install-from-homebrew.md), the DBdeployer installation met
   </label>
   <section id="MacOSContent">
 
-After <a href="https://github.com/datacharmer/dbdeployer">installing DBdeployer</a>:
-
-Install a MySQL 5.7 client:
+After <a href="https://github.com/datacharmer/dbdeployer">installing DBdeployer</a>, install a MySQL 5.7 client:
 <pre>
 curl -LO https://dev.mysql.com/get/Downloads/MySQL-5.7/mysql-5.7.25-macos10.14-x86_64.tar.gz
 dbdeployer unpack mysql-5.7.25-macos10.14-x86_64.tar.gz
@@ -43,9 +41,7 @@ dbdeployer deploy single 3.0.0 --client-from=5.7.25
 </section>
   <section id="LinuxContent">
 
-After <a href="https://github.com/datacharmer/dbdeployer">installing DBdeployer</a>:
-
-Install a MySQL 5.7 client:
+After <a href="https://github.com/datacharmer/dbdeployer">installing DBdeployer</a>, install a MySQL 5.7 client:
 <pre>
 dbdeployer remote get mysql-5.7.25
 dbdeployer unpack mysql-5.7.25.tar.xz
@@ -59,4 +55,4 @@ dbdeployer deploy single 3.0.0 --client-from=5.7.25
 </pre>
 
   </section>
-</main>
+</main>

op-guide/docker-compose.md dev/how-to/get-started/local-cluster/install-from-docker-compose.md

@@ -1,7 +1,8 @@
 ---
 title: TiDB Docker Compose Deployment
 summary: Use Docker Compose to quickly deploy a TiDB testing cluster.
-category: operations
+category: how-to 
+aliases: ['/docs/op-guide/docker-compose/']
 ---
 
 # TiDB Docker Compose Deployment
@@ -173,6 +174,6 @@ docker-compose exec tispark-master /opt/spark/bin/pyspark
 docker-compose exec tispark-master /opt/spark/bin/sparkR
 ```
 
-For more details about TiSpark, see [here](../tispark/tispark-quick-start-guide.md).
+For more details about TiSpark, see [here](/tispark/tispark-quick-start-guide.md).
 
-Here is [a 5-minute tutorial](https://www.pingcap.com/blog/how_to_spin_up_an_htap_database_in_5_minutes_with_tidb_tispark/) for macOS users that shows how to spin up a standard TiDB cluster using Docker Compose on your local computer.
+Here is [a 5-minute tutorial](https://www.pingcap.com/blog/how_to_spin_up_an_htap_database_in_5_minutes_with_tidb_tispark/) for macOS users that shows how to spin up a standard TiDB cluster using Docker Compose on your local computer.

op-guide/kubernetes-local.md dev/how-to/get-started/local-cluster/install-from-kubernetes.md

@@ -1,7 +1,8 @@
 ---
 title: Deploy TiDB to Kubernetes Locally
 summary: Use TiDB Operator to quickly deploy a TiDB cluster on Kubernetes
-category: operations
+category: how-to
+aliases: ['/docs/op-guide/kubernetes-local/'] 
 ---
 
 # Deploy TiDB to Kubernetes Locally

op-guide/history-read.md dev/how-to/get-started/read-historical-data.md

@@ -1,10 +1,11 @@
 ---
-title: Reading Data from History Versions
+title: Read Historical Data
 summary: Learn about how TiDB reads data from history versions.
-category: advanced
+category: how-to
+aliases: ['/docs/op-guide/history-read/'] 
 ---
 
-# Reading Data From History Versions
+# Read Historical Data
 
 This document describes how TiDB reads data from the history versions, how TiDB manages the data versions, as well as an example to show how to use the feature.
 
@@ -33,7 +34,7 @@ After reading data from history versions, you can read data from the latest vers
 
 TiDB implements Multi-Version Concurrency Control (MVCC) to manage data versions. The history versions of data are kept because each update/removal creates a new version of the data object instead of updating/removing the data object in-place. But not all the versions are kept. If the versions are older than a specific time, they will be removed completely to reduce the storage occupancy and the performance overhead caused by too many history versions.
 
-In TiDB, Garbage Collection (GC) runs periodically to remove the obsolete data versions. For GC details, see [TiDB Garbage Collection (GC)](../op-guide/gc.md)
+In TiDB, Garbage Collection (GC) runs periodically to remove the obsolete data versions. For GC details, see [TiDB Garbage Collection (GC)](/op-guide/gc.md)
 
 Pay special attention to the following two variables: