diff --git a/src/assets/images/architecture/data-flow/resource-watch-pipeline.png b/src/assets/images/architecture/data-flow/resource-watch-pipeline.png new file mode 100644 index 0000000..f45f787 Binary files /dev/null and b/src/assets/images/architecture/data-flow/resource-watch-pipeline.png differ diff --git a/src/assets/images/architecture/data-flow/terminal-exec-session.png b/src/assets/images/architecture/data-flow/terminal-exec-session.png new file mode 100644 index 0000000..b74c607 Binary files /dev/null and b/src/assets/images/architecture/data-flow/terminal-exec-session.png differ diff --git a/src/assets/images/architecture/data-flow/workflow-api-flow.png b/src/assets/images/architecture/data-flow/workflow-api-flow.png new file mode 100644 index 0000000..5edad55 Binary files /dev/null and b/src/assets/images/architecture/data-flow/workflow-api-flow.png differ diff --git a/src/assets/images/architecture/data-flow/workflow-status-stream.png b/src/assets/images/architecture/data-flow/workflow-status-stream.png new file mode 100644 index 0000000..66fecd7 Binary files /dev/null and b/src/assets/images/architecture/data-flow/workflow-status-stream.png differ diff --git a/src/assets/images/architecture/data-flow/workflow-versioning.png b/src/assets/images/architecture/data-flow/workflow-versioning.png new file mode 100644 index 0000000..265c70e Binary files /dev/null and b/src/assets/images/architecture/data-flow/workflow-versioning.png differ diff --git a/src/assets/images/architecture/ui-frontend/node-data-flow.png b/src/assets/images/architecture/ui-frontend/node-data-flow.png new file mode 100644 index 0000000..f72c069 Binary files /dev/null and b/src/assets/images/architecture/ui-frontend/node-data-flow.png differ diff --git a/src/content/docs/architecture/data-flow.md b/src/content/docs/architecture/data-flow.md index abe78e5..93de673 100644 --- a/src/content/docs/architecture/data-flow.md +++ b/src/content/docs/architecture/data-flow.md @@ -9,6 +9,8 @@ This page traces the data flow through the entire system for the most important This is the primary flow -- a user creates a visual workflow and deploys it to Kubernetes. +![Workflow API Flow](../../../assets/images/architecture/data-flow/workflow-api-flow.png) + ### Phase 1: Design ![Workflow Creation - Design Phase](../../../assets/images/architecture/data-flow/workflow-creation.png) @@ -67,20 +69,22 @@ After deployment, the core maintains active watchers on Kubernetes resources: ![Real-Time Resource Monitoring](../../../assets/images/architecture/data-flow/realtime-monitoring.png) +### Resource Watch Pipeline + +![Resource Watch Pipeline](../../../assets/images/architecture/data-flow/resource-watch-pipeline.png) + +### SSE Status Stream + +![SSE Status Stream](../../../assets/images/architecture/data-flow/workflow-status-stream.png) + +### Terminal Exec Session + +![Terminal Exec Session](../../../assets/images/architecture/data-flow/terminal-exec-session.png) + ## Version Control Flow Workflows support git-like versioning: -``` -Save Workflow → Auto-increment version → Store snapshot in workflow_versions collection - │ - ├── Compare: GET /versions/compare?v1=1&v2=3 - │ → Returns NodeDiff[] and EdgeDiff[] - │ → UI shows side-by-side CompareCanvas - │ - └── Restore: POST /versions/:v/restore - → Creates new version with old content - → Updates workflow.nodes and workflow.edges -``` +![Workflow Versioning](../../../assets/images/architecture/data-flow/workflow-versioning.png) Each version stores a complete snapshot of nodes and edges, enabling full rollback and diff comparison. diff --git a/src/content/docs/architecture/ui-frontend.md b/src/content/docs/architecture/ui-frontend.md index aeb83e7..453040d 100644 --- a/src/content/docs/architecture/ui-frontend.md +++ b/src/content/docs/architecture/ui-frontend.md @@ -208,13 +208,7 @@ WorkflowCanvas.tsx Each node on the canvas has a `data` property matching a TypeScript interface (defined in `lib/types/nodes.ts`). When a user edits node settings: -``` -User edits in Settings Panel - → WorkflowStore.updateNodeData() - → nodeUpdateHandler callback - → React Flow setNodes() - → Canvas re-renders -``` +![Node Data Flow](../../../assets/images/architecture/ui-frontend/node-data-flow.png) ### Secret Handling diff --git a/src/content/docs/guides/example.md b/src/content/docs/guides/example.md deleted file mode 100644 index ebd0f3b..0000000 --- a/src/content/docs/guides/example.md +++ /dev/null @@ -1,11 +0,0 @@ ---- -title: Example Guide -description: A guide in my new Starlight docs site. ---- - -Guides lead a user through a specific task they want to accomplish, often with a sequence of steps. -Writing a good guide requires thinking about what your users are trying to do. - -## Further reading - -- Read [about how-to guides](https://diataxis.fr/how-to-guides/) in the Diátaxis framework diff --git a/src/content/docs/reference/example.md b/src/content/docs/reference/example.md deleted file mode 100644 index 0224f09..0000000 --- a/src/content/docs/reference/example.md +++ /dev/null @@ -1,11 +0,0 @@ ---- -title: Example Reference -description: A reference page in my new Starlight docs site. ---- - -Reference pages are ideal for outlining how things work in terse and clear terms. -Less concerned with telling a story or addressing a specific use case, they should give a comprehensive outline of what you're documenting. - -## Further reading - -- Read [about reference](https://diataxis.fr/reference/) in the Diátaxis framework