docs(nx-dev): put all angular recipes together

[meeroslav]

Current Behavior

Recipes related to Angular are scattered in Adopting Nx, Adopting Nx From Angular CLI and Other

Expected Behavior

All Angular related recipes should be in the same Angular section:

• Migrations from CLI and JS
• NgRx specific
• Tailwind with Angular

Compare the menu structure at: https://nx-dev-git-fork-meeroslav-fix-docs-move-angular-recipes-nrwl.vercel.app/recipes

Related Issue(s)

Fixes #

[vercel[bot]]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated (UTC)
nx-dev	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Jul 5, 2023 0:59am

[vercel[bot]]

Deployment failed with the following error:

The provided GitHub repository does not contain the requested branch or commit reference. Please ensure the repository is not empty.

[nx-cloud[bot]]

☁️ Nx Cloud Report

CI is running/has finished running commands for commit 95c2541752816beb215edb9f71fd3a4dbecb9cfe. As they complete they will appear below. Click to see the status, the terminal output, and the build insights.

📂 See all runs for this branch

---

✅ Successfully ran 1 target

• nx affected -t e2e-macos --parallel=1 --base=446539a5acfa9ff59d36f1b5c01e13bdfc59083f --head=95c2541752816beb215edb9f71fd3a4dbecb9cfe

---

Sent with 💌 from NxCloud.

[juristr]

@meeroslav should this be funneled into the broader discussion on how to reorg some of the stuff we have on the docs page? Like, if we add a section for Angular, we should probably have one for React, Next, Node,...

Right the side-menu organization is kept agnostic from tech but from an Nx focus like migrating etc.. which I agree has its flaws, which is why we should discuss this in general.

As we had already discussed, there are different angles

• Nx specific recipes
• Tech specific recipes related on how to use Nx with but not necessarily related to any Nx tech specific plugin
• Nx plugin specific recipes

[meeroslav]

We already had segment called Adopting Nx form Angular CLI so that's not new.

I believe an Angular user might come to recipes looking for Angular-related content or a framework agnostic one. There shouldn't be any recipes in the Other as each recipe needs to belong somewhere.

Grouping NgRx-related with Angular migration recipes makes sense, in my opinion.

Same should go for React specific recipes.

But we can have a discussion on the topic first.

[meeroslav]

Closing as we will refactor the docs further

[github-actions[bot]]

This pull request has already been merged/closed. If you experience issues related to these changes, please open a new issue referencing this pull request.