docs: Add YouTube Videos

docs/articles/argocd-integration.md

@@ -5,7 +5,8 @@ of both Testkube, ArgoCD and GitOps principles.
 
 :::tip
 For a high-level introduction to using Testkube with ArgoCD including a step-by-step tutorial, please check out
-our [GitOps blogpost](https://testkube.io/blog/a-gitops-powered-kubernetes-testing-machine-with-argocd-and-testkube).
+our [GitOps blogpost](https://testkube.io/blog/a-gitops-powered-kubernetes-testing-machine-with-argocd-and-testkube) and watch our YouTube video:
+ <center><iframe width="350" height="200" src="https://www.youtube.com/embed/jvWPMUpOePE" title="GitOps-Powered Testing with Testkube and ArgoCD" frameborder="0" allow="accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture; web-share" referrerpolicy="strict-origin-when-cross-origin" allowfullscreen></iframe></center>
 :::
 
 ## Managing Testkube CRDs with ArgoCD

docs/articles/defining-tests.md

@@ -13,7 +13,7 @@ Defining test executions is most commonly done by DevOps/Build engineers, based
 
 ## Defining Test Execution in Testkube
 
-Testkube uses [Test Workflows](../articles/test-workflows.md) as a generic abstraction for defining how your tests are executed. Test Workflows uses a declarative YAML vocabulary specifically designed for executing tests, with built-in functionality for: 
+Testkube uses [Test Workflows](../articles/test-workflows.mdx) as a generic abstraction for defining how your tests are executed. Test Workflows uses a declarative YAML vocabulary specifically designed for executing tests, with built-in functionality for: 
 
 - Retrieving tests from Git repositories, inline files and external volumes.
 - Executing any test or testing tool available as a Docker image.

docs/articles/examples/gatling-basic.md

@@ -28,3 +28,7 @@ The uploaded report is available in the Artifacts tab:
 
 </TabItem>
 </Tabs>
+
+See how to effortlessly perform load testing in Kubernetes using Gatling and Testkube from the Testkube UI here:
+
+<center><iframe width="500" height="300" src="https://youtube.com/embed/mgnwhg9KZ2I" title="Create & Run Gatling Tests with Testkube" frameborder="0" allow="accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture; web-share" referrerpolicy="strict-origin-when-cross-origin" allowfullscreen></iframe></center>

docs/articles/examples/postman-basic.md

@@ -19,3 +19,8 @@ After execution, you can see the log output from the test executions under the e
 Below is an example workflow for executing the Postman collection using an official Testkube Template.
 
 <SimplePostmanFromTemplate/>
+
+ :::note
+Please visit YouTube to watch our video on how to Simplify API Testing in Kubernetes with Postman and Testkube:
+<center><iframe width="500" height="300" src="https://www.youtube.com/embed/7HAwEtFDwvU" title="Simplify API Testing in Kubernetes with Postman and Testkube" frameborder="0" allow="accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture; web-share" referrerpolicy="strict-origin-when-cross-origin" allowfullscreen></iframe></center>
+:::

docs/articles/test-workflows-test-suites.md

@@ -10,7 +10,11 @@ import RequiresCommercialWorkflows from "./_commercial-workflows-note.mdx"
 With Test Workflows it is possible to run downstream Test Workflows and Tests with `execute` operation,
 similarly to what you can do in Test Suites.
 
-## Advantages over original Test Suite
+Watch Test Workflows in action to create comprehensive system tests:
+
+<center><iframe width="400" height="200" src="https://youtube.com/embed/kvcq-J_ZhVA" title="Creating System Test Workflows using Testkube" frameborder="0" allow="accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture; web-share" referrerpolicy="strict-origin-when-cross-origin" allowfullscreen></iframe></center>
+
+## Advantages Over Original Test Suites
 
 As it is regular Test Workflow, where a single step is dispatching downstream Test Workflows and Tests,
 the execution is very flexible. You can:
@@ -98,7 +102,7 @@ To run Tests as part of the `execute` step, you have to add its reference in the
 You need to provide `name`, along with optional `executionRequest` values for parametrization,
 that are similar to the regular Test execution request.
 
-### Controlling the concurrency level
+### Controlling the Concurrency Level
 
 You can use `parallelism` property to control how many Test Workflows and Tests will be running at once.
 
@@ -138,7 +142,7 @@ spec:
 </TabItem>
 </Tabs>
 
-## Nesting workflows
+## Nesting Workflows
 Workflows can be nested - workflow can execute workflow(s) executing other workflow(s). [**Parallelism**](#controlling-the-concurrency-level) can then be used to control the execution flow.
 
 Example:
@@ -184,11 +188,11 @@ spec:
       - name: soapui-workflow-suite
 ```
 
-## Passing input from files
+## Passing Input from Files
 
 It may happen that you will need to pass information from the file system. You can either pass the files using Test Workflow expressions (like `file("./file-content.txt")`) or using a `tarball` syntax.
 
-### Specific files
+### Specific Files
 
 You can easily use Test Workflow expressions to fetch some files and send them as a configuration variable:
 
@@ -215,7 +219,7 @@ spec:
           script: '{{ file("/data/repo/test/k6/executor-tests/k6-smoke-test-without-envs.js") }}'
 ```
 
-### Multiple files transfer
+### Multiple Files Transfer
 
 To transfer multiple files, similarly to `transfer` in [**Parallel Steps**](./test-workflows-parallel.md#copying-content-inside),
 you can use a `tarball` syntax that will pack selected files and return the URL to download them:
@@ -261,7 +265,7 @@ spec:
   - shell: tree /data/repo
 ```
 
-### Matrix and sharding
+### Matrix and Sharding
 
 The `execute` operation supports matrix and sharding, to run multiple replicas and/or distribute the load across multiple runs.
 It is supported by regular matrix/sharding properties (`matrix`, `shards`, `count` and `maxCount`) for each Test Workflow or Test reference.

docs/articles/test-workflows.md → docs/articles/test-workflows.mdx

@@ -1,9 +1,30 @@
 # Test Workflows
 
 ## Introduction
+
+import TwoColumns from '@site/src/components/TwoColumns';
+
+<TwoColumns
+  left={<>
+
+ <p></p><p></p><p></p><p></p><p></p><p></p><p></p><p></p><p></p><p></p><p></p><p></p> 
+
+<p>
 Test Workflows are an easy and extremely powerful way to define and run your tests in 
-your Kubernetes clusters. Thanks to their flexibility, Test Workflows solve many of the 
+your Kubernetes clusters. 
+</p>
+
+
+
+<p>Thanks to their flexibility, Test Workflows solve many of the 
 problems that can occur with standard Tests, including:
+</p>
+
+  </>}
+  right={<p>
+    <iframe width="350" height="170" src="https://www.youtube.com/embed/iHUTYT6L2Ns" title="Testkube 2.0: A New Era for Cloud Native Testing with Test Workflows" frameborder="0" allow="accelerometer; autoplay; clboard-write; encrypted-media; gyroscope; picture-in-picture; web-share" referrerpolicy="strict-origin-when-cross-origin" allowfullscreen></iframe>
+  </p>}
+/>
 
 - Running Tests using different testing tool versions and dependencies.
 - Defining multiple steps for the execution of the tests.
@@ -578,3 +599,4 @@ Status:
       Name:            k6-workflow
       Namespace:       testkube
 ```
+

docs/articles/triggering-tests.md

@@ -17,7 +17,7 @@ The decoupling of test definition and execution from your CI/CD is one of the mo
 - From your CI/CD workflows using one of our [CI/CD integrations](../articles/cicd-overview.mdx).
 - In response to Kubernetes events using [Triggers](../articles/test-triggers).
 - Manually via the [CLI](../articles/install/1-cli.mdx) or the [Testkube Dashboard](../articles/testkube-dashboard.md).
-- At a recurring schedule using [Test Workflow Scheduling](../articles/test-workflows.md).
+- At a recurring schedule using [Test Workflow Scheduling](../articles/test-workflows.mdx).
 - From any other tool using the [Testkube REST API](/openapi/overview).
 
 ![CI/CD Integrations](../img/concepts-cicd-integrations.png)