wp-graphql VS Guzzle

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

Guzzle is a PHP HTTP client library. It’s a simple and effective solution for sending HTTP requests and managing HTTP/1.1 and HTTP/2.0 responses. This versatile tool excels in several areas, allowing developers to build query strings quickly, send POST requests, upload JSON data, and handle other HTTP-related tasks. Moreover, Guzzle facilitates both synchronous and asynchronous request handling, providing flexibility for different scenarios.

Symfony HTTP Client or Guzzle. If new build then Symfony, but have a lot of existing implementations with Guzzle. Both have worked very well. Worst case fallback to cURL.

but if you'd rather make raw requests, guzzle is a good option (though I'd opt for the sdk): https://github.com/guzzle/guzzle

PHP has built-in cURL support, but I never use it. I like using Guzzle or Symfony's http-client.

I just ran into multiple errors regarding the pre-packaged cURL: It does not feature accepting compressed responses (which I suppose is due to absense of `libz` being compiled/linked in).

I am busy building a small application that monitors websites using guzzle. My idea is to run through the list of websites alphabetically and make a guzzle request to each and update my table with the http response codes of each site.

Like Node.js, the PHP ecosystem has quite a number of good HTTP request libraries. Guzzle is perhaps one of the most well known, but there are many other popular libraries out there. Luckily, PHP also has some interface standards around HTTP clients and messages, particularly PSR-7, PSR-17, and PSR-18,