graphql-api-for-wp VS faustjs

GraphQL API for WordPress

There's another GraphQL plugin you can check, maybe it will work better: https://graphql-api.com/

Alongside, I did a demo of the GraphQL API for WordPress plugin. It's all me showing how to use the plugin in the wp-admin, for some 30 min.

For plugin GraphQL API for WordPress I have chosen the latter approach, attempting to create a GraphQL schema that, even though it is based on WordPress and works for WordPress, it is not tied to WordPress (for instance, by removing inconsistent names and relationships).

I just finished coding this same website, graphql-api.com, and launched it 2 weeks ago (yay! 🥳 Btw, how do you like it? Be welcome to give me feedback, via DM or email)

This is a channel to share news concerning the development of the GraphQL API for WordPress with the community, sent the first week of each month.

Yep, this is all good, and then there's also headless WordPress, as to have WP in the back-end to manage the data, but use React to build the client-side, having the 2 communicate via the WP REST API (in core), or [WPGraphQL] or the GraphQL API for WordPress (plugins that must be installed).

GraphQL + Persisted queries via the GraphQL API for WordPress plugin

You can try out the GraphQL API for WordPress: https://graphql-api.com

Yesterday I presented plugin GraphQL API for WordPress in WordCamp India, with a 30-min demo that covers:

Yeah, in hindsight, we would have used Next/Vercel. So we're tactically moving over to that. There are many new frameworks, like Astro, that are really exciting, but it seems like Next is the best choice if you have a data-heavy app that has a dynamic mix of SSR and static pages. For Wordpress in particular, I'd recommend that you check out Faust.js. It's build with Next and I'm amazed by how well it works with Wordpress without much effort: https://faustjs.org/

https://faustjs.org is a great headless Wordpress solution for Nextjs. I've tried several CMS solutions and ultimately WordPress is invariably the friendliest option from a client perspective.

I'm working through a large project where we're leveraging WordPress and Next.js. Check out Faust.js (https://faustjs.org/) which works as a layer to handle a lot of the query/template/routing stuff that maybe isn't super-intuitive when trying to hook WordPress up headlessly...

- FaustJS (built for headless WP on NextJS w/ full site editing capabilities)

Faust.js is the front-end JavaScript framework built on top of Next.js, created to make developing headless WordPress sites easier. The idea of this new version is to make a parity between the WordPress world that a developer might be used to but replicate it as much as possible in the JavaScript front-end world.

This is where it started. Then there is also Faustjs started by WPEngine. https://faustjs.org/

https://faustjs.org/ built specifically for headless WP