This epic is to track a new major version of gatsby-source-wordpress which is currently being worked on. This will be a ground-up rewrite using WPGraphQL instead of the REST API in order to enable better caching, previews, incremental builds, and an overall better developer experience.
How it will be done
The next major version of gatsby-source-wordpress is V4, and the release will coincide with the release of WPGraphQL V1. This project will inform some potential changes in WPGraphQL as a concrete example of a framework implementing many WordPress conventions and functionalities headlessly via WPGQL. There will also be a WPGatsby WordPress plugin that will modify the WPGQL schema when changes are Gatsby-specific, as well as add support for incremental builds and preview on the WP side.
Additionally, an opinionated theme, gatsby-theme-wordpress, will be built and it will compose a few new plugins together to implement many WordPress conventions and functionalities such as the template hierarchy, automatic routing (page creation using the WP permalink structure), ability to use the WP admin template selector, easy use of WP menus, and more.
Philosophy
We want to enable you to do what you're already doing with WordPress and more.
The intention behind the theme is to reduce friction as much as possible both for WordPress developers coming to Gatsby and for anyone else that's interested in using WP and Gatsby together for a wonderful and familiar admin experience. We want to lower the barrier of entry and make it as easy as possible for everyone to use Gatsby and React with WordPress. As a very large portion of the web is built on WordPress, our hope is that this will empower many more people to build React apps/sites and push the WordPress community and the internet as a whole forward.
The intention behind the source plugin is to create a scalable, cacheable integration with WordPress. It will support Gatsby cloud Preview and incremental builds and will generally be more efficient than current solutions and will have an improved DX.
Responsibilities
I will be leading the new source plugin and theme, and @jasonbahl
will of course be leading WPGraphQL V1. The two of us will be leading the WPGatsby plugin together.
[ ] Makes gql mutations sending available templates back to WP
[ ] Need to think about how this will work with multiple frontends (staging, production, local, etc)
[ ] gatsby-wordpress-menus
[ ] Should enable using a menu slug or location in a React component to display a menu. See github.com/TylerBarnes/wordsby/wik... for a related implementation
Not in scope now but may be implemented in the future
By the way: The future of WordPress with Gatsby is discussed here in the following issue on GitHub.
Intro
This epic is to track a new major version of
gatsby-source-wordpresswhich is currently being worked on. This will be a ground-up rewrite using WPGraphQL instead of the REST API in order to enable better caching, previews, incremental builds, and an overall better developer experience.How it will be done
The next major version of
gatsby-source-wordpressis V4, and the release will coincide with the release of WPGraphQL V1. This project will inform some potential changes in WPGraphQL as a concrete example of a framework implementing many WordPress conventions and functionalities headlessly via WPGQL. There will also be aWPGatsbyWordPress plugin that will modify the WPGQL schema when changes are Gatsby-specific, as well as add support for incremental builds and preview on the WP side.Additionally, an opinionated theme,
gatsby-theme-wordpress, will be built and it will compose a few new plugins together to implement many WordPress conventions and functionalities such as the template hierarchy, automatic routing (page creation using the WP permalink structure), ability to use the WP admin template selector, easy use of WP menus, and more.Philosophy
We want to enable you to do what you're already doing with WordPress and more.
The intention behind the theme is to reduce friction as much as possible both for WordPress developers coming to Gatsby and for anyone else that's interested in using WP and Gatsby together for a wonderful and familiar admin experience. We want to lower the barrier of entry and make it as easy as possible for everyone to use Gatsby and React with WordPress. As a very large portion of the web is built on WordPress, our hope is that this will empower many more people to build React apps/sites and push the WordPress community and the internet as a whole forward.
The intention behind the source plugin is to create a scalable, cacheable integration with WordPress. It will support Gatsby cloud Preview and incremental builds and will generally be more efficient than current solutions and will have an improved DX.
Responsibilities
I will be leading the new source plugin and theme, and @jasonbahl will of course be leading WPGraphQL V1. The two of us will be leading the
WPGatsbyplugin together.Github Project Links
Initial scope
This will likely change as things progress, but for now:
[ ]
gatsby-source-wordpress@v4[ ]
WPGatsby[ ]
gatsby-theme-wordpressgatsby-wordpress-permalink-structurepathof each page or postgatsby-wordpress-template-hierarchygatsby-wordpress-template-syncgatsby-wordpress-menusNot in scope now but may be implemented in the future
Looking forward to WPGatsby :)