Collaborative lesson development: review

[rkdarst]

Review on this lesson, in context of current training. These are unsorted thoughts, not actionable yet!

• It seems focused on contributing to our lessons. Should the top start with why we use the static file + github flow? Why it's good? What are the disadvantages? Do we try to convice people to use this? Offer help to get started?
• What can an exercise be? Doing most of the lesson stuff requires git, which we assume people don't have. We could make some questions and have them figure them out by looking at the repo. Or, set up a new lesson (too much). Or ...?
• How do we balance sphinx-lesson with jekyll lesson? We can perhaps also say there is some new but identical carpentries style, that we can't find. Should I add some interesting features of sphinx-lesson?
• Perhaps the main flow through this episode can be:
  • Styles of lesson design, what we do use static sites. How it helps learning
  • Tour of the styles and how they work in general
  • How CodeRefinery works for it's lessons
  • How git contributes to collaboration.

I don't think there is time to do much, but these are ideas. Adding a bit to the top and changing about the framing might be worth it.

I predict that this will go quite fast as it is, and the next teaching demo will also be fast. So, we should try to use a bit more time.

[bast]

Thanks for the write-up. I might be able to build this in, this episode needs some change.

[bast]

Unassigned. I will not implement this fully but will take some of this in. Later more.