manifest / integrations / wp-graphql-block-editor
WPGraphQL Block Editor
EXPERIMENTAL plugin extending WPGraphQL to support querying (Gutenberg) Blocks as data, using Server Side Block registries to map Blocks to the GraphQL Schema.
by Jason Bahl, WPGraphQL · github.com/wp-graphql/wp-graphql-block-editor · website
★ 34stars
5forks
Install
No release zip yet. The repository archive installs, but the folder name will carry the branch suffix and updates will not flow:
wp plugin install https://github.com/wp-graphql/wp-graphql-block-editor/archive/refs/heads/master.zipDeclares an update source (https://github.com/wp-graphql/wp-graphql-block-editor), so updates arrive through the plugin's own updater.
From the readme
WPGraphQL Block Editor
This is an experimental plugin to work toward compatiblity between the WordPress Gutenberg Block
Editor and WPGraphQL, based on Server Side registration of Gutenberg Blocks.
This stems from this blog post: https://www.wpgraphql.com/2021/03/09/gutenberg-and-decoupled-applications/
And this Github issue: https://github.com/wp-graphql/wp-graphql/issues/1764
BETA NOTICE
This plugin is an experimental beta plugin. It is not officially supported at the moment and will have breaking changes as it progresses. Use at your own risk.
Problems
Server Awareness
Gutenberg is a JavaScript application where Blocks are registered in JavaScript and the WordPress
server doesn't know what a block is, what attributes a block can have, etc.
Without server awareness of Gutenberg blocks, APIs such as WP-CLI, the WP REST API and WPGraphQL can't
expose blocks in a scalable way for decoupled clients to interact with.
Query Blocks as Data
Developers that are working with WordPress in a decoupled context, with WPGraphQL specifically, have
expressed a desire to want to query Gutenberg Blocks as data, then use the data in Component-based
architectures with Next, Vue, React Nati