Update/documentation/extending last looks

docs/extending/data-source.md

@@ -53,13 +53,29 @@ $zipcode_query = HttpQuery::from_array( [
 ])
 ```
 
-In this case the `data_source` has a built in `get_endpoint()` method. You could also retrieve the endpoint this way:
+In this case the `data_source` has a built in `get_endpoint()` method. Other configuration options can be retireved directly. If you had a Data Source config like:
+
+```php
+$comp_data_source = HttpDataSource::from_array( [
+    'service_config' => [
+        '__version' => 1,
+        'display_name' => 'More Complicated Example API',
+        'endpoint' => 'https://api.complexexample.com/',
+		'some_identifier' => 'table-2',
+        'request_headers' => [
+            'Content-Type' => 'application/json',
+            'X-Api-Key' => MY_API_KEY_CONSTANT,
+        ],
+    ],
+] );
+```
+You could retrieve `some_identifier` directly:
 
 ```php
 $zipcode_query = HttpQuery::from_array( [
-    'data_source' => $zipcode_data_source,
-    'endpoint' => function ( array $input_variables ) use ( $zipcode_data_source ): string {
-        return  $zipcode_data_source->to_array()['service_config']['endpoint'] . $input_variables['zip_code'];
+    'data_source' => $comp_data_source,
+    'endpoint' => function ( array $input_variables ) use ( $comp_data_source ): string {
+        return  return $comp_data_source->get_endpoint() . $zipcode_data_source->to_array()['service_config']['some_identifier'] . "/" . $input_variables['search'];
     },
 ])
 ```

docs/extending/overrides.md

@@ -1,8 +1,10 @@
 # Overrides
 
-Overrides provide a way to customize the behavior of remote data blocks on a per-block basis. You can use them to modify the underlying query input variables, adjust the query response, or change the caching behavior. Overrides are defined when you register a remote data block and can be enabled or disabled via the block settings in the editor.
+Overrides provide a way to customize the behavior of remote data blocks on a per-block basis. You can use them to modify the underlying query input variables, adjust the query response, or change the caching behavior. Overrides are defined when you register a remote data block and can be enabled or disabled via the block settings in the WordPress editor. 
 
-The actual implementation of overrides is left to you. Here is an example of an override that modifies the query input variables based on a query variable (supplied by a rewrite rule):
+If you have multiple instnaces of the same remote data block in a piece of content, each instance can have a different number of overrides enabled. The default behavior is no overrides.
+
+The actual implementation of overrides is left to you. Here is an example of an override that modifies the query input variables based on a URL query string variable. You would use this to build a one "single product page" in the WordPress admin that would be able to display any product, based on the product id. The example takes advantage of the [`add_rewrite_rule`](https://developer.wordpress.org/reference/functions/add_rewrite_rule/) method and [`query_vars`](https://developer.wordpress.org/reference/hooks/query_vars/) filter that are built into WordPress.
 
 ```php
 register_remote_data_block( [
@@ -39,6 +41,8 @@ add_filter( 'remote_data_blocks_query_input_variables', function ( array $input_
 }, 10, 2 );
 ```
 
+As you can see the `remote_data_blocks_query_input_variables` filter is passed a list of enabled overrides. You need to add logic to identify which filters are enabled and act accordingly.
+
 The `overrides` property in the block registration array enables a panel in the block settings that allows content authors to enable or disable the override:
 
 <img width="276" alt="An overrides panel in a remote data block settings panel" src="https://github.com/user-attachments/assets/e701e621-99f9-4c2e-b34d-cfef352af2ae" />

docs/extending/query-runner.md

@@ -4,7 +4,7 @@ A query runner executes a query and processes the results of a query. The defaul
 
 - Your API does not respond with JSON or requires custom deserialization logic.
 - Your API uses a non-HTTP transport.
-- You want to implement custom processing of the response data, which is not possible with the provided filters.
+- You want to implement custom processing of the response data, which is not possible with the [provided filters](./hooks.md).
 
 ## Custom QueryRunner for HTTP queries
 

docs/quickstart.md

@@ -1,6 +1,8 @@
 # Quickstart
 
-The most basic way to see Remote Data Blocks in action is to launch the plugin in WordPress Playground. You can do this by clicking the "Launch in WordPress Playground" badge in the [README](../README.md).
+The most basic way to see Remote Data Blocks in action is to launch the plugin in WordPress Playground. 
+
+[![Launch in WordPress Playground](https://img.shields.io/badge/Launch%20in%20WordPress%20Playground-DA9A45?style=for-the-badge&logo=wordpress)](https://playground.wordpress.net/?blueprint-url=https://raw.githubusercontent.com/Automattic/remote-data-blocks/trunk/blueprint.json)
 
 However, the more advanced use case is providing your own custom configuration through code. This guide will walk you through the steps to do this.