-
Notifications
You must be signed in to change notification settings - Fork 17
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
Create ongoing training and learning opportunities for users #128
Comments
Makes sense to me... wondering if we should focus on videos or written stuff first? 🤔 |
@damianavila what I've found useful is to start off writing a "Tutorials" section in docs, and then in a workshop, use that tutorial ~verbatim as a step-by-step guide. That will surface issues, confusion points, etc and those can be fed back into the tutorial docs. It is trickier if you want to maintain "slides" and things like this in addition to the tutorial docs. One option there is to define slides that are lightweight and just point to the tutorial to step through. That way there's one source of truth. Or, we could do something clever and use a RISE presentation or something, but I suspect we'll need to wait until somebody has more dedicated time for this |
Interesting 😜.
I agree. |
Background and proposal
Context
Many users do not immediately know how to best-use 2i2c's infrastructure for their research / educational use-case. We cannot cover domain-specific training for all communities, but we could provide a some regular touch-points to help onboard users and clear up problems with major workflows. This would also be a good opportunity to get some face-to-face feedback about the service itself.
Proposal
We should set up a recurring seminar or workshop series that covers major questions and confusions that users may have.
Implementation guide and constraints
Topics to cover
This wouldn't be unique to a scientific field, but might cover the major use-cases we expect 95% of our users to have. For example:
Where to store material
We could store each of these as tutorials on docs.2i2c.org, in a dedicated "user tutorials" section (and perhaps another set of tutorials in a "hub administrator tutorials" section). The documentation would be step-by-step, and if we were running live workshops to step others through an analysis, these tutorials would be reference material we'd use.
Updates and ongoing work
The text was updated successfully, but these errors were encountered: