Regular updates (Apr 7)

README.md

@@ -11,7 +11,7 @@ code.
 Make sure you have the latest LTS version of [Node.js](https://nodejs.org) and
 [Yarn](https://yarnpkg.com) installed.
 
-Run `yarn command`.
+Run `yarn`.
 
 ## Commands
 

content/docs/command-reference/cache/index.md

@@ -15,9 +15,9 @@ positional arguments:
 
 ## Description
 
-At DVC initialization, a new `.dvc/` directory will be created for internal
-configuration and cache
-[files and directories](/doc/user-guide/dvc-files-and-directories) that are
+At DVC initialization, a new `.dvc/` directory is created for internal
+configuration and <abbr>cache</abbr>
+[files and directories](/doc/user-guide/dvc-files-and-directories), that are
 hidden from the user.
 
 The cache is where your data files, models, etc. (anything you want to version

content/docs/command-reference/init.md

@@ -22,9 +22,9 @@ advanced scenarios:
 - [Initializing DVC without Git](#how-does-it-affect-dvc-commands) - support for
   SCM other than Git, deployment automation cases, etc.
 
-At DVC initialization, a new `.dvc/` directory will be created for internal
-configuration and cache
-[files and directories](/doc/user-guide/dvc-files-and-directories) that are
+At DVC initialization, a new `.dvc/` directory is created for internal
+configuration and <abbr>cache</abbr>
+[files and directories](/doc/user-guide/dvc-files-and-directories), that are
 hidden from the user.
 
 ### Initializing DVC in subdirectories

content/docs/command-reference/remote/index.md

@@ -74,9 +74,9 @@ For the typical process to share the <abbr>project</abbr> via remote, see
 ### What is a "local remote" ?
 
 While the term may seem contradictory, it doesn't have to be. The "local" part
-refers to the machine where the project is stored, so it can be any directory
-accessible to the same system. The "remote" part refers specifically to the
-project/repository itself. Read "local, but external" storage.
+refers to the location of the storage relative to the project, so it can be any
+directory in the file system. "Remote" is the term that refers to the storage.
+Read "local cache backup".
 
 </details>
 

content/docs/command-reference/remote/list.md

@@ -45,9 +45,9 @@ Let's for simplicity add a _default_ local remote:
 ### What is a "local remote" ?
 
 While the term may seem contradictory, it doesn't have to be. The "local" part
-refers to the machine where the project is stored, so it can be any directory
-accessible to the same system. The "remote" part refers specifically to the
-project/repository itself. Read "local, but external" storage.
+refers to the location of the storage relative to the project, so it can be any
+directory in the file system. "Remote" is the term that refers to the storage.
+Read "local cache backup".
 
 </details>
 

content/docs/index.md

@@ -1,8 +1,27 @@
 # DVC Documentation
 
-Welcome! In here you may find all the guiding material and technical documents
-needed to learn about DVC: how to use it, how it works, and where to go for
-additional resources.
+Welcome! In here you may find all the material and technical details needed to
+learn about DVC: how to use it, how it works, and where to go for additional
+resources.
+
+## What is DVC?
+
+Data Version Control, or DVC, is **a new type of experiment management
+software** built on top of the existing engineering toolset that you're already
+used to, particularly [Git](https://git-scm.com) source code management. DVC
+reduces the gap between existing tools and data science needs.
+
+If you store and process data files or datasets to produce other data or machine
+learning models, and you want to
+
+- capture and save <abbr>data artifacts</abbr> the same way you capture code;
+- track and switch between different versions of data or models easily;
+- understand how data or models were built in the first place;
+- be able to compare models and metrics to each other;
+- bring software engineering best practices to your data science team;
+- among other [use cases](/doc/use-cases)
+
+DVC is for you!
 
 ## Before you start
 

content/docs/sidebar.json

@@ -1,6 +1,7 @@
 [
   {
-    "slug": "home",
+    "slug": "",
+    "label": "Home",
     "source": "index.md"
   },
   {
@@ -30,32 +31,14 @@
     "children": [
       {
         "slug": "get-started",
-        "source": false,
+        "source": "get-started/index.md",
         "tutorials": {
           "katacoda": "https://katacoda.com/dvc/courses/get-started/initialize"
         },
         "children": [
-          "agenda",
-          "initialize",
-          "configure",
-          "add-files",
-          "store-data",
-          "retrieve-data",
-          "import-data",
-          {
-            "label": "Connect with Code",
-            "slug": "connect-code-and-data"
-          },
-          "pipeline",
-          "visualize",
-          "reproduce",
-          "metrics",
-          "experiments",
-          "compare-experiments",
-          {
-            "label": "Get Older Files",
-            "slug": "older-versions"
-          }
+          "versioning-basics",
+          "data-pipelines",
+          "experiment-management"
         ]
       },
       {

content/docs/tutorials/deep/preparation.md

@@ -61,9 +61,9 @@ $ pip install -r code/requirements.txt
 DVC works on top of Git repositories. You run DVC initialization in a repository
 directory to create DVC meta files and directories.
 
-At DVC initialization, a new `.dvc/` directory will be created for internal
-configuration and cache
-[files and directories](/doc/user-guide/dvc-files-and-directories) that are
+At DVC initialization, a new `.dvc/` directory is created for internal
+configuration and <abbr>cache</abbr>
+[files and directories](/doc/user-guide/dvc-files-and-directories), that are
 hidden from the user. We describe some DVC internals below for a better
 understanding of how it works.