Fix redirects (#1697)

## Type of change
<!-- Please be sure to add the appropriate label to your PR. -->
Evan flagged some broken redirects for us. This PR fixes those.

I also have had a sticky note on my desk to rearrange the Getting
Started guides into alphabetical order, so I added those changes to this
PR as well.

### What should this PR do?
<!-- Does this PR resolve an issue? Please include a reference to it.
-->
resolves #1696 

### Why are we making this change?
<!-- What larger problem does this PR address? -->

### What are the acceptance criteria? 
<!-- What should be happening for this PR to be accepted? Please list
criteria. -->
<!-- Do any stakeholders need to be tagged in this review? If so, please
add them. -->

### How should this PR be tested?
<!-- What should your reviewer do to test this PR? Please list steps.
-->
I updated the links directly so they should all work, no need to check
the actual redirects. I did adjust the relevant doc's alias, though,
which should catch anything I missed.

---------

Signed-off-by: Mark Drake <mark@chainguard.dev>

content/chainguard/administration/custom-idps/custom-idps/index.md

@@ -240,4 +240,4 @@ In the case of an outage or misconfiguration of your identity provider, it can b
 
 As an OIDC login account needs to be set up to bootstrap the SSO identity provider initially, it’s possible to keep this account as a breakglass account in case you need it for recovery. However, the nature of these OIDC provider accounts is such that it is difficult to share them as a breakglass resource as they’re often tied to a single user.
 
-Instead of relying on an account with an OIDC login provider, you can alternatively set up an assumable identity to use as a backup account. Refer to our [conceptual guide on assumable identities](/chainguard/chainguard-enforce/iam-groups/assumable-ids/) to learn more.
+Instead of relying on an account with an OIDC login provider, you can alternatively set up an assumable identity to use as a backup account. Refer to our [conceptual guide on assumable identities](/chainguard/administration/iam-organizations/assumable-ids/) to learn more.

content/chainguard/administration/iam-organizations/assumable-ids.md

@@ -3,6 +3,8 @@ title : "Overview of Assumable Identities in Chainguard"
 linktitle: "Assumable Identities"
 aliases: 
 - /chainguard/chainguard-enforce/authentication/assumable-ids/
+- /chainguard/chainguard-enforce/iam-groups/assumable-ids/
+- /chainguard/administration/iam-organizations/assumable-ids/
 lead: ""
 description: "An overview of what assumable identities are and how they can be used with Chainguard assets."
 type: "article"

content/chainguard/administration/iam-organizations/identity-examples/aws-identity.md

@@ -14,7 +14,7 @@ images: []
 weight: 012
 ---
 
-Chainguard's [*assumable identities*](/chainguard/chainguard-enforce/iam-groups/assumable-ids/) are identities that can be assumed by external applications or workflows in order to perform certain tasks that would otherwise have to be done by a human.
+Chainguard's [*assumable identities*](/chainguard/administration/iam-organizations/assumable-ids/) are identities that can be assumed by external applications or workflows in order to perform certain tasks that would otherwise have to be done by a human.
 
 This procedural tutorial outlines how to create an identity using Terraform, and then create an AWS role that will assume the identity to interact with Chainguard resources. This can be used to authorize requests from AWS Lambda, ECS, EKS, or any other AWS service that supports [IAM roles for service accounts](https://docs.aws.amazon.com/eks/latest/userguide/iam-roles-for-service-accounts.html).
 
@@ -305,4 +305,4 @@ Following that, all of the example resources created in this guide will be remov
 
 ## Learn more
 
-For more information about how assumable identities work in Chainguard, check out our [conceptual overview of assumable identities](/chainguard/chainguard-enforce/iam-groups/assumable-ids/). Additionally, the Terraform documentation includes a section on [recommended best practices](https://developer.hashicorp.com/terraform/cloud-docs/recommended-practices) which you can refer to if you'd like to build on this Terraform configuration for a production environment.
+For more information about how assumable identities work in Chainguard, check out our [conceptual overview of assumable identities](/chainguard/administration/iam-organizations/assumable-ids/). Additionally, the Terraform documentation includes a section on [recommended best practices](https://developer.hashicorp.com/terraform/cloud-docs/recommended-practices) which you can refer to if you'd like to build on this Terraform configuration for a production environment.

content/chainguard/administration/iam-organizations/identity-examples/bitbucket-identity.md

@@ -14,7 +14,7 @@ images: []
 weight: 020
 ---
 
-Chaingaurd's [*assumable identities*](/chainguard/chainguard-enforce/iam-groups/assumable-ids/) are identities that can be assumed by external applications or workflows in order to perform certain tasks that would otherwise have to be done by a human.
+Chaingaurd's [*assumable identities*](/chainguard/administration/iam-organizations/assumable-ids/) are identities that can be assumed by external applications or workflows in order to perform certain tasks that would otherwise have to be done by a human.
 
 This procedural tutorial outlines how to create an identity using Terraform, and then how to update a Bitbucket pipeline so that it can assume the identity and interact with Chainguard resources.
 
@@ -286,4 +286,4 @@ Following that, all of the example resources created in this guide will be remov
 
 ## Learn more
 
-For more information about how assumable identities work in Chainguard, check out our [conceptual overview of assumable identities](/chainguard/chainguard-enforce/iam-groups/assumable-ids/). Additionally, the Terraform documentation includes a section on [recommended best practices](https://developer.hashicorp.com/terraform/cloud-docs/recommended-practices) which you can refer to if you'd like to build on this Terraform configuration for a production environment. Likewise, for more information on using Bitbucket pipelines, we encourage you to check out the [official project documentation](https://support.atlassian.com/bitbucket-cloud/docs/get-started-with-bitbucket-pipelines/), particularly their [documentation on OIDC](https://support.atlassian.com/bitbucket-cloud/docs/integrate-pipelines-with-resource-servers-using-oidc/).
+For more information about how assumable identities work in Chainguard, check out our [conceptual overview of assumable identities](/chainguard/administration/iam-organizations/assumable-ids/). Additionally, the Terraform documentation includes a section on [recommended best practices](https://developer.hashicorp.com/terraform/cloud-docs/recommended-practices) which you can refer to if you'd like to build on this Terraform configuration for a production environment. Likewise, for more information on using Bitbucket pipelines, we encourage you to check out the [official project documentation](https://support.atlassian.com/bitbucket-cloud/docs/get-started-with-bitbucket-pipelines/), particularly their [documentation on OIDC](https://support.atlassian.com/bitbucket-cloud/docs/integrate-pipelines-with-resource-servers-using-oidc/).

content/chainguard/administration/iam-organizations/identity-examples/buildkite-identity.md

@@ -14,7 +14,7 @@ images: []
 weight: 015
 ---
 
-Chainguard's [*assumable identities*](/chainguard/chainguard-enforce/iam-groups/assumable-ids/) are identities that can be assumed by external applications or workflows in order to perform certain tasks that would otherwise have to be done by a human.
+Chainguard's [*assumable identities*](/chainguard/administration/iam-organizations/assumable-ids/) are identities that can be assumed by external applications or workflows in order to perform certain tasks that would otherwise have to be done by a human.
 
 This procedural tutorial outlines how to create an identity using Terraform, and then how to update a Buildkite pipeline so that it can assume the identity and interact with Chainguard resources.
 
@@ -296,4 +296,4 @@ Following that, all of the example resources created in this guide will be remov
 
 ## Learn more
 
-For more information about how assumable identities work in Chainguard, check out our [conceptual overview of assumable identities](/chainguard/chainguard-enforce/iam-groups/assumable-ids/). Additionally, the Terraform documentation includes a section on [recommended best practices](https://developer.hashicorp.com/terraform/cloud-docs/recommended-practices) which you can refer to if you'd like to build on this Terraform configuration for a production environment. Likewise, for more information on using Buildkite, we encourage you to check out the [official project documentation](https://buildkite.com/docs), particularly their [documentation on Buildkite OIDC](https://buildkite.com/docs/agent/v3/cli-oidc).
+For more information about how assumable identities work in Chainguard, check out our [conceptual overview of assumable identities](/chainguard/administration/iam-organizations/assumable-ids/). Additionally, the Terraform documentation includes a section on [recommended best practices](https://developer.hashicorp.com/terraform/cloud-docs/recommended-practices) which you can refer to if you'd like to build on this Terraform configuration for a production environment. Likewise, for more information on using Buildkite, we encourage you to check out the [official project documentation](https://buildkite.com/docs), particularly their [documentation on Buildkite OIDC](https://buildkite.com/docs/agent/v3/cli-oidc).

content/chainguard/administration/iam-organizations/identity-examples/gitlab-identity.md

@@ -14,7 +14,7 @@ images: []
 weight: 010
 ---
 
-Chainguard's [*assumable identities*](/chainguard/chainguard-enforce/iam-groups/assumable-ids/) are identities that can be assumed by external applications or workflows in order to perform certain tasks that would otherwise have to be done by a human.
+Chainguard's [*assumable identities*](/chainguard/administration/iam-organizations/assumable-ids/) are identities that can be assumed by external applications or workflows in order to perform certain tasks that would otherwise have to be done by a human.
 
 This procedural tutorial outlines how to create an identity using Terraform, and then create a GitLab CI/CD pipeline that will assume the identity to interact with Chainguard resources.
 
@@ -296,4 +296,4 @@ Following that, all of the example resources created in this guide will be remov
 
 ## Learn more
 
-For more information about how assumable identities work in Chainguard, check out our [conceptual overview of assumable identities](/chainguard/chainguard-enforce/iam-groups/assumable-ids/). Additionally, the Terraform documentation includes a section on [recommended best practices](https://developer.hashicorp.com/terraform/cloud-docs/recommended-practices) which you can refer to if you'd like to build on this Terraform configuration for a production environment. Likewise, for more information on using GitLab CI/CD pipelines, we encourage you to check out the [official documentation on the subject](https://docs.gitlab.com/ee/ci/pipelines/).
+For more information about how assumable identities work in Chainguard, check out our [conceptual overview of assumable identities](/chainguard/administration/iam-organizations/assumable-ids/). Additionally, the Terraform documentation includes a section on [recommended best practices](https://developer.hashicorp.com/terraform/cloud-docs/recommended-practices) which you can refer to if you'd like to build on this Terraform configuration for a production environment. Likewise, for more information on using GitLab CI/CD pipelines, we encourage you to check out the [official documentation on the subject](https://docs.gitlab.com/ee/ci/pipelines/).

content/chainguard/administration/iam-organizations/identity-examples/keycloak-identity.md

@@ -14,7 +14,7 @@ images: []
 weight: 040
 ---
 
-Chainguard's [*assumable identities*](/chainguard/chainguard-enforce/iam-groups/assumable-ids/) are identities that can be assumed by external applications or workflows in order to perform certain tasks that would otherwise have to be done by a human.
+Chainguard's [*assumable identities*](/chainguard/administration/iam-organizations/assumable-ids/) are identities that can be assumed by external applications or workflows in order to perform certain tasks that would otherwise have to be done by a human.
 
 This procedural tutorial outlines how to create an identity using Terraform, and then assume the identity with the CLI to interact with Chainguard resources.
 
@@ -289,4 +289,4 @@ Following that, all of the example resources created in this guide will be remov
 
 ## Learn more
 
-For more information about how assumable identities work in Chainguard, check out our [conceptual overview of assumable identities](/chainguard/chainguard-enforce/iam-groups/assumable-ids/). Additionally, the Terraform documentation includes a section on [recommended best practices](https://developer.hashicorp.com/terraform/cloud-docs/recommended-practices) which you can refer to if you'd like to build on this Terraform configuration for a production environment. For more information about OIDC you can find a lot of documentation on the [OpenID Foundation website](https://openid.net/). For Keycloak specific information, we encourage you to check out the [official Keycloak documentation](https://www.keycloak.org/documentation)
+For more information about how assumable identities work in Chainguard, check out our [conceptual overview of assumable identities](/chainguard/administration/iam-organizations/assumable-ids/). Additionally, the Terraform documentation includes a section on [recommended best practices](https://developer.hashicorp.com/terraform/cloud-docs/recommended-practices) which you can refer to if you'd like to build on this Terraform configuration for a production environment. For more information about OIDC you can find a lot of documentation on the [OpenID Foundation website](https://openid.net/). For Keycloak specific information, we encourage you to check out the [official Keycloak documentation](https://www.keycloak.org/documentation)

content/chainguard/chainguard-images/getting-started/cilium/index.md

@@ -13,7 +13,7 @@ images: []
 menu:
   docs:
     parent: "getting-started"
-weight: 610
+weight: 005
 toc: true
 ---
 

content/chainguard/chainguard-images/getting-started/go.md

@@ -13,7 +13,7 @@ images: []
 menu:
   docs:
     parent: "getting-started"
-weight: 610
+weight: 010
 toc: true
 ---
 

content/chainguard/chainguard-images/getting-started/istio.md

@@ -13,7 +13,7 @@ images: []
 menu:
   docs:
     parent: "getting-started"
-weight: 610
+weight: 015
 toc: true
 ---
 

content/chainguard/chainguard-images/getting-started/laravel.md

@@ -11,7 +11,7 @@ images: []
 menu:
   docs:
     parent: "getting-started"
-weight: 610
+weight: 020
 toc: true
 ---
 

content/chainguard/chainguard-images/getting-started/mariadb/index.md

@@ -13,7 +13,7 @@ images: []
 menu:
   docs:
     parent: "getting-started"
-weight: 610
+weight: 025
 toc: true
 ---
 

content/chainguard/chainguard-images/getting-started/nemo/index.md

@@ -13,7 +13,7 @@ images: []
 menu:
   docs:
     parent: "getting-started"
-weight: 612
+weight: 030
 toc: true
 ---
 

content/chainguard/chainguard-images/getting-started/nginx/index.md

@@ -13,7 +13,7 @@ images: []
 menu:
   docs:
     parent: "getting-started"
-weight: 610
+weight: 035
 toc: true
 ---
 

content/chainguard/chainguard-images/getting-started/node.md

@@ -13,7 +13,7 @@ images: []
 menu:
   docs:
     parent: "getting-started"
-weight: 610
+weight: 040
 toc: true
 ---
 

content/chainguard/chainguard-images/getting-started/php.md

@@ -13,7 +13,7 @@ images: []
 menu:
   docs:
     parent: "getting-started"
-weight: 610
+weight: 045
 toc: true
 ---
 

content/chainguard/chainguard-images/getting-started/postgres/index.md

@@ -13,7 +13,7 @@ images: []
 menu:
   docs:
     parent: "getting-started"
-weight: 610
+weight: 050
 toc: true
 ---
 

content/chainguard/chainguard-images/getting-started/python.md

@@ -13,7 +13,7 @@ images: []
 menu:
   docs:
     parent: "getting-started"
-weight: 610
+weight: 055
 toc: true
 ---
 

content/chainguard/chainguard-images/getting-started/pytorch-cuda/index.md

@@ -13,7 +13,7 @@ images: []
 menu:
   docs:
     parent: "getting-started"
-weight: 611
+weight: 060
 toc: true
 ---
 

content/chainguard/chainguard-images/getting-started/ruby.md

@@ -13,7 +13,7 @@ images: []
 menu:
   docs:
     parent: "getting-started"
-weight: 610
+weight: 065
 toc: true
 ---