ui: add interactive tutorial links to the appropriate pages

[kurianbenoy]

This is to create an easier run time environment for our tutorials like how pytorch docs tutorial has:

https://pytorch.org/tutorials/beginner/blitz/tensor_tutorial.html

[shcheklein]

We can reuse Katacoda's scenarios @dashohoxha is building for this.

[jorgeorpinel]

...we should start integrating it with the engine (add a button). Any suggestions on how can it look like?

Agree! That seems like the main purpose of this ticket 😋. As for how it can look, maybe pretty similar to the PyTorch tutorial link provided,

[algomaster99]

@shcheklein We have already hyperlinked it. https://dvc.org/doc/tutorials/interactive. Where are we planning to put the interactive buttons?

[kurianbenoy]

So we're discarding Kaggle kernels for now right?

I don't even know what they are, but for me it is ok, as long as somebody is willing to work on them.

I feel there will be some maintenance challenges to support jupyter-notebook based interactive tutorials in Kaggle with DVC like @jorgeorpinel said for Documentation team. And to be honest a CLI tool like DVC is not best to be run in a notebook.

I have already added the get started tutorial as a jupyter notebook sometime back.

https://www.kaggle.com/kurianbenoy/introduction-to-data-version-control-dvc

[jorgeorpinel]

Agree, I think we should stick with Katacoda, and also ignoring Colab for now unless a contributor wants to develop and maintain that.

We have already hyperlinked it. https://dvc.org/doc/tutorials/interactive. Where are we planning to put the interactive buttons?

By "interactive button" we mean a pretty link right? Yeah it's just a matter of design. Refer to #670 (comment) and #670 (comment). I think whoever takes on this task should just come up with a suggestion as of where in the docs layout to place this.

Perhaps a first step is to implement automatic recognition of md links to katacoda.com/dvc/..., turning them into buttons, and let the doc writer decide where to put them in each doc. Or <button> tags with value="katacoda.com/dvc/...". Idk, just brainstorming here.

[iesahin]

What's the current status about this ticket? GS pages seem to have links to scenarios. Is there anything that should be modified in the docs about this?

[shcheklein]

GS is outdated, not all pages have Katakoda unfortunately, also consider the most recent update @dberenbaum is doing in #2195

[jorgeorpinel]

I think ultimately #1400 is about the content itself, and this one is about the design. We have this now:

Wide screens

Narrow screens/mobile

I think if we are OK with that interface we could indeed close this. But I think the narrow/mobile view should spell out "Katacoda" at least.

[shcheklein]

I think if we are OK with that interface we could indeed close this. But I think the narrow/mobile view should spell out "Katacoda" at least.

I think this not in the scope of this ticket, @jorgeorpinel

[shcheklein]

I guess we need to close this one and create the new one ticket that is specifically focused on content, not ui/ux

[shcheklein]

Since I see we go back and forth with labels, it's clear that we interpret in different ways

[jorgeorpinel]

There's #1400 for the content so yes, I wanted to think this was about something else. Thanks!