Not really. A straightforward implementation has nothing to do with database usage. A resolver is an endpoint. You can leverage that like you can in any other http backend server.
Yeah, I think there is a perception that people want direct queries into their database, but that is actually not the correct way to think about graphql.
Make the investment to learn Flux if you are using React. Now that we have had Flux in production for a few months, I think have React without Flux is a handicap. I think reading about it is harder than just building something with it. My advice? Build something small with it, and you will at least know Flux. Then you can decide to use it or not. We use facebook's flux implementation, and have no regrets.
This is great. We currently hold a weekly clojure class at work, and this will be very helpful to some of the people who attend. The more content the better!
I made a similar cheat sheet years ago as a PDF. It got some popularity around the developer community. I think it being html/an open source document, you can use it in many different ways (including printing it out and putting it on your wall). The fact that I have already received pull request I think shows it might be a good idea.