clean up docs

apps/docs/pages/_meta.json

@@ -11,7 +11,7 @@
   "systems": "Systems",
   "environments": "Environments",
   "targets": "Targets",
-  "workflows": "Workflow (CI)",
+  "jobs": "Jobs",
   "variables": "Variables",
   "runbooks": "Runbooks",
   "advanced": "Advanced",
@@ -22,5 +22,6 @@
     "title": "Integrations"
   },
   "github": "GitHub",
-  "google-cloud": "Google Cloud"
+  "google-cloud": "Google Cloud",
+  "kubernetes": "Kubernetes"
 }

apps/docs/pages/deployments.mdx

@@ -40,6 +40,14 @@ The typical deployment process in Ctrlplane involves the following steps:
   deployment, providing you with visibility into the progress and success of
   your releases.
 
+import { Callout } from "nextra/components";
+
+<Callout type="info">
+  Its common to have multiple targets a single application may deploy too. It is
+  best practice to have a single deployment with a pipeline that supports
+  deploying to these different systems.
+</Callout>
+
 ## Benefits of Deployments in Ctrlplane
 
 - **Automation:** Automates the entire deployment process, reducing manual

apps/docs/pages/examples/deploy-to-gke.mdx

@@ -0,0 +1 @@
+# Provisiong and deploying to GKE

apps/docs/pages/github/actions-dispatcher.mdx

@@ -4,3 +4,39 @@ GitHub Actions Dispatcher is allows you to trigger other GitHub Actions
 workflows from a single workflow. This is useful when you want to run multiple
 workflows in parallel or when you want to trigger a workflow from another
 repository.
+
+## Creating Actions
+
+<Callout type="info">
+  Due to [limitations of the GitHub
+  API](https://github.com/orgs/community/discussions/9752), workflows do not
+  return the run ID. Inorder for Ctrl Plane to get the ID it generates a random
+  one that is passed into the pipeline and is expected to be added to the Run
+  name. This can be done by adding
+
+```yaml
+name: Receiving Workflow
+run-name: Receiving Workflow [${{ inputs.distinct_id && inputs.distinct_id || 'N/A' }}]
+
+on:
+  workflow_dispatch:
+    inputs:
+      distinct_id:
+        description: "Distinct ID"
+        required: false
+```
+
+</Callout>
+
+### Configuring a workflows
+
+Each provider will make there own assmputions about how values and properties
+are expected to be passed to the underlying workflow. In this section we will
+outline the format inwhich data will be passed in.
+
+First, the workflow must be able to be triggered by a dispatch.
+
+```yaml
+on:
+  workflow_dispatch: {}
+```

apps/docs/pages/google-cloud/compute-scanner.mdx

@@ -3,10 +3,28 @@
 The Compute Scanner is a tool that scans Google Cloud projects for new instances
 and creates them for related deployments automatically.
 
-Ctrlplane offers a managed and unmanaged version of the Compute Scanner.
+Currently the compute scanner supports importing the following resources:
+
+- Google Kubernetes Engine Clusters (GKE)
 
 ## Managed Compute Scanner
 
-The managed Compute Scanner is a service that is hosted
-and managed by Ctrlplane. When adding a target provider you
-will se an option to enable the managed Compute Scanner.
+The managed Compute Scanner is build into the Ctrlplane solution. Each workspace
+will is assigned a google service account. You need to invite this service
+account to your projects you would like it to scan. Then in the UI, you can add
+a new provider, select the managed install and add all the projects you will
+like it to scale. Once you hit submit you may need to wait a few mins while it
+scanns and imports all compute resources.
+
+## Unmanaged Compute Scanner
+
+The unmanaged Compute Scanner is a standalone tool that can be run in your
+infrastrcuture. Similar to the managed solution, it imports all compute
+resources from your projects. The unmanaged scanner is a docker container that
+can be run in your infrastructure. You will need to provide the service account
+credentials to the container.
+
+You may want to use the unmanaged solution when you want fine control over the scanner.
+
+| Environment Variable | Description | Required | Default |
+| :------------------- | :---------- | -------- | ------- |

apps/docs/pages/kubernetes/jobs-agent.mdx

@@ -0,0 +1,13 @@
+# Jobs Agent
+
+The Kubernetes Job Agent seamlessly integrates with your Kubernetes clusters,
+enabling you to trigger Kubernetes Jobs directly from within Ctrlplane. It
+responds to events like new software releases, new target discoveries, or
+updates to existing targets. This powerful integration allows you to leverage
+Ctrlplane's flexible management capabilities while harnessing the robust job
+execution capabilities of Kubernetes.
+
+- **Job Creation:** Dynamically creates Kubernetes Jobs based on predefined
+  templates or specifications.
+- **Handlebars for Templating:** Utilizes Handlebars templating to dynamically
+  generate Kubernetes Job manifests.

apps/docs/pages/targets/_meta.json

@@ -1,5 +1,4 @@
 {
-  "introduction": "Introduction",
   "labels": "Labels",
   "target-providers": "Target Providers",
   "schemas": "Schemas"

apps/docs/pages/targets/schemas/_meta.json

@@ -1 +1,3 @@
-{}
+{
+  "kubernetes": "kubernetes/v1"
+}

apps/docs/pages/targets/schemas/kubernetes.mdx

@@ -1,7 +1,41 @@
-# Kubernetes
+# `kubernetes/v1`
 
-## `kubernetes/v1` Schemas
+## ClusterAPI
 
-### KubernetesAPI
+```yaml
+version: kubernetes/v1
+kind: ClusterAPI
+config:
+  name: string
+  server:
+    certificateAuthorityData: string
+    endpoint: url
+labels:
+  kubernetes/version: string
+  kubernetes/distribution: string
+  kubernetes/master-version: string
+  kubernetes/master-version-major: string
+  kubernetes/master-version-minor: string
+  kubernetes/master-version-patch: string
+```
 
-### KubernetesNmamespace
+## Namespace
+
+```yaml
+version: kubernetes/v1
+kind: Namespace
+config:
+  name: string
+  namespace: string
+  server:
+    certificateAuthorityData: string
+    endpoint: url
+labels:
+  kubernetes/namespace: string
+  kubernetes/version: string
+  kubernetes/distribution: string
+  kubernetes/master-version: string
+  kubernetes/master-version-major: string
+  kubernetes/master-version-minor: string
+  kubernetes/master-version-patch: string
+```

packages/validators/src/targets/kubernetes-v1.ts

@@ -7,6 +7,7 @@ const clusterConfig = z.object({
     endpoint: z.string().url(),
   }),
 });
+
 export const kubernetesClusterApiV1 = z.object({
   version: z.literal("kubernetes/v1"),
   kind: z.literal("ClusterAPI"),