docs(misc): remove outdated Angular multiple-workspace migration page (#34913)

## Current Behavior
The "Migrating Multiple Angular CLI Workspaces" page is a 26-line stub
with only a YouTube video. It doesn't mention `nx import` and contains
outdated guidance. The single-workspace migration guide (`angular.mdoc`)
also has outdated sections: a list of supported builders, a full CI
setup walkthrough, an irrelevant "From Nx Console" section, and a
reference to `karma.conf.js`.

## Expected Behavior
- The `angular-multiple.mdoc` page is removed with a redirect to the
main Angular migration guide.
- The main migration guide mentions `nx import` for consolidating
multiple Angular CLI projects.
- Outdated sections (Modified folder structure, Set up CI, From Nx
Console) are removed and replaced with concise links.
- The `nx-and-angular.mdoc` guide links to `nx import` docs instead of
the deleted page.

Preview:
https://deploy-preview-34913--nx-docs.netlify.app/docs/technologies/angular/migration/angular-multiple
(redirects to the updated page)


## Related Issue(s)
Closes DOC-419

Author: jaysoo

astro-docs/netlify.toml

@@ -49,6 +49,11 @@ to = "/docs/extending-nx/create-preset"
 from = "/docs/guides/adopting-nx/adding-to-monorepos"
 to = "/docs/guides/adopting-nx/adding-to-monorepo"
 
+# Angular multiple workspace migration page removed (DOC-419)
+[[redirects]]
+from = "/docs/technologies/angular/migration/angular-multiple"
+to = "/docs/technologies/angular/migration/angular"
+
 # Rewrite for base path handling (keeps URL the same)
 [[redirects]]
 from = "/docs/*"

astro-docs/src/content/docs/technologies/angular/Guides/nx-and-angular.mdoc

@@ -412,7 +412,7 @@ npx nx@latest init
 
 or alternatively using the `--integrated` flag if you want to create an Nx monorepo right away. Learn more about all the details on the [dedicated docs page](/docs/technologies/angular/migration/angular).
 
-There is also a guide describing how to [consolidate multiple Angular CLI projects into a single Nx monorepo](/docs/technologies/angular/migration/angular-multiple).
+You can also use [`nx import`](/docs/guides/adopting-nx/import-project) to bring multiple Angular CLI projects into a single Nx monorepo while preserving git history.
 
 You can learn more about Angular & Nx by following our dedicated tutorials:
 

astro-docs/src/content/docs/technologies/angular/Migration/angular-multiple.mdoc

@@ -43,6 +43,10 @@ The command applies the following changes to your workspace:
 - Updates your `package.json` scripts to use `nx` instead of `ng`.
 - Splits your `angular.json` into `project.json` files for each project with updated paths.
 
+### Importing additional Angular CLI projects
+
+If you have multiple Angular CLI workspaces that you want to consolidate into a single Nx monorepo, you can use [`nx import`](/docs/guides/adopting-nx/import-project) to bring additional projects into an existing Nx workspace while preserving their git history.
+
 After the changes are applied, your workspace file structure should look similar to the one below:
 
 {% filetree %}
@@ -75,36 +79,13 @@ After the changes are applied, your workspace file structure should look similar
   - .gitignore
   - .prettierignore
   - .prettierrc
-  - karma.conf.js
   - nx.json
   - package.json
   - README.md
   - tsconfig.base.json
 
 {% /filetree %}
 
-### Modified folder structure
-
-The automated migration supports Angular CLI workspaces with a standard structure, configurations and features. It supports workspaces using the following executors (builders):
-
-- `@angular-devkit/build-angular:application`
-- `@angular-devkit/build-angular:browser`
-- `@angular-devkit/build-angular:browser-esbuild`
-- `@angular-devkit/build-angular:dev-server`
-- `@angular-devkit/build-angular:extract-i18n`
-- `@angular-devkit/build-angular:karma`
-- `@angular-devkit/build-angular:ng-packagr`
-- `@angular-devkit/build-angular:prerender`
-- `@angular-devkit/build-angular:protractor`
-- `@angular-devkit/build-angular:server`
-- `@angular-devkit/build-angular:ssr-dev-server`
-- `@angular-eslint/builder:lint`
-- `@cypress/schematic:cypress`
-- `@nguniversal/builders:prerender`
-- `@nguniversal/builders:ssr-dev-server`
-
-Support for other executors may be added in the future.
-
 ## After migration
 
 Your workspace is now powered by Nx! You can verify that your application still runs as intended:
@@ -116,106 +97,7 @@ Your workspace is now powered by Nx! You can verify that your application still
 
 > Your project graph will grow as you add and use more applications and libraries. You can add the `--watch` flag to `nx graph` to see the changes in-browser as you add them.
 
-## Set up CI for your Angular workspace
-
-This tutorial walked you through how Nx can improve the local development experience, but the biggest difference Nx makes is in CI. As repositories get bigger, making sure that the CI is fast, reliable and maintainable can get very challenging. Nx provides a solution.
-
-- Nx reduces wasted time in CI with the [`affected` command](/docs/features/ci-features/affected).
-- Nx Replay's [remote caching](/docs/features/ci-features/remote-cache) will reuse task artifacts from different CI executions making sure you will never run the same computation twice.
-- Nx Agents [efficiently distribute tasks across machines](/docs/concepts/ci-concepts/parallelization-distribution) ensuring constant CI time regardless of the repository size. The right number of machines is allocated for each PR to ensure good performance without wasting compute.
-- Nx Atomizer [automatically splits](/docs/features/ci-features/split-e2e-tasks) large e2e tests to distribute them across machines. Nx can also automatically [identify and rerun flaky e2e tests](/docs/features/ci-features/flaky-tasks).
-
-### Connect to Nx Cloud
-
-Nx Cloud is a companion app for your CI system that provides remote caching, task distribution, e2e tests deflaking, better DX and more.
-
-Now that we're working on the CI pipeline, it is important for your changes to be pushed to a GitHub repository.
-
-1. Commit your existing changes with `git add . && git commit -am "updates"`
-2. [Create a new GitHub repository](https://github.com/new)
-3. Follow GitHub instructions to push your existing code to the repository
-
-Now connect your repository to Nx Cloud with the following command:
-
-```shell
-npx nx@latest connect
-```
-
-A browser window will open to register your repository in your [Nx Cloud](https://cloud.nx.app) account. The link is also printed to the terminal if the windows does not open, or you closed it before finishing the steps. The app will guide you to create a PR to enable Nx Cloud on your repository.
-
-![](../../../../../assets/tutorials/nx-cloud-github-connect.avif)
-
-Once the PR is created, merge it into your main branch.
-
-![](../../../../../assets/tutorials/github-cloud-pr-merged.avif)
-
-And make sure you pull the latest changes locally:
-
-```shell
-git pull
-```
-
-You should now have an `nxCloudId` property specified in the `nx.json` file.
-
-### Create a CI workflow
-
-Use the following command to generate a CI workflow file.
-
-```shell
-npx nx generate ci-workflow --ci=github
-```
-
-This generator creates a `.github/workflows/ci.yml` file that contains a CI pipeline that will run the `lint`, `test`, `build` and `e2e` tasks for projects that are affected by any given PR. Since we are using Nx Cloud, the pipeline will also distribute tasks across multiple machines to ensure fast and reliable CI runs.
-
-The key lines in the CI pipeline are:
-
-```yml {% meta="{13-17,23-26}" %}
-// .github/workflows/ci.yml
-name: CI
-# ...
-jobs:
-  main:
-    runs-on: ubuntu-latest
-    steps:
-      - uses: actions/checkout@v4
-        with:
-          fetch-depth: 0
-          filter: tree:0
-
-      # This enables task distribution via Nx Cloud
-      # Run this command as early as possible, before dependencies are installed
-      # Learn more at https://nx.dev/ci/reference/nx-cloud-cli#npx-nxcloud-startcirun
-      # Connect your workspace by running "nx connect" and uncomment this
-      - run: npx nx-cloud start-ci-run --distribute-on="3 linux-medium-js" --stop-agents-after="build"
-      - uses: actions/setup-node@v3
-        with:
-          node-version: 22
-          cache: 'npm'
-      - run: npm ci
-      - uses: nrwl/nx-set-shas@v4
-      # Nx Affected runs only tasks affected by the changes in this PR/commit. Learn more: https://nx.dev/ci/features/affected
-      - run: npx nx affected -t lint test build
-```
-
-### Open a pull request
-
-Commit the changes and open a new PR on GitHub.
-
-```shell
-git add .
-git commit -m 'add CI workflow file'
-git push origin add-workflow
-```
-
-When you view the PR on GitHub, you will see a comment from Nx Cloud that reports on the status of the CI run.
-
-![Nx Cloud report](../../../../../assets/tutorials/github-pr-cloud-report.avif)
-
-The `See all runs` link goes to a page with the progress and results of tasks that were run in the CI pipeline.
-
-![Run details](../../../../../assets/tutorials/nx-cloud-run-details.avif)
-
-For more information about how Nx can improve your CI pipeline, [check out our details CI guides](/docs/guides/nx-cloud/setup-ci).
+For guidance on setting up CI, see the [CI setup guide](/docs/guides/nx-cloud/setup-ci).
 
 ## Learn more
 
@@ -228,21 +110,4 @@ Learn more about the advantages of Nx in the following guides:
 - [Integrate with Editors](/docs/getting-started/editor-setup)
 - [Advanced Angular Micro Frontends with Dynamic Module Federation](/docs/technologies/angular/guides/dynamic-module-federation-with-angular)
 
-## From Nx Console
-
-Nx Console no longer supports the Angular CLI. Angular CLI users will receive a notice, asking if they want to switch to Nx. When you click this button, we'll run the `nx init` command to set up the Nx CLI, allowing for cached builds, and for you to share this cache with your teammates via Nx Cloud.
-
-If you're not ready to make the change yet, you can come back to this later:
-
-- If you're using Nx Console: open the Vs Code command palette and start typing "Convert Angular CLI to Nx Workspace".
-- Regardless of using Nx Console (or your IDE): run `npx nx@latest init` from the root of your project.
-
-Once the script has run, commit the changes. Reverting this commit will effectively undo the changes made.
-
-{% cardgrid %}
-
 {% linkcard title="Nx and the Angular CLI" description="Differences between Nx and the Angular CLI" href="/docs/technologies/angular/guides/nx-and-angular" /%}
-
-{% linkcard title="Multiple Angular Repositories to one Nx Workspace" description="Combine multiple Angular CLI workspaces into one Nx workspace" href="/docs/technologies/angular/migration/angular-multiple" /%}
-
-{% /cardgrid %}