I wrote a book for O'Reilly about GitHub and their API and for some reason no one noticed that we added a chapter on Gollum (there isn't an API to access Gollum

I wrote a book for O'Reilly about GitHub and their API and for some reason no one noticed that we added a chapter on Gollum (there isn't an API to access Gollum on github). It was the weakest one of the chapters, IMHO, but, you know, deadlines. O'Reilly was gracious enough to release it under CC, so you can read that chapter (and the whole book actually) here: https://buildingtoolswithgithub.teddyhyde.io/chapter-03-gollum.html https://buildingtoolswithgithub.teddyhyde.io/chapter-03-goll... There is a section on using Rugged, the ruby git library and how you can use that with Gollum. https://buildingtoolswithgithub.teddyhyde.io/chapter-03-gollum.html#using-the-rugged-library https://buildingtoolswithgithub.teddyhyde.io/chapter-03-goll... While writing this book, I found it really fascinating to learn about how git works by trying to manage a Gollum wiki. For example, if you add an image to multiple places in a repository, it only needs to store it once because git can tell it is already in there. https://buildingtoolswithgithub.teddyhyde.io/chapter-03-gollum.html#optimizing-for-image-storage https://buildingtoolswithgithub.teddyhyde.io/chapter-03-goll...