I have an alternative use-case for Cayley that I would like to see adopted into the main project.
I'm using Cayley entirely in the browser by transpiling to JS using GopherJS, storing the graph in "memstore".
It works surprisingly well, with my largest graph so far having 325k quads and using 1.85Gb of memory (including browser overhead) on Safari.
The generated minified JS for the app I'm developing is 2.8Mb (482Kb gzipped). To get it that "small" I had to remove the "net" dependency from "pborman/uuid". This was trivial, see node.go/node_js.go at https://github.com/elliott5/uuid/tree/gopherjs .
A future GopherJS-specific version of Cayley could use of the standard browser data-storage options, or have an online/offline capability by using https://pouchdb.com/ for example.
I hope extending the use of Cayley into the browser environment will be of interest to the community.
In terms of building examples to recruit new users, using this approach has the great advantage of not requiring a server.
It might also lead to better graph visualisation capabilities (maybe using D3).
To better demonstrate the possibilities, I've adapted the trivial example code for "using Cayley as a library" to show it being used in JS. Actually I only needed to add 2 lines, and them only to produce a pop-up "Alert" when you visit the page! You can see it at https://elliott5.github.io/cayleyjs/ - the Go code lines marked ***** are those of interest. I've also included the generated JS directly into the HTML file, so that you can see what is going on.