Website Content - Collection of issues and wishes

[erikwrede]

This issue serves as a collection point for issues and wishes regarding the website. Let's drop our thoughts here and try to bring it to a structured form later.

• assignee(s): @erikwrede
• source: Redesign GraphQL.org's homepage #21 (comment)

---

I personally see the following points:

• Content is very focused on the query language itself, not on its integration into software. => "Reads like an introduction to SQL, not like the introduction to a powerful tool that can revolutionize the way you define, consume and utilize APIs to build next-generation apps."
• Fragment usage is not well-represented and explained
• Lack of common patterns & best practices
• Best practices in large projects (Backend & Frontend)
• No hands-on examples (e.g. "copy this example for Apollo or Strawberry or ChiliCream")
• We need more content that inspires visitors, rather than plainly informing them

[martinbonnin]

• Best practices for handling new enums/unions. Especially how to make sure your older client is compatible with newer types being added.
• Best practices arround error modeling. When to model errors as data vs plain GraphQL errors.

[erikwrede]

Best practices arround error modelling. When to model errors as data vs plain GraphQL errors.

I like that! Maybe we can include/host something like https://github.com/graphql-rules/graphql-rules?

[martinbonnin]

Not directly related to the GraphQL technical content itself but would be cool to have:

• events page
• ambassadors