No UPDATE in official site migrations

- Updated the JSON component description to clarify its integration with external services and the ability to serve both HTML and JSON based on the HTTP Accept header.
- Added examples demonstrating how to request JSON responses using `curl`.
- Removed the obsolete migration file that documented the JSON response format feature, consolidating information into the main documentation.

Author: lovasoa

examples/official-site/sqlpage/migrations/01_documentation.sql

@@ -893,7 +893,7 @@ Numbers can be displayed
     },
     {
         "feature": "APIs",
-        "description": "Allows building JSON REST APIs and integrating with external APIs.",
+        "description": "Allows building JSON REST APIs, integrates with external services, and can serve the same page as HTML in a browser or as JSON to tools like `curl -H \"Accept: application/json\" http://localhost:8080/users.sql`.",
         "benefits": "Enables automation and integration with other platforms, facilitates data exchange."
     },
     {

examples/official-site/sqlpage/migrations/11_json.sql

@@ -18,6 +18,10 @@ This component **must appear at the top of your SQL file**, before any other dat
 An HTTP response can have only a single datatype, and it must be declared in the headers.
 So if you have already called the `shell` component, or another traditional HTML component,
 you cannot use this component in the same file.
+
+SQLPage can also return JSON or JSON Lines when the incoming request says it prefers them with an HTTP `Accept` header, so the same `/users.sql` page can show a table in a browser but return raw data to `curl -H "Accept: application/json" http://localhost:8080/users.sql`.
+
+Use this component when you want to control the payload or force JSON output even for requests that would normally get HTML.
 ',
         'code',
         '0.9.0'
@@ -84,6 +88,12 @@ select * from users;
     {"username":"James","userid":1},
     {"username":"John","userid":2}
 ]
+```
+
+Clients can also receive JSON or JSON Lines automatically by requesting the same SQL file with an HTTP `Accept` header such as `application/json` or `application/x-ndjson` when the component is omitted, for example:
+
+```
+curl -H "Accept: application/json" http://localhost:8080/users.sql
 ```
     '
     ),