docs(alerts): move alert creation to its own page

docs/product/monitors-and-alerts/alerts/index.mdx

@@ -1,6 +1,6 @@
 ---
 title: Alerts
-description: Use Alerts to notify or take action on important issues. 
+description: Use Alerts to notify or take action on important issues.
 sidebar_order: 60
 og_image: /og-images/product-alerts.png
 ---
@@ -15,29 +15,19 @@ Sentry's **Alerts** take action when issues in your organization match pre-defin
 
 ![alert-config =800x](./img/alert-details.png)
 
-## Creating an Alert
+## Creating Alerts
 
-<Arcade src="https://demo.arcade.software/yXRDN2qTVqtedkfpQIbB?embed" />
+You can create an Alert from **Monitors > [Alerts](https://sentry.io/monitors/alerts)**. When creating an Alert, you'll configure the issue sources, event triggers, filters, actions, and Alert throttling.
 
-To create an Alert, go to the [Alerts](https://sentry.io/monitors/alerts) page in Sentry and click **Create Alert**.
+For an in-depth walkthrough of each setting, see [Creating an Alert](/product/monitors-and-alerts/alerts/create-alerts/).
 
-### Select Sources and Environments
-
-The source of an Alert can be one or more Projects, or one or more Monitors. After you choose sources, pick which **environment(s)** the alert evaluates. By default, alerts run across all environments.
-
-### Set Triggers
-
-A trigger is an action that must occur for the Alert to run. All trigger actions are issue state based. For example, you may want to send a notification to your team's Slack channel _when an issue is created_. You can select multiple triggers in a single Alert. They will run under an `ANY` condition, meaning that if any one of the triggers happen, the Alert will run.
-
-### Set Filters
-
-Filters are conditions that must be met for the Alert to run. For example, you may want to create a ticket _only for issues that are assigned to a specific team_ and _at a certain severity_. You can create multiple filters in a single Alert, and group them under either `ANY` or `ALL` conditions. For `ANY` conditions, if any one of the filters are true, the Alert will run. For `ALL` conditions, only if all of the filters are true, the Alert will run.
+<Alert>
 
-### Add Actions
+Alerts are an Organization-level feature. Org Owners, Org Managers, Org Admins, and Team Admins can always create and edit Alerts. Org Members and Team Contributors can too, as long as **Let Members Create and Edit Monitors and Alerts** is enabled (the default) in your [organization settings](https://sentry.io/settings/organization/). Alerts scoped to all projects are restricted to Org Owners and Org Managers.
 
-Actions run when triggers and filters match. Depending on your integrations, actions can include chat notifications (Slack, Microsoft Teams, Discord), email, on-call tools (PagerDuty, Opsgenie), issue trackers (Jira, Azure DevOps, Linear), webhooks, and [integrations](/integrations/integration-platform/).
+</Alert>
 
-**Note:** Some integrations are only available for certain sources or issue types. Check [Integrations](/integrations/) for your workspace.
+Available actions depend on the [integrations](/integrations/) installed in your organization, and some integrations are only available for certain sources or issue types.
 
 ### When to Notify the Team
 
@@ -51,12 +41,6 @@ Using Alerts with custom filters allows you to notify the team about critical is
 
 You can see a list of all your Alerts on the [Alerts](https://sentry.io/monitors/alerts) page. By default, Alerts are filtered down to your projects.
 
-<Alert>
-
-Alerts are an Organization-level feature. By default, all team members can create and edit Alerts. You can update this setting in [Organization Membership settings](https://sentry.io/settings/organization/).
-
-</Alert>
-
 By clicking on an Alert, you can view the details, edit the Alert, or turn it on or off.
 
 The details page will show a high level chart of how often the Alert has run, a list of the most recent runs, the configuration, and connected monitors.
@@ -66,10 +50,15 @@ The details page will show a high level chart of how often the Alert has run, a
 The main goal is to create Alerts that are valuable and not too noisy.
 
 Here are some quick tips:
+
 - Use filters to narrow down the issues that are critical for to your team to be notified about.
 - Select only the triggers that matter for Alerting actions. For example, you may want to create a Jira ticket any time an issue is created, but only be notified in Slack when an issue is a certain severity.
-- Consider how your team works in terms of triaging. For example, do you want individual alerts routing to specific project, or service channels, or one alert to catch them all in a team channel? 
+- Consider how your team works in terms of triaging. For example, do you want individual alerts routing to specific project, or service channels, or one alert to catch them all in a team channel?
 
 ## Sentry Notifications
 
 Besides Alerts, Sentry sends you notifications about various things like [issue state changes](/product/issues/states-triage/), [release deploys](/product/releases/), and [quota usage](/pricing/quotas/). You can fine-tune these notifications, as well as your personal alert settings, in **User Settings > Notifications**. Learn more about notifications and adjusting their associated settings in [the full documentation](/product/notifications/).
+
+## Learn More
+
+<PageGrid />

docs/product/monitors-and-alerts/index.mdx

@@ -14,7 +14,7 @@ Sentry separates **what you detect** from **what you do about it**:
 
 Using both Monitors and Alerts gives you a path from signal → triageable issue → team workflow, without wiring every integration by hand for every edge case.
 
-For a concise **Issues-centric** explanation (how this shows up in your triage flow), see [Monitors and Alerts](/product/issues/monitors-and-alerts/). For **hands-on setup**, see [Creating an Alert](/product/monitors-and-alerts/alerts/#creating-an-alert).
+For a concise **Issues-centric** explanation (how this shows up in your triage flow), see [Monitors and Alerts](/product/issues/monitors-and-alerts/). For **hands-on setup**, see [Creating an Alert](/product/monitors-and-alerts/alerts/create-alerts/).
 
 ## End-to-End Flow
 

docs/product/monitors-and-alerts/monitors/crons/job-monitoring.mdx

@@ -32,7 +32,7 @@ To monitor the same job in different environments, use a shared schedule to send
 
 ### Alerting on Specific Environments
 
-To only receive failing or missed monitor notifications for a specific environment or set of environments, scope your **[Alert](/product/monitors-and-alerts/alerts/)** sources and **environments** to match the check-in you care about, and use filters (for example on tags such as `monitor.slug`) where needed. See [Select Sources and Environments](/product/monitors-and-alerts/alerts/#select-sources-and-environments). For how the check-in `environment` is sent, see your SDK [environment configuration](/platform-redirect/?next=/configuration/environments/).
+To only receive failing or missed monitor notifications for a specific environment or set of environments, scope your **[Alert](/product/monitors-and-alerts/alerts/)** sources and **environments** to match the check-in you care about, and use filters (for example on tags such as `monitor.slug`) where needed. See [Select a Source](/product/monitors-and-alerts/alerts/create-alerts/#step-1-select-a-source). For how the check-in `environment` is sent, see your SDK [environment configuration](/platform-redirect/?next=/configuration/environments/).
 
 ### Existing Limitations:
 

docs/product/monitors-and-alerts/monitors/uptime-monitoring/index.mdx

@@ -95,7 +95,7 @@ Uptime checks include spans called _uptime request spans_ that Sentry automatica
 
 ## Notifications
 
-To start getting notifications for a new downtime issue, [configure an Alert](/product/monitors-and-alerts/alerts/#creating-an-alert) that matches outage / downtime issues and add actions for email, Slack, on-call tools, or other integrations.
+To start getting notifications for a new downtime issue, [configure an Alert](/product/monitors-and-alerts/alerts/create-alerts/) that matches outage / downtime issues and add actions for email, Slack, on-call tools, or other integrations.
 
 ![Uptime alert configuration](./img/uptime-alert.png)
 

docs/product/monitors-and-alerts/monitors/uptime-monitoring/troubleshooting.mdx

@@ -24,4 +24,4 @@ See [IP Ranges](/security-legal-pii/security/ip-ranges/#uptime-monitoring) for a
 
 ## Verify That Alerts Match Downtime Issues
 
-Uptime monitors create downtime issues. If you're not receiving notifications when downtimes are detected, make sure you've [configured an Alert](/product/monitors-and-alerts/alerts/#creating-an-alert) whose sources and filters match those issues, with actions for the channels you expect.
+Uptime monitors create downtime issues. If you're not receiving notifications when downtimes are detected, make sure you've [configured an Alert](/product/monitors-and-alerts/alerts/create-alerts/) whose sources and filters match those issues, with actions for the channels you expect.

redirects.js

@@ -2994,19 +2994,19 @@ const userDocsRedirects = [
   },
   {
     source: '/product/alerts/create-alerts/',
-    destination: '/product/monitors-and-alerts/alerts/',
+    destination: '/product/monitors-and-alerts/alerts/create-alerts/',
   },
   {
     source: '/product/alerts/create-alerts/issue-alert-config/',
-    destination: '/product/monitors-and-alerts/alerts/',
+    destination: '/product/monitors-and-alerts/alerts/create-alerts/',
   },
   {
     source: '/product/alerts/create-alerts/metric-alert-config/',
     destination: '/product/monitors-and-alerts/monitors/',
   },
   {
     source: '/product/alerts/create-alerts/routing-alerts/',
-    destination: '/product/monitors-and-alerts/alerts/',
+    destination: '/product/monitors-and-alerts/alerts/create-alerts/',
   },
   {
     source: '/product/alerts/create-alerts/uptime-alert-config/',