A deprecated example Gatsby blog site sourcing content from WordPress via the WPGraphQL API.
Gatsby WPGraphQL Blog Example is a demonstration project that shows how to build a static blog using Gatsby and source all content from a WordPress site via the WPGraphQL GraphQL API. It solves the problem of creating fast, static websites while leveraging WordPress's robust content management interface. The project illustrates a decoupled architecture where content is authored in WordPress and consumed by Gatsby at build time.
Developers and teams looking to understand how to integrate WordPress as a headless CMS with Gatsby using GraphQL. It's particularly useful for those exploring static site generation with existing WordPress content.
It provides a concrete, working example of a modern Jamstack setup with WordPress and Gatsby, demonstrating real-world data sourcing patterns like menus, pagination, and taxonomies. Developers choose this to learn best practices for building performant static sites powered by WordPress content.
Demo showing how to use WPGraphQL as the source for Gatsby Sites
Open-Awesome is built by the community, for the community. Submit a project, suggest an awesome list, or help improve the catalog on GitHub.
Demonstrates full data sourcing from WordPress including menus, pages, authors, and taxonomies via WPGraphQL, as listed in the features with checkmarks for each component.
Based on a WordCamp talk with setup videos, providing practical insights into decoupled architectures and GraphQL data fetching patterns.
Includes live WordPress and Gatsby sites, allowing developers to inspect the end result and data flow in a real-world context.
The README explicitly marks it as deprecated and recommends against use, citing that Gatsby Source GraphQL is no longer ideal and suggesting Gatsby Source WordPress Experimental instead.
Relies on Gatsby Source GraphQL, which has known limitations compared to the newer experimental plugin, potentially leading to setup issues and lack of updates.
Focuses on a basic blog example, so it may not address advanced scenarios like dynamic content updates or performance optimizations for larger sites.