Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Review onboarding experience and get started #3331

Closed
4 of 7 tasks
shcheklein opened this issue Feb 22, 2023 · 3 comments
Closed
4 of 7 tasks

Review onboarding experience and get started #3331

shcheklein opened this issue Feb 22, 2023 · 3 comments
Assignees
Labels
A: onboarding Improving and simplifying users happy path. How do we get them have value asap? priority-p1 Regular product backlog 📦 product Needs product input or is being actively worked on

Comments

@shcheklein
Copy link
Member

shcheklein commented Feb 22, 2023

We've done a lot of things recently greatly simplifying user experience when they first come and try to use DVC through VS Code. Namely, we introduced the onboarding flow where we share DVCLive snippet, we introduced a way to migrate to pipelines (dvc.yaml generation). we create a way to connect Studio and VS Code.

We need to spend some time reviewing everything one more time and update messages, documentation, Gif if needed.

@shcheklein shcheklein added priority-p1 Regular product backlog 📦 product Needs product input or is being actively worked on A: onboarding Improving and simplifying users happy path. How do we get them have value asap? labels Feb 22, 2023
@shcheklein shcheklein self-assigned this Feb 22, 2023
@dberenbaum
Copy link
Contributor

From https://iterativeai.slack.com/archives/CUSNDR35K/p1686138538724399?thread_ts=1686068465.203069&cid=CUSNDR35K and related to https://github.com/iterative/studio/issues/5933#issuecomment-1580736124, it might be good to explain under experiments that the experiments are saved in Git and the user doesn't need to commit each experiment themselves.

@julieg18
Copy link
Contributor

Reviewed our "pipeline" process and reviewed a couple things that could possibly be improved:

"Create Pipeline" message

image
  • Is just mentioning experiment reproduction enough info to explain what the command is doing? Should we expand a bit more on what a pipeline is or is it most likely clear enough for users new to DVC?

Run Experiment Button

When you click the "Run Experiment" button without dvc.yaml, it runs the create a pipeline command:

Screen.Recording.2023-06-26.at.7.10.30.PM.mov
  • Similar to the previous comment, is it obvious enough that creating a pipeline is how we run the experiment? Otherwise, it might seem odd that "Run Experiment" opens a quick pick for setting up a pipeline.

Generated dvc.yaml


# Read about DVC pipeline configuration (https://dvc.org/doc/user-guide/project-structure/dvcyaml-files#stages)
# to customize your stages even more
stages:
  train:
    cmd: python requirements.txt
    deps:
      - requirements.txt
  • There's an empty line on top of the file. Minor but the file will look a little cleaner without it.

@julieg18
Copy link
Contributor

After a discussion with Ivan, going to close this issue as most of the tasks are finished and dvc.yaml related tasks are in #4194.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
A: onboarding Improving and simplifying users happy path. How do we get them have value asap? priority-p1 Regular product backlog 📦 product Needs product input or is being actively worked on
Projects
None yet
Development

No branches or pull requests

3 participants