Life is h as d and so is learning GraphQL @carolstran
meeshkan.com
github.com/unmock
queerjs.com
globaldiversitycfpday.com
@carolstran
@carolstran
@carolstran graph.cool
@carolstran
@carolstran
@carolstran
@carolstran
@carolstran
@carolstran
@carolstran
@carolstran
@carolstran
GraphQL @carolstran
GraphQL @carolstran
@carolstran
@carolstran
Go to GraphiQL and “try it out” @carolstran bit.ly/graphiql-demo
Work your way through the documentation @carolstran graphql.org
@carolstran graphql.org
@carolstran
@carolstran
@carolstran
@carolstran graphql.org
@carolstran graphql.org
@carolstran graphql.org/learn
@carolstran graphql.org/learn
@carolstran
@carolstran
Anyone who encounters GraphQL, needs to be able to understand it @carolstran
@carolstran gatsbyjs.org
@carolstran
The problems and what we can do about it @carolstran
Problem Just because GraphQL is “self- documenting," doesn’t mean you should stop writing docs @carolstran
@carolstran bit.ly/github-gql-api
@carolstran bit.ly/github-gql-api
“This type of documentation is great after you understand the domain area and the business cases and you’ve built some confidence making queries and mutations… — Andrew Johnston @carolstran bit.ly/andrew-api-docs
…but without more detailed documentation that covers the conceptual materials, you’re not going to get there.” — Andrew Johnston @carolstran bit.ly/andrew-api-docs
“Documenting API endpoints explains how individual tools work, explaining how to use those tools together is a whole other area of documentation effort. ” — Chris Ward @carolstran bit.ly/documenting-graphql
@carolstran gatsbyjs.org/docs/querying-with-graphql/
Problem GraphQL is dominated by the JavaScript community @carolstran
@carolstran bit.ly/graphql-def
@carolstran
JavaScript C/C++ Rust TypeScript Swift Go Ruby .NET Scala PHP Erlang Clojure Python Elixir R Java Haskell (and more) @carolstran
@carolstran graphql.org/learn
@carolstran graphql.org/learn
@carolstran graphql.org/code
Problem Assumed knowledge and specific terminology @carolstran
Everyone is a beginner at some point @carolstran
Listing pre-reqs for a tutorial will help prevent headaches @carolstran
@carolstran bit.ly/graphql-glossary
@carolstran bit.ly/fb-graphapi
Quick wins some short documentation tips @carolstran
Quick win Be confident with your definitions @carolstran
Quick win There’s a time and place for analogies @carolstran
@carolstran
Quick win There’s a time and place for analogies (and that place is Twitter) @carolstran
@carolstran bit.ly/burger-tweet
Quick win Don’t integrate tools or services without explanation @carolstran
Quick win Be transparent about any downfalls @carolstran
M os e res ov rces for learning GraphQL and beyond @carolstran
Res ov rce HowToGraphQL.com @carolstran
@carolstran howtographql.com
Res ov rce A Frontend Developer’s Guide to GraphQL @carolstran github.com/peggyrayzis/guide-to-graphql
@carolstran css-tricks.com/front-end-developers-guide-graphql/
Res ov rce GitHub's GraphQL API @carolstran bit.ly/github-gql-api
@carolstran bit.ly/github-gql-api
Res ov rce Community Resources on official GraphQL docs graphql.org/community @carolstran
@carolstran graphql.org/community
Res ov rce https://so-you-want-to-learn- graphql.netlify.com/ github.com/carolstran/so-you-want-to-learn-graphql @carolstran
@carolstran github.com/carolstran/so-you-want-to-learn-graphql
One last thing (but actually, I promise) @carolstran
@carolstran bit.ly/javascript-monads
Please don’t let GraphQL become the new monads @carolstran
Recommend
More recommend