I've used GitLab in the past years but this schoolyear I'm focusing on a chat-based teaching style with Gitter and GitHub. Gitter-chat is used quite intensely - mainly during in-class-hours - for assignments, tips, pictures (live demo screenshots), links, ... Every student has their own workstation to participate.
Sometimes I use Assignment-Repo's but there is also the Course-Repo which is mainly edited after class-hours (mainly because my courseware is still being converted to GitHub).
In the Course-Repo there is a
README.md which contains ALL the links to little courseware-snippets. These snippets are roughly organised by topic in subdirectories. They are to be read, re-read and practiced regularly by students. Each snippet ideally focuses on one syntactic and/or conceptual skill (like a for-loop, an array, ... - I teach programming). The
README.md provides a kind of chronological/topical index: a starting-point for regular practice.
I am thinking about using these techniques in the (near) future:
- In the README-index, each link can include an emoticon (, , ...) to show which topics are new or have to be focused on during a single session. The commits with the emoticons can be updated live in the beginning of a lesson but also weekly (for the bigger picture). These emoticon-commits can be kept in separate, temporary branches (removed biyearly for example). They track the course-progress.
- pupils must fork the Course-Repo to make their own note-commits. These notes can be shared with the teacher, should the need arise. (For now, I'm letting students make a little portfolio-repo with their own notes.)