Publishing category restructure (#3425)

helinanever · zgoldie · web-flow · commit 038369a3fbed · 2026-04-01T15:52:32.000+03:00
* Update configuration and content files to enhance publishing categories and menu structure

- Modified `config.yaml` to introduce new menu items for tester distribution, publishing to stores, and static hosting.
- Updated multiple content files to associate them with the newly created menu categories for better organization, including Firebase App Distribution, GitHub Releases, and various store publishing guides.
- Adjusted sidebar template logic to ensure proper rendering of menu items based on the new structure.

* Refactor publishing categories in configuration and content files

- Updated `config.yaml` to rename and reorganize menu items related to publishing, including changes from "Tester distribution" to "Publishing" and "Distributing".
- Modified multiple content files to reflect the new menu categories, ensuring proper association with the updated structure for Firebase App Distribution, GitHub Releases, and various store publishing guides.
- Enhanced organization of publishing-related documentation for better clarity and accessibility.

* Restructure YAML/Flutter docs to match sidebar sections by content folder

- Remove menuCategories from all pages; sidebar lists pages by Hugo section only
- Move distributing guides to yaml-distributing/ and flutter-distributing/
- Duplicate iOS device provisioning into yaml-testing/ and flutter-testing/;
  remove custom-menu-position; alias /testing/ios-provisioning on YAML copy
- Add aliases on moved pages for old yaml-publishing / flutter-publishing URLs
- Move pub.dev under yaml-distributing with alias for previous path
- Simplify breadcrumbs (no menuCategories branch)

* Update links and aliases in Flutter documentation

- Corrected the link in the tip section of flutter-projects.md to point to the updated path for distributing packages on pub.dev.
- Added an alias in pub.dev.md to maintain compatibility with the previous publishing URL.

* Move build dashboards to distribution

* Update weights

* Update category names

* Revert frontend changes

---------

Co-authored-by: zgoldie &lt;hello@zachgoldie.com&gt;
Co-authored-by: zgoldie &lt;73491442+zgoldie@users.noreply.github.com&gt;
diff --git a/config.yaml b/config.yaml
@@ -67,18 +67,22 @@ menu:
           parent: yaml
           weight: 4
         - identifier: yaml-publishing
-          name: Publishing
+          name: Publishing to the stores
           parent: yaml
           weight: 5
+        - identifier: yaml-distributing
+          name: Build distribution
+          parent: yaml
+          weight: 6
         - identifier: yaml-notification
           name: Notifications
           parent: yaml
-          weight: 6
+          weight: 7
 
         - identifier: integrations
           name: Integrations
           parent: yaml
-          weight: 7
+          weight: 8
         - identifier: knowledge-base
           name: Advanced configuration
           weight: 8
@@ -131,10 +135,14 @@ menu:
           name: Publishing
           parent: flutter
           weight: 5
+        - identifier: flutter-distributing
+          name: Distributing
+          parent: flutter
+          weight: 6
         - identifier: flutter-notification
           name: Notifications
           parent: flutter
-          weight: 6
+          weight: 7
         
  
 
diff --git a/content/billing/pricing.md b/content/billing/pricing.md
@@ -288,7 +288,7 @@ If you need to support older versions of your application and need access to old
 
 You can download build artifacts via the Codemagic UI or using the [Codemagic REST API](../rest-api/builds/). 
 
-To keep copies of your future build artifacts, we advise you to set up publishing to external storage, see an example [here](../yaml-publishing/aws/).
+To keep copies of your future build artifacts, we advise you to set up publishing to external storage, see an example [here](../yaml-distributing/aws/).
 
 ### Instance Types
 
diff --git a/content/flutter-configuration/flutter-projects.md b/content/flutter-configuration/flutter-projects.md
@@ -13,7 +13,7 @@ aliases:
 With Codemagic, you can build and test Flutter apps for Android, iOS, web, macOS and Linux as well as [test widgets](../testing/testing-widgets). It is also possible to set up a [workflow](../flutter/creating-workflows) that runs tests only.
 
 {{<notebox>}}
-**Tip:** If you're interested in building Flutter/Dart packages and publishing them to [pub.dev](https://pub.dev/), you can do so with [`codemagic.yaml`](../getting-started/yaml), see an example [here](../yaml-publishing/pub.dev).
+**Tip:** If you're interested in building Flutter/Dart packages and publishing them to [pub.dev](https://pub.dev/), you can do so with [`codemagic.yaml`](../getting-started/yaml), see an example [here](../yaml-distributing/pub.dev).
 {{</notebox>}}
 
 ## Selecting build platforms and build machines
diff --git a/content/flutter-distributing/app-preview.md b/content/flutter-distributing/app-preview.md
@@ -3,13 +3,14 @@ title: Previewing apps in the browser
 description: Test your iOS or Android app in the browser with App Preview
 weight: 4
 aliases:
+  - /flutter-testing/app-preview
 ---
 
 App Preview is our iOS simulator and Android emulator running in your browser. Launch and interact with your iOS or Android app right in the browser, regardless of the operating system you are using. Test your app against different device and OS configurations, emulate GPS location or demo the latest app version without needing access to a physical device. 
 
 {{< youtube l1VeZXtO0zQ >}}
 
-**Tip:** The following sections describe creating previewable artifacts using Flutter Workflow Editor. If you're using codemagic.yaml, follow the instructions [here](../yaml-testing/app-preview).
+**Tip:** The following sections describe creating previewable artifacts using Flutter Workflow Editor. If you're using codemagic.yaml, follow the instructions [here](../yaml-distributing/app-preview).
 
 ## Enabling App Preview and Free Trial
 
diff --git a/content/flutter-distributing/build-dashboards.md b/content/flutter-distributing/build-dashboards.md
@@ -5,6 +5,7 @@ weight: 3
 aliases: 
   - /knowledge-base/shared-dashboards
   - /knowledge-base/public-dashboards
+  - /knowledge-others/build-dashboards
 ---
 
 Build dashboards make it possible for teams to share the list of team's builds, release notes (if passed) and build artifacts with people outside Codemagic using a public link (build logs will not be exposed). This is a convenient option for distributing builds to testers or sharing build artifacts with stakeholders.
diff --git a/content/flutter-distributing/firebase-app-distribution.md b/content/flutter-distributing/firebase-app-distribution.md
@@ -3,19 +3,21 @@ description: Deploy a Flutter app to Firebase App Distribution using the Flutter
 title: Firebase App Distribution with Flutter workflow editor
 linkTitle: Firebase App Distribution
 weight: 5
-aliases: /publishing/firebase-app-distribution
+aliases:
+  - /publishing/firebase-app-distribution
+  - /flutter-publishing/firebase-app-distribution
 ---
 
 Set up publishing to [Firebase App Distribution](https://firebase.google.com/docs/app-distribution) to distribute your Android and iOS apps to testers.
 
 {{<notebox>}}
-**Note:** This guide only applies to workflows configured with the **Flutter workflow editor**. If your workflow is configured with **codemagic.yaml**, please go to [Publishing an app to Firebase App Distribution](../yaml-publishing/firebase-app-distribution).
+**Note:** This guide only applies to workflows configured with the **Flutter workflow editor**. If your workflow is configured with **codemagic.yaml**, please go to [Publishing an app to Firebase App Distribution](../yaml-distributing/firebase-app-distribution).
 {{</notebox>}}
 
 ## Requirements
 
 - [Add Firebase to your Flutter project](https://firebase.google.com/docs/flutter/setup)
-- Generate a [Firebase token](https://firebase.google.com/docs/cli#cli-ci-systems) locally or set up a [service account](https://docs.codemagic.io/yaml-publishing/firebase-app-distribution/#requirements) with **Firebase App Distribution Admin** role to authenticate with Firebase App Distribution.
+- Generate a [Firebase token](https://firebase.google.com/docs/cli#cli-ci-systems) locally or set up a [service account](https://docs.codemagic.io/yaml-distributing/firebase-app-distribution/#requirements) with **Firebase App Distribution Admin** role to authenticate with Firebase App Distribution.
 - If your app uses Firebase services, you need to upload the Firebase configuration files to Codemagic, see the instructions [here](/knowledge-base/load-firebase-configuration/).
 - Set up [iOS code signing](../code-signing/ios-code-signing). Note that an Ad Hoc or Enterprise distribution profile is required to distribute the app outside your development team.
 - Set up [Android code signing](../code-signing/android-code-signing). If you do not set up code signing, the artifact will be signed with a debug keystore from Codemagic build machine.
diff --git a/content/flutter-distributing/github-releases.md b/content/flutter-distributing/github-releases.md
@@ -3,7 +3,9 @@ description: How to create a GitHub release with artifacts using the Flutter wor
 title: GitHub releases with Flutter workflow editor
 linkTitle: GitHub releases
 weight: 9
-aliases: /publishing/github-release/
+aliases:
+  - /publishing/github-release/
+  - /flutter-publishing/github-releases
 ---
 
 Codemagic enables you to create a GitHub release automatically and upload generated artifacts when your build is triggered on tag creation. Read more about GitHub releases in [GitHub's documentation](https://docs.github.com/en/github/administering-a-repository/about-releases).
diff --git a/content/flutter-distributing/publishing-to-aws.md b/content/flutter-distributing/publishing-to-aws.md
@@ -3,6 +3,8 @@ description: How to publish a web app to Amazon S3 using Flutter workflow editor
 title: Amazon S3 publishing using Flutter workflow editor
 linkTitle: Amazon S3
 weight: 8
+aliases:
+  - /flutter-publishing/publishing-to-aws
 ---
 
 In order to publish your web application to AWS S3:
diff --git a/content/flutter-distributing/publishing-to-codemagic-static-pages.md b/content/flutter-distributing/publishing-to-codemagic-static-pages.md
@@ -2,7 +2,9 @@
 description: How to publish a web app to a custom subdomain using the Flutter workflow editor
 title: Codemagic Static Pages
 weight: 7
-aliases: /publishing/publishing-to-codemagic-static-pages
+aliases:
+  - /publishing/publishing-to-codemagic-static-pages
+  - /flutter-publishing/publishing-to-codemagic-static-pages
 ---
 
 You can publish your web app to a custom subdomain of `codemagic.app` for easy access.
diff --git a/content/flutter-distributing/shorebird.md b/content/flutter-distributing/shorebird.md
@@ -5,7 +5,8 @@ linkTitle: Code Push with Shorebird
 meta_title: Publish Flutter Apps with Shorebird OTA Updates
 meta_description: Integrate Shorebird with Codemagic to publish Flutter apps and deliver over-the-air updates from CI/CD workflows.
 weight: 4
-aliases: 
+aliases:
+  - /flutter-publishing/shorebird
 ---
 
 Code push for Flutter is a cloud service by [Shorebird](https://shorebird.dev/) that allows developers to push over-the-air (OTA) app updates directly to users' devices without publishing each update on app stores. With Codemagic, you can use Shorebird to build and publish a release or a patch for Android and iOS.
diff --git a/content/flutter-testing/ios-provisioning.md b/content/flutter-testing/ios-provisioning.md
@@ -0,0 +1,49 @@
+---
+title: Registering iOS test devices
+description: Automatically add new test devices to Apple Developer Portal
+weight: 4
+---
+
+To be able to test iOS builds on physical devices outside TestFlight, e.g. by downloading the app artifact from Slack or a [public link](/yaml-distributing/build-dashboards), the test devices have to be registered in Apple Developer Portal and included in the provisioning profile used for code signing the app. Codemagic enables you to send your trusted testers a device registration link to obtain their device UDIDs and automatically add them to the list of devices in Apple Developer Portal.
+
+{{<notebox>}}
+**Note:** This feature is available for [teams](../teams/teams) only. If you are using a personal account, this has to be done manually by [Registering your devices using your Developer Account](https://developer.apple.com/documentation/xcode/distributing-your-app-to-registered-devices#Register-Devices-in-Your-Developer-Account).
+
+You can also check the [Register Devices](https://help.apple.com/developer-account/#/dev40df0d9fa) section using Your Developer Account.
+{{</notebox>}}
+
+## Requirements
+
+* You have to be a team admin to manage iOS test devices. 
+* The **Apple Developer Portal integration** must be connected in **Team integrations** to be able to register new devices. This requires creating an App Store Connect API key with **Developer** permissions, see how to create one [here](https://developer.apple.com/documentation/appstoreconnectapi/creating_api_keys_for_app_store_connect_api).
+
+## Creating a tester group
+
+1. Navigate to **Teams > Your team > iOS test devices**.
+2. Click **Create tester group**. A popup window appears with details about the tester group.
+3. Enter the **Tester group name**. All the devices registered from this invitation will be added to this group in Codemagic.
+4. Select the **Developer Portal API key**. The API key determines under which Apple Developer Portal account the devices will be registered.
+5. Then enter the **Tester email addresses** that will receive the device registration link. Note that you can later send new invitations to add more devices to this group.
+6. Finally, click **Send registration link**. 
+
+To add devices to an existing group, find the group in the **Tester groups** section and click **Add new devices**. 
+
+{{<notebox>}}
+**Note:** It is important to choose the actual bundle identifier when building an not use any XC Wildcards. Otherwise, the tester group will be unable to install the app and will get the error **_"This app cannot be installed because its integrity could not be verified_**"
+{{</notebox>}}
+
+## Device registration
+
+Your testers will receive an email with instructions to register a device. The registration link in email invitation is valid for 7 days.
+
+The email contains a QR code and the **Register device** button to download a configuration profile that must be installed on the device. The configuration profile collects the device UDID and forwards it to Codemagic for registration. On successful registration, the device will be added to Apple Developer Portal and listed in the tester group in Codemagic.
+
+## Deleting test devices and groups
+
+To delete devices from a tester group, click the pencil icon next to the group to edit it and select the devices to be removed. 
+
+To delete a tester group, click the bin icon next to the tester group. Deleting the group will also delete all registered devices in the group from Codemagic.
+
+Note that deleting a device or a tester group from Codemagic does not remove the devices from Apple Developer Portal.
+
+To remove devices from [Apple Developer Portal](https://developer.apple.com/), navigate to **Certificates, Identifiers & Profiles > Devices**, select a device and click **Disable**.
diff --git a/content/getting-started/teams.md b/content/getting-started/teams.md
@@ -66,7 +66,7 @@ Users that have triggered builds can be invited to the team by clicking **Add to
 
 ## Build dashboards
 
-The build dashboards feature makes it possible to share the team's builds and build artifacts via a public link. Read more about this feature [here](/yaml-publishing/build-dashboards).
+The build dashboards feature makes it possible to share the team's builds and build artifacts via a public link. Read more about this feature [here](/yaml-distributing/build-dashboards).
 
 ## Managing team integrations
 
diff --git a/content/knowledge-codemagic/build-versioning.md b/content/knowledge-codemagic/build-versioning.md
@@ -342,7 +342,7 @@ Additionally, you will need to provide project ID (e.g. `228333310124`) and appl
 
 #### Creating Firebase service account credentials
 
-You will need to set up a [Firebase service account](https://docs.codemagic.io/yaml-publishing/firebase-app-distribution/).
+You will need to set up a [Firebase service account](https://docs.codemagic.io/yaml-distributing/firebase-app-distribution/).
 
 #### Configuring the API access environment variables
 
diff --git a/content/partials/quickstart/next-steps.md b/content/partials/quickstart/next-steps.md
@@ -1,5 +1,5 @@
 While this basic workflow configuration is incredibly useful, it is certainly not the end of the road and there are numerous advanced actions that Codemagic can help you with.
 
-We encourage you to investigate [Running tests with Codemagic](../yaml-testing/testing) to get you started with testing, as well as additional guides such as the one on running tests on [Firebase Test Lab](../yaml-testing/firebase-test-lab) or [Registering iOS test devices](../testing/ios-provisioning).
+We encourage you to investigate [Running tests with Codemagic](../yaml-testing/testing) to get you started with testing, as well as additional guides such as the one on running tests on [Firebase Test Lab](../yaml-testing/firebase-test-lab) or [Registering iOS test devices](../yaml-testing/ios-provisioning).
 
 Documentation on [using codemagic.yaml](../yaml/yaml-getting-started) teaches you to configure additional options such as [changing the instance type](../yaml/yaml-getting-started/#instance-type) on which to build, or configuring builds to be [automatically triggered](https://docs.codemagic.io/yaml/yaml-getting-started/#triggering) on repository events.
diff --git a/content/yaml-distributing/app-preview.md b/content/yaml-distributing/app-preview.md
@@ -3,15 +3,16 @@ title: Previewing apps in the browser
 description: Test your iOS or Android app in the browser with App Preview
 meta_title: Create App Previews in Codemagic
 meta_description: Create app previews in Codemagic using codemagic.yaml to test builds and share interactive preview links.
-weight: 4
+weight: 2
 aliases:
+  - /yaml-testing/app-preview
 ---
 
 App Preview is our iOS simulator and Android emulator running in your browser. Launch and interact with your iOS or Android app right in the browser, regardless of the operating system you are using. Test your app against different device and OS configurations, emulate GPS location or demo the latest app version without needing access to a physical device. 
 
 {{< youtube l1VeZXtO0zQ >}}
 
-**Tip:** The following sections describe creating previewable artifacts using codemagic.yaml. If you're using the Flutter Workflow Editor, follow the instructions [here](../flutter-testing/app-preview).
+**Tip:** The following sections describe creating previewable artifacts using codemagic.yaml. If you're using the Flutter Workflow Editor, follow the instructions [here](../flutter-distributing/app-preview).
 
 ## Enabling App Preview and Free Trial
 
diff --git a/content/yaml-distributing/aws.md b/content/yaml-distributing/aws.md
@@ -2,13 +2,14 @@
 title: Amazon S3 publishing using codemagic.yaml
 linkTitle: Amazon S3
 description: How to publish build artifacts to Amazon S3 using codemagic.yaml
-weight: 11
+weight: 10
 aliases: 
   - /publishing/publish-build-artifacts-to-amazon-s3
   - /flutter-publishing/publish-build-artifacts-to-amazon-s3
   - /knowledge-base/publish-build-artifacts-to-amazon-s3
   - /custom-scripts/publish-build-artifacts-to-amazon-s3
   - /testing/aws
+  - /yaml-publishing/aws
 ---
 
 In order to publish your web application to AWS S3, you need to configure your access credentials in Codemagic. You can follow the [instructions](https://aws.amazon.com/getting-started/hands-on/backup-to-s3-cli/) provided by Amazon to create your account and get the necessary details.
diff --git a/content/yaml-distributing/build-dashboards.md b/content/yaml-distributing/build-dashboards.md
@@ -1,11 +1,12 @@
 ---
 title: Build dashboards
 description: Use public links to distribute builds and artifacts in codemagic.yaml
-weight: 3
-aliases: 
+weight: 1
+aliases:
   - /publishing-yaml/public-dashboards
   - /yaml-publishing/public-dashboards
   - /yaml-publishing/shared-dashboards
+  - /yaml-publishing/build-dashboards
 ---
 
 Build dashboards make it possible for teams to share the list of team's builds, release notes (if passed) and build artifacts with people outside Codemagic using a public link (build logs will not be exposed). This is a convenient option for distributing builds to testers or sharing build artifacts with stakeholders.
diff --git a/content/yaml-distributing/cloudflare-pages.md b/content/yaml-distributing/cloudflare-pages.md
@@ -1,7 +1,9 @@
 ---
 title: Cloudflare Pages
 description: How to deploy a website to Cloudflare Pages using codemagic.yaml
-weight: 14
+weight: 6
+aliases:
+  - /yaml-publishing/cloudflare-pages
 ---
 
 [**Cloudflare Pages**](https://pages.cloudflare.com/) is a JAMstack platform for frontend developers to collaborate and deploy websites.
@@ -105,4 +107,4 @@ Here's a workflow for building a Flutter web application and then publish it to
       slack:
         channel: "#builds"
         notify_on_build_start: true
-{{< /highlight >}}
+{{< /highlight >}}
diff --git a/content/yaml-distributing/firebase-app-distribution.md b/content/yaml-distributing/firebase-app-distribution.md
@@ -2,12 +2,14 @@
 title: Firebase App Distribution with codemagic.yaml
 linkTitle: Firebase App Distribution
 description: How to deploy an app to Firebase App Distribution using codemagic.yaml
-weight: 5
+weight: 3
+aliases:
+  - /yaml-publishing/firebase-app-distribution
 ---
 
 </p>
 {{<notebox>}}
-**Note:** This guide only applies to workflows configured with the **codemagic.yaml**. If your workflow is configured with **Flutter workflow editor**, please go to [Publishing an app to Firebase App Distribution with Flutter workflow editor](../publishing/firebase-app-distribution).
+**Note:** This guide only applies to workflows configured with the **codemagic.yaml**. If your workflow is configured with **Flutter workflow editor**, please go to [Publishing an app to Firebase App Distribution with Flutter workflow editor](../flutter-distributing/firebase-app-distribution).
 {{</notebox>}}
 
 ### Requirements
diff --git a/content/yaml-distributing/firebase-hosting.md b/content/yaml-distributing/firebase-hosting.md
@@ -1,7 +1,9 @@
 ---
 title: Firebase Hosting
 description: How to deploy an app to Firebase Hosting using codemagic.yaml
-weight: 7
+weight: 4
+aliases:
+  - /yaml-publishing/firebase-hosting
 ---
 
 </p>
@@ -15,7 +17,7 @@ Publishing to Firebase Hosting with Codemagic is a straightforward process as th
 ### Using Firebase Google Service Account
 1. To get started you will need a Google service account user with `Cloud Build Service Account`, `Firebase Admin` and `API Keys Admin roles` as shown in the Firebase [docs](https://cloud.google.com/build/docs/deploying-builds/deploy-firebase#required_iam_permissions).
 
-2. You can follow the step-by-step guide to create the service account user [here](../yaml-publishing/firebase-app-distribution/).
+2. You can follow the step-by-step guide to create the service account user [here](../yaml-distributing/firebase-app-distribution/).
 
 3. Configure the `JSON` key received from step 2 as an environment variable name `FIREBASE_SERVICE_ACCOUNT` .
 
diff --git a/content/yaml-distributing/github-releases.md b/content/yaml-distributing/github-releases.md
@@ -2,7 +2,9 @@
 title: Github Releases with codemagic.yaml
 linkTitle: GitHub releases
 description: How to deploy an app to Github Releases using codemagic.yaml
-weight: 9
+weight: 7
+aliases:
+  - /yaml-publishing/github-releases
 ---
 
 <p>
@@ -70,4 +72,4 @@ In order to enable Codemagic to publish releases to GitHub, you need to grant it
          # Any number of artifacts can be included with the release.
 {{< /highlight >}}
 
-See more options about `gh release create` usage from [GitHub CLI official docs](https://cli.github.com/manual/gh_release_create)
+See more options about `gh release create` usage from [GitHub CLI official docs](https://cli.github.com/manual/gh_release_create)
diff --git a/content/yaml-distributing/google-cloud-storage.md b/content/yaml-distributing/google-cloud-storage.md
diff --git a/content/yaml-distributing/post-publish.md b/content/yaml-distributing/post-publish.md
diff --git a/content/yaml-distributing/pub.dev.md b/content/yaml-distributing/pub.dev.md
diff --git a/content/yaml-distributing/publishing-to-codemagic-static-pages.md b/content/yaml-distributing/publishing-to-codemagic-static-pages.md
diff --git a/content/yaml-distributing/tester-groups.md b/content/yaml-distributing/tester-groups.md
diff --git a/content/yaml-quick-start/first-signed-build.md b/content/yaml-quick-start/first-signed-build.md
diff --git a/content/yaml-testing/ios-provisioning.md b/content/yaml-testing/ios-provisioning.md
