Gitops auto promotion req (#1316)

* Update promotion-flow.md

* Update promotion-flow.md

* Add promotion hooks

* Rename and update promotion hooks

* Update promotion-hooks.md

* Add promotion hooks to nav yamls

* Add sym link for promotion hooks to _gitops  collection

* Update promotion-hooks.md

* Update promotion-hooks.md

Edits after feedback from Dev

* Update content

Added draft diagram for promotion context behavior and content updates

* Update promotion-hooks.md

* Remove entities from mapping file

* Update

* Update diagram

* Update promotion-hooks.md

* Add new articles fro service accounts and promotion contexts

* Updates

* Update content for promotion contexts

Added walkthrough example for promotion context

* Update promotion-context-promotion-workflows.md

* Update hook-slack-notification-example.png

* Update promotion-context-promotion-workflows.md

* Add promotion context example

Added example template to define promotion context and use in  promotion hook

* Update overview title

* Update promotion-context-promotion-workflows.md

* Add feedback from review

Implemented feedback from Francisco's review

* Update product-releases.md

* Add note on early access

Added note on early access availability for publish

* Fix links

Fixed links after self-review

Author: NimRegev

_data/argohub-home-content.yml

@@ -87,7 +87,7 @@
     - title: Promotion building blocks
       localurl: /gitops/promotions/promotion-components/
     - title: Promotion setup guidelines
-      localurl: /gitops/promotions/create-promotion-sequence/
+      localurl: /gitops/promotions/create-promotion-sequence/   
     - title: YAML specs
       localurl: /gitops/promotions/yaml/
     - title: Triggering promotions

_data/argohub-nav.yml

@@ -260,10 +260,10 @@
       url: "/promotion-policy"  
     - title: Promotion Workflows
       url: "/promotion-workflow"
-    - title: Service accounts for Promotion Workflows
-      url: "/service-accounts-promotion-workflows"      
     - title: Promotion hooks
-      url: "/promotion-hooks"          
+      url: "/promotion-hooks"     
+    - title: Service accounts for Promotion Workflows
+      url: "/service-accounts-promotion-workflows"                     
     - title: Promotion contexts in promotion hooks
       url: "/promotion-context-promotion-workflows"     
     - title: Product promotion settings

_docs/promotions/promotion-context-promotion-workflows.md

@@ -23,7 +23,8 @@ A **promotion context** is a user-defined JSON object that allows you to pass cu
 Defining a promotion context with the custom parameters and then **exporting the context** makes these custom values available to all subsequent hooks in the same Promotion Flow. Each hook can access and use the values from the promotion context as needed.  
 Using promotion contexts enables scenarios like notifying specific Slack channels or linking Jira tickets to releases. See [How promotion context works during execution](#how-promotion-context-works-during-execution).  
 
-To see a practical example, follow the [Walkthrough: Using promotion hooks in Promotion Flows to handle promotion failures](#walkthough-using-promotion-hooks-in-promotion-flows-to-handle-promotion-failures), where you create different Promotion Workflows with hooks, define a promotion context in a workflow, and assign hooks at different stages of the Promotion Flow.
+To see a practical example, follow the [Walkthrough: Using promotion hooks in Promotion Flows to handle promotion failures](#walkthrough-using-promotion-hooks-in-promotion-flows-to-handle-promotion-failures), where you create different Promotion Workflows with hooks, define a promotion context in a workflow, and assign hooks at different stages of the Promotion Flow.
+
 
 
 ## Creating and exporting a promotion context 

_docs/promotions/promotion-hooks.md

@@ -57,7 +57,8 @@ See [Assigning promotion hooks in Promotion Flows](#assigning-promotion-hooks-in
 Explore examples in [Codefresh Hub for Argo](https://codefresh.io/argohub/){:target="\_blank"}.
 
 ##### Arguments in promotion hooks
-A default set of arguments are available to all Promotion Workflows with hooks. See [Default arguments in Promotion Workflows with hooks](#default-arguments-for-promotion-hooks).
+A default set of arguments are available to all Promotion Workflows with hooks. See [Default arguments in Promotion Workflows with hooks](#default-arguments-in-promotion-workflows-with-hooks).
+
 
 ## Promotion hooks vs. Pre- and Post-Action Promotion Workflows
 
@@ -97,7 +98,9 @@ The table below describes the default arguments that are replaced with values th
 |`FAILED_ENVIRONMENTS` | The environment or environments which failed in the release with this information: {::nomarkdown}<ul><li><b>Name</b>: The name of the environment that failed to complete the release. For example, production</li><li><b>Status</b>: The release or promotion status for the environment. Can be one of the following: <ul><li>Successful</li><li>Running</li><li>Suspended</li><li>Failed</li><li>Terminated</li></ul></li><li><b>Error-message</b>: The system-generated error message identifying the reason for the failed promotion. For example, <code class="highlighter-rouge">Product release was automatically terminated because the workflow state remained unknown</code>. {:/}| OnFailed hooks only  | 
 
 ## Promotion contexts in Promotion Workflows with hooks
-In a Promotion Flow, hooks may need custom parameters beyond the default ones available to the promotion mechanism. Because promotion hooks run within GitOps Runtimes in your own clusters, they do not automatically have access to these custom internal parameters. To pass custom values like Jira ticket IDs, approver names, or Slack channel information between hooks in the same Promotion Flow, you must define and export a promotion context. For details, see [Creating and exporting a promotion context](#creating-and-exporting-a-promotion-context).
+
+In a Promotion Flow, hooks may need custom parameters beyond the default ones available to the promotion mechanism. Because promotion hooks run within GitOps Runtimes in your own clusters, they do not automatically have access to these custom internal parameters. To pass custom values like Jira ticket IDs, approver names, or Slack channel information between hooks in the same Promotion Flow, you must define and export a promotion context. For details, see [Promotion contexts in promotion hooks]({{site.baseurl}}/docs/promotions/promotion-context-promotion-workflows/).
+
 
 
 ## Service accounts for promotion hooks
@@ -293,6 +296,8 @@ You cannot assign a Promotion Hook Workflow to the Trigger Environment itself.
 
 ## Related articles
 [Configure Promotion Flows]({{site.baseurl}}/docs/promotions/promotion-flow/)  
+[Promotion contexts in promotion hooks]({{site.baseurl}}/docs/promotions/promotion-context-promotion-workflows/)  
+[Service accounts for Promotion Workflows]({{site.baseurl}}/docs/promotions/service-accounts-promotion-workflows/)  
 [Configure Promotion Workflows]({{site.baseurl}}/docs/promotions/promotion-workflow/)  
 [Promotion Flow YAML]({{site.baseurl}}/docs/promotions/yaml/promotion-flow-crd/)  
 [Tracking product releases]({{site.baseurl}}/docs/promotions/product-releases/)