fix broken links

Signed-off-by: nikki everett <[email protected]>

docs/docs-beta/docs/dagster-plus/deployment/code-locations/code-location-history.md

@@ -54,4 +54,4 @@ If you notice an issue with newly deployed code, or your code fails to deploy su
 ## Next steps
 
 - Learn more about [Code Locations](/dagster-plus/deployment/code-locations)
-- Learn how to [Alert when a code location fails to load](/dagster-plus/deployment/alerts#alerting-when-a-code-location-fails-to-load)
+- Learn how to [Alert when a code location fails to load](/dagster-plus/features/alerts#alerting-when-a-code-location-fails-to-load)

docs/docs-beta/docs/dagster-plus/deployment/hybrid/agents/kubernetes.md

@@ -95,7 +95,7 @@ An exhaustive list of settings is available [here](/dagster-plus/deployment/hybr
 
 ### Configure your agents to serve branch deployments
 
-[Branch deployments](/dagster-plus/deployment/branch-deployments) are lightweight staging environments created for each code change. To configure your Dagster+ agent to manage them:
+[Branch deployments](/dagster-plus/features/branch-deployments) are lightweight staging environments created for each code change. To configure your Dagster+ agent to manage them:
 
 ```yaml
 # values.yaml

docs/docs-beta/docs/dagster-plus/deployment/hybrid/index.md

@@ -40,7 +40,7 @@ When you inform Dagster+ about a new code location, we enqueue instructions for
 
 ### Runs
 
-Your definitions might include [automations](/guides/automation) that launch runs or materialize assets. Or your developers might launch runs directly with the web UI.
+Your definitions might include [automations](/guides/automate) that launch runs or materialize assets. Or your developers might launch runs directly with the web UI.
 
 When a run needs to be launched, Dagster+ enqueues instructions for your agent to launch a new run. The next time your agent polls Dagster+ for new work, it will see instructions about how to launch your run. It will delegate those instructions to your code server and your code server will launch a run - a new run will typically require its own container.
 

docs/docs-beta/docs/dagster-plus/deployment/serverless/ci-cd-in-serverless.md

@@ -6,12 +6,12 @@ sidebar_position: 300
 
 # CI/CD in Serverless
 
-If you're a GitHub or GitLab user, you can use our predefined workflows to seamlessly deploy and synchronize your code to Dagster+. You can also use other Git providers or a local Git repository with our [dagster-cloud CLI](/dagster-plus/deployment/branch-deployments/dagster-cloud-cli) to run your own CI/CD process.
+If you're a GitHub or GitLab user, you can use our predefined workflows to seamlessly deploy and synchronize your code to Dagster+. You can also use other Git providers or a local Git repository with our [dagster-cloud CLI](/dagster-plus/features/branch-deployments/dagster-cloud-cli) to run your own CI/CD process.
 
 <Tabs groupId="method">
 <TabItem value="GitHub" label="With GitHub">
 
-If you're a GitHub user, with a single click our GitHub app with GitHub Actions can set up a repo containing skeleton code and configuration for you consistent with Dagster+'s best practices. Pushing your code changes to the `main` branch will automatically deploy them to your `prod` Serverless deployment. Pull requests will spin up ephemeral [branch deployments](/dagster-plus/deployment/branch-deployments) that you can view in the Dagster+ UI for previewing and testing.
+If you're a GitHub user, with a single click our GitHub app with GitHub Actions can set up a repo containing skeleton code and configuration for you consistent with Dagster+'s best practices. Pushing your code changes to the `main` branch will automatically deploy them to your `prod` Serverless deployment. Pull requests will spin up ephemeral [branch deployments](/dagster-plus/features/branch-deployments) that you can view in the Dagster+ UI for previewing and testing.
 
 :::note
 **If you are importing a Dagster project that's in an existing GitHub repo:**
@@ -28,13 +28,13 @@ If you're a GitHub user, with a single click our GitHub app with GitHub Actions
 
 <TabItem value="GitLab" label="With GitLab">
 
-If you're a GitLab user, with a single click our GitLab app can set up a repo containing skeleton code and CI/CD configuration for you consistent with Dagster+'s best practices. Pushing your code changes to the `main` branch will automatically deploy them to your `prod` Serverless deployment. Pull requests will spin up ephemeral [branch deployments](/dagster-plus/deployment/branch-deployments) that you can view in the Dagster+ UI for previewing and testing.
+If you're a GitLab user, with a single click our GitLab app can set up a repo containing skeleton code and CI/CD configuration for you consistent with Dagster+'s best practices. Pushing your code changes to the `main` branch will automatically deploy them to your `prod` Serverless deployment. Pull requests will spin up ephemeral [branch deployments](/dagster-plus/features/branch-deployments) that you can view in the Dagster+ UI for previewing and testing.
 
 </TabItem>
 
 <TabItem value="Other" label="Other Git providers or local development">
 
-If you don't want to use our automated GitHub/GitLab process, we offer [the powerful `dagster-cloud` command-line interface (CLI)](/dagster-plus/deployment/branch-deployments/dagster-cloud-cli) that you can use in another CI environment or locally.
+If you don't want to use our automated GitHub/GitLab process, we offer [the powerful `dagster-cloud` command-line interface (CLI)](/dagster-plus/features/branch-deployments/dagster-cloud-cli) that you can use in another CI environment or locally.
 
 First, [create a new project](/getting-started/quickstart) with the Dagster open source CLI.
 
@@ -62,7 +62,7 @@ install_requires=[
 
 :::
 
-Next, install the [`dagster-cloud` CLI](/dagster-plus/deployment/branch-deployments/dagster-cloud-cli) and use its `configure` command to authenticate it to your Dagster+ organization.
+Next, install the [`dagster-cloud` CLI](/dagster-plus/features/branch-deployments/dagster-cloud-cli) and use its `configure` command to authenticate it to your Dagster+ organization.
 
 **Note:** The CLI requires a recent version of Python 3 and Docker.
 
@@ -71,7 +71,7 @@ pip install dagster-cloud
 dagster-cloud configure
 ```
 
-You can also configure the `dagster-cloud` tool non-interactively; see [the CLI docs](/dagster-plus/deployment/branch-deployments/dagster-cloud-cli) for more information.
+You can also configure the `dagster-cloud` tool non-interactively; see [the CLI docs](/dagster-plus/features/branch-deployments/dagster-cloud-cli) for more information.
 
 Finally, deploy your project to Dagster+ using the `serverless` command:
 

docs/docs-beta/docs/dagster-plus/deployment/serverless/run-isolation.md

@@ -15,7 +15,7 @@ Dagster+ Serverless offers two settings for run isolation: isolated and non-isol
 To follow the steps in this guide, you'll need:
 
 - An active Dagster+ Serverless deployment
-- An understanding of [Dagster+ deployment settings](/dagster-plus/deployment/settings)
+- An understanding of [Dagster+ deployment settings](/dagster-plus/deployment/deployment-settings)
 </details>
 
 ---
@@ -57,7 +57,7 @@ While launching runs from the Launchpad, un-check `Isolate run environment`. Whe
 
 To avoid crashes and memory exhaustion, only one non-isolated run will execute at once by default. While a non-isolated run is in progress, the Launchpad will only allow isolated runs to be launched.
 
-This limit can be configured in [deployment settings](/dagster-plus/deployment/settings).
+This limit can be configured in [deployment settings](/dagster-plus/deployment/deployment-settings).
 
 ```yaml
 non_isolated_runs:

docs/docs-beta/docs/dagster-plus/deployment/serverless/security.md

@@ -24,11 +24,11 @@ The default I/O manager cannot be used if you are a Serverless user who:
 - Are otherwise working with data subject to GDPR or other such regulations
   :::
 
-In Serverless, code that uses the default [I/O manager](/guides/io-managers) is automatically adjusted to save data in Dagster+ managed storage. This automatic change is useful because the Serverless filesystem is ephemeral, which means the default I/O manager wouldn't work as expected.
+In Serverless, code that uses the default [I/O manager](/guides/build/configure/io-managers) is automatically adjusted to save data in Dagster+ managed storage. This automatic change is useful because the Serverless filesystem is ephemeral, which means the default I/O manager wouldn't work as expected.
 
 However, this automatic change also means potentially sensitive data could be **stored** and not just processed or orchestrated by Dagster+.
 
-To prevent this, you can use [another I/O manager](/guides/io-managers#built-in) that stores data in your infrastructure or [adapt your code to avoid using an I/O manager](/guides/io-managers#before-you-begin).
+To prevent this, you can use [another I/O manager](/guides/build/configure/io-managers#built-in) that stores data in your infrastructure or [adapt your code to avoid using an I/O manager](/guides/build/configure/io-managers#before-you-begin).
 
 :::note
 You must have [boto3](https://pypi.org/project/boto3/) or `dagster-cloud[serverless]` installed as a project dependency otherwise the Dagster+ managed storage can fail and silently fall back to using the default I/O manager.

docs/docs-beta/docs/dagster-plus/features/alerts/index.md

@@ -3,7 +3,7 @@ title: Setting up alerts on Dagster+
 sidebar_label: "Dagster+ Alerts"
 sidebar_position: 30
 ---
-[comment]: <> (This file is automatically generated by `dagster-plus/deployment/alerts/generate_alerts_doc.py`)
+[comment]: <> (This file is automatically generated by `dagster-plus/features/alerts/generate_alerts_doc.py`)
 
 Dagster+ allows you to configure alerts to automatically fire in response to a range of events. These alerts can be sent to a variety of different services, depending on your organization's needs.
 
@@ -80,16 +80,16 @@ If desired, add **tags** in the format `{key}:{value}` to filter the runs that w
   ```
   <Tabs groupId="notification_service">
     <TabItem value='email' label='Email'>
-      <CodeExample filePath="dagster-plus/deployment/alerts/schedule-sensor-failure-email.yaml" language="yaml" />
+      <CodeExample filePath="dagster-plus/features/alerts/schedule-sensor-failure-email.yaml" language="yaml" />
     </TabItem>
     <TabItem value='microsoft_teams' label='Microsoft Teams'>
-      <CodeExample filePath="dagster-plus/deployment/alerts/schedule-sensor-failure-microsoft_teams.yaml" language="yaml" />
+      <CodeExample filePath="dagster-plus/features/alerts/schedule-sensor-failure-microsoft_teams.yaml" language="yaml" />
     </TabItem>
     <TabItem value='pagerduty' label='PagerDuty'>
-      <CodeExample filePath="dagster-plus/deployment/alerts/schedule-sensor-failure-pagerduty.yaml" language="yaml" />
+      <CodeExample filePath="dagster-plus/features/alerts/schedule-sensor-failure-pagerduty.yaml" language="yaml" />
     </TabItem>
     <TabItem value='slack' label='Slack'>
-      <CodeExample filePath="dagster-plus/deployment/alerts/schedule-sensor-failure-slack.yaml" language="yaml" />
+      <CodeExample filePath="dagster-plus/features/alerts/schedule-sensor-failure-slack.yaml" language="yaml" />
     </TabItem>
   </Tabs>
 
@@ -120,16 +120,16 @@ If desired, add **tags** in the format `{key}:{value}` to filter the runs that w
   ```
   <Tabs groupId="notification_service">
     <TabItem value='email' label='Email'>
-      <CodeExample filePath="dagster-plus/deployment/alerts/job-running-over-one-hour-email.yaml" language="yaml" />
+      <CodeExample filePath="dagster-plus/features/alerts/job-running-over-one-hour-email.yaml" language="yaml" />
     </TabItem>
     <TabItem value='microsoft_teams' label='Microsoft Teams'>
-      <CodeExample filePath="dagster-plus/deployment/alerts/job-running-over-one-hour-microsoft_teams.yaml" language="yaml" />
+      <CodeExample filePath="dagster-plus/features/alerts/job-running-over-one-hour-microsoft_teams.yaml" language="yaml" />
     </TabItem>
     <TabItem value='pagerduty' label='PagerDuty'>
-      <CodeExample filePath="dagster-plus/deployment/alerts/job-running-over-one-hour-pagerduty.yaml" language="yaml" />
+      <CodeExample filePath="dagster-plus/features/alerts/job-running-over-one-hour-pagerduty.yaml" language="yaml" />
     </TabItem>
     <TabItem value='slack' label='Slack'>
-      <CodeExample filePath="dagster-plus/deployment/alerts/job-running-over-one-hour-slack.yaml" language="yaml" />
+      <CodeExample filePath="dagster-plus/features/alerts/job-running-over-one-hour-slack.yaml" language="yaml" />
     </TabItem>
   </Tabs>
 
@@ -160,16 +160,16 @@ If desired, select a **target** from the dropdown menu to scope this alert to a
   ```
   <Tabs groupId="notification_service">
     <TabItem value='email' label='Email'>
-      <CodeExample filePath="dagster-plus/deployment/alerts/schedule-sensor-failure-email.yaml" language="yaml" />
+      <CodeExample filePath="dagster-plus/features/alerts/schedule-sensor-failure-email.yaml" language="yaml" />
     </TabItem>
     <TabItem value='microsoft_teams' label='Microsoft Teams'>
-      <CodeExample filePath="dagster-plus/deployment/alerts/schedule-sensor-failure-microsoft_teams.yaml" language="yaml" />
+      <CodeExample filePath="dagster-plus/features/alerts/schedule-sensor-failure-microsoft_teams.yaml" language="yaml" />
     </TabItem>
     <TabItem value='pagerduty' label='PagerDuty'>
-      <CodeExample filePath="dagster-plus/deployment/alerts/schedule-sensor-failure-pagerduty.yaml" language="yaml" />
+      <CodeExample filePath="dagster-plus/features/alerts/schedule-sensor-failure-pagerduty.yaml" language="yaml" />
     </TabItem>
     <TabItem value='slack' label='Slack'>
-      <CodeExample filePath="dagster-plus/deployment/alerts/schedule-sensor-failure-slack.yaml" language="yaml" />
+      <CodeExample filePath="dagster-plus/features/alerts/schedule-sensor-failure-slack.yaml" language="yaml" />
     </TabItem>
   </Tabs>
 
@@ -200,16 +200,16 @@ If desired, select a **target** from the dropdown menu to scope this alert to a
   ```
   <Tabs groupId="notification_service">
     <TabItem value='email' label='Email'>
-      <CodeExample filePath="dagster-plus/deployment/alerts/asset-check-failed-email.yaml" language="yaml" />
+      <CodeExample filePath="dagster-plus/features/alerts/asset-check-failed-email.yaml" language="yaml" />
     </TabItem>
     <TabItem value='microsoft_teams' label='Microsoft Teams'>
-      <CodeExample filePath="dagster-plus/deployment/alerts/asset-check-failed-microsoft_teams.yaml" language="yaml" />
+      <CodeExample filePath="dagster-plus/features/alerts/asset-check-failed-microsoft_teams.yaml" language="yaml" />
     </TabItem>
     <TabItem value='pagerduty' label='PagerDuty'>
-      <CodeExample filePath="dagster-plus/deployment/alerts/asset-check-failed-pagerduty.yaml" language="yaml" />
+      <CodeExample filePath="dagster-plus/features/alerts/asset-check-failed-pagerduty.yaml" language="yaml" />
     </TabItem>
     <TabItem value='slack' label='Slack'>
-      <CodeExample filePath="dagster-plus/deployment/alerts/asset-check-failed-slack.yaml" language="yaml" />
+      <CodeExample filePath="dagster-plus/features/alerts/asset-check-failed-slack.yaml" language="yaml" />
     </TabItem>
   </Tabs>
 
@@ -235,16 +235,16 @@ Alerts are sent only when a schedule/sensor transitions from **success** to **fa
   ```
   <Tabs groupId="notification_service">
     <TabItem value='email' label='Email'>
-      <CodeExample filePath="dagster-plus/deployment/alerts/schedule-sensor-failure-email.yaml" language="yaml" />
+      <CodeExample filePath="dagster-plus/features/alerts/schedule-sensor-failure-email.yaml" language="yaml" />
     </TabItem>
     <TabItem value='microsoft_teams' label='Microsoft Teams'>
-      <CodeExample filePath="dagster-plus/deployment/alerts/schedule-sensor-failure-microsoft_teams.yaml" language="yaml" />
+      <CodeExample filePath="dagster-plus/features/alerts/schedule-sensor-failure-microsoft_teams.yaml" language="yaml" />
     </TabItem>
     <TabItem value='pagerduty' label='PagerDuty'>
-      <CodeExample filePath="dagster-plus/deployment/alerts/schedule-sensor-failure-pagerduty.yaml" language="yaml" />
+      <CodeExample filePath="dagster-plus/features/alerts/schedule-sensor-failure-pagerduty.yaml" language="yaml" />
     </TabItem>
     <TabItem value='slack' label='Slack'>
-      <CodeExample filePath="dagster-plus/deployment/alerts/schedule-sensor-failure-slack.yaml" language="yaml" />
+      <CodeExample filePath="dagster-plus/features/alerts/schedule-sensor-failure-slack.yaml" language="yaml" />
     </TabItem>
   </Tabs>
 
@@ -268,16 +268,16 @@ You can set up alerts to fire when any code location fails to load due to an err
   ```
   <Tabs groupId="notification_service">
     <TabItem value='email' label='Email'>
-      <CodeExample filePath="dagster-plus/deployment/alerts/code-location-error-email.yaml" language="yaml" />
+      <CodeExample filePath="dagster-plus/features/alerts/code-location-error-email.yaml" language="yaml" />
     </TabItem>
     <TabItem value='microsoft_teams' label='Microsoft Teams'>
-      <CodeExample filePath="dagster-plus/deployment/alerts/code-location-error-microsoft_teams.yaml" language="yaml" />
+      <CodeExample filePath="dagster-plus/features/alerts/code-location-error-microsoft_teams.yaml" language="yaml" />
     </TabItem>
     <TabItem value='pagerduty' label='PagerDuty'>
-      <CodeExample filePath="dagster-plus/deployment/alerts/code-location-error-pagerduty.yaml" language="yaml" />
+      <CodeExample filePath="dagster-plus/features/alerts/code-location-error-pagerduty.yaml" language="yaml" />
     </TabItem>
     <TabItem value='slack' label='Slack'>
-      <CodeExample filePath="dagster-plus/deployment/alerts/code-location-error-slack.yaml" language="yaml" />
+      <CodeExample filePath="dagster-plus/features/alerts/code-location-error-slack.yaml" language="yaml" />
     </TabItem>
   </Tabs>
 
@@ -305,16 +305,16 @@ You can set up alerts to fire if your Hybrid agent hasn't sent a heartbeat in th
   ```
   <Tabs groupId="notification_service">
     <TabItem value='email' label='Email'>
-      <CodeExample filePath="dagster-plus/deployment/alerts/code-location-error-email.yaml" language="yaml" />
+      <CodeExample filePath="dagster-plus/features/alerts/code-location-error-email.yaml" language="yaml" />
     </TabItem>
     <TabItem value='microsoft_teams' label='Microsoft Teams'>
-      <CodeExample filePath="dagster-plus/deployment/alerts/code-location-error-microsoft_teams.yaml" language="yaml" />
+      <CodeExample filePath="dagster-plus/features/alerts/code-location-error-microsoft_teams.yaml" language="yaml" />
     </TabItem>
     <TabItem value='pagerduty' label='PagerDuty'>
-      <CodeExample filePath="dagster-plus/deployment/alerts/code-location-error-pagerduty.yaml" language="yaml" />
+      <CodeExample filePath="dagster-plus/features/alerts/code-location-error-pagerduty.yaml" language="yaml" />
     </TabItem>
     <TabItem value='slack' label='Slack'>
-      <CodeExample filePath="dagster-plus/deployment/alerts/code-location-error-slack.yaml" language="yaml" />
+      <CodeExample filePath="dagster-plus/features/alerts/code-location-error-slack.yaml" language="yaml" />
     </TabItem>
   </Tabs>