Update the ADO migrations landing page to the journey-landing layout (#60613)

guntrip · Copilot · Copilot · web-flow · commit 60b194a31463 · 2026-04-07T15:08:22.000Z
Co-authored-by: Copilot Autofix powered by AI &lt;175728472+Copilot@users.noreply.github.com&gt;
Co-authored-by: Copilot &lt;198982749+Copilot@users.noreply.github.com&gt;
diff --git a/content/README.md b/content/README.md
@@ -26,6 +26,7 @@ See the [contributing docs](https://docs.github.com/en/contributing) for general
   - [`learningTracks`](#learningtracks)
   - [`includeGuides`](#includeguides)
   - [`journeyTracks`](#journeytracks)
+  - [`journeyArticlesHeading`](#journeyarticlesheading)
   - [`contentType`](#contenttype)
   - [`communityRedirect`](#communityRedirect)
   - [`effectiveDate`](#effectiveDate)
@@ -284,6 +285,24 @@ journeyTracks:
       - href: '/actions/deployment/deploying-with-github-actions'
 ```
 
+### `journeyArticlesHeading`
+- Purpose: Override the default "Articles" heading shown above the article list on single-track journey landing pages.
+- Type: `String`
+- Only applicable when used with `layout: journey-landing` and a single journey track.
+- Optional. If omitted, the heading defaults to the translated value of `journey_landing.articles_heading` ("Articles").
+
+Example:
+
+```yaml
+layout: journey-landing
+journeyArticlesHeading: "Guides"
+journeyTracks:
+  - id: ado_migration
+    title: Run your migration
+    guides:
+      - href: /migrations/ado/understand-migrations-from-azure-devops-to-github
+```
+
 ### `contentType`
 - Purpose: Indicate the type of article.
 - Type: `String`, one of `get-started`, `concepts`, `how-tos`, `reference`, `tutorials`, `rai`, `landing` (only applies to `content/<product>/index.md` files).
diff --git a/content/migrations/ado/follow-up-tasks.md b/content/migrations/ado/follow-up-tasks.md
@@ -1,5 +1,5 @@
 ---
-title: "Phase 6. Follow-up tasks"
+title: "Follow-up tasks"
 shortTitle: "6. Follow-up tasks"
 intro: "After each migration has finished, you'll need to complete some additional tasks before the repository is ready for work."
 versions:
@@ -8,6 +8,8 @@ versions:
 contentType: other
 category:
   - Migrate from Azure DevOps
+redirect_from:
+  - /migrations/ado/phase-6-follow-up-tasks
 ---
 
 ## Checking the migration status
diff --git a/content/migrations/ado/index.md b/content/migrations/ado/index.md
@@ -1,34 +1,41 @@
 ---
-title: Migrating from Azure DevOps to GitHub
+title: Migrating from Azure DevOps
 shortTitle: Migrate from Azure DevOps
-intro: "Plan and execute a migration from Azure DevOps to {% data variables.product.prodname_ghe_cloud %}. This six-phase guide explains how to configure access, migrate, and the follow-up tasks needed to get your repositories ready for work."
+intro: Plan and execute a migration from Azure DevOps to {% data variables.product.prodname_ghe_cloud %}. This six-part guide explains how to configure access, migrate, and the follow-up tasks needed to get your repositories ready for work.
 versions:
   fpt: '*'
   ghec: '*'
 children:
-  - /phase-1-understand-migrations-from-azure-devops-to-github
-  - /phase-2-manage-access
-  - /phase-3-install-and-configure-github-enterprise-importer
-  - /phase-4-prepare-for-your-migration-from-azure-devops-to-github
-  - /phase-5-migrate-your-repositories-from-azure-devops-to-github
-  - /phase-6-follow-up-tasks
+  - /understand-migrations-from-azure-devops-to-github
+  - /manage-access
+  - /install-and-configure-github-enterprise-importer
+  - /prepare-for-your-migration-from-azure-devops-to-github
+  - /migrate-your-repositories-from-azure-devops-to-github
+  - /follow-up-tasks
   - /key-differences-between-azure-devops-and-github
   - /use-graphql-to-migrate-repositories-from-azure-devops-to-github-enterprise-cloud
   - /granting-the-migrator-role
 redirect_from:
   - /migrations/using-github-enterprise-importer/migrating-from-azure-devops-to-github-enterprise-cloud
+introLinks:
+  ado_key_differences: /migrations/ado/key-differences-between-azure-devops-and-github
 contentType: tutorials
 heroImage: /assets/images/banner-images/hero-3
-layout: bespoke-landing
 sidebarLink:
   text: Get started
   href: /migrations/ado
-carousels:
-  recommended:
-    - /phase-1-understand-migrations-from-azure-devops-to-github
-    - /phase-2-manage-access
-    - /phase-3-install-and-configure-github-enterprise-importer
-    - /phase-4-prepare-for-your-migration-from-azure-devops-to-github
-    - /phase-5-migrate-your-repositories-from-azure-devops-to-github
-    - /phase-6-follow-up-tasks
+layout: journey-landing
+journeyArticlesHeading: "Steps to completing your migration"
+journeyTracks:
+  - id: ado_migration
+    title: Run your migration
+    description: Migrate your repositories from Azure DevOps to GitHub.
+    guides:
+      - href: /migrations/ado/understand-migrations-from-azure-devops-to-github
+      - href: /migrations/ado/manage-access
+      - href: /migrations/ado/install-and-configure-github-enterprise-importer
+      - href: /migrations/ado/prepare-for-your-migration-from-azure-devops-to-github
+      - href: /migrations/ado/migrate-your-repositories-from-azure-devops-to-github
+      - href: /migrations/ado/follow-up-tasks
 ---
+
diff --git a/content/migrations/ado/install-and-configure-github-enterprise-importer.md b/content/migrations/ado/install-and-configure-github-enterprise-importer.md
@@ -1,5 +1,5 @@
 ---
-title: "Phase 3. Install and configure GitHub Enterprise Importer"
+title: "Install and configure GitHub Enterprise Importer"
 shortTitle: "3. Configure GitHub Enterprise Importer"
 intro: "Install the {% data variables.product.prodname_ado2gh_cli %} and configure your environment for the migration."
 versions:
@@ -8,6 +8,8 @@ versions:
 contentType: other
 category:
   - Migrate from Azure DevOps
+redirect_from:
+  - /migrations/ado/phase-3-install-and-configure-github-enterprise-importer
 ---
 
 ## Step 1: Install the {% data variables.product.prodname_ado2gh_cli %}
@@ -22,7 +24,7 @@ GitHub Enterprise Importer is a collection of extensions for {% data variables.p
 
 Before you can use the {% data variables.product.prodname_ado2gh_cli_short %} to migrate to {% data variables.product.prodname_ghe_cloud %}, you must create {% data variables.product.pat_generic %}s that can access the source and destination organizations, then set the {% data variables.product.pat_generic %}s as environment variables.
 
-1. Make sure you have your {% data variables.product.pat_generic %}s for both {% data variables.product.github %} and Azure DevOps ready. See [AUTOTITLE](/migrations/ado/phase-2-manage-access).
+1. Make sure you have your {% data variables.product.pat_generic %}s for both {% data variables.product.github %} and Azure DevOps ready. See [AUTOTITLE](/migrations/ado/phase-2-manage-access?token-backtrack#create-a-personal-access-token-classic-on-github) if you haven't already created a token.
 1. Set environment variables for the {% data variables.product.pat_generic %}s, replacing TOKEN in the commands below with the {% data variables.product.pat_generic %}s you previously created. Use `GH_PAT` for the destination organization and `ADO_PAT` for the source organization.
 
    * If you're using Terminal, use the `export` command.
@@ -40,7 +42,3 @@ Before you can use the {% data variables.product.prodname_ado2gh_cli_short %} to
       ```
 
 {% data reusables.enterprise-migration-tool.set-target-api-url %}
-
-## Next steps
-
-In the next phase, you'll use {% data variables.product.prodname_ghe_cloud %} to prepare for the migration. See [AUTOTITLE](/migrations/ado/phase-4-prepare-for-your-migration-from-azure-devops-to-github).
diff --git a/content/migrations/ado/manage-access.md b/content/migrations/ado/manage-access.md
@@ -1,5 +1,5 @@
 ---
-title: "Phase 2. Manage access"
+title: "Manage access"
 shortTitle: "2. Manage access"
 intro: "Set up the required access for migrating from Azure DevOps to {% data variables.product.github %}."
 versions:
@@ -9,6 +9,7 @@ contentType: other
 redirect_from:
   - /migrations/using-github-enterprise-importer/migrating-from-azure-devops-to-github-enterprise-cloud/managing-access-for-a-migration-from-azure-devops
   - /migrations/ado/managing-access-for-a-migration-from-azure-devops
+  - /migrations/ado/phase-2-manage-access
 category:
   - Migrate from Azure DevOps
 ---
@@ -55,7 +56,3 @@ If you use your IdP's IP allow list (such as Azure CAP) to restrict access to yo
 ## Allow migrations to bypass repository rulesets
 
 {% data reusables.enterprise-migration-tool.repository-migrations-bypass %}
-
-## Next steps
-
-In the next phase, you'll install and configure {% data variables.product.prodname_importer_proper_name %}. See [AUTOTITLE](/migrations/ado/phase-3-install-and-configure-github-enterprise-importer).
diff --git a/content/migrations/ado/migrate-your-repositories-from-azure-devops-to-github.md b/content/migrations/ado/migrate-your-repositories-from-azure-devops-to-github.md
@@ -1,5 +1,5 @@
 ---
-title: "Phase 5. Migrate your repositories from Azure DevOps to Github"
+title: "Migrate your repositories from Azure DevOps to GitHub"
 shortTitle: "5. Migrate repositories"
 intro: Perform a trial run and then migrate your repositories from Azure DevOps to {% data variables.product.github %}.
 versions:
@@ -12,6 +12,7 @@ redirect_from:
   - /migrations/using-github-enterprise-importer/migrating-repositories-with-github-enterprise-importer/migrating-repositories-from-azure-devops-to-github-enterprise-cloud
   - /migrations/using-github-enterprise-importer/migrating-from-azure-devops-to-github-enterprise-cloud/migrating-repositories-from-azure-devops-to-github-enterprise-cloud
   - /migrations/ado/migrating-repositories-from-azure-devops-to-github-enterprise-cloud
+  - /migrations/ado/phase-5-migrate-your-repositories-from-azure-devops-to-github
 category:
   - Migrate from Azure DevOps
 ---
@@ -70,7 +71,3 @@ If your trial run was successful, and you were able to complete the follow-up ta
 >[!WARNING] We recommend halting work in the repositories you are migrating. Any changes made during or after the migration will need to be manually migrated.
 
 {% data reusables.enterprise-migration-tool.migrate-multiple-repos %}
-
-## Next steps
-
-In the next and final phase, you'll perform follow-up tasks, check logs, and get your repositories ready to use. See [AUTOTITLE](/migrations/ado/phase-6-follow-up-tasks).
diff --git a/content/migrations/ado/prepare-for-your-migration-from-azure-devops-to-github.md b/content/migrations/ado/prepare-for-your-migration-from-azure-devops-to-github.md
@@ -1,5 +1,5 @@
 ---
-title: "Phase 4. Prepare for your migration from Azure DevOps to GitHub"
+title: "Prepare for your migration from Azure DevOps to GitHub"
 shortTitle: "4. Prepare to migrate"
 intro: Plan your migration by understanding your timeline, what data will be migrated, and your organizational structure.
 versions:
@@ -8,6 +8,8 @@ versions:
 contentType: other
 category:
   - Migrate from Azure DevOps
+redirect_from:
+  - /migrations/ado/phase-4-prepare-for-your-migration-from-azure-devops-to-github
 ---
 
 ## Determine how much you have to migrate
@@ -59,7 +61,3 @@ TEAM-PROJECT-Maintainers | Maintainer
 TEAM-PROJECT-Admins | Admin
 
 To give access to migrated repositories, you can add people to these teams. You can do this manually on {% data variables.product.prodname_dotcom %}, or if you chose to link the teams to Azure Active Directory (AAD) groups during your migration, by managing group membership in AAD. For more information about manually managing team membership, see [AUTOTITLE](/organizations/organizing-members-into-teams/adding-organization-members-to-a-team).
-
-## Next steps
-
-In the next phase, you'll perform a dry run and then migrate your repositories. See [AUTOTITLE](/migrations/ado/phase-5-migrate-your-repositories-from-azure-devops-to-github).
diff --git a/content/migrations/ado/understand-migrations-from-azure-devops-to-github.md b/content/migrations/ado/understand-migrations-from-azure-devops-to-github.md
@@ -1,7 +1,7 @@
 ---
-title: "Phase 1. Understand migrations from Azure DevOps to GitHub"
-shortTitle: "1. Understand migrations"
-intro: "{% data variables.product.prodname_importer_proper_name %} can automate migrating from Azure DevOps."
+title: Understand migrations from Azure DevOps to GitHub
+shortTitle: 1. Understand migrations
+intro: '{% data variables.product.prodname_importer_proper_name %} can automate migrating from Azure DevOps.'
 versions:
   fpt: '*'
   ghec: '*'
@@ -14,6 +14,7 @@ redirect_from:
   - /migrations/using-github-enterprise-importer/understanding-github-enterprise-importer/migrating-from-azure-devops-with-github-enterprise-importer
   - /migrations/using-github-enterprise-importer/migrating-from-azure-devops-to-github-enterprise-cloud/overview-of-a-migration-from-azure-devops-to-github-enterprise-cloud
   - /migrations/ado/overview-of-a-migration-from-azure-devops-to-github-enterprise-cloud
+  - /migrations/ado/phase-1-understand-migrations-from-azure-devops-to-github
 category:
   - Migrate from Azure DevOps
 ---
@@ -26,6 +27,8 @@ You can only use {% data variables.product.prodname_importer_proper_name %} to m
 
 Before you create your enterprise account on {% data variables.product.prodname_dotcom %}, decide whether your enterprise will use {% data variables.product.prodname_emus %}. This affects how your members authenticate and how you manage identities and access. See [AUTOTITLE](/enterprise-cloud@latest/enterprise-onboarding/getting-started-with-your-enterprise/choose-an-enterprise-type).
 
+To learn more about the differences between {% data variables.product.prodname_dotcom %} and Azure DevOps, see [AUTOTITLE](/migrations/ado/key-differences-between-azure-devops-and-github).
+
 ## Support for Azure Pipelines and Azure Boards
 
 Both Azure Pipelines and Azure Boards can be fully integrated with your {% data variables.product.prodname_dotcom %} experience. You can configure your enterprise account and Azure DevOps so you can keep using these services while also benefitting from having your repositories hosted on {% data variables.product.prodname_dotcom %}.
@@ -61,8 +64,3 @@ There are limits to what {% data variables.product.prodname_importer_proper_name
 * **Delayed code search functionality:** Re-indexing the search index can take a few hours after a repository is migrated, and code searches may return unexpected results until re-indexing is complete.
 * **Rulesets configured for your organization can cause migrations to fail:** For example, if you configured a rule that requires email addresses for commit authors to end with `@monalisa.cat`, and the repository you're migrating contains commits that don't comply with this rule, your migration will fail.
 * **Mannequin content might not be searchable:** Mannequins are placeholder users to which imported content (such as issues, pull requests, comments, etc.) is associated. When you search for content associated with a mannequin, such as assigned issues, the issues may not be found. Once a mannequin is reclaimed, the content should be found via the new owner.
-
-
-## Next steps
-
-In the next article, you'll decide who will perform the migration and prepare access to both Azure DevOps and {% data variables.product.prodname_ghe_cloud %}. See [AUTOTITLE](/migrations/ado/phase-2-manage-access).
diff --git a/data/ui.yml b/data/ui.yml
@@ -285,6 +285,7 @@ product_landing:
   try_ghas_for_free: Try GitHub Advanced Security for free
   generate_secret_risk_assessment_report_for_free: Find out how to run a free secret risk assessment
   plan_your_migration: Plan your migration
+  ado_key_differences: Key differences between Azure DevOps and GitHub
   releases: Releases
   guides: Guides
   explore_guides: Explore guides
diff --git a/src/fixtures/fixtures/data/ui.yml b/src/fixtures/fixtures/data/ui.yml
@@ -285,6 +285,7 @@ product_landing:
   try_ghas_for_free: Try GitHub Advanced Security for free
   generate_secret_risk_assessment_report_for_free: Find out how to run a free secret risk assessment
   plan_your_migration: Plan your migration
+  ado_key_differences: Key differences between Azure DevOps and GitHub
   releases: Releases
   guides: Guides
   explore_guides: Explore guides
diff --git a/src/frame/lib/frontmatter.ts b/src/frame/lib/frontmatter.ts
@@ -208,6 +208,12 @@ export const schema: Schema = {
     learningTracks: {
       type: 'array',
     },
+    // Optional heading override for the single-track journey landing UI
+    journeyArticlesHeading: {
+      type: 'string',
+      translatable: true,
+      description: 'Override the default "Articles" heading on single-track journey landing pages',
+    },
     // Journey tracks for journey landing pages
     journeyTracks: {
       type: 'array',
diff --git a/src/landings/components/journey/JourneyLanding.tsx b/src/landings/components/journey/JourneyLanding.tsx
@@ -5,7 +5,8 @@ import { JourneyLearningTracks } from './JourneyLearningTracks'
 import { UtmPreserver } from '@/frame/components/UtmPreserver'
 
 export const JourneyLanding = () => {
-  const { title, intro, heroImage, introLinks, journeyTracks } = useLandingContext()
+  const { title, intro, heroImage, introLinks, journeyTracks, journeyArticlesHeading } =
+    useLandingContext()
 
   return (
     <DefaultLayout>
@@ -14,7 +15,10 @@ export const JourneyLanding = () => {
         <LandingHero title={title} intro={intro} heroImage={heroImage} introLinks={introLinks} />
 
         <div className="container-xl px-3 px-md-6 mt-6 mb-4">
-          <JourneyLearningTracks tracks={journeyTracks ?? []} />
+          <JourneyLearningTracks
+            tracks={journeyTracks ?? []}
+            articlesHeading={journeyArticlesHeading}
+          />
         </div>
       </div>
     </DefaultLayout>
diff --git a/src/landings/components/journey/JourneyLearningTracks.tsx b/src/landings/components/journey/JourneyLearningTracks.tsx
@@ -8,9 +8,10 @@ import styles from './JourneyLearningTracks.module.scss'
 
 type JourneyLearningTracksProps = {
   tracks: JourneyTrack[]
+  articlesHeading?: string | null
 }
 
-export const JourneyLearningTracks = ({ tracks }: JourneyLearningTracksProps) => {
+export const JourneyLearningTracks = ({ tracks, articlesHeading }: JourneyLearningTracksProps) => {
   const { t } = useTranslation('journey_landing')
 
   if (!tracks || tracks.length === 0) {
@@ -55,11 +56,12 @@ export const JourneyLearningTracks = ({ tracks }: JourneyLearningTracksProps) =>
   // simple single journey
   if (tracks.length === 1) {
     const track = tracks[0]
+    const headingText = articlesHeading || t('articles_heading')
 
     return (
       <div data-testid="journey-single-track">
         <div className={styles.trackHeader}>
-          <h2 className="h1 text-bold mb-4">{t('articles_heading')}</h2>
+          <h2 className="h1 text-bold mb-4">{headingText}</h2>
         </div>
         <ol className={`${styles.trackGuides} pl-0`} data-testid="journey-articles">
           {(track.guides || []).map((article: { href: string; title: string }) => (
diff --git a/src/landings/context/LandingContext.tsx b/src/landings/context/LandingContext.tsx
@@ -29,6 +29,7 @@ export type LandingContextT = {
   introLinks?: Record<string, string> | null
   // For journey landing pages
   journeyTracks?: JourneyTrack[]
+  journeyArticlesHeading?: string | null
   // For article grid category filtering
   includedCategories?: string[]
 }
@@ -42,6 +43,7 @@ type LandingPage = NonNullable<Context['page']> & {
   rawPermissions?: string
   introLinks?: Record<string, string> | null
   resolvedJourneyTracks?: JourneyTrack[]
+  journeyArticlesHeading?: string
 }
 
 export const LandingContext = createContext<LandingContextT | null>(null)
@@ -109,6 +111,7 @@ export const getLandingContextFromRequest = async (
     introLinks: page.introLinks || null,
     carousels,
     journeyTracks,
+    journeyArticlesHeading: page.journeyArticlesHeading || null,
     includedCategories: page.includedCategories || [],
   }
 }
