As GraphQL continues to emerge in the API space, an increasing number of advocates have lauded it for being “self-documenting” or “self-descriptive”. Some have even gone as far as to say GraphQL doesn’t need documentation.

I want to debunk this “self-documenting” myth, explain the importance of naming in GraphQL; something co-creator Lee Byron has promoted himself, and share why I think technical writers still have an important role to play in its documentation.