Merge pull request #2627 from OctopusDeploy/ellen/project-triggers

Project Triggers documentation updates

Author: ellen-octopus

public/docs/projects/project-triggers/images/octopus-triggers-diagram.png

@@ -8,11 +8,7 @@ description: Built-in package repository triggers allows you to automatically cr
 navOrder: 15
 ---
 
-:::div{.hint}
-**Built-in package repository triggers were formerly known as Automatic Release Creation**
-
-We have renamed the feature and refreshed the UI, but it still works the same way behind the scenes.
-:::
+Formerly known as ***Automatic Release Creation***. Functionality remains the same.
 
 ## Getting started {#BuiltInPackageRepositoryTriggers-GettingStarted}
 

src/pages/docs/projects/project-triggers/built-in-package-repository-triggers.md

@@ -1,21 +1,30 @@
 ---
 layout: src/layouts/Default.astro
 pubDate: 2023-01-01
-modDate: 2024-08-28
+modDate: 2025-02-14
 title: Project triggers
 icon: fa-solid fa-flag
 description: Project Triggers allow you to define unattended behavior for your project such as automatically deploying a release to an environment.
 navOrder: 90
 ---
 
-Project triggers allow you to define an unattended behavior for your [projects](/docs/projects).
+Project triggers allow you to automate your deployments by responding to events, for example, changes in your deployment targets or time-based schedules.
 
-Project triggers allow you to choose from a subset of **events** that can occur in Octopus Deploy, apply a **filter** to those events, and decide on an **action** you want performed once the trigger fires. The example below shows an automatic deployment trigger configured to fire when a [deployment target](/docs/infrastructure/) that belongs to the **Production** [environment](/docs/infrastructure/environments) becomes available, and has the **web-server** [target tag](/docs/infrastructure/deployment-targets/target-tags).
+Choose from a subset of **events** that can occur in Octopus Deploy, apply a **filter** to those events, and decide what **action** you want performed after the trigger fires.
+
+## Trigger example
+
+The example below is an automatic deployment trigger that fires when a [deployment target](/docs/infrastructure/) that belongs to the **Production** [environment](/docs/infrastructure/environments) becomes available and is tagged with the **web-server** [target tag](/docs/infrastructure/deployment-targets/target-tags).
 
 :::figure
 ![](/docs/projects/project-triggers/images/octopus-triggers-diagram.png)
 :::
 
-:::div{.success}
-We have written a [comprehensive guide](/docs/deployments/patterns/elastic-and-transient-environments) about using project triggers with a focus on deploying to elastic and transient environments.
-:::
+## Types of triggers
+
+- [Git repository triggers](/docs/projects/project-triggers/git-triggers): specify Git repositories to be monitored for new commits that will automatically trigger a release of your project.
+- [Deployment target triggers](/docs/projects/project-triggers/deployment-target-triggers): specify which events on your deployment targets will automatically trigger a release of your project.
+- [Scheduled deployment triggers](/docs/projects/project-triggers/scheduled-deployment-trigger): define a recurring time-based schedule to automate deploying releases for your project.
+- [External feed triggers](/docs/projects/project-triggers/external-feed-triggers): specify container images or Helm charts that will automatically trigger a release of your project.
+- [Built-in package repository triggers](/docs/projects/project-triggers/built-in-package-repository-triggers): specify which package updates from the built-in package repository will automatically trigger a release of your project.
+