I've thought a little about moving the book into its own repo. It really depends how extensive we want the book content to be. I think the biggest reasons for doing this would be: 1. Separation of concerns: CI jobs, project tracking board/milestones, branches are specifically for book dev (i.e:

gh-pages

branch). 2. Less "bloat" when cloning the repo I think the first reason is less of a concern since we don't have many people working on the book atm. The second one might be bigger as we continue to add images to the book, but again we're not too big so perhaps not worth losing sleep over right now.