5 Comments

  1. Guido Walter Pettinari

    It’s great to see WPGraphQL getting the attention it deserves!
    I love the project and the idea behind: making WordPress viable for a fast headless CMS/e-commerce solution.

    I really hope WPGraphQL devs will team up with Vue Storefront devs (a great PWA e-commerce frontend) to make a fast and beautiful headless WooCommerce site… am I dreaming too much? 😜

    Report

  2. Nirmal Kumar

    Can anyone explain what benefits we get out of GraphQL API for WordPress?

    Report

    • Justin W Hall

      The same advantages you get from a GraphQL endpoint over REST. You FETCHing becomes succinct. In other words, you don’t over/under fetch data.

      A made of example. Let’s say you’re rendering a Post with the WP REST API. You might need:

      1) The menu
      2) The post_content
      3) Rich user meta (that doesn’t get returned in the post endpoint)

      To do so with the WP REST API you’d likely make 3 REST requests. One for each of the above. Furthermore, those REST requests would return a bunch of data that you ver likely may not use.

      Enter GraphQL. GQL let’s you define schemas and at the end of the day, through some pretty simple Query syntax, you could query for your menu, post_content and user meta in one request that contains exactly what you need. No more. No less.

      Report

    • Jason Bahl

      Hey!

      WPGraphQL allows developers the ability to declaratively and efficently interact with WordPress data using the GraphQL query language.

      There are many benefits to using GraphQL, but a big one is performance. Requesting data from GraphQL allows the consumer to specify the fields needed, which allows the WordPress server to do the minimum processing needed to get the data returned to the consumer. Where in other APIs, such as REST, the server sends an entire payload of data and does all the relational queries to get connected term IDs, etc even if the consumer is only interested in the title, for example.

      There are also many features of the GraphQL Query Language, such as aliasing and query fragments that make component-based development (React, Vue, etc) much easier to manage, as the data dependencies can be handled by the component, and not be some arbitrary data layer of the client application.

      Report

  3. Muhammad Muhsin

    This is great new for the WordPress + GraphQL community. WPGraphQL is a very useful project that deserves a lot of attention from developers and backers alike. Jason is someone who really cares about the community.

    I wish WPGrapQL all the success!

    Report

Comments are closed.

%d bloggers like this: