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

Documentation for end-users of 2i2c hubs #129

Open
2 tasks
choldgraf opened this issue Dec 7, 2021 · 1 comment
Open
2 tasks

Documentation for end-users of 2i2c hubs #129

choldgraf opened this issue Dec 7, 2021 · 1 comment
Labels
Enhancement An improvement to something or creating something new.

Comments

@choldgraf
Copy link
Member

choldgraf commented Dec 7, 2021

Problem statement

We currently have documentation for 2i2c Hub administrators at docs.2i2c.org, but we do not have a dedicated place for Hub users. This means that many users may not be familiar with how to do basic operations on a hub, or how to use it to its potential.

Solution

We need end-user documentation that covers the major aspects of doing work on a JupyterHub in the cloud. It should exist at a dedicated URL such as users.2i2c.org and should be easy to find for users that are unfamiliar with Jupyter workflows and may be unable to do things like log in to the JupyterHub.

We should define a basic Tutorial, as well as some common "How to"-style operations that we think 80% of hub users will want to do.

Appetite

1 sprint

Because a lot of this content is already out there, we should get a minimal viable product up within one sprint. This will help us get the most important pieces set up early on so that we have something to offer other communities.

Guidance

Including all of our current user personas in docs.2i2c.org is probably too much. Instead we should explore using three different documentation sites for these, and cross-linking between them. For example, something like:

User guide

users.2i2c.org

This is for end-users of a 2i2c Hub. AKA, somebody that logs on to a hub and wants to run their own workflows.

A good starting point is the Pangeo scientists guide and related user-facing documentation there, which is a good start for major workflows we should cover.

Administrator guide

administrators.2i2c.org

This is for somebody that administers a hub on behalf of others.

We can start with what we have at docs.2i2c.org, and spin that off into a dedicated guide. Probably some things in the Pangeo docs as well.

  • Include information about how to add to / remove a package from a user image repo

About the service

service.2i2c.org

This is meta information about the service itself, it is designed for a decision maker who is considering using a 2i2c hub service.

User personas

I think there are three user personas to include:

  • a classroom persona
  • a team-based research persona
  • a scalable+cloud computing persona

Out of scope

  • This should not be a comprehensive guide to data science, it should be focused on the basic steps that 80% of our users would want to try within the first few weeks of them using a hub.
  • This should not be a comprehensive "guide to Jupyter" - we want to assume some basic experience with the Jupyter ecosystem, and point to other tutorials and guides for people that need to learn from scratch, and focus these docs on the workflows that are particularly useful for our personas

Related issues

@choldgraf choldgraf added 🏷️ documentation Enhancement An improvement to something or creating something new. labels Dec 7, 2021
@choldgraf choldgraf changed the title [Project] Documentation for end-users of 2i2c hubs Documentation for end-users of 2i2c hubs Dec 7, 2021
@sgibson91
Copy link
Member

sgibson91 commented Jan 7, 2022

I would also add that a "comprehensive guide to JupyterHub" is also out of scope - we should upstream/link out other resources/advanced usage patterns, etc.

@choldgraf choldgraf transferred this issue from 2i2c-org/infrastructure Mar 14, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Enhancement An improvement to something or creating something new.
Projects
No open projects
Status: Ready to work
Development

No branches or pull requests

2 participants