replaces new /documentation/ links

Paul Savoie · Paul Savoie · commit 66341994cd97 · 2025-08-04T10:44:14.000+02:00
diff --git a/docs/artifact-configuration/reference.md b/docs/artifact-configuration/reference.md
@@ -284,7 +284,7 @@ Create detached GPG signatures to sign any file with a GPG key
 >
 > Our documentation uses the term GPG for these key and signature types. While OpenPGP would be the technically correct term, is often referred to via its de-facto standard implementation, _GNU Privacy Guard_ (GPG or GnuPG). The first implementation was _Pretty Good Privacy_ (PGP), and the format was ultimately standardized as OpenPGP. 
 >
-> The GPG community uses various terms for certificates, including _GPG Key_, _Public Key_, _Transferable Public Key_ and _Certificate_. To avoid confusion with the public key of a asymmetric key pair, and for consistency within our documentation, we use the term _GPG Key_ as a specific type of _Certificate_. See [Managing Certificates](/documentation/managing-certificates#certificate-types) for more information.
+> The GPG community uses various terms for certificates, including _GPG Key_, _Public Key_, _Transferable Public Key_ and _Certificate_. To avoid confusion with the public key of a asymmetric key pair, and for consistency within our documentation, we use the term _GPG Key_ as a specific type of _Certificate_. See [Managing Certificates](/managing-certificates#certificate-types) for more information.
 
 {:.panel.note}
 > **Detached signature files and GPG key reference**
diff --git a/docs/assets/js/main-bundle.js b/docs/assets/js/main-bundle.js
diff --git a/docs/crypto-providers/cryptoki.md b/docs/crypto-providers/cryptoki.md
@@ -58,7 +58,7 @@ Check the output of `openssl version` on your target system to select the correc
 
 ### Configuration
 
-See [SignPath Crypto Providers](/documentation/crypto-providers/#crypto-provider-configuration) for general configuration options.
+See [SignPath Crypto Providers](/crypto-providers/#crypto-provider-configuration) for general configuration options.
 
 ### Parameters {#cryptoki-parameters}
 
diff --git a/docs/crypto-providers/gpg.md b/docs/crypto-providers/gpg.md
@@ -12,7 +12,7 @@ description: Creating GPG signatures with SignPath
 
 ## Terminology
 
-GPG uses various terms for certificates. We use the term **_GPG key_** in our GPG documentation, but keep in mind that other parts of the SignPath documentation will use the general term _certificate_. See [Managing Certificates](/documentation/managing-certificates#certificate-types) for more information.
+GPG uses various terms for certificates. We use the term **_GPG key_** in our GPG documentation, but keep in mind that other parts of the SignPath documentation will use the general term _certificate_. See [Managing Certificates](/managing-certificates#certificate-types) for more information.
 
 ### Using GnuPG with PKCS #11
 
@@ -64,7 +64,7 @@ While executing each signing tool, SignPath is called to perform a hash-based si
 
 For `gnupg-pkcs11-scd`, `stdout` console output must be disabled. Use the log files for troubleshooting.
 
-The [`InitializeSignPathCryptoProviderGpgSigning` helper function](/documentation/crypto-providers/gpg#configure-gnupg) uses the following logging directories:
+The [`InitializeSignPathCryptoProviderGpgSigning` helper function](/crypto-providers/gpg#configure-gnupg) uses the following logging directories:
 
 * SignPath Cryptoki logs: `/tmp/SignPathLogs/<timestamp>.log`
 * `gnupg-pkcs11-scd` logs: `/tmp/SignPathLogs/gnupg-pkcs11-scd.log`
diff --git a/docs/crypto-providers/macos.md b/docs/crypto-providers/macos.md
@@ -20,7 +20,7 @@ Simply copy-deploy the `SignPathCryptoTokenKit.app` application to the target sy
 
 ### Configuration
 
-See [SignPath Crypto Providers](/documentation/crypto-providers/#crypto-provider-configuration) for general configuration options.
+See [SignPath Crypto Providers](/crypto-providers/#crypto-provider-configuration) for general configuration options.
 
 ### Background
 
diff --git a/docs/crypto-providers/windows.md b/docs/crypto-providers/windows.md
@@ -85,7 +85,7 @@ msiexec /x SignPathCryptoProviders-$Version.msi /qn /L* uninstall.log | Out-Host
 
 ### Configuration
 
-See [SignPath Crypto Providers](/documentation/crypto-providers/#crypto-provider-configuration) for general configuration options.
+See [SignPath Crypto Providers](/crypto-providers/#crypto-provider-configuration) for general configuration options.
 
 ## Using KSP/CSP parameters of signing tools
 
diff --git a/docs/managing-certificates.md b/docs/managing-certificates.md
@@ -22,7 +22,7 @@ With SignPath, you have the following options for creating or importing a certif
 * **Self-signed X.509 certificates** are not signed by any certificate authority and therefore not trusted. You can use them for testing your release process.
 * **X.509 certificate signing requests (CSRs)** can be created using SignPath. You can use the CSR to purchase a certificate from a trusted certificate authority (CA). By creating a CSR, you ensure that the private key is created directly on our hardware security module (HSM) and cannot be compromised. This is the recommended way for securing your code signing process. Once issued, you can [upload the certificate](#ca-issued-x509-certificates) to SignPath.
 * **PFX-imported X.509 certificates**: If you already own a certificate, you can simply upload it. However, as your private key may have already been exposed, we recommend to use PFX imports only as a temporary solution. (Only available for RSA keys.)
-* **GPG keys** are certificates based on the OpenPGP standard, usually referred to as GPG or GnuPG. They can be used to sign arbitrary files using [GPG detached signatures](/documentation/artifact-configuration/reference#create-gpg-signature) or using our [crypto providers](/documentation/crypto-providers/gpg). GPG is also the foundation of many Linux and Open Source signing formats including RPM and Debian package signing.
+* **GPG keys** are certificates based on the OpenPGP standard, usually referred to as GPG or GnuPG. They can be used to sign arbitrary files using [GPG detached signatures](/artifact-configuration/reference#create-gpg-signature) or using our [crypto providers](/crypto-providers/gpg). GPG is also the foundation of many Linux and Open Source signing formats including RPM and Debian package signing.
 
 {:.panel.info}
 > **GPG keys and certificates**
diff --git a/docs/redirects/app/PowershellArtifactConfigurationParametersLink.md b/docs/redirects/app/PowershellArtifactConfigurationParametersLink.md
@@ -1,4 +1,4 @@
 ---
 # Used in the powershell module
-redirect_to: /documentation/artifact-configuration/syntax#parameters
+redirect_to: /artifact-configuration/syntax#parameters
 ---
diff --git a/docs/redirects/app/PowershellGetCertificateByMicrosoftTemplateIdLink.md b/docs/redirects/app/PowershellGetCertificateByMicrosoftTemplateIdLink.md
@@ -1,4 +1,4 @@
 ---
 # Used in the powershell module
-redirect_to: /documentation/powershell/Get-CertificateByMicrosoftTemplateId
+redirect_to: /powershell/Get-CertificateByMicrosoftTemplateId
 ---
diff --git a/docs/redirects/app/PowershellGetSignedArtifactLink.md b/docs/redirects/app/PowershellGetSignedArtifactLink.md
@@ -1,4 +1,4 @@
 ---
 # Used in the powershell module
-redirect_to: /documentation/powershell/Get-SignedArtifact
+redirect_to: /powershell/Get-SignedArtifact
 ---
diff --git a/docs/redirects/app/PowershellSubmitSigningRequestLink.md b/docs/redirects/app/PowershellSubmitSigningRequestLink.md
@@ -1,4 +1,4 @@
 ---
 # Used in the powershell module
-redirect_to: /documentation/powershell/Submit-SigningRequest
+redirect_to: /powershell/Submit-SigningRequest
 ---
diff --git a/docs/redirects/app/UsersNotificationsLink.md b/docs/redirects/app/UsersNotificationsLink.md
@@ -1,4 +1,4 @@
 ---
 # Used in the change notification view
-redirect_to: /documentation/users#notifications
+redirect_to: /users#notifications
 ---
diff --git a/docs/redirects/connectors/azure-devops-submit-signing-request-task.md b/docs/redirects/connectors/azure-devops-submit-signing-request-task.md
@@ -1,4 +1,4 @@
 ---
 # Used for the link the Azure DevOps Task
-redirect_to: /documentation/trusted-build-systems/azure-devops
+redirect_to: /trusted-build-systems/azure-devops
 ---
diff --git a/docs/trusted-build-systems/azure-devops.md b/docs/trusted-build-systems/azure-devops.md
@@ -8,7 +8,7 @@ description: Azure DevOps
 
 ## Prerequisites
 
-* In SignPath: [Use the predefined Trusted Build System](/documentation/trusted-build-systems#configuration) _Azure DevOps (dev.azure.com)_.
+* In SignPath: [Use the predefined Trusted Build System](/trusted-build-systems#configuration) _Azure DevOps (dev.azure.com)_.
 * Create an artifact configuration with the following format:
     ```xml
     <?xml version="1.0" encoding="utf-8" ?>
@@ -20,7 +20,7 @@ description: Azure DevOps
       </zip-file>
     </artifact-configuration>
     ```
-    See [Artifact Configurations](/documentation/artifact-configuration) for more details.
+    See [Artifact Configurations](/artifact-configuration) for more details.
 
     {:.panel.info}
     > **Root folder in artifact configuration**
@@ -43,7 +43,7 @@ description: Azure DevOps
 The Azure DevOps connector performs the following checks:
 
 * A build was actually performed by an Azure DevOps pipeline, not by some other entity in possession of the API token
-* [Origin metadata](/documentation/origin-verification) is provided by Azure DevOps, not the build script, and can therefore not be forged
+* [Origin metadata](/origin-verification) is provided by Azure DevOps, not the build script, and can therefore not be forged
 * The artifact is stored on the Azure DevOps server before it is submitted for signing
 
 ## Usage
@@ -90,7 +90,7 @@ steps:
 | `serviceUnavailableTimeoutInSeconds`          | `600`                         | Total time in seconds that the action will wait for a single service call to succeed (across several retries).
 
 | `downloadSignedArtifactTimeoutInSeconds`      | `300`                         | HTTP timeout when downloading the signed artifact. Defaults to 5 minutes.
-| `parameters`                                  |                               | Multiline-string of values that map to [user-defined parameters](/documentation/artifact-configuration/syntax#parameters) in the Artifact Configuration. Use one line per parameter with the format `<name>: "<value>"` where `<value>` needs to be a valid JSON string.
+| `parameters`                                  |                               | Multiline-string of values that map to [user-defined parameters](/artifact-configuration/syntax#parameters) in the Artifact Configuration. Use one line per parameter with the format `<name>: "<value>"` where `<value>` needs to be a valid JSON string.
 
 ### Action output variables
 
diff --git a/package-lock.json b/package-lock.json
diff --git a/webpack/changelog.js b/webpack/changelog.js
diff --git a/yarn.lock b/yarn.lock

Original file line number	Diff line number	Diff line change
`@@ -284,7 +284,7 @@ Create detached GPG signatures to sign any file with a GPG key`
`284`	`284`	`>`
`285`	`285`	`> Our documentation uses the term GPG for these key and signature types. While OpenPGP would be the technically correct term, is often referred to via its de-facto standard implementation, _GNU Privacy Guard_ (GPG or GnuPG). The first implementation was _Pretty Good Privacy_ (PGP), and the format was ultimately standardized as OpenPGP.`
`286`	`286`	`>`
`287`		`-> The GPG community uses various terms for certificates, including _GPG Key_, _Public Key_, _Transferable Public Key_ and _Certificate_. To avoid confusion with the public key of a asymmetric key pair, and for consistency within our documentation, we use the term _GPG Key_ as a specific type of _Certificate_. See [Managing Certificates](/documentation/managing-certificates#certificate-types) for more information.`
	`287`	`+> The GPG community uses various terms for certificates, including _GPG Key_, _Public Key_, _Transferable Public Key_ and _Certificate_. To avoid confusion with the public key of a asymmetric key pair, and for consistency within our documentation, we use the term _GPG Key_ as a specific type of _Certificate_. See [Managing Certificates](/managing-certificates#certificate-types) for more information.`
`288`	`288`
`289`	`289`	`{:.panel.note}`
`290`	`290`	`> Detached signature files and GPG key reference`