> For the complete documentation index, see [llms.txt](https://docs.ccv.brown.edu/archive-jupyterhub/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.ccv.brown.edu/archive-jupyterhub/workflows.md).

# Determine Your Workflow

Guide for students Ⓢ and instructors Ⓣto choosing a workflow and finding related documentation

Depending on how familiar students are to *Version Control* technologies such as ***Git***, different workflows may fit best the strategy used to distribute coding materials and assignments.

## Ⓢ① Students in classes that are new to programming and/or version control

### Related sections in the documentation (look for ① and Ⓢ in the section title):

* [Getting Started](/archive-jupyterhub/getting-started/signin.md)
* [Using Your Hub](/archive-jupyterhub/using-your-hub/interface-overview.md)
* [Getting Support](/archive-jupyterhub/help-and-support/getting-support.md)

## Ⓣ① Teachers looking for a simple way to **distribute materials to students who will NOT be introduced to git.**

There are two options:

### Direct Upload:

This simple workflow assumes **no git knowledge** from the student nor the instructor. Notebook files are shared via CANVAS and directly uploaded to JupyterHub

![Direct File Upload Workflow](https://2883398872-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-LLCCXzhzhO5fUT5UTHC-887967055%2Fuploads%2Fgit-blob-b15d5fbc3943bd7c7193b1271332d4fd9023324b%2FDirect%20Upload.png?alt=media)

#### Related sections in the documentation (look for Ⓣ ① in the section title):

* [Getting Started](/archive-jupyterhub/github-classroom-student-guide/overview.md)
* [Using Your Hub](/archive-jupyterhub/getting-started/signin.md)

### Via Smart Link

Using this workflow, teachers have the ability to generate a **smart link** that pulls the materials automatically for students into their JupyterHub. If you are a teacher using this method, you will need **basic familiarity with git and github.**

![Workflow when synching content using a (special) link](https://2883398872-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-LLCCXzhzhO5fUT5UTHC-887967055%2Fuploads%2Fgit-blob-dc20f5a651ead68e717aa58ad78796bb059ccf2b%2Fauto%20pull%20.png?alt=media)

#### Related sections in the documentation :

* [Content sync via link Ⓣ①](/archive-jupyterhub/content-sync-via-link/nbgitpuller.md)

## ⓉⓈ② Teachers and Students using Git/GitHub and GitHub Classroom

Using Git and GitHub to distribute your materials encourages best practices for software development and additionally adds versioning to changes made to the source code, allowing students to revert to prior versions if necessary. If you will be using Git, we recommend using ***GitHub Classroom*** to help automate the process.

### Related sections in the documentation (look for ② in the section title):

Ⓢ Students should familiarize themselves with:

* [Content Sync via GIT](/archive-jupyterhub/git-basics/overview.md)
* [GitHub Classroom (Student Guide)](/archive-jupyterhub/github-classroom-student-guide/overview.md)

Ⓣ Teachers should familiarize themselves with:

* [Content Sync via GIT](/archive-jupyterhub/git-basics/overview.md)
* [GitHub Classroom (Instructor Guide)](/archive-jupyterhub/github-classroom-instructor-guide/overview.md)