docs(misc): rewrite turborepo migration guide as step-by-step

astro-docs/STYLE_GUIDE.md

@@ -100,6 +100,22 @@ The reverse is just as common in AI drafts: a short claim followed by a longer s
 
 **The test:** If two adjacent sentences share a subject and the second adds no new fact, merge them.
 
+### Cut signpost openers
+
+A short sentence that announces what a paragraph is about, before the paragraph says it, is a
+label rather than a claim. This one survives the drama-beat test, because the sentences after it
+do add facts, so sweep for it separately.
+
+- Don't: "CI is the other gap. Turborepo scales past one machine through manual binning, while Nx Agents distributes at the task level."
+- Do: "Turborepo scales past one machine through manual binning, while Nx Agents distributes at the task level."
+
+Naming a count is the same move ("Two smaller differences.", "Three things to know."). Either
+fold the label into the sentence that follows or delete it. A real list gets bullets and an
+introductory line instead.
+
+**The test:** Delete the first sentence of each paragraph. If the paragraph still says everything
+it said before, leave it deleted.
+
 ### Cut significance clauses
 
 Naming a property and then explaining why the reader should care about it is a generated shape.
@@ -181,7 +197,7 @@ Run passes in this order. Structural first, vocabulary last.
 
 1. Canonical-home audit: where does each substantive point live?
 2. Repetition count: grep your two or three core findings. If a finding appears more than twice in prose, the third is probably redundant.
-3. Drama-beat sweep, both orders. Also grep for `?` and for significance clauses ("which is what makes", "and that's why").
+3. Drama-beat sweep, both orders. Read the first sentence of each paragraph on its own and cut the ones that only label it. Also grep for `?` and for significance clauses ("which is what makes", "and that's why").
 4. Closer pass.
 5. Claim audit: for each absolute and each counterfactual, check what evidence in the doc supports that strength. Weaken or cite. Check invented numbers the same way.
 6. End-to-end consistency read.

astro-docs/netlify.toml

@@ -126,6 +126,11 @@ to = "/docs/guides/adopting-nx/adding-to-monorepo"
 from = "/docs/guides/adopting-nx/nx-vs-turborepo"
 to = "/docs/guides/comparisons/nx-vs-turborepo"
 
+# Turborepo migration guide moved to the Knowledge Base (DOC-571)
+[[redirects]]
+from = "/docs/guides/adopting-nx/from-turborepo"
+to = "/docs/kb/from-turborepo"
+
 # Angular multiple workspace migration page removed (DOC-419)
 [[redirects]]
 from = "/docs/technologies/angular/migration/angular-multiple"

astro-docs/sidebar.mts

@@ -311,10 +311,6 @@ const learnGroups: SidebarItems = [
             label: 'Preserving Git histories',
             link: 'guides/adopting-nx/preserving-git-histories',
           },
-          {
-            label: 'Migrating from Turborepo',
-            link: 'guides/adopting-nx/from-turborepo',
-          },
         ],
       },
       {

astro-docs/src/content/docs/guides/Adopting Nx/adding-to-monorepo.mdoc

@@ -424,6 +424,6 @@ For more information about how Nx can improve your CI pipeline, check out our [d
 
 {% linkcard title="Nx Ignore" description="Learn about how to ignore certain projects using .nxignore" href="/docs/reference/nxignore" /%}
 
-{% linkcard title="Migrating from Turborepo to Nx" description="Read about Migrating from Turborepo to Nx" href="/docs/guides/adopting-nx/from-turborepo" /%}
+{% linkcard title="Migrating from Turborepo to Nx" description="Read about Migrating from Turborepo to Nx" href="/docs/kb/from-turborepo" /%}
 
 {% /cardgrid %}

astro-docs/src/content/docs/kb/angular-nx-version-matrix.mdoc

@@ -4,7 +4,6 @@ description: Find the Nx versions that support each Angular version, including r
 sidebar:
   label: Angular and Nx Version Matrix
 filter: 'type:Guides'
-featured: true
 topics:
   - 'Angular'
 ---