In gitbook, I don’t know of a way to link to a part of the book and limit access to just that part. For me, being super lazy, I link to the start of the part that I want them to read and list the topics and I tell them that the book is organized in same order that material is presented in class. If they wish to read ahead, I don’t see a problem with it. If you want to limit it week by week, you would need to put each week into a separate book on gitbook… but I can’t think of any other method to release this week by week othewise.
I was using github before GH classroom existed, so for me GH classroom is more of a repository creation/access management tool. I use GH Classroom to create repositories within an organization because it helps with managing access rights. Before gh classroom, I had a google form that students would use to fill in their names and github id’s and then I would take that info and run a bash script to create teams and access. Someone would always fill in that form wrong by adding things like brackets to indicate their preferred name and break my script so it was really annoying.
For the courses I teach, I have a common repo that all students have read access to where I post everything. This is where the creation of a “group assignment” that has only 1 team for content access comes in. Doing this method, in github, I can create a single repository that all students can access by using a link and hitting a “join” button which is super easy to deal with and I don’t have to manage lists of userid’s. When you create a “group assignment” with one team, what gh classroom will do is create a single repo and a single team within your course organization. Any student who “joins” the assignment is added to that one team on github. I change the access level to the course repository of that one team to “read”, so that students can’t alter my course repository content. I then use the repository’s wiki as a means to hand out “documents” (assignments, labs, notes… everything). I have a skeleton “Home page” that I copy over that has a list of links to everything. So as you can see, long term content are full urls, while short term content are not. I then go and populate the short term content as I go. If that short term content is not yet posted, I just make the page and put “coming soon” on it… this will give me a url to that content even if its not done and I can put a link to it in the school’s LMS. Here is the skeleton that I have (shortened of course… but you sort of get a feel for the setup).
* [Course Addenda](Course-Addenda)
* [Course Notes](https://catherine-leung.gitbook.io/data-strutures-and-algorithms/)
* [Lab 0](Lab-0)
* [Lab 1](Lab-1)
* [Lab 2](Lab-2)
* [assignment 1](assignment-1)
* [assignment 2](assignment-2)
* [Style Guide](https://github.com/cathyatseneca/Common/wiki/style-guide)
* [my animations, sorting, linked list, stacks, queues](http://cathyatseneca.github.io/DSAnim/index.html)
* [GDB Guide](https://github.com/cathyatseneca/Common/wiki/gdb-guide)
* [gdb - lldb command map](https://lldb.llvm.org/use/map.html)
* [Drawing Template for Linked Lists](https://scs.senecac.on.ca/~catherine.leung/img/blankll.pdf)
The addenda has weekly topics, and here is how I post that:
All readings are from the subject notes: https://catherine-leung.gitbook.io/data-strutures-and-algorithms/
| Week | Topics and Reading | Assessment - Out | Assessment Due and Weight |
| week 1 | [Introduction](https://catherine-leung.gitbook.io/data-strutures-and-algorithms/), [Algorithms analysis](https://catherine-leung.gitbook.io/data-strutures-and-algorithms/algorithms-analysis), [Asymptotic Notation](https://catherine-leung.gitbook.io/data-strutures-and-algorithms/algorithms-analysis/big-o-little-o-theta-omega-notation)|Lab 0, Lab 1| Lab 0 - 0% |
| week 2 | [Recursion](https://catherine-leung.gitbook.io/data-strutures-and-algorithms/recursion), [Lists](https://catherine-leung.gitbook.io/data-strutures-and-algorithms/lists)| Lab 2 and A1 | |
You could also just make the main wiki page your readme.md file content instead of wiki… but I prefer the wiki.
Anyhow, I hope this helps clarify what I usually do.