You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Right now, our guide documentation is structured for somebody who wants to learn Viash and develop components from scratch.
A more straightforward approach for somebody to get to learn how to use is to have a couple of stand-alone guides for specific use cases, such as:
Transforming an existing R, Python, or Bash script into a component (identifying parameters, creating viash code block, creating viash config, adding runners and engines)
Todo: also support jupyter notebook?
Creating a Viash component for a standalone CLI tool
Combining existing components from Viash Hub into a pipeline
I propose we create separate pages for some of the most common use cases and include it as a separate chapter in the guide. We can create separate issues for any of these use cases
The text was updated successfully, but these errors were encountered:
Right now, our guide documentation is structured for somebody who wants to learn Viash and develop components from scratch.
A more straightforward approach for somebody to get to learn how to use is to have a couple of stand-alone guides for specific use cases, such as:
I propose we create separate pages for some of the most common use cases and include it as a separate chapter in the guide. We can create separate issues for any of these use cases
The text was updated successfully, but these errors were encountered: