diff --git a/content/docs/changelog/0.18.md b/content/docs/changelog/0.18.md index 08dbf0f167..24fa0be71b 100644 --- a/content/docs/changelog/0.18.md +++ b/content/docs/changelog/0.18.md @@ -21,9 +21,10 @@ really excited to share the progress with you: - Commands startup latency reduced 3x -- πŸ“™ **Documentation got better** - a whole new [Get Started](/doc/get-started) - section, new [Use Cases](/doc/use-cases), [User Guide](/doc/user-guide), and - lot of other great stuff you can find here. +- πŸ“™ **Documentation got better** - a whole ne + [Get Started](/doc/tutorials/get-started) section, new + [Use Cases](/doc/use-cases), [User Guide](/doc/user-guide), and lot of other + great stuff you can find here. - πŸ™‚ **Usability improvements** - DVC interface got more informative and easier to use: diff --git a/content/docs/changelog/0.35.md b/content/docs/changelog/0.35.md index a3063ec96d..60889aeb16 100644 --- a/content/docs/changelog/0.35.md +++ b/content/docs/changelog/0.35.md @@ -13,8 +13,9 @@ improvements) we have done in the last few months: all DVC commands that also have `-a` or `--all-branches` (use all Git branches). -- πŸ“– The [Get Started](/doc/get-started/agenda) section has been simplified - (e.g. to use tags instead of branches) and extended. We have also prepared a +- πŸ“– The [Get Started](/doc/tutorials/get-started/agenda) section has been + simplified (e.g. to use tags instead of branches) and extended. We have also + prepared a [DVC project on GitHub](https://github.com/iterative/example-get-started) that reflects the sequence of chapters in the β€œget started” section. You can now download the whole project and reproduce all the models. diff --git a/content/docs/command-reference/add.md b/content/docs/command-reference/add.md index 45ab8ba64b..e44dea9c43 100644 --- a/content/docs/command-reference/add.md +++ b/content/docs/command-reference/add.md @@ -226,8 +226,8 @@ $ dvc run -f train.dvc \ python train.py ``` -> To follow the full example, see -> [Tutorial: Versioning](/doc/tutorials/versioning). +> To follow the full example, see the [Versioning](/doc/tutorials/versioning) +> tutorial. If instead we use the `--recursive` (`-R`) option, the output looks like this: diff --git a/content/docs/command-reference/checkout.md b/content/docs/command-reference/checkout.md index 1b1d02e9cc..31859673ff 100644 --- a/content/docs/command-reference/checkout.md +++ b/content/docs/command-reference/checkout.md @@ -102,8 +102,8 @@ be pulled from remote storage using `dvc pull`. Let's employ a simple workspace with some data, code, ML models, pipeline stages, such as the DVC project created in our -[Get Started](/doc/get-started) section. Then we can see what happens with -`git checkout` and `dvc checkout` as we switch from tag to tag. +[Get Started](/doc/tutorials/get-started) section. Then we can see what happens +with `git checkout` and `dvc checkout` as we switch from tag to tag.
diff --git a/content/docs/command-reference/commit.md b/content/docs/command-reference/commit.md index 4ba72d7d71..4632f77b0a 100644 --- a/content/docs/command-reference/commit.md +++ b/content/docs/command-reference/commit.md @@ -96,8 +96,8 @@ reproducibility in those cases. Let's employ a simple workspace with some data, code, ML models, pipeline stages, such as the DVC project created in our -[Get Started](/doc/get-started) section. Then we can see what happens with -`git commit` and `dvc commit` in different situations. +[Get Started](/doc/tutorials/get-started) section. Then we can see what happens +with `git commit` and `dvc commit` in different situations.
diff --git a/content/docs/command-reference/diff.md b/content/docs/command-reference/diff.md index d064751442..7151a4231c 100644 --- a/content/docs/command-reference/diff.md +++ b/content/docs/command-reference/diff.md @@ -58,7 +58,8 @@ for example when `dvc init` was used with the `--no-scm` option. ## Examples -For these examples we can use the [Get Started](/doc/get-started) project. +For these examples we can use the [Get Started](/doc/tutorials/get-started) +project.
@@ -103,8 +104,8 @@ $ dvc diff Let's checkout the [3-add-file](https://github.com/iterative/example-get-started/releases/tag/3-add-file) -tag, corresponding to the [Add Files](/doc/get-started/add-files) _Get Started_ -chapter, right after we added `data.xml` file with DVC: +tag, corresponding to the [Add Files](/doc/tutorials/get-started/add-files) _Get +Started_ chapter, right after we added `data.xml` file with DVC: ```dvc $ git checkout 3-add-file diff --git a/content/docs/command-reference/fetch.md b/content/docs/command-reference/fetch.md index 4e34086792..7cbcbc6daa 100644 --- a/content/docs/command-reference/fetch.md +++ b/content/docs/command-reference/fetch.md @@ -46,16 +46,16 @@ since files tracked by DVC should already exist in remote storage, but won't be in the project's cache. (Refer to `dvc remote` for more information on DVC remotes.) These necessary data or model files are listed as dependencies or outputs in a DVC-file (target [stage](/doc/command-reference/run)) so they -are required to [reproduce](/doc/get-started/reproduce) the corresponding -[pipeline](/doc/command-reference/pipeline). (See +are required to [reproduce](/doc/tutorials/get-started/reproduce) the +corresponding [pipeline](/doc/command-reference/pipeline). (See [DVC-File Format](/doc/user-guide/dvc-file-format) for more information on dependencies and outputs.) `dvc fetch` ensures that the files needed for a DVC-file to be -[reproduced](/doc/get-started/reproduce) exist in cache. If no `targets` are -specified, the set of data files to fetch is determined by analyzing all -DVC-files in the current branch, unless `--all-branches` or `--all-tags` is -specified. +[reproduced](/doc/tutorials/get-started/reproduce) exist in cache. If no +`targets` are specified, the set of data files to fetch is determined by +analyzing all DVC-files in the current branch, unless `--all-branches` or +`--all-tags` is specified. The default remote is used (see `dvc config core.remote`) unless the `--remote` option is used. @@ -63,10 +63,10 @@ option is used. `dvc fetch`, `dvc pull`, and `dvc push` are related in that these 3 commands perform data synchronization among local and remote storage. The specific way in which the set of files to push/fetch/pull is determined begins with calculating -file hashes when these are [added](/doc/get-started/add-files) with DVC. File -hashes are stored in the corresponding DVC-files (typically versioned with Git). -Only the hashes specified in DVC-files currently in the workspace are considered -by `dvc fetch` (unless the `-a` or `-T` options are used). +file hashes when these are [added](/doc/tutorials/get-started/add-files) with +DVC. File hashes are stored in the corresponding DVC-files (typically versioned +with Git). Only the hashes specified in DVC-files currently in the workspace are +considered by `dvc fetch` (unless the `-a` or `-T` options are used). ## Options @@ -93,8 +93,8 @@ by `dvc fetch` (unless the `-a` or `-T` options are used). - `-a`, `--all-branches` - fetch cache for all Git branches instead of just the current workspace. This means DVC may download files needed to reproduce different versions of a DVC-file - ([experiments](/doc/get-started/experiments)), not just the ones currently in - the workspace. + ([experiments](/doc/tutorials/get-started/experiments)), not just the ones + currently in the workspace. - `-T`, `--all-tags` - fetch cache for all Git tags. Similar to `-a` above. Note that both options can be combined, for example using the `-aT` flag. @@ -110,8 +110,8 @@ by `dvc fetch` (unless the `-a` or `-T` options are used). Let's employ a simple workspace with some data, code, ML models, pipeline stages, such as the DVC project created in our -[Get Started](/doc/get-started) section. Then we can see what happens with -`dvc fetch` as we switch from tag to tag. +[Get Started](/doc/tutorials/get-started) section. Then we can see what happens +with `dvc fetch` as we switch from tag to tag.
diff --git a/content/docs/command-reference/get.md b/content/docs/command-reference/get.md index 755a5a2ee1..d543d65fd7 100644 --- a/content/docs/command-reference/get.md +++ b/content/docs/command-reference/get.md @@ -148,8 +148,8 @@ https://remote.dvc.org/get-started/66/2eb7f64216d9c2c1088d0a5e2c6951 location to place the artifact within the workspace. Combining these two options allows us to do something we can't achieve with the regular `git checkout` + `dvc checkout` process – see for example the -[Get Older Data Version](/doc/get-started/older-versions) chapter of our _Get -Started_. +[Get Older Data Version](/doc/tutorials/get-started/older-versions) chapter of +our _Get Started_. Let's use the [get started example repo](https://github.com/iterative/example-get-started) @@ -161,12 +161,12 @@ $ git clone https://github.com/iterative/example-get-started $ cd example-get-started ``` -If you are familiar with our [Get Started](/doc/get-started) project (used in -these examples), you may remember that the chapter where we train a first -version of the model corresponds to the the `baseline-experiment` tag in the -repo. Similarly `bigrams-experiment` points to an improved model (trained using -bigrams). What if we wanted to have both versions of the model "checked out" at -the same time? `dvc get` provides an easy way to do this: +If you are familiar with our [Get Started](/doc/tutorials/get-started) project +(used in these examples), you may remember that the chapter where we train a +first version of the model corresponds to the the `baseline-experiment` tag in +the repo. Similarly `bigrams-experiment` points to an improved model (trained +using bigrams). What if we wanted to have both versions of the model "checked +out" at the same time? `dvc get` provides an easy way to do this: ```dvc $ dvc get . model.pkl --rev baseline-experiment diff --git a/content/docs/command-reference/import-url.md b/content/docs/command-reference/import-url.md index 64af042a5e..564bb78458 100644 --- a/content/docs/command-reference/import-url.md +++ b/content/docs/command-reference/import-url.md @@ -123,7 +123,7 @@ up to date from the external data source. ## Examples To illustrate these examples we will be using the project explained -in the [Get Started](/doc/get-started) section. +in the [Get Started](/doc/tutorials/get-started) section.
@@ -132,8 +132,8 @@ in the [Get Started](/doc/get-started) section. Start by cloning our example repo if you don't already have it. Then move into the repo and checkout the [2-remote](https://github.com/iterative/example-get-started/releases/tag/2-remote) -tag, corresponding to the [Configure](/doc/get-started/configure) _Get Started_ -chapter: +tag, corresponding to the [Configure](/doc/tutorials/get-started/configure) _Get +Started_ chapter: ```dvc $ git clone https://github.com/iterative/example-get-started @@ -143,14 +143,14 @@ $ mkdir data ``` You should now have a blank workspace, just before the -[Add Files](/doc/get-started/add-files) chapter. +[Add Files](/doc/tutorials/get-started/add-files) chapter.
## Example: Tracking a remote file -An advanced alternate to [Add Files](/doc/get-started/add-files) chapter of the -_Get Started_ section is to use `dvc import-url`: +An advanced alternate to [Add Files](/doc/tutorials/get-started/add-files) +chapter of the _Get Started_ section is to use `dvc import-url`: ```dvc $ dvc import-url https://data.dvc.org/get-started/data.xml \ @@ -196,9 +196,9 @@ regenerating a data artifact based on the updated data source. [Pipeline](/doc/command-reference/pipeline) reproduction can be triggered based on a changed external dependency. -Let's use the [Get Started](/doc/get-started) project again, simulating an -updated external data source. (Remember to prepare the workspace, -as explained in [Examples](#examples)) +Let's use the [Get Started](/doc/tutorials/get-started) project again, +simulating an updated external data source. (Remember to prepare the +workspace, as explained in [Examples](#examples)) To illustrate this scenario, let's use a local file system directory (external to the workspace) to simulate a remote data source location. (In real life, the @@ -243,8 +243,8 @@ And instead of an `etag` we have an `md5` hash value. We did this so its easy to edit the data file. Let's now manually reproduce a -[processing chapter](/doc/get-started/connect-code-and-data) from the _Get -Started_ project. Download the example source code archive and unzip it: +[processing chapter](/doc/tutorials/get-started/connect-code-and-data) from the +_Get Started_ project. Download the example source code archive and unzip it: ```dvc $ wget https://code.dvc.org/get-started/code.zip diff --git a/content/docs/command-reference/import.md b/content/docs/command-reference/import.md index bc886ebec4..203239f1df 100644 --- a/content/docs/command-reference/import.md +++ b/content/docs/command-reference/import.md @@ -64,8 +64,9 @@ and data `path` fields, and the `outs` section contains the corresponding local workspace `path` field. This is enough data about the imported data, to enable DVC efficiently determining whether the local copy is out of date. -To actually [track the data](https://dvc.org/doc/get-started/add-files), -`git add` (and `git commit`) the import stage. +To actually +[track the data](https://dvc.org/doc/tutorials/get-started/add-files), `git add` +(and `git commit`) the import stage. Note that import stages are considered always locked, meaning that if you run `dvc repro`, they won't be updated. Use `dvc update` to update the downloaded diff --git a/content/docs/command-reference/install.md b/content/docs/command-reference/install.md index 2898e6823f..2110694605 100644 --- a/content/docs/command-reference/install.md +++ b/content/docs/command-reference/install.md @@ -117,8 +117,8 @@ repos: Let's employ a simple workspace with some data, code, ML models, pipeline stages, such as the DVC project created in our -[Get Started](/doc/get-started) section. Then we can see what happens with -`dvc install` in different situations. +[Get Started](/doc/tutorials/get-started) section. Then we can see what happens +with `dvc install` in different situations.
diff --git a/content/docs/command-reference/metrics/diff.md b/content/docs/command-reference/metrics/diff.md index f1495d06d2..8cc97f0a0f 100644 --- a/content/docs/command-reference/metrics/diff.md +++ b/content/docs/command-reference/metrics/diff.md @@ -70,8 +70,8 @@ They're calculated between two commits (hash, branch, tag, or any Let's employ a simple workspace with some data, code, ML models, pipeline stages, such as the DVC project created in our -[Get Started](/doc/get-started) section. Then we can see what happens with -`dvc install` in different situations. +[Get Started](/doc/tutorials/get-started) section. Then we can see what happens +with `dvc install` in different situations.
diff --git a/content/docs/command-reference/metrics/show.md b/content/docs/command-reference/metrics/show.md index 210df40304..60d0499301 100644 --- a/content/docs/command-reference/metrics/show.md +++ b/content/docs/command-reference/metrics/show.md @@ -105,6 +105,6 @@ Examples in [add](/doc/command-reference/metrics/add), [remove](/doc/command-reference/metrics/remove) cover most of the basic cases for the `dvc metrics show`. -The [Compare Experiments](/doc/get-started/compare-experiments) chapter of our -_Get Started_ section covers the `-a` option to collect and print a metric file -value across all Git branches. +The [Compare Experiments](/doc/tutorials/get-started/compare-experiments) +chapter of our _Get Started_ section covers the `-a` option to collect and print +a metric file value across all Git branches. diff --git a/content/docs/command-reference/pipeline/index.md b/content/docs/command-reference/pipeline/index.md index e4127a1446..6b4d6684e5 100644 --- a/content/docs/command-reference/pipeline/index.md +++ b/content/docs/command-reference/pipeline/index.md @@ -1,6 +1,6 @@ # pipeline -A set of commands to manage [pipelines](/doc/get-started/pipeline): +A set of commands to manage [pipelines](/doc/tutorials/get-started/pipeline): [show](/doc/command-reference/pipeline/show) and [list](/doc/command-reference/pipeline/list). diff --git a/content/docs/get-started/index.md b/content/docs/get-started/index.md deleted file mode 100644 index 55f2a7898e..0000000000 --- a/content/docs/get-started/index.md +++ /dev/null @@ -1,24 +0,0 @@ -# Get Started - -_Get Started_ is a step-by-step introduction into basic DVC features. It doesn't -go into details much, but provides links and expandable sections to learn more. - -You'll need [Git](https://git-scm.com) to run the commands in this guide. Also, -if DVC is not installed, please follow these [instructions](/doc/install) to do -so. - -Before you start ... - -βœ… Please, join our [community](/chat) or see these [support](/support) channels -if you have any questions or need any help. We are very responsive ⚑. - -βœ… Check out our [GitHub repository](https://github.com/iterative/dvc) and give -us a ⭐ if you like the project! - -βœ… Contribute to DVC [on GitHub](https://github.com/iterative/dvc) or help us -improve this [documentation](https://github.com/iterative/dvc.org) πŸ™. - -When you're done, feel free to check out official and community -[tutorials](/doc/tutorials). They provide in-depth explanations, -[interactive](/doc/tutorials/interactive) scenarios, and various examples on how -DVC can be used. diff --git a/content/docs/index.md b/content/docs/index.md new file mode 100644 index 0000000000..f23d119383 --- /dev/null +++ b/content/docs/index.md @@ -0,0 +1,29 @@ +# 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. + +## Before you start + +βœ… Please join our [community](/community) or use the [support](/support) +channels if you have any questions or need specific help. We are very responsive +⚑. + +βœ… Check out our [GitHub repository](https://github.com/iterative/dvc) and give +us a ⭐ if you like the project! + +βœ… Contribute to DVC [on GitHub](https://github.com/iterative/dvc) or help us +improve this [documentation](https://github.com/iterative/dvc.org) πŸ™. + +## Main topics + +- Learn how to [install](/doc/install) and + [get started](/doc/tutorials/get-started) with DVC in the first sections. +- Explore the main [reasons](/doc/use-cases) to adopt DVC. +- Study the detailed [inner-workings](/doc/user-guide) of DVC, as well as each + one of its [commands](/doc/command-reference) and Python + [functions](/doc/api-reference). + +Please choose a topic from the sidebar to the left, or click the `Next` button +below to start from the beginning β†˜ diff --git a/content/docs/sidebar.json b/content/docs/sidebar.json index 05c59ac6fc..7d097daf07 100644 --- a/content/docs/sidebar.json +++ b/content/docs/sidebar.json @@ -1,33 +1,7 @@ [ { - "slug": "get-started", - "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" - } - ] + "slug": "home", + "source": "index.md" }, { "slug": "install", @@ -54,6 +28,36 @@ "slug": "tutorials", "source": "tutorials/index.md", "children": [ + { + "slug": "get-started", + "source": false, + "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" + } + ] + }, { "slug": "interactive", "label": "Interactive Tutorials" diff --git a/content/docs/tutorials/deep/sharing-data.md b/content/docs/tutorials/deep/sharing-data.md index f03177ce69..8591107b36 100644 --- a/content/docs/tutorials/deep/sharing-data.md +++ b/content/docs/tutorials/deep/sharing-data.md @@ -22,8 +22,8 @@ can be done using the CLI as shown below. > have write access to it, so in order to follow the tutorial you will need to > either create your own S3 bucket or use other types of > [remote storage](/doc/command-reference/remote). E.g. you can set up a local -> remote as we did in the [Configure](/doc/get-started/configure) chapter of -> _Get Started_. +> remote as we did in the [Configure](/doc/tutorials/get-started/configure) +> chapter of _Get Started_. ```dvc $ dvc remote add -d upstream s3://dvc-public/remote/tutorial/nlp diff --git a/content/docs/get-started/add-files.md b/content/docs/tutorials/get-started/add-files.md similarity index 100% rename from content/docs/get-started/add-files.md rename to content/docs/tutorials/get-started/add-files.md diff --git a/content/docs/get-started/agenda.md b/content/docs/tutorials/get-started/agenda.md similarity index 90% rename from content/docs/get-started/agenda.md rename to content/docs/tutorials/get-started/agenda.md index 1a61701c76..ca56dfbdec 100644 --- a/content/docs/get-started/agenda.md +++ b/content/docs/tutorials/get-started/agenda.md @@ -1,5 +1,9 @@ # Agenda +You'll need [Git](https://git-scm.com) to run the commands in this guide. Also, +if DVC is not installed, please follow these [instructions](/doc/install) to do +so. + In the next few sections we'll build a simple natural language processing (NLP) project from scratch. If you'd like to get the final result or have any issues along the way, you can download the fully reproducible diff --git a/content/docs/get-started/compare-experiments.md b/content/docs/tutorials/get-started/compare-experiments.md similarity index 89% rename from content/docs/get-started/compare-experiments.md rename to content/docs/tutorials/get-started/compare-experiments.md index d23b3ff78b..21e09a8450 100644 --- a/content/docs/get-started/compare-experiments.md +++ b/content/docs/tutorials/get-started/compare-experiments.md @@ -17,8 +17,8 @@ $ dvc repro evaluate.dvc `git checkout master` and `dvc checkout` commands ensure that we have the latest experiment code and data respectively. And `dvc repro`, as we discussed in the -[Reproduce](/doc/get-started/reproduce) chapter, is a way to run all the -necessary commands to build the model and measure its performance. +[Reproduce](/doc/tutorials/get-started/reproduce) chapter, is a way to run all +the necessary commands to build the model and measure its performance. ```dvc $ git commit -am "Evaluate bigrams model" diff --git a/content/docs/get-started/configure.md b/content/docs/tutorials/get-started/configure.md similarity index 100% rename from content/docs/get-started/configure.md rename to content/docs/tutorials/get-started/configure.md diff --git a/content/docs/get-started/connect-code-and-data.md b/content/docs/tutorials/get-started/connect-code-and-data.md similarity index 91% rename from content/docs/get-started/connect-code-and-data.md rename to content/docs/tutorials/get-started/connect-code-and-data.md index 0cece0c266..1bec301c0c 100644 --- a/content/docs/get-started/connect-code-and-data.md +++ b/content/docs/tutorials/get-started/connect-code-and-data.md @@ -74,10 +74,10 @@ $ dvc run -f prepare.dvc \ `dvc run` generates the `prepare.dvc` DVC-file. It has the same [format](/doc/user-guide/dvc-file-format) as the file we created in the -[previous section](/doc/get-started/add-files) to track `data.xml`, except in -this case it has additional information about the `data/prepared` output (a -directory where two files, `train.tsv` and `test.tsv`, will be written to), and -about the Python command that is required to build it. +[previous section](/doc/tutorials/get-started/add-files) to track `data.xml`, +except in this case it has additional information about the `data/prepared` +output (a directory where two files, `train.tsv` and `test.tsv`, will be written +to), and about the Python command that is required to build it.
@@ -121,8 +121,9 @@ wdir: . ``` > `dvc run` is just the first of a set of DVC command required to generate a -> [pipeline](/doc/get-started/pipeline), or in other words, instructions on how -> to build a ML model (data file) from previous data files (or directories). +> [pipeline](/doc/tutorials/get-started/pipeline), or in other words, +> instructions on how to build a ML model (data file) from previous data files +> (or directories). Let's briefly mention what the command options used above mean for this particular example: diff --git a/content/docs/get-started/experiments.md b/content/docs/tutorials/get-started/experiments.md similarity index 100% rename from content/docs/get-started/experiments.md rename to content/docs/tutorials/get-started/experiments.md diff --git a/content/docs/get-started/import-data.md b/content/docs/tutorials/get-started/import-data.md similarity index 83% rename from content/docs/get-started/import-data.md rename to content/docs/tutorials/get-started/import-data.md index d911d3c0c9..6900533d5c 100644 --- a/content/docs/get-started/import-data.md +++ b/content/docs/tutorials/get-started/import-data.md @@ -1,9 +1,9 @@ # Import Data -We've seen how to [push](/doc/get-started/store-data) and -[pull](/doc/get-started/retrieve-data) data from/to a DVC project's -[remote](/doc/command-reference/remote). But what if we wanted to integrate a -dataset or ML model produced in one project into another one? +We've seen how to [push](/doc/tutorials/get-started/store-data) and +[pull](/doc/tutorials/get-started/retrieve-data) data from/to a DVC +project's [remote](/doc/command-reference/remote). But what if we wanted +to integrate a dataset or ML model produced in one project into another one? One way is to manually download the data (with `wget` or `dvc get`, for example) and use `dvc add` to track it, but the connection between the projects would be @@ -11,7 +11,7 @@ lost. We wouldn't be able to tell where the data came from or whether there are new versions available. A better alternative is the `dvc import` command: