diff --git a/public/static/docs/changelog/0.18.md b/public/static/docs/changelog/0.18.md index 27890748e4..242bf5e3ca 100644 --- a/public/static/docs/changelog/0.18.md +++ b/public/static/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/learn/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/public/static/docs/changelog/0.35.md b/public/static/docs/changelog/0.35.md index 774fd547d6..25ac5be81d 100644 --- a/public/static/docs/changelog/0.35.md +++ b/public/static/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/learn/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/public/static/docs/command-reference/add.md b/public/static/docs/command-reference/add.md index 45ab8ba64b..75e2ebea61 100644 --- a/public/static/docs/command-reference/add.md +++ b/public/static/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/learn/versioning) +> tutorial. If instead we use the `--recursive` (`-R`) option, the output looks like this: diff --git a/public/static/docs/command-reference/checkout.md b/public/static/docs/command-reference/checkout.md index 1b1d02e9cc..1515c9f71a 100644 --- a/public/static/docs/command-reference/checkout.md +++ b/public/static/docs/command-reference/checkout.md @@ -102,7 +102,7 @@ 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 +[Get Started](/learn/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/public/static/docs/command-reference/commit.md b/public/static/docs/command-reference/commit.md index 4ba72d7d71..ba0e3ab731 100644 --- a/public/static/docs/command-reference/commit.md +++ b/public/static/docs/command-reference/commit.md @@ -96,7 +96,7 @@ 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 +[Get Started](/learn/get-started) section. Then we can see what happens with `git commit` and `dvc commit` in different situations.
diff --git a/public/static/docs/command-reference/diff.md b/public/static/docs/command-reference/diff.md index d064751442..6e574c4970 100644 --- a/public/static/docs/command-reference/diff.md +++ b/public/static/docs/command-reference/diff.md @@ -58,7 +58,7 @@ 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](/learn/get-started) project.
@@ -103,8 +103,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](/learn/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/public/static/docs/command-reference/fetch.md b/public/static/docs/command-reference/fetch.md index 4e34086792..cb529a576f 100644 --- a/public/static/docs/command-reference/fetch.md +++ b/public/static/docs/command-reference/fetch.md @@ -46,13 +46,13 @@ 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 +are required to [reproduce](/learn/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 +[reproduced](/learn/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. @@ -63,7 +63,7 @@ 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 +file hashes when these are [added](/learn/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). @@ -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](/learn/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,7 +110,7 @@ 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 +[Get Started](/learn/get-started) section. Then we can see what happens with `dvc fetch` as we switch from tag to tag.
@@ -126,8 +126,7 @@ $ cd example-get-started
-The workspace looks almost like in this -[pipeline setup](/doc/tutorials/pipelines): +The workspace looks almost like in this [pipeline setup](/doc/learn/pipelines): ```dvc . diff --git a/public/static/docs/command-reference/get.md b/public/static/docs/command-reference/get.md index 755a5a2ee1..6561a7ce1f 100644 --- a/public/static/docs/command-reference/get.md +++ b/public/static/docs/command-reference/get.md @@ -148,7 +148,7 @@ 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 +[Get Older Data Version](/learn/get-started/older-versions) chapter of our _Get Started_. Let's use the @@ -161,7 +161,7 @@ $ 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 +If you are familiar with our [Get Started](/learn/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 diff --git a/public/static/docs/command-reference/import-url.md b/public/static/docs/command-reference/import-url.md index 64af042a5e..c531fddcf8 100644 --- a/public/static/docs/command-reference/import-url.md +++ b/public/static/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/learn/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/learn/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/learn/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/learn/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,7 +196,7 @@ 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 +Let's use the [Get Started](/doc/learn/get-started) project again, simulating an updated external data source. (Remember to prepare the workspace, as explained in [Examples](#examples)) @@ -243,7 +243,7 @@ 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 +[processing chapter](/doc/learn/get-started/connect-code-and-data) from the _Get Started_ project. Download the example source code archive and unzip it: ```dvc diff --git a/public/static/docs/command-reference/import.md b/public/static/docs/command-reference/import.md index bc886ebec4..497fd55beb 100644 --- a/public/static/docs/command-reference/import.md +++ b/public/static/docs/command-reference/import.md @@ -64,7 +64,7 @@ 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), +To actually [track the data](https://dvc.org/doc/learn/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 @@ -187,7 +187,7 @@ $ dvc get https://github.com/iterative/dataset-registry \ tutorial/ver/data.zip ``` -> Used in our [versioning tutorial](/doc/tutorials/versioning) +> Used in our [versioning tutorial](/doc/learn/versioning) Or diff --git a/public/static/docs/command-reference/install.md b/public/static/docs/command-reference/install.md index 7d716dfd40..99ed0ad61b 100644 --- a/public/static/docs/command-reference/install.md +++ b/public/static/docs/command-reference/install.md @@ -88,7 +88,7 @@ To disable them, you need to **remove** or **edit** those files (i.e. 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 +[Get Started](/doc/learn/get-started) section. Then we can see what happens with `dvc install` in different situations.
diff --git a/public/static/docs/command-reference/metrics/diff.md b/public/static/docs/command-reference/metrics/diff.md index f1495d06d2..d189e48949 100644 --- a/public/static/docs/command-reference/metrics/diff.md +++ b/public/static/docs/command-reference/metrics/diff.md @@ -70,7 +70,7 @@ 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 +[Get Started](/doc/learn/get-started) section. Then we can see what happens with `dvc install` in different situations.
diff --git a/public/static/docs/command-reference/metrics/show.md b/public/static/docs/command-reference/metrics/show.md index 210df40304..0d45cafae8 100644 --- a/public/static/docs/command-reference/metrics/show.md +++ b/public/static/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/learn/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/public/static/docs/command-reference/pipeline/index.md b/public/static/docs/command-reference/pipeline/index.md index e4127a1446..cddcfb14da 100644 --- a/public/static/docs/command-reference/pipeline/index.md +++ b/public/static/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/learn/get-started/pipeline): [show](/doc/command-reference/pipeline/show) and [list](/doc/command-reference/pipeline/list). diff --git a/public/static/docs/command-reference/repro.md b/public/static/docs/command-reference/repro.md index b3318944a9..d6f2e01775 100644 --- a/public/static/docs/command-reference/repro.md +++ b/public/static/docs/command-reference/repro.md @@ -157,7 +157,7 @@ and only execute the final stage. For simplicity, let's build a pipeline defined below. (If you want get your hands-on something more real, see this shot -[pipeline tutorial](/doc/tutorials/pipelines)). It takes this `text.txt` file: +[pipeline tutorial](/doc/learn/pipelines)). It takes this `text.txt` file: ``` dvc diff --git a/public/static/docs/command-reference/run.md b/public/static/docs/command-reference/run.md index c97553f36f..01d0483db8 100644 --- a/public/static/docs/command-reference/run.md +++ b/public/static/docs/command-reference/run.md @@ -54,7 +54,7 @@ Note that `dvc repro` provides an interface to check state and reproduce this graph (pipeline) later. This concept is similar to the one of the [Make](https://www.gnu.org/software/make/) in software build automation, but DVC captures data and caches relevant data artifacts along -the way. See [this tutorial](/doc/tutorials/pipelines) to learn more and try +the way. See [this tutorial](/doc/learn/pipelines) to learn more and try creating a pipeline. ### Avoiding unexpected behavior diff --git a/public/static/docs/get-started/index.md b/public/static/docs/get-started/index.md deleted file mode 100644 index 6ae3871a68..0000000000 --- a/public/static/docs/get-started/index.md +++ /dev/null @@ -1,13 +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. - -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/public/static/docs/tutorials/community.md b/public/static/docs/learn/community.md similarity index 100% rename from public/static/docs/tutorials/community.md rename to public/static/docs/learn/community.md diff --git a/public/static/docs/tutorials/deep/define-ml-pipeline.md b/public/static/docs/learn/deep/define-ml-pipeline.md similarity index 100% rename from public/static/docs/tutorials/deep/define-ml-pipeline.md rename to public/static/docs/learn/deep/define-ml-pipeline.md diff --git a/public/static/docs/tutorials/deep/index.md b/public/static/docs/learn/deep/index.md similarity index 100% rename from public/static/docs/tutorials/deep/index.md rename to public/static/docs/learn/deep/index.md diff --git a/public/static/docs/tutorials/deep/preparation.md b/public/static/docs/learn/deep/preparation.md similarity index 100% rename from public/static/docs/tutorials/deep/preparation.md rename to public/static/docs/learn/deep/preparation.md diff --git a/public/static/docs/tutorials/deep/reproducibility.md b/public/static/docs/learn/deep/reproducibility.md similarity index 100% rename from public/static/docs/tutorials/deep/reproducibility.md rename to public/static/docs/learn/deep/reproducibility.md diff --git a/public/static/docs/tutorials/deep/sharing-data.md b/public/static/docs/learn/deep/sharing-data.md similarity index 95% rename from public/static/docs/tutorials/deep/sharing-data.md rename to public/static/docs/learn/deep/sharing-data.md index f03177ce69..c9c1730319 100644 --- a/public/static/docs/tutorials/deep/sharing-data.md +++ b/public/static/docs/learn/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/learn/get-started/configure) chapter +> of _Get Started_. ```dvc $ dvc remote add -d upstream s3://dvc-public/remote/tutorial/nlp diff --git a/public/static/docs/get-started/add-files.md b/public/static/docs/learn/get-started/add-files.md similarity index 100% rename from public/static/docs/get-started/add-files.md rename to public/static/docs/learn/get-started/add-files.md diff --git a/public/static/docs/get-started/agenda.md b/public/static/docs/learn/get-started/agenda.md similarity index 75% rename from public/static/docs/get-started/agenda.md rename to public/static/docs/learn/get-started/agenda.md index d1a6eeffee..74fed2f3e9 100644 --- a/public/static/docs/get-started/agenda.md +++ b/public/static/docs/learn/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 @@ -13,10 +17,9 @@ Otherwise, bear with us and we'll introduce some basic DVC concepts to get the same results together! The idea for this project is a simplified version of our -[Deep Dive Tutorial](/doc/tutorials/deep). It explores the NLP problem of -predicting tags for a given StackOverflow question. For example, we might want a -classifier that can classify (or predict) posts about Python by tagging them -with `python`. +[Deep Dive Tutorial](/doc/learn/deep). It explores the NLP problem of predicting +tags for a given StackOverflow question. For example, we might want a classifier +that can classify (or predict) posts about Python by tagging them with `python`. ![](/static/img/example-flow-2x.png) diff --git a/public/static/docs/get-started/compare-experiments.md b/public/static/docs/learn/get-started/compare-experiments.md similarity index 94% rename from public/static/docs/get-started/compare-experiments.md rename to public/static/docs/learn/get-started/compare-experiments.md index d23b3ff78b..b8892ff803 100644 --- a/public/static/docs/get-started/compare-experiments.md +++ b/public/static/docs/learn/get-started/compare-experiments.md @@ -17,7 +17,7 @@ $ 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 +[Reproduce](/doc/learn/get-started/reproduce) chapter, is a way to run all the necessary commands to build the model and measure its performance. ```dvc diff --git a/public/static/docs/get-started/configure.md b/public/static/docs/learn/get-started/configure.md similarity index 100% rename from public/static/docs/get-started/configure.md rename to public/static/docs/learn/get-started/configure.md diff --git a/public/static/docs/get-started/connect-code-and-data.md b/public/static/docs/learn/get-started/connect-code-and-data.md similarity index 92% rename from public/static/docs/get-started/connect-code-and-data.md rename to public/static/docs/learn/get-started/connect-code-and-data.md index 0cece0c266..057407b751 100644 --- a/public/static/docs/get-started/connect-code-and-data.md +++ b/public/static/docs/learn/get-started/connect-code-and-data.md @@ -62,8 +62,7 @@ $ git commit -m "Add source code files to repo" Having installed the `src/prepare.py` script in your repo, the following command transforms it into a reproducible [stage](/doc/command-reference/run) for the ML -pipeline we're building (described in the -[next chapter](/doc/tutorials/pipelines)). +pipeline we're building (described in the [next chapter](/doc/learn/pipelines)). ```dvc $ dvc run -f prepare.dvc \ @@ -74,8 +73,8 @@ $ 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 +[previous section](/doc/learn/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 +120,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/learn/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/public/static/docs/get-started/experiments.md b/public/static/docs/learn/get-started/experiments.md similarity index 100% rename from public/static/docs/get-started/experiments.md rename to public/static/docs/learn/get-started/experiments.md diff --git a/public/static/docs/get-started/import-data.md b/public/static/docs/learn/get-started/import-data.md similarity index 83% rename from public/static/docs/get-started/import-data.md rename to public/static/docs/learn/get-started/import-data.md index d911d3c0c9..59da9f1ce1 100644 --- a/public/static/docs/get-started/import-data.md +++ b/public/static/docs/learn/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/learn/get-started/store-data) and +[pull](/doc/learn/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: