docs: add explanation about GET Vs POST queries

docs/explanation/get-vs-post.md

@@ -0,0 +1,44 @@
+# GET vs POST in WPGraphQL
+
+When interacting with WPGraphQL, selecting the correct HTTP method to fetch data is crucial. This guide explains the differences between using a GET request with a query parameter versus a POST request to the /graphql endpoint.
+
+## Context
+
+WPGraphQL is a GraphQL API for WordPress, enabling flexible and efficient data queries. Unlike traditional REST APIs that require multiple endpoints, GraphQL allows querying specific data through a single endpoint.
+
+# Details
+
+WPGraphQL supports querying data using the `/graphql` endpoint in two primary ways:
+
+* **GET Request with Query Parameter**: You can query WPGraphQL by appending your GraphQL query as a query parameter to the `/graphql` endpoint. This method is useful for simple queries or testing purposes.
+
+```bash
+curl 'http://myexample.local/graphql?query={generalSettings{url}}'
+```
+**Note**: GET requests have inherent URL length limitations (typically 2,000-8,000 characters depending on the browser and server). Complex GraphQL queries can easily exceed these limits, making this method impractical for anything beyond basic queries.
+
+Each property is provided as an HTTP query parameter, with values separated by an ampersand (&).
+
+GraphQL requests with variables don't work in GET requests because they need to be parsed as JSON.
+
+Only query operations can be executed; mutation operations don't work with GET requests.
+
+GET requests can be particularly beneficial when used with caching mechanisms like the [Smart Cache plugin](https://wordpress.org/plugins/wpgraphql-smart-cache/). Since GET queries are part of the URL, they can be easily cached, reducing server load and improving response times for frequently requested data. This makes them a good choice for read-only queries where performance and efficiency are priorities.
+
+* **POST Request**: This is the standard method for querying WPGraphQL. You send a POST request to the `/graphql` endpoint with your GraphQL query in the request body. It supports complex queries and is more secure.
+
+```bash
+curl -X POST \
+  http://myexample.local/graphql \
+  -H 'Content-Type: application/json' \
+  -d '{"query": "{ generalSettings { url } }"}'
+```
+
+# Comparison
+| Method                   | Security                                 | Complexity      | Support    | Use Case               |
+|--------------------------|------------------------------------------|-----------------|------------|------------------------|
+| POST                     | More secure, hides query in request body | Complex queries | Production | complex data retrieval  |
+| GET with Query Parameter | Less secure due to query exposure in URL | Simple queries (no mutations)  | Testing    | simple data retrieval |
+
+# Summary
+While both methods have their uses, POST requests are generally recommended for WPGraphQL due to their flexibility, security advantages, and ability to handle complex queries. However, GET requests can be useful for simple, cacheable queries and is useful when paired with caching mechanisms like the Smart Cache plugin. Consider your specific use case, security requirements, and caching needs when choosing between the two methods.

docs/explanation/what-url-should-use-to-fetch-data.md

@@ -0,0 +1,43 @@
+# What URL should I use to fetch data from WPGraphQL? (/graphql with query parameter vs /graphql with POST request)
+
+When interacting with WPGraphQL, choosing the correct URL and method to fetch data is crucial. This explanation clarifies the difference between using a GET request with a query parameter and a POST request to the `/graphql` endpoint.
+
+## Context
+
+WPGraphQL is a GraphQL API for WordPress, allowing you to query data in a flexible and efficient manner. GraphQL itself is a query language for APIs that provides a unified endpoint for data retrieval. Historically, APIs have used REST endpoints, which require multiple requests to gather related data. GraphQL, on the other hand, allows you to fetch specific data with a single query. WPGraphQL integrates this capability into WordPress.
+
+# Details
+
+WPGraphQL supports querying data using the `/graphql` endpoint in two primary ways:
+
+* **GET Request with Query Parameter**: You can query WPGraphQL by appending your GraphQL query as a query parameter to the `/graphql` endpoint. This method is useful for simple queries or testing purposes.
+
+```bash
+curl 'http://myexample.local/graphql?query={generalSettings{url}}'
+```
+**Note**: GET requests have inherent URL length limitations (typically 2,000-8,000 characters depending on the browser and server). Complex GraphQL queries can easily exceed these limits, making this method impractical for anything beyond basic queries.
+
+Each property is provided as an HTTP query parameter, with values separated by an ampersand (&).
+
+GraphQL requests with variables don't work in GET requests because they need to be parsed as JSON.
+
+Only query operations can be executed; mutation operations don't work with GET requests.
+
+* **POST Request**: This is the standard method for querying WPGraphQL. You send a POST request to the `/graphql` endpoint with your GraphQL query in the request body. It supports complex queries and is more secure.
+
+```bash
+curl -X POST \
+  http://myexample.local/graphql \
+  -H 'Content-Type: application/json' \
+  -d '{"query": "{ generalSettings { url } }"}'
+```
+
+# Comparison
+| Method                   | Security                                 | Complexity      | Support    | Use Case               |
+|--------------------------|------------------------------------------|-----------------|------------|------------------------|
+| POST                     | More secure, hides query in request body | Complex queries | Production | complex data retrieval  |
+| GET with Query Parameter | Less secure due to query exposure in URL | Simple queries (no mutations)  | Testing    | simple data retrieval |
+
+# Summary
+While both methods have their uses, POST requests are generally recommended for WPGraphQL due to their flexibility, security advantages, and ability to handle complex queries. However, GET requests can be useful for simple, cacheable queries or quick testing. Consider your specific use case, security requirements, and caching needs when choosing between the two methods.
+