wp-graphql VS WordPress Packagist

Are you dead set on building a Nuxt + Vue application? Partial to NextJS like I am? Well good news everyone, WordPress has done a pretty decent job over the past couple of years building out the WordPress API and enabling developers to leverage WordPress as a Headless CMS. Pair that with the amazing WPGraphQL Pluginand you’re cooking with JavaScript. You get all the benefits of really solid backend CMS that end users are familiar with, and can grasp with a 1 hour CMS training, distributed using your favorite flavor of JavaScript.

It's very easy to use when you use https://www.wpgraphql.com/ Here's an example of a repeatable component I set up using the repeater filled. It might help you.

I am using Headless Wordpress with https://www.wpgraphql.com/ for API hosted on SiteGround and Nextjs for frontend.

I think you might be looking for WPGraphQL

- WPGraphQL

Look at other popular plugins to see what they do, and how that's different from what you did. For example browse a bit through https://github.com/wp-graphql/wp-graphql

As you can see I'm getting all the posts from my Wordpress GraphQL endpoint and receiving the title, excerpt, slug and date fields, there's more I can get if I follow the GraphQL API for Wordpress documentation, but that's all I need for the demo.

How does this compare to WPGraphQL https://www.wpgraphql.com that's been around for quite some time (https://github.com/wp-graphql/wp-graphql)

Did you find shortcomings with that plugin?

You can use wordpress as a backend and then hook up your frontend through a graphql api plugin.

You want to use WP as a headless CMS. Look at https://www.wpgraphql.com

If I have to use WordPress for something, I'll build it as a standard PHP project, requiring WordPress and any themes/plugins as a Composer dependencies from johnpbloch/wordpress and WordPress Packagist (more info here). If I need to do any significant templating, I like to use Timber.

Use it together with https://wpackagist.org/ and you can update all plugins/themes by latest or by version number.

Another option you can look at is Bedrock by Roots - that is sets WP as an app with composer already set up. It allows you to install WP plugins (from official WP repo) via composer (WP Packagist). The structure is set up to allow for git workflow. Also helpful if you want to make use of a bunch of composer packages on your site.

https://wpackagist.org/ in the example you see "repositories", now in that array you can put your plugins github-link and set the other settings. with composer install you install them and with composer update you update them

Side question: I know that the WordPress ecosystem has been moving toward better support for Composer – e.g., with WPackagist. But wouldn't plugins installed/updated via Composer run into the same issue?