Open nuke-web3 opened 1 year ago
I for sure support the first goal of splitting starter code out into their own repos. I think they should also be referenced in this repo so instructors know that they exist, where to find them, and when they are expected to be used.
I'm not clear on the second goal.
To include in removal from this repo, into their own and standardize the naming & document flow:
Related to #492
mono repo for handouts all at once via github team for students?
The idea here is to have all student facing content to be in dedicated repos, and if it's OK to hand out all non-code things in a single place, it would be handy to have everything in a repo (and rely less on notion for example)
In my ideal world the entire academy is a set of git based templates that could be in a monorepo itself for us to spin up a new cohort anytime, with only a few things to tweak for each cohort (branding, specific info about locations, staff info, etc.)
This repo should be dedicated exclusively to slides and instructor facing notes on running the academy.
All student facing material outside slides, especially if students need to clone it or access that isn't slides should live in independent repos:
This will greatly increase the ease of running the academy and help isolate what parts of content are distributed to students.