WPGraphQL, a popular plugin that brings powerful GraphQL functionality to WordPress sites, is gaining a new level of endorsement within the WordPress ecosystem. Its creator, Jason Bahl, recently joined Automattic, aligning WPGraphQL with WordPress’s parent company and positioning it to become an official “canonical plugin” on WordPress.org.
What is WPGraphQL?
WPGraphQL introduces a GraphQL API for WordPress, allowing developers to query WordPress data more efficiently and flexibly compared to traditional REST APIs. This is especially useful for building “headless” WordPress sites—websites where the frontend is decoupled from the backend—letting developers create more dynamic, scalable, and customizable applications.
The Canonical Plugin Concept
The idea of “canonical plugins” was introduced to WordPress users in 2009 as a way to provide highly reliable, community-developed plugins that meet the highest standards of code quality, security, and compatibility with WordPress’s core. These plugins are maintained by a team of developers and designed to serve the most common needs within WordPress with exceptional quality.
Canonical plugins are deeply integrated with WordPress core. They undergo rigorous testing to ensure compatibility with each WordPress release, giving users confidence in the security and reliability of their features. In the WordPress admin section, canonical plugins are highlighted as recommended plugins, adding a layer of trust for users who seek community-backed solutions.
Jason Bahl’s Journey with WPGraphQL
Jason Bahl launched WPGraphQL in 2016 and spent years enhancing its capabilities, working with teams at Gatsby and later WP Engine, where he published over 100 releases and implemented major updates such as WPGraphQL Smart Cache. At WP Engine, however, Bahl saw his time on WPGraphQL limited as the company’s priorities shifted. This prompted him to consider other opportunities to better serve the open-source community.
Reflecting on this, Bahl noted that WP Engine’s focus on internal projects sometimes limited resources for WPGraphQL and other community-driven work. He expressed hope that organizations relying on open-source projects like WPGraphQL might better integrate open-source contributions into their long-term strategies.
A New Chapter with Automattic
Bahl’s move to Automattic signals a major step for WPGraphQL and open-source GraphQL functionality within WordPress. While Bahl doesn’t fully agree with every decision made by WordPress founder Matt Mullenweg, he recognizes Mullenweg’s long-standing dedication to open-source initiatives and views Automattic as an ideal home for WPGraphQL.
“Automattic has an incredible history of supporting open-source projects,” Bahl said, “and I believe it’s the perfect home for WPGraphQL. This move will ensure WPGraphQL remains free and open-source while encouraging more community contributions.”
Community Reactions and Future Implications
The WordPress community has reacted with enthusiasm, seeing Automattic’s support as a positive development for WPGraphQL’s continued growth. With Automattic’s backing, WPGraphQL is positioned to receive increased visibility, more robust support, and stronger integration with WordPress core. For developers invested in building modern, decoupled WordPress experiences, WPGraphQL’s canonical plugin status brings an assurance of long-term sustainability and alignment with the WordPress ecosystem.
Bahl has reassured the community that WPGraphQL will remain free and open-source, reinforcing Automattic’s commitment to open-source principles and empowering developers to innovate within WordPress’s flexible framework.
WPGraphQL to Become Canonical WordPress Plugin with Automattic’s Backing
