From f5026f13a5f751e7ed28cd8497e2e02decada39b Mon Sep 17 00:00:00 2001
From: Yael Schuster-Davidi <62833511+YaelSchuster@users.noreply.github.com>
Date: Tue, 2 Dec 2025 10:55:22 +0200
Subject: [PATCH 01/10] Revise documentation agent for clarity and details

Updated documentation agent to clarify roles and responsibilities for creating and editing documentation and blog posts. Added details on pull requests and image embedding syntax.
---
 .github/agents/blogs-docs.agent.md | 39 ++++++++++++++++++++++++++++++
 1 file changed, 39 insertions(+)
 create mode 100644 .github/agents/blogs-docs.agent.md

diff --git a/.github/agents/blogs-docs.agent.md b/.github/agents/blogs-docs.agent.md
new file mode 100644
index 0000000000..56d446bb9e
--- /dev/null
+++ b/.github/agents/blogs-docs.agent.md
@@ -0,0 +1,39 @@
+---
+name: Blog-Docs-Writer
+description: Specialized agent for creating new documentation, editing existing documentation, and writing blog posts for new features.
+tools: ['read', 'search', 'edit']
+---
+
+You are a documentation specialist designed to write technical documentation, edit technical documentation, and summarize new features for blog blurbs or standalone blog posts. If you are editing or creating documentation, you create a pull request at the end of the creation process. 
+
+**First determine**
+- Does the user want to create docs, edit docs, create a blog blurb, a standalone blog, or some combination of the above? These are the only actions you can do
+- Does the user have specifications, related documentation, or other content that can be used for reference?
+- If there are no specifications, can the user describe the feature and the necessary elements for the document to be created?
+- If creating new docs, which type of document (how-to, tutorial, conceptual, FAQ) does the user want to create?
+- Are there ideal examples of this kind of document within the repo?
+
+**Blog blurb**
+- What is the feature and why should I care 
+- Screenshots 
+- Link to learn more in documentation 
+
+**Standalone blog**
+- an expanded version of the blog blurb
+- include scenarios for when to use this feature and how it can be used in conjunction with other parts of the product
+- include a next steps section for users to get started
+
+**New document**
+- Use relative links (e.g., `docs/CONTRIBUTING.md`) instead of absolute URLs for files within the repository
+- Use Microsoft style guide rules when writing
+- Use the templates from the .github/agents/ folder
+
+**Document edits**
+
+**File Types You Work With:**
+- markdown (.md)
+- images (.png) - all images must be hosted in the media/doc-file-name folder and embedded using the following example syntax: :::image type="content" source="media\add-source-sample-data-enhanced\add-sample-data.png" alt-text="A screenshot of selecting Sample data to add to an existing eventstream.":::
+- table of contents files of type .yml
+
+**Pull request**
+- If you are creating new documentation or updating existing, after the document is done then you must create a pull request (PR) under the user's fork against the main branch of the microsoft fork

From 06af8ecea52a3972129ebaee542d89e59ea6aa4d Mon Sep 17 00:00:00 2001
From: Yael Schuster-Davidi <62833511+YaelSchuster@users.noreply.github.com>
Date: Tue, 2 Dec 2025 11:29:28 +0200
Subject: [PATCH 02/10] Update blogs-docs.agent.md

---
 .github/agents/blogs-docs.agent.md | 1 +
 1 file changed, 1 insertion(+)

diff --git a/.github/agents/blogs-docs.agent.md b/.github/agents/blogs-docs.agent.md
index 56d446bb9e..5b1ba753b5 100644
--- a/.github/agents/blogs-docs.agent.md
+++ b/.github/agents/blogs-docs.agent.md
@@ -37,3 +37,4 @@ You are a documentation specialist designed to write technical documentation, ed
 
 **Pull request**
 - If you are creating new documentation or updating existing, after the document is done then you must create a pull request (PR) under the user's fork against the main branch of the microsoft fork
+- If you are creating a blog, return the content as text. Do not create a PR. 

From 023b179798d2d149dac9a4264488650bdc27e23a Mon Sep 17 00:00:00 2001
From: Yael Schuster-Davidi <62833511+YaelSchuster@users.noreply.github.com>
Date: Tue, 2 Dec 2025 11:32:37 +0200
Subject: [PATCH 03/10] Create tutorial template for documentation

Added a tutorial template for documentation purposes.
---
 .github/agents/templates/tutorial.md | 174 +++++++++++++++++++++++++++
 1 file changed, 174 insertions(+)
 create mode 100644 .github/agents/templates/tutorial.md

diff --git a/.github/agents/templates/tutorial.md b/.github/agents/templates/tutorial.md
new file mode 100644
index 0000000000..d5fbf84bad
--- /dev/null
+++ b/.github/agents/templates/tutorial.md
@@ -0,0 +1,174 @@
+---
+title: Page title has the greatest effect on search
+description: The meta-description is not crawled for search rank, but is displayed in the browser.
+author: <github account>
+ms.author: <MS alias>
+ms.service: <service-slug>
+ms.topic: tutorial
+ms.custom: mvc
+ms.date: 11/16/2017
+
+---
+<!---Recommended: Remove all the comments in this template before you
+sign-off or merge to main.--->
+
+<!---Tutorials are scenario-based procedures for the top customer tasks
+identified in milestone one of the
+[C+E Skilling content model](contribute-get-started-mvc.md).
+You only use tutorials to show the single best procedure for completing
+an approved top 10 customer task.
+--->
+
+# Tutorial: <do something with X> 
+<!---Required:
+Starts with "Tutorial: "
+Make the first word following "Tutorial:" a verb.
+--->
+
+Introductory paragraph.
+<!---Required:
+Lead with a light intro that describes, in customer-friendly language,
+what the customer will learn, or do, or accomplish. Answer the
+fundamental "why would I want to do this?" question.
+--->
+
+In this tutorial, you learn how to:
+
+> [!div class="checklist"]
+> * All tutorials include a list summarizing the steps to completion
+> * Each of these bullet points align to a key H2
+> * Use these green checkboxes in a tutorial
+<!---Required:
+Include the outline of the tutorial in the beginning and at
+the end of every tutorial. These will align to the **procedural** H2
+headings for the activity. You do not need to include all H2 headings.
+Leave out the prerequisites, clean-up resources and next steps--->
+
+If you don't have a <service> subscription, create a free trial account...
+<!--- Required, if a free trial account exists.
+Because we intend tutorials to help new customers use the product or
+service to finish a top task, include a link to a free trial before the
+first H2, if one exists. You can find listed examples in
+[Write tutorials](contribute-how-to-mvc-tutorial.md)
+--->
+
+<!---Avoid notes, tips, and important boxes. Readers tend to skip over
+them. Better to put that info directly into the article text.--->
+
+## Prerequisites
+
+- First prerequisite
+- Second prerequisite
+- Third prerequisite
+<!---If you need them, make Prerequisites your first H2 in a tutorial. If
+there's something a customer needs to take care of before they start (for
+example, creating a VM) it's OK to link to that content before they
+begin.--->
+
+## Sign in to <service/product/tool name>
+
+Sign in to the [<service> portal](url).
+<!---If you need to sign in to the portal to do the tutorial, the article requires this H2 and
+link.--->
+
+## Procedure 1
+
+<!---Required:
+Tutorials are prescriptive and guide the customer through an end-to-end
+procedure. Make sure to use specific naming for setting up accounts and
+configuring technology.
+Don't link off to other content - include whatever the customer needs to
+finish the scenario in the article. For example, if the customer needs
+to set permissions, include the permissions they need to set, and the
+specific settings in the tutorial procedure. Don't send the customer to
+another article to read about it.
+In a break from tradition, do not link to reference topics in the
+procedural part of the tutorial when using cmdlets or code. Provide customers 
+what they need to know in the tutorial to successfully finish
+the tutorial.
+For portal-based procedures, minimize bullets and numbering.
+For the CLI or PowerShell based procedures, don't use bullets or
+numbering.
+--->
+
+Include a sentence or two to explain only what the reader needs to do to finish the
+procedure.
+
+1. Step one of the procedure
+1. Step two of the procedure
+1. Step three of the procedure
+   :::image type="content" border="true" source="media/contribute-how-to-mvc-tutorial/browser.png" alt-text="Browser.":::
+
+   <!---Use screenshots but be judicious to maintain a reasonable length. 
+   Make sure screenshots align to the
+   [current standards](https://review.learn.microsoft.com/help/contribute/contribute-how-to-create-screenshot).
+   If users access your product/service via a web browser the first 
+   screenshot should always include the full browser window in Chrome or
+   Safari. This is to show users that the portal is browser-based - OS 
+   and browser agnostic.--->
+1. Step four of the procedure
+
+## Procedure 2
+
+Include a sentence or two to explain only what the reader needs to do to finish the procedure.
+
+1. Step one of the procedure
+1. Step two of the procedure
+1. Step three of the procedure
+
+## Procedure 3
+
+Include a sentence or two to explain only what the reader needs to do to finish the
+procedure.
+<!---Code requires specific formatting. Here are a few useful examples of
+commonly used code blocks. Make sure to use the interactive functionality
+where possible.
+For the CLI or PowerShell based procedures, don't use bullets or
+numbering.--->
+
+Here is an example of a code block for Java:
+
+    ```java
+    cluster = Cluster.build(new File("src/remote.yaml")).create();
+    ...
+    client = cluster.connect();
+    ```
+
+or a code block for Azure CLI:
+
+    ```azurecli-interactive 
+    az vm create --resource-group myResourceGroup --name myVM --image win2016datacenter --admin-username azureuser --admin-password <password>
+    ```
+or a code block for Azure PowerShell:
+
+    ```azurepowershell-interactive
+    New-AzureRmContainerGroup -ResourceGroupName myResourceGroup -Name mycontainer -Image mcr.microsoft.com/windows/servercore/iis:nanoserver -OsType Windows -IpAddressType Public
+    ```
+
+## Clean up resources
+
+If you're not going to continue to use this application, delete
+<resources> with the following steps:
+
+1. From the left-hand menu...
+2. ...click Delete, enter...and then click Delete
+
+<!---Required:
+To avoid any costs associated with following the tutorial procedure, a
+Clean up resources (H2) should come just before Next steps (H2)
+--->
+
+## Next steps
+
+Advance to the next article to learn how to create...
+> [!div class="nextstepaction"]
+> [Next steps button](contribute-get-started-mvc.md)
+
+<!--- Required:
+Tutorials should always have a Next steps H2 that points to the next
+logical tutorial in a series, or, if there are no other tutorials, to
+some other cool thing the customer can do. A single link in the blue box
+format should direct the customer to the next article - and you can
+shorten the title in the boxes if the original one doesn't fit.
+Do not use a "More info section" or a "Resources section" or a "See also
+section". --->

From 88ef8e32f1a7c5c4c8e8cfe9d82e09d57b14413c Mon Sep 17 00:00:00 2001
From: Yael Schuster-Davidi <62833511+YaelSchuster@users.noreply.github.com>
Date: Tue, 2 Dec 2025 11:34:05 +0200
Subject: [PATCH 04/10] Create overview.md

---
 .github/agents/templates/overview.md | 80 ++++++++++++++++++++++++++++
 1 file changed, 80 insertions(+)
 create mode 100644 .github/agents/templates/overview.md

diff --git a/.github/agents/templates/overview.md b/.github/agents/templates/overview.md
new file mode 100644
index 0000000000..670f773e76
--- /dev/null
+++ b/.github/agents/templates/overview.md
@@ -0,0 +1,80 @@
+---
+title: [Follow SEO guidance at 
+https://review.learn.microsoft.com/en-us/help/platform/seo-meta-title]
+description: "[Article description]."
+author: [your GitHub alias]
+ms.author: [your Microsoft alias or a team alias]
+ms.service: [the approved service name]
+ms.topic: overview #Don't change
+ms.date: [mm/dd/yyyy]
+
+#customer intent: As a <role>, I want <what> so that <why>.
+
+---
+
+<!-- --------------------------------------
+
+- Use this template with pattern instructions for:
+
+Overview
+
+- Before you sign off or merge:
+
+Remove all comments except the customer intent.
+
+- Feedback:
+
+https://aka.ms/patterns-feedback
+
+-->
+
+# What is [product or service]?
+
+<!-- Required: Article headline - H1
+
+Identify the product or service and the feature area
+you are providing overview information about.
+
+-->
+
+[Introduce and explain the purpose of the article.]
+
+<!-- Required: Introductory paragraphs (no heading)
+
+Write a brief introduction that can help the user
+determine whether the article is relevant for them
+and to describe how the article might benefit them.
+
+-->
+
+## [Feature section]
+
+[Introduce a section that describes a feature.]
+
+<!-- Required: Feature sections - H2
+
+In two or more H2 sections, describe key features of
+the product or service. Consider sections for basic
+requirements, dependencies, limitations, and overhead.
+
+-->
+
+## Related content
+
+- [Related article title](link.md)
+- [Related article title](link.md)
+- [Related article title](link.md)
+
+<!-- Optional: Related content - H2
+
+Consider including a "Related content" H2 section that 
+lists links to 1 to 3 articles the user might find helpful.
+
+-->
+
+<!--
+
+Remove all comments except the customer intent
+before you sign off or merge to the main branch.
+
+-->

From 9e1211ac1a08edab6b20b51f641db9119b03530b Mon Sep 17 00:00:00 2001
From: Yael Schuster-Davidi <62833511+YaelSchuster@users.noreply.github.com>
Date: Tue, 2 Dec 2025 11:34:49 +0200
Subject: [PATCH 05/10] Create concept article template with guidelines

Added a template for concept articles with SEO guidance.
---
 .github/agents/templates/concept.md | 102 ++++++++++++++++++++++++++++
 1 file changed, 102 insertions(+)
 create mode 100644 .github/agents/templates/concept.md

diff --git a/.github/agents/templates/concept.md b/.github/agents/templates/concept.md
new file mode 100644
index 0000000000..a3258fa13d
--- /dev/null
+++ b/.github/agents/templates/concept.md
@@ -0,0 +1,102 @@
+---
+title: [Follow SEO guidance at 
+https://review.learn.microsoft.com/en-us/help/platform/seo-meta-title]
+description: "[Article description]."
+author: [your GitHub alias]
+ms.author: [your Microsoft alias or a team alias]
+ms.service: [the approved service name]
+ms.topic: concept-article #Don't change.
+ms.date: [mm/dd/yyyy]
+
+#customer intent: As a <role>, I want <what> so that <why>.
+
+---
+
+<!-- --------------------------------------
+
+- Use this template with pattern instructions for:
+
+Concept
+
+- Before you sign off or merge:
+
+Remove all comments except the customer intent.
+
+- Feedback:
+
+https://aka.ms/patterns-feedback
+
+-->
+
+# [noun phrase] concept(s)
+
+or
+
+# [noun] overview
+
+<!-- Required: Article headline - H1
+
+Identify the product, service, or feature the
+article covers.
+
+-->
+
+[Introduce and explain the purpose of the article.]
+
+<!-- Required: Introductory paragraphs (no heading)
+
+Write a brief introduction that can help the user
+determine whether the article is relevant for them
+and to describe the concept the article covers.
+
+For definitive concepts, it's better to lead with a
+sentence in the form, "X is a (type of) Y that does Z."
+
+-->
+
+## Prerequisites
+
+<!--Optional: Prerequisites - H2
+
+If this section is needed, make "Prerequisites" your
+first H2 in the article.
+
+Use clear and unambiguous language and use
+an unordered list format. 
+
+-->
+
+## [Main idea]
+
+[Describe a main idea.]
+
+<!-- Required: Main ideas - H2
+
+Use one or more H2 sections to describe the main ideas
+of the concept.
+
+Follow each H2 heading with a sentence about how
+the section contributes to the whole. Then, describe 
+the concept's critical features as you define what it is.
+
+-->
+
+## Related content
+
+- [Related article title](link.md)
+- [Related article title](link.md)
+- [Related article title](link.md)
+
+<!-- Optional: Related content - H2
+
+Consider including a "Related content" H2 section that 
+lists links to 1 to 3 articles the user might find helpful.
+
+-->
+
+<!--
+
+Remove all comments except the customer intent
+before you sign off or merge to the main branch.
+
+-->

From 78cfc9139f8fab22805bab2eb390b4e830aee2c5 Mon Sep 17 00:00:00 2001
From: Yael Schuster-Davidi <62833511+YaelSchuster@users.noreply.github.com>
Date: Tue, 2 Dec 2025 11:35:13 +0200
Subject: [PATCH 06/10] Create quickstart.md template for articles

Add quickstart template for documentation
---
 .github/agents/templates/quickstart.md | 188 +++++++++++++++++++++++++
 1 file changed, 188 insertions(+)
 create mode 100644 .github/agents/templates/quickstart.md

diff --git a/.github/agents/templates/quickstart.md b/.github/agents/templates/quickstart.md
new file mode 100644
index 0000000000..da5187134b
--- /dev/null
+++ b/.github/agents/templates/quickstart.md
@@ -0,0 +1,188 @@
+---
+title: [Follow SEO guidance at 
+https://review.learn.microsoft.com/en-us/help/platform/seo-meta-title]
+description: "[Article description]."
+author: [your GitHub alias]
+ms.author: [your Microsoft alias or a team alias]
+ms.service: [the approved service name]
+ms.topic: quickstart  #Don't change
+ms.date: [mm/dd/yyyy]
+
+#customer intent: As a <role>, I want <what> so that <why>.
+
+---
+  
+<!-- --------------------------------------
+
+- Use this template with pattern instructions for:
+
+Quickstart
+
+- Use the Quickstart pattern when you want to show a user 
+how to complete a task to get started with a product or 
+service in their own environment.
+
+- Before you sign off or merge:
+
+Remove all comments except the customer intent.
+
+- Feedback:
+
+https://aka.ms/patterns-feedback
+
+-->
+
+# Quickstart: [verb] * [noun]
+ 
+<!-- Required: Article headline - H1
+
+Identify the product or service and the feature area
+the quickstart covers.
+
+-->
+
+[Introduce and explain the purpose of the article.]
+
+<!-- Required: Introductory paragraphs (no heading)
+
+Write a brief introduction that can help the user determine 
+whether the article is relevant for them. Begin with a 
+sentence that says, "In this quickstart, you . . . ."
+
+-->
+
+If you don't have a service subscription, create a free
+trial account . . .
+
+<!-- Required: Free account links (no heading)
+
+Because quickstarts are intended to help new customers
+use a product or service, include a link to a 
+free trial before the first H2 or in the prerequisites.
+
+-->
+
+## Prerequisites
+
+<!-- Optional: Prerequisites - H2
+
+If included, "Prerequisites" must be the first H2 in the article.
+
+List any items that are needed for the quickstart,
+such as permissions or software.
+
+If the user needs to sign in to a portal to do
+the quickstart, provide instructions and a link.
+
+-->
+
+## Open [Cloud Shell, Azure CLI, or PowerShell]
+
+<!-- Optional: Open a demo environment - H2
+
+If you want to refer to using Azure Cloud Shell,
+the Azure CLI, or Azure PowerShell, include the
+instructions as a first step, after the "Prerequisites" section if prerequisites are included.
+
+Include information about Cloud Shell only if all commands can 
+run in Cloud Shell.
+
+Use include files if they are available.
+
+-->
+
+## [verb] * [noun]
+
+[Introduce a task and its role in completing the process.]
+
+<!-- Required: Tasks to complete in the process - H2
+
+In one or more numbered H2 sections, describe tasks that 
+the user completes in the process the quickstart describes.
+
+-->
+
+1. Procedure step
+1. Procedure step
+1. Procedure step
+
+<!-- Required: Steps to complete the tasks - H2
+
+Use ordered lists to describe how to complete tasks in 
+the process. Be consistent when you describe how to
+use a method or tool to complete the task.
+
+Code requires specific formatting. Here are a few useful 
+examples of commonly used code blocks. Make sure to 
+use the interactive functionality when possible.
+
+For the CLI-based or PowerShell-based procedures,
+don't use bullets or numbering.
+
+Here is an example of a code block for Java:
+
+```java
+cluster = Cluster.build(new File("src/site.yaml")).create();
+...
+client = cluster.connect();
+```
+
+Here's a code block for the Azure CLI:
+
+```azurecli-interactive 
+az vm create --resource-group myResourceGroup --name myVM 
+--image win2016datacenter --admin-username azureuser 
+--admin-password <password>
+```
+
+This is a code block for Azure PowerShell:
+
+```azurepowershell-interactive
+New-AzureRmContainerGroup -ResourceGroupName 
+myResourceGroup -Name mycontainer 
+-Image mcr.microsoft.com/windows/servercore/iis:nanoserver 
+-OsType Windows -IpAddressType Public
+```
+-->
+
+## Clean up resources
+
+<!-- Optional: Steps to clean up resources - H2
+
+Provide steps the user takes to clean up resources that
+were created to complete the article.
+
+-->
+
+## Next step -or- Related content
+
+> [!div class="nextstepaction"]
+> [Next sequential article title](link.md)
+
+-or-
+
+- [Related article title](link.md)
+- [Related article title](link.md)
+- [Related article title](link.md)
+
+<!-- Optional: Next step or Related content - H2
+
+Consider adding one of these H2 sections (not both):
+
+A "Next step" section that uses 1 link in a blue box 
+to point to a next, consecutive article in a sequence.
+
+-or- 
+
+If the quickstart is not part of a sequence, use a 
+"Related content" section that lists links to 
+1 to 3 articles the user might find helpful.
+
+-->
+
+<!--
+
+Remove all comments except the customer intent
+before you sign off or merge to the main branch.
+
+-->

From 1f921b484c3301b474280b031d30a4b95a1dae0c Mon Sep 17 00:00:00 2001
From: Yael Schuster-Davidi <62833511+YaelSchuster@users.noreply.github.com>
Date: Tue, 2 Dec 2025 11:35:43 +0200
Subject: [PATCH 07/10] Add How To article template

This file serves as a template for creating 'How To' articles, including sections for prerequisites, procedures, and related content.
---
 .github/agents/templates/how-to.md | 125 +++++++++++++++++++++++++++++
 1 file changed, 125 insertions(+)
 create mode 100644 .github/agents/templates/how-to.md

diff --git a/.github/agents/templates/how-to.md b/.github/agents/templates/how-to.md
new file mode 100644
index 0000000000..7185b3434d
--- /dev/null
+++ b/.github/agents/templates/how-to.md
@@ -0,0 +1,125 @@
+---
+title: [Follow SEO guidance at 
+https://review.learn.microsoft.com/en-us/help/platform/seo-meta-title]
+description: "[Article description]."
+author: [your GitHub alias]
+ms.author: [your Microsoft alias or a team alias]
+ms.service: [the approved service name]
+ms.topic: how-to #Don't change
+ms.date: [mm/dd/yyyy]
+
+#customer intent: As a <role>, I want <what> so that <why>.
+
+---
+
+<!-- --------------------------------------
+
+- Use this template with pattern instructions for:
+
+How To
+
+- Before you sign off or merge:
+
+Remove all comments except the customer intent.
+
+- Feedback:
+
+https://aka.ms/patterns-feedback
+
+-->
+
+# "[verb] * [noun]"
+
+<!-- Required: Article headline - H1
+
+Identify the product or service and the task the
+article describes.
+
+-->
+
+[Introduce and explain the purpose of the article.]
+
+<!-- Required: Introductory paragraphs (no heading)
+
+Write a brief introduction that can help the user
+determine whether the article is relevant for them
+and to describe the task the article covers.
+
+-->
+
+## Prerequisites
+
+<!-- Optional: Prerequisites - H2
+
+If included, "Prerequisites" must be the first H2 in the article.
+
+List any items that are needed to complete the How To,
+such as permissions or software.
+
+If you need to sign in to a portal to complete the How To, 
+provide instructions and a link.
+
+-->
+
+## "[verb] * [noun]"
+
+[Introduce the procedure.]
+
+1. Procedure step
+1. Procedure step
+1. Procedure step
+
+<!-- Required: Steps to complete the task - H2
+
+In one or more H2 sections, organize procedures. A section
+contains a major grouping of steps that help the user complete
+a task.
+
+Begin each section with a brief explanation for context, and
+provide an ordered list of steps to complete the procedure.
+
+If it applies, provide sections that describe alternative tasks or
+procedures.
+
+-->
+
+## Clean up resources
+
+<!-- Optional: Steps to clean up resources - H2
+
+Provide steps the user can take to clean up resources that
+they might no longer need.
+
+-->
+
+## Next step -or- Related content
+
+> [!div class="nextstepaction"]
+> [Next sequential article title](link.md)
+
+-or-
+
+* [Related article title](link.md)
+* [Related article title](link.md)
+* [Related article title](link.md)
+
+<!-- Optional: Next step or Related content - H2
+
+Consider adding one of these H2 sections (not both):
+
+A "Next step" section that uses 1 link in a blue box 
+to point to a next, consecutive article in a sequence.
+
+-or- 
+
+A "Related content" section that lists links to 
+1 to 3 articles the user might find helpful.
+
+-->
+
+<!--
+
+Remove all comments except the customer intent
+before you sign off or merge to the main branch.
+
+-->

From bdc7e645398c3e1b7497f0eb6d8907798c54fb19 Mon Sep 17 00:00:00 2001
From: Yael Schuster-Davidi <62833511+YaelSchuster@users.noreply.github.com>
Date: Tue, 2 Dec 2025 11:36:14 +0200
Subject: [PATCH 08/10] Add 'quickstart' and 'overview' to document types

---
 .github/agents/blogs-docs.agent.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/.github/agents/blogs-docs.agent.md b/.github/agents/blogs-docs.agent.md
index 5b1ba753b5..ad85152767 100644
--- a/.github/agents/blogs-docs.agent.md
+++ b/.github/agents/blogs-docs.agent.md
@@ -10,7 +10,7 @@ You are a documentation specialist designed to write technical documentation, ed
 - Does the user want to create docs, edit docs, create a blog blurb, a standalone blog, or some combination of the above? These are the only actions you can do
 - Does the user have specifications, related documentation, or other content that can be used for reference?
 - If there are no specifications, can the user describe the feature and the necessary elements for the document to be created?
-- If creating new docs, which type of document (how-to, tutorial, conceptual, FAQ) does the user want to create?
+- If creating new docs, which type of document (how-to, tutorial, conceptual, quickstart, overview) does the user want to create?
 - Are there ideal examples of this kind of document within the repo?
 
 **Blog blurb**

From 0c6b7699d704cd2b9d05b5a6ed2ce87faaa987b7 Mon Sep 17 00:00:00 2001
From: Yael Schuster-Davidi <62833511+YaelSchuster@users.noreply.github.com>
Date: Tue, 2 Dec 2025 11:41:30 +0200
Subject: [PATCH 09/10] Revise documentation process and templates

Updated the structure and instructions for documentation creation and editing, including clarifications on document types and templates.
---
 .github/agents/blogs-docs.agent.md | 14 ++++++++++----
 1 file changed, 10 insertions(+), 4 deletions(-)

diff --git a/.github/agents/blogs-docs.agent.md b/.github/agents/blogs-docs.agent.md
index ad85152767..6c968289da 100644
--- a/.github/agents/blogs-docs.agent.md
+++ b/.github/agents/blogs-docs.agent.md
@@ -6,13 +6,18 @@ tools: ['read', 'search', 'edit']
 
 You are a documentation specialist designed to write technical documentation, edit technical documentation, and summarize new features for blog blurbs or standalone blog posts. If you are editing or creating documentation, you create a pull request at the end of the creation process. 
 
-**First determine**
+1. **First determine**
 - Does the user want to create docs, edit docs, create a blog blurb, a standalone blog, or some combination of the above? These are the only actions you can do
+
+2. **Next ask for**
 - Does the user have specifications, related documentation, or other content that can be used for reference?
 - If there are no specifications, can the user describe the feature and the necessary elements for the document to be created?
-- If creating new docs, which type of document (how-to, tutorial, conceptual, quickstart, overview) does the user want to create?
+- If creating new docs, which type of document (how-to, tutorial, conceptual, quickstart, overview) does the user want to create? 
 - Are there ideal examples of this kind of document within the repo?
 
+3. **Then**
+- create a work plan, including outline. Do not proceed until the user has approved. Take into account the following general structures:
+
 **Blog blurb**
 - What is the feature and why should I care 
 - Screenshots 
@@ -26,14 +31,15 @@ You are a documentation specialist designed to write technical documentation, ed
 **New document**
 - Use relative links (e.g., `docs/CONTRIBUTING.md`) instead of absolute URLs for files within the repository
 - Use Microsoft style guide rules when writing
-- Use the templates from the .github/agents/ folder
+- Use templates in the ~/.github/agents/templates folder for the selected type. 
 
-**Document edits**
+4. Now create the requested documents
 
 **File Types You Work With:**
 - markdown (.md)
 - images (.png) - all images must be hosted in the media/doc-file-name folder and embedded using the following example syntax: :::image type="content" source="media\add-source-sample-data-enhanced\add-sample-data.png" alt-text="A screenshot of selecting Sample data to add to an existing eventstream.":::
 - table of contents files of type .yml
+- text output for blog posts
 
 **Pull request**
 - If you are creating new documentation or updating existing, after the document is done then you must create a pull request (PR) under the user's fork against the main branch of the microsoft fork

From ea5cc0ad453d014d5d63255cfd35583a07d4a551 Mon Sep 17 00:00:00 2001
From: Yael Schuster-Davidi <62833511+YaelSchuster@users.noreply.github.com>
Date: Tue, 2 Dec 2025 12:52:39 +0200
Subject: [PATCH 10/10] Update blogs-docs.agent.md

---
 .github/agents/blogs-docs.agent.md | 63 +++++++++++++++---------------
 1 file changed, 31 insertions(+), 32 deletions(-)

diff --git a/.github/agents/blogs-docs.agent.md b/.github/agents/blogs-docs.agent.md
index 6c968289da..2b7ac06045 100644
--- a/.github/agents/blogs-docs.agent.md
+++ b/.github/agents/blogs-docs.agent.md
@@ -4,43 +4,42 @@ description: Specialized agent for creating new documentation, editing existing
 tools: ['read', 'search', 'edit']
 ---
 
-You are a documentation specialist designed to write technical documentation, edit technical documentation, and summarize new features for blog blurbs or standalone blog posts. If you are editing or creating documentation, you create a pull request at the end of the creation process. 
+You are a documentation specialist designed to write technical documentation, edit technical documentation, and summarize new features for blog blurbs or standalone blog posts. If you are editing or creating documentation, you create a pull request at the end of the creation process. Do not create a pull request until the content has been approved.
 
 1. **First determine**
-- Does the user want to create docs, edit docs, create a blog blurb, a standalone blog, or some combination of the above? These are the only actions you can do
+  - Does the user want to create docs, edit docs, create a blog blurb, a standalone blog, or some combination of the above? These are the only actions you can do. 
 
 2. **Next ask for**
-- Does the user have specifications, related documentation, or other content that can be used for reference?
-- If there are no specifications, can the user describe the feature and the necessary elements for the document to be created?
-- If creating new docs, which type of document (how-to, tutorial, conceptual, quickstart, overview) does the user want to create? 
-- Are there ideal examples of this kind of document within the repo?
-
-3. **Then**
-- create a work plan, including outline. Do not proceed until the user has approved. Take into account the following general structures:
-
-**Blog blurb**
-- What is the feature and why should I care 
-- Screenshots 
-- Link to learn more in documentation 
-
-**Standalone blog**
-- an expanded version of the blog blurb
-- include scenarios for when to use this feature and how it can be used in conjunction with other parts of the product
-- include a next steps section for users to get started
-
-**New document**
-- Use relative links (e.g., `docs/CONTRIBUTING.md`) instead of absolute URLs for files within the repository
-- Use Microsoft style guide rules when writing
-- Use templates in the ~/.github/agents/templates folder for the selected type. 
+  - Does the user have specifications, related documentation, or other content that can be used for reference?
+  - If there are no specifications, can the user describe the feature and the necessary elements for the document to be created?
+  - If creating new docs, which type of document (how-to, tutorial, conceptual, quickstart, overview) does the user want to create? 
+  - Are there ideal examples of this kind of document within the repo?
+
+3. Create a work plan, including outline. Do not proceed until the user has approved. Take into account the following general structures:
+  
+  **Blog blurb**
+  - What is the feature and why should I care 
+  - Screenshots 
+  - Link to learn more in documentation 
+
+  **Standalone blog**
+  - an expanded version of the blog blurb
+  - include scenarios for when to use this feature and how it can be used in conjunction with other parts of the product
+  - include a next steps section for users to get started
+  
+  **New document**
+  - Use relative links (e.g., `docs/CONTRIBUTING.md`) instead of absolute URLs for files within the repository
+  - Use Microsoft style guide rules when writing
+  - Use templates in the ~/.github/agents/templates folder for the selected type. 
 
 4. Now create the requested documents
 
-**File Types You Work With:**
-- markdown (.md)
-- images (.png) - all images must be hosted in the media/doc-file-name folder and embedded using the following example syntax: :::image type="content" source="media\add-source-sample-data-enhanced\add-sample-data.png" alt-text="A screenshot of selecting Sample data to add to an existing eventstream.":::
-- table of contents files of type .yml
-- text output for blog posts
+  **File Types You Work With:**
+  - markdown (.md)
+  - images (.png) - all images must be hosted in the media/doc-file-name folder and embedded using the following example syntax: :::image type="content" source="media\add-source-sample-data-enhanced\add-sample-data.png" alt-text="A screenshot of selecting Sample data to add to an existing eventstream.":::
+  - table of contents files of type .yml
+  - text output for blog posts
 
-**Pull request**
-- If you are creating new documentation or updating existing, after the document is done then you must create a pull request (PR) under the user's fork against the main branch of the microsoft fork
-- If you are creating a blog, return the content as text. Do not create a PR. 
+  **Pull request**
+  - If you are creating new documentation or updating existing, after the document is done then you must create a pull request (PR) under the user's fork against the main branch of the microsoft fork
+  - If you are creating a blog, return the content as text. Do not create a PR.