diff --git a/.github/workflows/link-check-deploy.yml b/.github/workflows/link-check-deploy.yml
index 45068a38d8..1dca96cd73 100644
--- a/.github/workflows/link-check-deploy.yml
+++ b/.github/workflows/link-check-deploy.yml
@@ -13,6 +13,8 @@ jobs:
       github.event.deployment_status.state == 'success'
     steps:
       - uses: actions/checkout@v2
+        with:
+          fetch-depth: 0
       - id: build_check
         uses: LouisBrunner/checks-action@v1.0.0
         with:
@@ -21,7 +23,7 @@ jobs:
           status: queued
       - name: Run Link Check
         id: check
-        uses: iterative/link-check.action@v0.8
+        uses: iterative/link-check.action@v0.9
         with:
           diff: true
           configFile: config/link-check/config.yml
diff --git a/content/docs/sidebar.json b/content/docs/sidebar.json
index 1a79209f4f..93d26bd2a7 100644
--- a/content/docs/sidebar.json
+++ b/content/docs/sidebar.json
@@ -148,6 +148,7 @@
         "source": "experiment-management/index.md",
         "children": [
           "running-experiments",
+          "comparing-experiments",
           "sharing-experiments",
           "cleaning-experiments",
           "checkpoints"
diff --git a/content/docs/user-guide/experiment-management/comparing-experiments.md b/content/docs/user-guide/experiment-management/comparing-experiments.md
new file mode 100644
index 0000000000..7ad3083fe6
--- /dev/null
+++ b/content/docs/user-guide/experiment-management/comparing-experiments.md
@@ -0,0 +1,501 @@
+# Comparing Experiments
+
+You'll need a way to compare experiment results and track their corresponding
+parameters. DVC provides commands to list, tabulate and contrast them. Let's see
+how they can help you streamline the experimentation process.
+
+## List experiments in the workspace
+
+You can get a list of existing experiments in the repository with
+`dvc exp list`. Without any options, this command lists the experiments based on
+the latest commit of the current branch (Git `HEAD`).
+
+```dvc
+$ dvc exp list
+refs/tags/baseline-experiment:
+        cnn-64
+        cnn-128
+```
+
+If you want to list all the experiments in the repository regardless of their
+parent commit, use the `--all` flag.
+
+```dvc
+$ dvc exp list --all
+refs/tags/baseline-experiment:
+        cnn-64
+        cnn-128
+main:
+        exp-93150
+```
+
+## List experiments in another Git remote
+
+As we discuss in [Sharing Experiments], you can use `dvc exp push` to upload
+experiments to Git remotes. `dvc exp list` can be used to list the experiments
+in a Git remote.
+
+```dvc
+$ dvc exp list origin
+refs/tags/baseline-experiment:
+        cnn-32
+        cnn-64
+```
+
+This command lists the experiments originated from `HEAD`. You can add any other
+options to the remote command, including `--all`. (see previous section).
+
+[sharing experiments]: /doc/user-guide/experiment-management/sharing-experiments
+
+## List experiment names to use in scripts
+
+`dvc exp list` may be printing more than the necessary information when it comes
+to feed its output to other commands. You can get only the names of the
+experiments via `--names-only` flag.
+
+For example, to get all the experiment names from a Git remote:
+
+```dvc
+$ for experiment in $(dvc exp list origin --names-only --all) ; do
+  dvc exp pull "${experiment}"
+done
+```
+
+## List experiments based on a specific commit, tag or branch
+
+The `--rev` option allows to specify a Git commit, tag or branch name to list
+the experiments based on it.
+
+For example, to list of experiments in a Git repository stemmed from a
+particular commit:
+
+```dvc
+$ dvc exp list origin --rev 23ceb4a
+23ceb4a:
+        cnn-32
+        cnn-96
+```
+
+or a tag:
+
+```dvc
+$ dvc exp list origin --rev baseline-experiment
+refs/tags/baseline-experiment:
+        cnn-64
+        cnn-128
+```
+
+or a fully specified Git reference:
+
+```dvc
+$ dvc exp list origin --rev refs/tags/baseline-experiment
+refs/tags/baseline-experiment:
+        cnn-64
+        cnn-128
+```
+
+## Show a table of experiments
+
+Experimentation is about generating many possibilities before selecting a few of
+them. You can get a table of experiments with `dvc exp show`, which displays all
+the parameters and metrics in a nicely formatted table.
+
+```dvc
+$ dvc exp show
+```
+
+```dvctable
+┏━━━━━━━━━━━━━━━━━━━━━━━┳━━━━━━━━━━━━━━┳━━━━━━━━━┳━━━━━━━━┳━━━━━━━━━━━━━━┳━━━━━━━━━━━━━━━━━━┓
+┃ neutral:**Experiment**            ┃ neutral:**Created**      ┃    metric:**loss** ┃    metric:**acc** ┃ param:**train.epochs** ┃ param:**model.conv_units** ┃
+┡━━━━━━━━━━━━━━━━━━━━━━━╇━━━━━━━━━━━━━━╇━━━━━━━━━╇━━━━━━━━╇━━━━━━━━━━━━━━╇━━━━━━━━━━━━━━━━━━┩
+│ workspace             │ -            │ 0.23657 │ 0.9127 │ 10           │ 16               │
+│ baseline-experiment   │ Sep 06, 2021 │ 0.23657 │ 0.9127 │ 10           │ 16               │
+│ ├── 6d13f33 [cnn-64]  │ Sep 09, 2021 │ 0.23385 │ 0.9153 │ 10           │ 64               │
+│ ├── 69503c6 [cnn-128] │ Sep 09, 2021 │ 0.23243 │  0.916 │ 10           │ 128              │
+└───────────────────────┴──────────────┴─────────┴────────┴──────────────┴──────────────────┘
+```
+
+`dvc exp show` only tabulates experiments in the workspace and in `HEAD`. You
+can use `--all` flag to show all the experiments in the project instead.
+
+## Customize the table of experiments
+
+The table output may become cluttered if you have a large number of parameters
+and metrics. `dvc exp show` provides several options to select the parameters
+and metrics to be shown in the table.
+
+The `--include-params` and `--include-metrics` options take a list of
+comma-separated parameter or metrics names (defined in `dvc.yaml`).
+
+```dvc
+$ dvc exp show --include-params train.epochs --include-metrics auc,precision
+```
+
+`````dvctable
+┏━━━━━━━━━━━━━━━━━━━━━━━┳━━━━━━━━━━━━━━┳━━━━━━━━━┳━━━━━━━━┳━━━━━━━━━━━━━━┓
+┃ neutral:**Experiment**            ┃ neutral:**Created**      ┃    metric:**loss** ┃    metric:**acc** ┃ param:**train.epochs** ┃
+┡━━━━━━━━━━━━━━━━━━━━━━━╇━━━━━━━━━━━━━━╇━━━━━━━━━╇━━━━━━━━╇━━━━━━━━━━━━━━┩
+│ workspace             │ -            │ 0.23657 │ 0.9127 │ 10           │
+│ baseline-experiment   │ Sep 06, 2021 │ 0.23657 │ 0.9127 │ 10           │
+│ ├── 6d13f33 [cnn-64]  │ Sep 09, 2021 │ 0.23385 │ 0.9153 │ 10           │
+│ └── 69503c6 [cnn-128] │ Sep 09, 2021 │ 0.23243 │  0.916 │ 10           │
+└───────────────────────┴──────────────┴─────────┴────────┴──────────────┘
+
+Alternatively, you can exclude certain parameters and metrics from the
+table by `--exclude-params` and `--exclude-metrics` options. These also take a comma-separated list.
+
+```dvc
+$ dvc exp show --exclude-params train.epochs --exclude-metrics auc
+```
+
+```dvctable
+┏━━━━━━━━━━━━━━━━━━━━━━━┳━━━━━━━━━━━━━━┳━━━━━━━━┳━━━━━━━━━━━━━━━━━━┓
+┃ neutral:**Experiment**            ┃ neutral:**Created**      ┃    metric:**acc** ┃ param:**model.conv_units** ┃
+┡━━━━━━━━━━━━━━━━━━━━━━━╇━━━━━━━━━━━━━━╇━━━━━━━━╇━━━━━━━━━━━━━━━━━━┩
+│ workspace             │ -            │ 0.9127 │ 16               │
+│ baseline-experiment   │ Sep 06, 2021 │ 0.9127 │ 16               │
+│ ├── 6d13f33 [cnn-64]  │ Sep 09, 2021 │ 0.9153 │ 64               │
+│ └── 69503c6 [cnn-128] │ Sep 09, 2021 │  0.916 │ 128              │
+└───────────────────────┴──────────────┴────────┴──────────────────┘
+```
+
+By default, `dvc exp show` also has a column for the timestamp. You may want to
+hide it with `--no-timestamp` option.
+
+```dvc
+$ dvc exp show --no-timestamp --include-params=model.conv_units --exclude-metrics=loss
+```
+
+````dvctable
+┏━━━━━━━━━━━━━━━━━━━━━━━┳━━━━━━━━┳━━━━━━━━━━━━━━━━━━┓
+┃ neutral:**Experiment**            ┃    metric:**acc** ┃ param:**model.conv_units** ┃
+┡━━━━━━━━━━━━━━━━━━━━━━━╇━━━━━━━━╇━━━━━━━━━━━━━━━━━━┩
+│ workspace             │ 0.9127 │ 16               │
+│ baseline-experiment   │ 0.9127 │ 16               │
+│ ├── 6d13f33 [cnn-64]  │ 0.9153 │ 64               │
+│ └── 69503c6 [cnn-128] │  0.916 │ 128              │
+└───────────────────────┴────────┴──────────────────┘
+
+By default `dvc exp show` sorts the experiments by their timestamp. You can sort
+the columns by params or metrics by the option `--sort-by` and `--sort-order`.
+`--sort-by` takes a metric or parameter name, and `--sort-order` takes either `asc` or `desc`.
+
+```dvc
+$ dvc exp show --sort-by auc --sort-order desc
+`````
+
+```dvctable
+┏━━━━━━━━━━━━━━━━━━━━━━━┳━━━━━━━━┳━━━━━━━━━━━━━━━━━━┓
+┃ neutral:**Experiment**            ┃    metric:**acc** ┃ param:**model.conv_units** ┃
+┡━━━━━━━━━━━━━━━━━━━━━━━╇━━━━━━━━╇━━━━━━━━━━━━━━━━━━┩
+│ workspace             │ 0.9127 │ 16               │
+│ baseline-experiment   │ 0.9127 │ 16               │
+│ ├── 6d13f33 [cnn-64]  │ 0.9153 │ 64               │
+│ └── 69503c6 [cnn-128] │  0.916 │ 128              │
+└───────────────────────┴────────┴──────────────────┘
+```
+
+## Get experiments table in JSON
+
+It's also possible to output the table of experiments in a machine-readable
+format, for example to parse in scripts. To do so, use the `--json` or `--csv`
+options.
+
+```dvc
+$ dvc exp show --json
+```
+
+```json
+{
+  "workspace": {
+    "baseline": {
+      "data": {
+        "timestamp": null,
+        "params": {
+          "params.yaml": {
+            "data": {
+              "train": {
+                "epochs": 10
+              },
+              "model": {
+                "conv_units": 16
+              }
+            }
+          }
+        },
+        "queued": false,
+        "running": false,
+        "executor": null,
+        "metrics": {
+          "metrics.json": {
+            "data": {
+              "loss": 0.236574187874794,
+              "acc": 0.9126999974250793
+            }
+          }
+        }
+      }
+    }
+  },
+  "23ceb4a6623d46a5c906f265b5846ef2f332f756": {
+    "baseline": {...}
+    "ca55d7d4763d74bfeac2ca08369489c2881c03ac": {...}
+    "6d13f334bbdd6ea40412d4ce9b5d81d6abb731ee": {...}
+    "69503c61df98752b07772415e0715655dc4ccaa0": {...}
+    "49779aa9c863a5503008eae08b03a6e707f8ddad": {...}
+  }
+}
+```
+
+The result is a JSON dictionary with the keys `workspace` and the Git commit IDs
+in SHA-256 digest. These commit IDs are those that the experiments are
+originated from. These commits contain a `baseline` key that denotes the
+baseline experiment of that particular commit and experiment IDs in SHA-256
+digest. The example output above is shortened to show this structure.
+
+Each experiment entry has the following structure:
+
+```json
+"49779aa9c863a5503008eae08b03a6e707f8ddad": {
+      "data": {
+        "timestamp": "2021-09-09T12:53:51",
+        "params": {
+          "params.yaml": {
+            "data": {
+              "train": {
+                "epochs": 10
+              },
+              "model": {
+                "conv_units": 96
+              }
+            }
+          }
+        },
+        "queued": false,
+        "running": false,
+        "executor": null,
+        "metrics": {
+          "metrics.json": {
+            "data": {
+              "loss": 0.2309877723455429,
+              "acc": 0.916100025177002
+            }
+          }
+        },
+        "name": "cnn-64"
+      }
+    }
+```
+
+As an example, let's feed our experiments to JSON-parsing tool
+[jq](https://stedolan.github.io/jq/) and filter through only metrics:
+
+```dvc
+$ dvc exp show --json | jq '.[].baseline.data.metrics'
+{
+  "metrics.json": {
+    "data": {
+      "loss": 0.236574187874794,
+      "acc": 0.9126999974250793
+    }
+  }
+}
+{
+  "metrics.json": {
+    "data": {
+      "loss": 0.236574187874794,
+      "acc": 0.9126999974250793
+    }
+  }
+}
+```
+
+## Get experiments table in CSV
+
+`dvc exp show` can also output the table in CSV, with `--csv`. It includes all
+the data found in the table.
+
+```dvc
+$ dvc exp show --csv
+```
+
+```csv
+Experiment,rev,typ,Created,parent,loss,acc,train.epochs,model.conv_units
+,workspace,baseline,,,0.236574187874794,0.9126999974250793,10,16
+baseline-experiment,23ceb4a,baseline,2021-09-06T23:38:07,,0.236574187874794,0.9126999974250793,10,16
+cnn-64,6d13f33,branch_commit,2021-09-09T13:06:05,,0.2338544875383377,0.9153000116348267,10,64
+cnn-128,69503c6,branch_commit,2021-09-09T12:53:51,,0.2324332743883133,0.9160000085830688,10,128
+```
+
+For example, let's parse the CSV output with [csvkit] to get a statistical
+summary about the experiments:
+
+```dvc
+$ dvc exp show --csv | csvstat
+...
+7. "acc"
+
+        Type of data:          Number
+        Contains null values:  False
+        Unique values:         5
+        Smallest value:        0.9127
+        Largest value:         0.9167
+        Sum:                   5.4895
+        Mean:                  0.914917
+        Median:                0.91565
+        StDev:                 0.001774
+        Most common values:    0.9127 (2x)
+                               0.9167 (1x)
+                               0.9153 (1x)
+                               0.9161 (1x)
+                               0.916 (1x)
+...
+```
+
+[csvkit]: https://csvkit.readthedocs.io/en/latest/
+
+## Compare specific experiments
+
+In addition to showing a summary table of experiments, DVC provides the
+`dvc exp diff` command to compare pairs of experiments by the difference in
+their metrics and params.
+
+```dvc
+$ dvc exp diff
+Path          Metric    Value    Change
+metrics.json  acc       0.9151   0.0024
+metrics.json  loss      0.23867  0.0020977
+
+Path         Param             Value    Change
+params.yaml  model.conv_units  256      240
+```
+
+Without experiment names, `dvc exp diff` shows the change between the last
+experiment and the last commit. So if the command doesn't print an output, there
+might be no experiment since the previous commit or it didn't produce changes in
+results. If you want to see all the parameters and metrics regardless of whether
+they have changed, you can use `--all` flag.
+
+```dvc
+$ dvc exp diff --all
+Path          Metric    Value    Change
+metrics.json  acc       0.9151   0.0024
+metrics.json  loss      0.23867  0.0020977
+
+Path         Param             Value    Change
+params.yaml  model.conv_units  256      240
+params.yaml  train.epochs      10       0
+```
+
+## Compare an experiment with the workspace
+
+When you want to compare two experiments, either the baseline experiment in a
+commit, branch, tag or an attached experiment with ID, you can supply their
+names to `dvc exp diff`.
+
+```
+$ dvc exp diff cnn-128 cnn-64
+Path          Metric    Value    Change
+metrics.json  acc       0.9153   0.00020003
+metrics.json  loss      0.23385  -0.0048174
+
+Path         Param             Value    Change
+params.yaml  model.conv_units  64       -192
+```
+
+## Customize the comparison output
+
+You can hide the file path of metrics and parameter files the `--no-path` option
+-- produces cleaner output for single params/metrics files, for example. You can
+also customize the amount of significant digits shown for numeric values with
+the `--precision` option (5 by default).
+
+```dvc
+$ dvc exp diff exp-25a26 cnn-64 --no-path --precision 2
+Metric    Value    Change
+acc       0.92     0.0002
+loss      0.23     -0.0048
+
+Param             Value    Change
+model.conv_units  64       -192
+```
+
+### Get the comparison in JSON
+
+Parsing the output of `dvc exp diff` may not be easy when you want to use it in
+other commands. `dvc exp diff` can output in JSON with `--json` flag.
+
+```dvc
+$ dvc exp diff exp-25a26 cnn-64 --json
+```
+
+```json
+{
+  "metrics": {
+    "metrics.json": {
+      "loss": {
+        "old": 0.2386719286441803,
+        "new": 0.2338544875383377,
+        "diff": -0.00481744110584259
+      },
+      "acc": {
+        "old": 0.9150999784469604,
+        "new": 0.9153000116348267,
+        "diff": 0.00020003318786621094
+      }
+    }
+  },
+  "params": {
+    "params.yaml": {
+      "model.conv_units": {
+        "old": 256,
+        "new": 64,
+        "diff": -192
+      }
+    }
+  }
+}
+```
+
+The output is a JSON dictionary with two keys, `metrics` and `params`, which
+have dictionaries as values. `metrics` and `params` dictionaries has keys for
+each of the metrics or params file, and for each file metrics and parameters are
+listed as keys.
+
+As an example, we can get only a specific metric with [jq]:
+
+```dvc
+$ dvc exp diff exp-25a26 cnn-64 --json | jq '.metrics."metrics.json".acc'
+{
+  "old": 0.9150999784469604,
+  "new": 0.9153000116348267,
+  "diff": 0.00020003318786621094
+}
+```
+
+### Get the comparison in Markdown table format
+
+`dvc exp diff` has also an option to output a [Github-Flavored Markdown][gfm]
+table to embed in the reports directly.
+
+[gfm]: https://github.github.com/gfm/#tables-extension-
+
+```dvc
+$ dvc exp diff exp-25a26 cnn-64 --md
+| Path         | Metric | Value   | Change     |
+| ------------ | ------ | ------- | ---------- |
+| metrics.json | acc    | 0.9153  | 0.00020003 |
+| metrics.json | loss   | 0.23385 | -0.0048174 |
+
+
+| Path        | Param            | Value | Change |
+| ----------- | ---------------- | ----- | ------ |
+| params.yaml | model.conv_units | 64    | -192   |
+```
+
+You can use this output to automatically update the documents with a command
+like:
+
+```dvc
+$ dvc exp diff exp-25a26 cnn-64 --md | xargs --replace=DIFFTABLE -- sed -i -e 's/EXPERIMENT_RESULT/DIFFTABLE/' my-template.md
+```