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
Improvement Description
This seems to be one of the most common stumbling blocks when working with QIIME 2. The scope of this could range from a static flow-chart type of document to a more sophisticated "choose-your-own-adventure" SPA.
The text was updated successfully, but these errors were encountered:
I ran a similar idea over with @gregcaporaso recently and he pointed me towards this thread.
I've been thinking about starting some sort of interactive wizard/flowchart to help new users how to navigate through q2 and in some cases aid in deciding how to continue to analyse their data past once importing phase which I believe was the main objective of this item. Since most of the common questions on the forum already have answers in the many tutorials and plugins, this would be more focused on pointing them to the right resource rather than rewriting the whole process. Of course, some sections would benefit from additional explanations as well. It can be something as basic as the wizards they use at GUSTAME or something more aesthetically pleasing and fun.
I'm happy to take a lead on this come the San Diego Workshop in May, but I wanted to make sure I'm not stepping on anyone's toes here and would also love to hear everyone's thoughts, recommendations, and vision on this, or perhaps something is already in the works?
Nothing is in the works, I think that sounds like a fantastic idea! I think we're also open to pretty much anything in terms of implementation. There's definitely a lot of flowchart/wizard libraries out there which could make life easy.
Improvement Description
This seems to be one of the most common stumbling blocks when working with QIIME 2. The scope of this could range from a static flow-chart type of document to a more sophisticated "choose-your-own-adventure" SPA.
The text was updated successfully, but these errors were encountered: