In the REST API podcast, Joe and I talked about Drupal’s upcoming support of GraphQL with their API, and how it’s so new. It is new, and it’s getting a lot of attention. Here’s a site to learn about it.
If you like trying out new open-source CMS applications now and then, check out Django-based Wagtail, which Mozilla and Google are using. Wagtail is designed for headless deployments where the frontend pulls content from the CMS with GraphQL queries.
Leonardo Maldonado explains why he thinks why GraphQL is the future of APIs. Leonardo has another interesting post on how to write your first React hook.
Renato Alves explains why GraphQL and WordPress work well together: “…to author a GraphQL API you only need a one-time effort…. and another advantage of using GraphQL is its ease of integration with multiple data sources.” There are some downsides, however. There are some “rough-edges” (like caching), access control, and a “steep learning curve.” Migrating…
Joe Howard explains at Torque how to begin developing headless WordPress sites. The main advantages are flexibility and control, easier multi-channel content publishing, and better security and speed. 👤🪓 Joe names three tools to help you get started: GraphQL API, GatsbyJS Framework, and Static Fuse‘s Gatsby themes and plugins.
Prisma and other contributors created howtographql.com, a free and open-source tutorial for learning GraphQL “from zero to production.” I found it in a newsletter for women and non-binary coders from Veni Kunche that’s worth a look as well.
Leonardo Losoviz asks, should WordPress should have a GraphQL API in core? Would WordPress be better off with both REST and GraphQL APIs for developers to choose from? 💬 Tell us what you think or jump right into the discussion in our #development channel.
