diff --git a/gatsby-config.js b/gatsby-config.js
index 52de39dd..f08c7e23 100644
--- a/gatsby-config.js
+++ b/gatsby-config.js
@@ -208,6 +208,10 @@ module.exports = {
{
title: "Export Content Fragments to Adobe Target",
path: "/extension-manager/extension-developed-by-adobe/exporting-content-fragment-to-adobe-target"
+ },
+ {
+ title: "Content Fragments Workflows",
+ path: "/extension-manager/extension-developed-by-adobe/content-fragments-workflows"
}
]
}
diff --git a/src/pages/extension-manager/extension-developed-by-adobe/content-fragments-workflows/index.md b/src/pages/extension-manager/extension-developed-by-adobe/content-fragments-workflows/index.md
new file mode 100644
index 00000000..50f85aeb
--- /dev/null
+++ b/src/pages/extension-manager/extension-developed-by-adobe/content-fragments-workflows/index.md
@@ -0,0 +1,66 @@
+---
+title: Content Fragments workflows
+description: Explore enhanced functionality in the Content Fragments Console and AEM Content Fragment Editor, simplifying workflow initiation.
+contributors:
+- AdobeDocs/uix
+---
+
+# Content Fragments workflows
+
+This extension expands functionality by leveraging extension points and introducing the capability to initiate an AEM workflow for selected content fragments.
+
+## Extension overview
+
+The extension enhances two AEM services: [AEM Content Fragments Console](../../../services/aem-cf-console-admin/) and [AEM Content Fragment Editor](../../../services/aem-cf-editor/). It adds a button to the `Action Bar` for the Content Fragments Console and a button to the `Header Menu` for the AEM Content Fragment Editor.
+
+When clicked, it opens a modal dialog through which you can initiate a workflow.
+
+AEM Content Fragments Console:
+
+
+
+AEM Content Fragment Editor:
+
+
+
+## Workflows modal and workflow launching
+
+
+
+The modal dialog consists of several elements through which you can initiate a workflow:
+
+- `Workflow Model` - a dropdown menu containing the workflows available to you within the organization.
+- `Workflow Title` - a title input field of the workflow process, which will be displayed on the result page of launched workflows in AEM.
+- `Content Fragments Grid` - a grid displaying a list of content fragments for which the workflow will be launched.
+- `Start Workflow button` - when clicked, initiates the workflow initialization process. The workflow starts asynchronously in the background of the application.
+
+To launch a workflow, you need to fill in all the required fields and click the `Start Workflow` button. This will initiate the workflow for each content fragment asynchronously. Each content fragment will have its own workflow process.
+
+## Working with references
+
+Within the grid listing the content fragments, there are two additional columns: `References` and `Referenced By` along with the ability to mark these options for each content fragment in the list using checkboxes.
+
+- `References` - by selecting this checkbox, you indicate that a separate workflow process should be created for all children fragments (references) up to the maximum allowed depth. If no children fragments (references) exist for this content fragment, the checkbox will not be displayed.
+- `Referenced By` - by selecting this checkbox, you indicate that a process will be created for its **direct** parent reference as well (not all parents in the "tree"). If the parent fragment's reference does not exist for this content fragment, the checkbox will not be displayed.
+
+**Notice:** when selecting multiple content fragments and combining the selected options of `References` and `Referenced By`, workflows will be launched only once for each content fragment (the one selected and its children or parent reference, depending on the specified options).
+
+For example, when selecting both parent and children content fragments and enabling the options `References` and `Referenced By` for them, only one workflow will be created for each content fragment, avoiding duplication of workflows and cyclic dependencies during workflows launching.
+
+[Learn about using references in Content Fragments](https://experienceleague.adobe.com/docs/experience-manager-cloud-service/content/headless/journeys/author/references.html?lang=en)
+
+## Result of running
+
+After clicking the `Start Workflow` button, the initialization of starting the workflow with the selected parameters will begin. You will then see the result of the workflow process start and several links to AEM pages, where you can view the execution result of the launched workflow.
+
+
+
+**Notice:** the status of the workflow start will be displayed, but not the result of its completion, which occurs asynchronously in the background. To find out the final result of the workflow execution, you need to follow the links that will be displayed below the result grid.
+
+## Limitations
+
+- `List of Workflows` - currently, by default, the dropdown displays a list of all workflows available for the organization. Limiting this list can be achieved through appropriate ACL configurations for the user.
+
+## Extension source
+
+- [GitHub](https://github.com/adobe/aem-uix-examples/tree/main/content-fragment-workflows)
\ No newline at end of file
diff --git a/src/pages/extension-manager/extension-developed-by-adobe/content-fragments-workflows/workflow-extension-cf-admin.png b/src/pages/extension-manager/extension-developed-by-adobe/content-fragments-workflows/workflow-extension-cf-admin.png
new file mode 100644
index 00000000..ceaac636
Binary files /dev/null and b/src/pages/extension-manager/extension-developed-by-adobe/content-fragments-workflows/workflow-extension-cf-admin.png differ
diff --git a/src/pages/extension-manager/extension-developed-by-adobe/content-fragments-workflows/workflow-extension-cf-editor.png b/src/pages/extension-manager/extension-developed-by-adobe/content-fragments-workflows/workflow-extension-cf-editor.png
new file mode 100644
index 00000000..d7620fdb
Binary files /dev/null and b/src/pages/extension-manager/extension-developed-by-adobe/content-fragments-workflows/workflow-extension-cf-editor.png differ
diff --git a/src/pages/extension-manager/extension-developed-by-adobe/content-fragments-workflows/workflow-extension-popup.png b/src/pages/extension-manager/extension-developed-by-adobe/content-fragments-workflows/workflow-extension-popup.png
new file mode 100644
index 00000000..456f36c0
Binary files /dev/null and b/src/pages/extension-manager/extension-developed-by-adobe/content-fragments-workflows/workflow-extension-popup.png differ
diff --git a/src/pages/extension-manager/extension-developed-by-adobe/content-fragments-workflows/workflow-extension-result.png b/src/pages/extension-manager/extension-developed-by-adobe/content-fragments-workflows/workflow-extension-result.png
new file mode 100644
index 00000000..f58b08fb
Binary files /dev/null and b/src/pages/extension-manager/extension-developed-by-adobe/content-fragments-workflows/workflow-extension-result.png differ
diff --git a/src/pages/extension-manager/extension-developed-by-adobe/index.md b/src/pages/extension-manager/extension-developed-by-adobe/index.md
index e3fd1e60..99c5b1f7 100644
--- a/src/pages/extension-manager/extension-developed-by-adobe/index.md
+++ b/src/pages/extension-manager/extension-developed-by-adobe/index.md
@@ -7,4 +7,14 @@ contributors:
Welcome to the Extensions Developed By Adobe! Explore user guides here to learn how to configure your environment for utilizing extensions from the Extension Manager, along with the supported user flows.
-[Exporting Content Fragment to Adobe Target](exporting-content-fragment-to-adobe-target)
\ No newline at end of file
+
+
+[Exporting Content Fragment to Adobe Target](exporting-content-fragment-to-adobe-target)
+
+Explore Exporting Content Fragments to Adobe Target
+
+
+
+[Content Fragments workflows](content-fragments-workflows)
+
+Explore enhanced functionality in the Content Fragments Console and AEM Content Fragment Editor, simplifying workflow initiation