Resolves skipped backporting between versions 0.29.0 and 0.30.0

website/versioned_docs/version-0.29.0/enterprise/getting-started/releases-enterprise.mdx

@@ -597,7 +597,7 @@ config
 - Weave GitOps default admin user can now “read” all objects. Why is this important? As users are trying out Weave GitOps they will most likely try it out with some of their favorite Cloud Native tools such as Crossplane, Tekton, Istio, etc. This enables them to see all of those resources and explore the full power of Weave GitOps. We still do not recommend this user for “production-use” cases, and customers should always be pushed towards implementing OIDC with scoped roles.
 
 #### Pipelines - adding Pipelines through Templates
-- From the Pipelines view you can add new Pipelines in a way which leverages GitOpsTemplates, additionally - to help users configure these, we’ve provided [documentation](../../pipelines/pipeline-templates.mdx) which has some samples.
+- From the Pipelines view you can add new Pipelines in a way which leverages GitOpsTemplates, additionally - to help users configure these, we’ve provided [documentation](../../pipelines/pipelines-templates.mdx) which has some samples.
 
 #### Support for multiple Flux instances on a single cluster
 - Support for running multiple flux instances in different namespaces on a single cluster for resource isolation.

website/versioned_docs/version-0.29.0/gitops-run/get-started.mdx → website/versioned_docs/version-0.29.0/gitops-run/gitops-run-get-started.mdx

@@ -1,5 +1,5 @@
 ---
-title: Tutorial
+title: Getting Started
 hide_title: true
 ---
 

website/versioned_docs/version-0.29.0/gitops-run/overview.mdx → website/versioned_docs/version-0.29.0/gitops-run/gitops-run-overview.mdx

@@ -1,5 +1,5 @@
 ---
-title: Overview
+title: GitOps Run Overview
 hide_title: true
 ---
 

website/versioned_docs/version-0.29.0/gitops-templates/quickstart-templates.mdx

@@ -67,7 +67,7 @@ templates are now available for use:
 
 ## Available Templates
 
-The following [pipeline](../pipelines/pipeline-templates.mdx) templates have
+The following [pipeline](../pipelines/pipelines-templates.mdx) templates have
 been made available on your Weave GitOps Enterprise instance:
 
 - `pipeline-view`: A template to create a sample pipeline to visualize a

website/versioned_docs/version-0.29.0/gitopssets/intro.mdx → website/versioned_docs/version-0.29.0/gitopssets/gitopssets-intro.mdx

@@ -28,11 +28,11 @@ GitOpsSets will create out of the single resource all the objects and Flux primi
 
 **The initial generators that are coming with the preview release are:**
 
-- [List Generator](./guide.mdx#list-generator): The simplest generator. Provide a list of Key/Value pairs that you want to feed the template with.
-- [Git Generator](./guide.mdx#gitrepository-generator): Enable to extract a set of files (environment-specific configurations) from a Flux GitRepository, and make the contents of these available to the templates, this would let you have config in *app-dev.json*, *app-staging.json* and *app-production.json* for example, and the contents of these would be available to the templates.
-- [Matrix Generator](./guide.mdx#matrix-generator): Combine slices of generators into the desired compounded input.
-- [Pull request Generator](./guide.mdx#pullrequests-generator): Automatically discover open pull requests within a repository to generate a new deployment.
-- [API Client Generator](./guide.mdx#apiclient-generator): Poll an HTTP endpoint and parse the result as the generated values.
+- [List Generator](./templating-from-generators.mdx#list-generator): The simplest generator. Provide a list of Key/Value pairs that you want to feed the template with.
+- [Git Generator](./templating-from-generators.mdx#gitrepository-generator): Enable to extract a set of files (environment-specific configurations) from a Flux GitRepository, and make the contents of these available to the templates, this would let you have config in *app-dev.json*, *app-staging.json* and *app-production.json* for example, and the contents of these would be available to the templates.
+- [Matrix Generator](./templating-from-generators.mdx#matrix-generator): Combine slices of generators into the desired compounded input.
+- [Pull request Generator](./templating-from-generators.mdx#pullrequests-generator): Automatically discover open pull requests within a repository to generate a new deployment.
+- [API Client Generator](./templating-from-generators.mdx#apiclient-generator): Poll an HTTP endpoint and parse the result as the generated values.
 
 
 ## Use cases

website/versioned_docs/version-0.29.0/pipelines/pipelines-intro.mdx

@@ -25,4 +25,4 @@ The Pipelines feature:
 	•	streamlines code deployment from one environment to another, and minimizes friction between application development and Ops teams
 	•	enables you to easily define which Helm charts are part of the environments you create—saving lots of time through automated package management
 
-Now that you know what delivery pipelines can do for you, follow the [guide to get started](../getting-started).
+Now that you know what delivery pipelines can do for you, follow the [guide to get started](../pipelines-getting-started).

website/versioned_docs/version-0.29.0/pipelines/promoting-applications.mdx

@@ -31,7 +31,7 @@ At the moment only applications defined as Flux `HelmReleases` are supported in
 <figcaption>An example of a pull request for an application promotion</figcaption>
 </figure>
 
-The [Getting started guide](../getting-started) describes how to create a basic pipeline for an application so you can visualize its deployments across a series of environments. You may also configure a pipeline in order to promote applications across a series of environments.
+The [Getting started guide](../pipelines-getting-started) describes how to create a basic pipeline for an application so you can visualize its deployments across a series of environments. You may also configure a pipeline in order to promote applications across a series of environments.
 There are currently two supported strategies for application promotions:
 - Pull request strategy: this strategy is used for applications that are delivered via Flux to all environments of a pipeline. Typically, the versions of these applications are stored in Git and therefore pull requests can be used to update them as part of a promotion.
 - Notification strategy: this strategy is used when an external CI system is responsible for promoting an application across the environments of a pipeline. In this strategy, the notification controller running on the management cluster is used to forward notifications of succesful promotions to external CI systems.

website/versioned_sidebars/version-0.29.0-sidebars.json

@@ -103,21 +103,21 @@
       "label": "GitOps Run",
       "link": {
         "type": "doc",
-        "id": "gitops-run/overview"
+        "id": "gitops-run/gitops-run-overview"
       },
       "items": [
-        "gitops-run/get-started"
+        "gitops-run/gitops-run-get-started"
       ]
     },
     {
       "type": "category",
       "label": "GitOpsSets",
       "items": [
-        "gitopssets/intro",
-        "gitopssets/installation",
-        "gitopssets/guide",
-        "gitopssets/api-reference",
-        "gitopssets/releases"
+        "gitopssets/gitopssets-intro",
+        "gitopssets/gitopssets-installation",
+        "gitopssets/templating-from-generators",
+        "gitopssets/gitopssets-api-reference",
+        "gitopssets/gitopssets-releases"
       ]
     },
     {
@@ -138,10 +138,10 @@
         "id": "pipelines/pipelines-intro"
       },
       "items": [
-        "pipelines/getting-started",
+        "pipelines/pipelines-getting-started",
         "pipelines/authorization",
         "pipelines/promoting-applications",
-        "pipelines/pipeline-templates",
+        "pipelines/pipelines-templates",
         "pipelines/pipelines-with-jenkins",
         "pipelines/pipelines-with-tekton",
         {