Dave Berenbaum

As a companion to #8411, we need to also handle version-aware dependencies. Ideally, we shouldn't even need to do anything here and we should check for version IDs when collecting...

The pre-commit hooks don't make sense for cloud versioned remotes. The `pre-commit` hook needs to actually push in order to get the cloud-versioned IDs, and a `pre-push` hook doesn't make...

worktree: drop dead code

1

There is a bunch of dead code from implementing the no-longer supported worktree remotes.

Model registry docs consolidation

3

This is an attempt to rework the docs in response to feedback that it's confusing and makes it hard to get started with our tools. I started with model registry...

start: drop/revise experiment collaboration

2

### Report Analytics show that this page has few views, low time on page, and high bounce rate. Let's consider dropping it or revising it.

Outline of docs structure

9

Opening for discussion. We recently finished moving all the remote info from the command reference to distinct user guides. I think it's way more organized now, but I worry that...

Advanced experiment configuration

2

Extracted from #4401. Related to both experiments and pipelines. - [ ] Templating, dict unpacking, advanced dvc.yaml features (close https://github.com/iterative/dvc.org/issues/2313) - [x] Hydra composition

Quickstart

2

### Report Our current "Get Started" pages are multiple pages, going through a full project. They are useful for someone who wants to set aside time to learn dvc, but...

vs code: pipelines

1

### Report VS Code can both help define the DAG and show the DAG. We need to show how this can help in https://dvc.org/doc/start/data-management/data-pipelines and/or https://dvc.org/doc/user-guide/pipelines.

Another thought on a lightweight way to help here: better docs in https://dvc.org/doc/dvclive/live/log_plot. Having an example of the input format for each template could go a long way. There are...