feat: Add documentation and screenshots for HTTP checks and load test…

…s - including multiple client locations feature

extensions/com.steadybit.extension_gatling/previews.yml

@@ -0,0 +1,10 @@
+---
+- type: image
+  src: design.png
+  alt: Steadybit's Gatling action to run a Gatling load test in the experiment
+- type: image
+  src: run.png
+  alt: The experiment run view with the Gatling load test results.
+- type: image
+  src: design-locations.png
+  alt: Optionally, the Gatling action supports the selection of the Gatling execution location in the experiment's design.

extensions/com.steadybit.extension_gatling/summary.mdx

@@ -1,3 +1,9 @@
 # Introduction
 
 The Gatling extension allows to integrate Gatling Load Tests into Steadybit Experiments.
+
+## Support Multiple Gatling Executions Locations
+Optionally, you can activate the extension's support for multiple Gatling execution locations.
+Once you have activated it, you can configure available Gatling execution locations for a team via environments and ensure you're always running the Gatling load test from the right internal location.
+Multiple Gatling execution locations are especially helpful when you have different load test hardware to support different scales of load test executions.
+See [extension-gatling's readme](https://github.com/steadybit/extension-gatling) for further information and migration guidelines.

extensions/com.steadybit.extension_http/previews.yml

@@ -0,0 +1,13 @@
+---
+- type: image
+  src: design.png
+  alt: Steadybit's HTTP Check to validate an HTTP-based endpoint and check for response time, content etc.
+- type: image
+  src: run.png
+  alt: The experiment run view with the HTTP check widget to validate endpoint's behavior.
+- type: image
+  src: explore-client-locations.png
+  alt: Optionally, the HTTP check discovers multiple client execution locations to ease testing of cluster-internal URLs.
+- type: image
+  src: design-client-locations.png
+  alt: Optionally, the HTTP check supports the selection of the client execution location in the experiment's design.

extensions/com.steadybit.extension_http/summary.mdx

@@ -1,3 +1,12 @@
 # Introduction
 
-With this extension you are able to check your http endpoints for availability and response time. You can also check the response body for specific strings.
+With this extension, you can check your HTTP endpoints for availability and response time.
+You can also check the response body for specific strings or validate the response time.
+
+You need to deploy the extension in your system, which allows users to easily validate non-public URLs.
+For instance, you can check Kubernetes internal URLs or validate URLs requiring a VPN connection otherwise.
+
+## Support Multiple Client Locations
+Optionally, you can activate the extension's support for multiple client locations.
+Once you have activated it, you can configure available client locations for a team via environments and ensure you're always running the HTTP check from the right internal location to verify non-public URLs.
+See [extension-http's readme](https://github.com/steadybit/extension-http) for further information and migration guidelines.

extensions/com.steadybit.extension_jmeter/previews.yml

@@ -0,0 +1,10 @@
+---
+- type: image
+  src: design.png
+  alt: Steadybit's JMeter action to run a JMeter load test in the experiment
+- type: image
+  src: run.png
+  alt: The experiment run view with the JMeter load test results.
+- type: image
+  src: design-locations.png
+  alt: Optionally, the JMeter action supports the selection of the JMeter execution location in the experiment's design.

extensions/com.steadybit.extension_jmeter/summary.mdx

@@ -1,3 +1,9 @@
 # Introduction
 
 The JMeter extension allows to integrate JMeter Load Tests into Steadybit Experiments.
+
+## Support Multiple JMeter Executions Locations
+Optionally, you can activate the extension's support for multiple JMeter execution locations.
+Once you have activated it, you can configure available JMeter execution locations for a team via environments and ensure you're always running the JMeter load test from the right internal location.
+Multiple JMeter execution locations are especially helpful when you have different load test hardware to support different scales of load test executions.
+See [extension-jmeter's readme](https://github.com/steadybit/extension-jmeter) for further information and migration guidelines.

extensions/com.steadybit.extension_k6/previews.yml

@@ -0,0 +1,10 @@
+---
+- type: image
+  src: design.png
+  alt: Steadybit's k6 action to run a k6 load test in the experiment
+- type: image
+  src: run.png
+  alt: The experiment run view with the k6 load test results.
+- type: image
+  src: design-locations.png
+  alt: Optionally, the k6 action supports the selection of the k6 execution location in the experiment's design.

extensions/com.steadybit.extension_k6/summary.mdx

@@ -1,3 +1,9 @@
 # Introduction
 
 The K6 extension allows to integrate K6 Load Tests into Steadybit Experiments. Local Test or Test using K6 Cloud are supported.
+
+## Support Multiple k6 Executions Locations
+Optionally, you can activate the extension's support for multiple k6 execution locations.
+Once you have activated it, you can configure available k6 execution locations for a team via environments and ensure you're always running the k6 load test from the right internal location.
+Multiple k6 execution locations are especially helpful when you have different load test hardware to support different scales of load test executions.
+See [extension-k6's readme](https://github.com/steadybit/extension-k6) for further information and migration guidelines.