ByDan Knauss
Posted on
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 completely to GraphQL without understanding its risks would be a bad mistake.
Leonardo Losoviz explores why you might want to support “CMS-agnosticism” using the GraphQL API for WordPress plugin and the 91 PHP packages it contains. 📦
We’re happy to hear that Jason Bahl is now going to be working on GraphQL for WordPress full time. The project is picking up steam, and I’m expecting significant updates soon. 🚂
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.
I am joined by Matt Mullenweg to discuss decision making, Gutenberg, core WordPress processes, Automattic’s business, and more.
Leonardo Losoviz describes how to implement a GraphQL server with components in PHP. He starts by defining components, and then he describes “the architectural design of the GraphQL server in PHP GraphQL by PoP, which uses components as a data structure instead of graphs.”
Here’s a plugin that introduces GraphQL to BuddyPress. Nice! 🔌
