Add syllabus docs #369
Add syllabus docs #369
Conversation
This is in no way complete. I'm trying to give enough background for people to be able to think about syllabus design in a way that is useful and not too overwhelming.
The core activity of syllabus design is getting the concept tree right. This is very tricky, and we recommend taking it in several smaller stages. This gives some suggestions for how to think about each stage.
Add section about selecting or coming up with stories for concept exercises.
This moves the community contributions section to the bottom of the document and tweaks the wording a bit. We will need to add a new subsection to this part about creating issues for concepts and exercises.
I haven't said anything about this explicitly, as I'm encouraging people to implement in layers, which I think will naturally help them think like this. |
We haven't figured this out yet; at least not to our satisfaction. Until we get a better handle on this, just encourage people to talk to us.
|
Okay, I have a very, very rough draft of some documentation about syllabus design. @junedev @angelikatyborska @SleeplessByte would you be willing to take a look at this and provide some initial feedback before we get more eyes on it? |
There was a problem hiding this comment.
@kytrinyx I really like what's there already. It resonates well with my understanding and the way it is described it hopefully lowers the barrier to get started for others. Well done!
I left the comments that came to my mind (besides all the "Yes, exactly!" feelings mentioned above). I hope they are not too nit-picky for the state of the draft. It is a bit hard to tell sometimes what exactly to already comment on.
Co-authored-by: Erik Schierboom <erik_schierboom@hotmail.com>
Co-authored-by: Erik Schierboom <erik_schierboom@hotmail.com>
Co-authored-by: Erik Schierboom <erik_schierboom@hotmail.com>
Co-authored-by: Erik Schierboom <erik_schierboom@hotmail.com>
|
Alright, I've reworked this. I think it might be okay as a first step, and we can iterate on it in smaller steps as we learn more about this whole process. I'm also planning on taking a stab at the "how to develop a concept exercise" which is tightly related to this documentation (and I may end up extracting some parts of this for the concept exercise documentation). Thoughts? Good to merge for now? Or any glaring omissions or weirdnesses? |
Co-authored-by: ee7 <45465154+ee7@users.noreply.github.com>
Co-authored-by: ee7 <45465154+ee7@users.noreply.github.com>
Co-authored-by: ee7 <45465154+ee7@users.noreply.github.com>
Co-authored-by: ee7 <45465154+ee7@users.noreply.github.com>
Co-authored-by: ee7 <45465154+ee7@users.noreply.github.com>
Co-authored-by: ee7 <45465154+ee7@users.noreply.github.com>
Co-authored-by: ee7 <45465154+ee7@users.noreply.github.com>
Co-authored-by: ee7 <45465154+ee7@users.noreply.github.com>
Co-authored-by: Jeremy Walker <jez.walker@gmail.com>
Co-authored-by: Jeremy Walker <jez.walker@gmail.com>
Co-authored-by: Jeremy Walker <jez.walker@gmail.com>
Co-authored-by: Jeremy Walker <jez.walker@gmail.com>
Co-authored-by: Jeremy Walker <jez.walker@gmail.com>
Co-authored-by: Jeremy Walker <jez.walker@gmail.com>
Co-authored-by: Jeremy Walker <jez.walker@gmail.com>
Co-authored-by: Jeremy Walker <jez.walker@gmail.com>
Co-authored-by: Jeremy Walker <jez.walker@gmail.com>
Co-authored-by: Jeremy Walker <jez.walker@gmail.com>
Co-authored-by: Jeremy Walker <jez.walker@gmail.com>
People should go solve the first exercise in several tracks to get a feel for it.
|
Thanks for the comments, suggestions, and nitpicks, @junedev @ErikSchierboom @iHiD @ee7. I'm going to squash and merge this, and then iterate further as the docs get read and we find more things to fix. |
Draft introduction to syllabus design. I'm trying to give enough background for people to be able to think about syllabus design in a way that is useful and not too overwhelming. Co-authored-by: Erik Schierboom <erik_schierboom@hotmail.com> Co-authored-by: ee7 <45465154+ee7@users.noreply.github.com> Co-authored-by: Jeremy Walker <jez.walker@gmail.com>
Fixes #367