Extends WPGraphQL schema with multilingual data from Polylang for headless WordPress sites.
WPGraphQL Polylang is a WordPress plugin that extends the WPGraphQL schema to include multilingual data from the Polylang plugin. It enables developers to query and manage translated content, languages, and translations through GraphQL in headless WordPress architectures. The plugin solves the problem of accessing structured multilingual content via GraphQL APIs for modern frontend applications.
WordPress developers building headless or decoupled websites using WPGraphQL who need to serve multilingual content. It's particularly useful for teams using Polylang for translation management and requiring GraphQL API access to that data.
Developers choose this plugin because it provides a clean, type-safe GraphQL interface for Polylang's multilingual features without custom REST endpoints. It integrates directly with WPGraphQL's schema, offers comprehensive language filtering and mutation support, and works with both free and Pro versions of Polylang.
WPGraphQL Polylang Extension for WordPress
Open-Awesome is built by the community, for the community. Submit a project, suggest an awesome list, or help improve the catalog on GitHub.
Adds language and translations fields to posts, pages, and custom post types, enabling full multilingual querying directly in GraphQL, as shown in the example query in the README.
Follows WPGraphQL's schema extension pattern for predictable, type-safe queries, respecting both Polylang's data structure and GraphQL's type system, as per the project philosophy.
Supports multilingual Advanced Custom Fields options pages with additional plugins, allowing site-wide settings per language, though it requires ACF Pro and specific setup steps detailed in the README.
Provides language filtering in queries and setting language during create and update mutations, offering complete control over content, as evidenced by the where arguments and mutation support features.
Requires WPGraphQL, Polylang, and for ACF features, additional plugins including the paid Advanced Custom Fields Pro, increasing setup overhead and potential points of failure.
The README directs users to GraphiQL for details, which may not provide comprehensive guidance for complex use cases, leaving developers to rely on auto-generated schema introspection.
Only works with Polylang, so projects using other multilingual plugins need separate solutions, as admitted in the README with the mention of WPML alternatives.
Requires specific versions of WPGraphQL (0.13.x or later) and Polylang (2.6.5 or later), which could lead to compatibility issues with other plugins or WordPress core updates.