From b682e1ed08f177246c3e6cf3d5033821d42f41a9 Mon Sep 17 00:00:00 2001 From: Will Russell Date: Tue, 3 Dec 2024 16:42:01 +0000 Subject: [PATCH] fix: apps formatting --- content/docs/06.enterprise/apps.md | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/content/docs/06.enterprise/apps.md b/content/docs/06.enterprise/apps.md index e7a5912655..65deda8283 100644 --- a/content/docs/06.enterprise/apps.md +++ b/content/docs/06.enterprise/apps.md @@ -9,7 +9,9 @@ Build custom UIs to interact with Kestra from the outside world. ## Overview -Apps let you use your Kestra workflows as the backend for custom applications. Within each app, you can specify custom frontend blocks, such as forms for data entry, output displays, approval buttons, or markdown blocks. **Flows** act as the **backend**, processing data and executing tasks, while Apps serve as frontend, allowing anyone to interact with your workflows regardless of their technical background. Business users can trigger new workflow executions, manually approve workflows that are paused, submit data to automated processes using simple forms, and view the execution results. +Apps let you use your Kestra workflows as the backend for custom applications. Within each app, you can specify custom frontend blocks, such as forms for data entry, output displays, approval buttons, or markdown blocks. + +**Flows** act as the **backend**, processing data and executing tasks, while **Apps** serve as **frontend**, allowing anyone to interact with your workflows regardless of their technical background. Business users can trigger new workflow executions, manually approve workflows that are paused, submit data to automated processes using simple forms, and view the execution results. You can think of Apps as **custom UIs for flows**, allowing your users to interact with Kestra from the outside world.