Coverage remained the same at 94.216% when pulling 0f7844b on docs-improvements into 2016011 on master.

Coverage remained the same at 93.934% when pulling 15b5e6a on docs-improvements into 6f03597 on master.

This is a huge leap forward @phalt, thank you. Most of my feedback above is stylistic and grammatical in nature. The broad strokes of your work are spot on. My only high level concerns:

• There's some duplication of content between the installation & basic tutorial guides. I'm worried our reader might get confused.
• To me, there's two logical groupings of the content that I don't think is obvious. The first three are squarely "get up and going" sort of guides whereas everything that proceeds that is a "let's dig in deeper" sort of flavor. I'm wondering whether it makes sense to distinguish tha.t
• We're treating Relay as an afterthought in a lot of these guides. I'm wondering whether it makes sense to factor it out into its own section?

Thanks for the feedback @dopeboy and @subwindow

Yes, my grammar isn't great so that feedback is useful for me!

Regarding your points:

There's some duplication of content between the installation & basic tutorial guides. I'm worried our reader might get confused.

I've not yet updated the basic tutorial guide but I want to reduce some of the duplication. I'm also aware the current docs are hard to read because it's all spread out. Does it make sense to duplicate a few things just to make it easier to read through a page in one go? Suggestions welcome.

To me, there's two logical groupings of the content that I don't think is obvious. The first three are squarely "get up and going" sort of guides whereas everything that proceeds that is a "let's dig in deeper" sort of flavor. I'm wondering whether it makes sense to distinguish that

Yeah I wanted to make this clearer and I think it'll be better as I finish up. I based the docs around how I see the project from the point of view of a user - what does a user want to do versus what does this project provide. For example - currently Django users come to these docs, see a bare minimum of content, and don't know they have to visit the core graphene docs to find what they need.

We're treating Relay as an afterthought in a lot of these guides. I'm wondering whether it makes sense to factor it out into its own section?

Again, I don't really see Relay as a separate topic but rather an extension on top of Queries / Mutations. This is my opinion, and I'm happy to change it if the consensus is that it should be separate. But I feel like it flows better to talk about Relay for Queries when talking about Queries, etc.

This is a vast improvement on what we currently have. Thank you 🙏

Just wanted to pop in and say thanks for updating the docs 🎉

@clarkmoody no problems, wait until you see what I do next!

@phalt great job! So much better!

@jkimbo thanks!