Update blog post links

Author: maartenba

astro.config.mjs

@@ -120,7 +120,7 @@ export default defineConfig({
         {
           icon: "rss",
           label: "Blog",
-          href: "https://blog.duendesoftware.com/",
+          href: "https://duendesoftware.com/blog",
         },
       ],
       components: {

src/content/docs/bff/samples/index.mdx

@@ -96,7 +96,7 @@ This sample shows how to use the BFF extensions for Microsoft YARP.
 ## OpenAPI and SwaggerUI
 
 This sample shows how to use OpenAPI and SwaggerUI in combination with BFF.
-A walkthrough is available [on the Duende blog](https://blog.duendesoftware.com/posts/20250430-managing-openapi-specifications-with-backend-for-frontend-and-swagger-ui).
+A walkthrough is available [on the Duende blog](https://duendesoftware.com/blog/20250430-managing-openapi-specifications-with-backend-for-frontend-and-swagger-ui).
 
 <LinkCard
   description="GitHub Repository for the BFF framework integration with OpenAPI and SwaggerUI"

src/content/docs/general/glossary.mdx

@@ -39,7 +39,7 @@ handling this key material, including storage and rotation.
 <CardGrid>
   <LinkCard
     description="Automatic Key Management post"
-    href="https://blog.duendesoftware.com/posts/20201028_key_management/"
+    href="https://duendesoftware.com/blog/20201028-key-management"
     title="More Details"
     target="_blank"
   />
@@ -65,7 +65,7 @@ server-side sessions enables more architectural features in your IdentityServer,
 <CardGrid>
   <LinkCard
     description="Server-side Session Management post"
-    href="https://blog.duendesoftware.com/posts/20220406_session_management/"
+    href="https://duendesoftware.com/blog/20220406-session-management"
     title="More Details"
     target="_blank"
   />
@@ -86,7 +86,7 @@ browser-based frontends (e.g. SPAs or Blazor WASM applications) with ASP.NET Cor
 <CardGrid>
   <LinkCard
     description="BFF Security Framework post"
-    href="https://blog.duendesoftware.com/posts/20210326_bff/"
+    href="https://duendesoftware.com/blog/20210326-bff"
     title="More Details"
     target="_blank"
   />
@@ -133,7 +133,7 @@ This is designed to address the performance concern and allowing changes to the
 <CardGrid>
   <LinkCard
     description="Dynamic Authentication Providers post"
-    href="https://blog.duendesoftware.com/posts/20210517_dynamic_providers/"
+    href="https://duendesoftware.com/blog/20210517-dynamic-providers"
     title="More Details"
     target="_blank"
   />
@@ -155,7 +155,7 @@ boundary.
 <CardGrid>
   <LinkCard
     description="Resource Isolation post"
-    href="https://blog.duendesoftware.com/posts/20201230_resource_isolation/"
+    href="https://duendesoftware.com/blog/20201230-resource-isolation"
     title="More Details"
     target="_blank"
   />
@@ -178,7 +178,7 @@ CIBA is one of the requirements to support the Financal-grade API compliance.
 <CardGrid>
   <LinkCard
     description="Client-Initiated Backchannel Authentication post"
-    href="https://blog.duendesoftware.com/posts/20220107_ciba/"
+    href="https://duendesoftware.com/blog/20220107-ciba"
     title="More Details"
     target="_blank"
   />

src/content/docs/identityserver/quickstarts/javascript-clients/index.md

@@ -16,7 +16,7 @@ with a backend and those without.
 
 Browser-based applications **with a backend** are more secure, making it the
 recommended style. This style uses the ["Backend For Frontend"
-pattern](https://blog.duendesoftware.com/posts/20210326_bff/), or "BFF" for
+pattern](https://duendesoftware.com/blog/20210326-bff), or "BFF" for
 short, which relies on the backend host to implement all the security
 protocol interactions with the token server. The `Duende.BFF` library is used in
 [this quickstart](/identityserver/quickstarts/javascript-clients/js-with-backend/) to easily support the BFF pattern.

src/content/docs/identityserver/tokens/refresh.md

@@ -117,7 +117,7 @@ the flag is off, the token is marked as consumed instead. Prior to version 6.3,
 marked as consumed.
 
 Rotating the tokens on every
-use [has limited security benefits](https://blog.duendesoftware.com/posts/20240405_refresh_token_reuse/) regardless of
+use [has limited security benefits](https://duendesoftware.com/blog/20240405-refresh-token-reuse) regardless of
 which type of client is used. And it comes with the cost of database pressure and reliability issues. Reusable refresh
 tokens are robust to network failures in a way that one time use tokens are not: if a one-time use refresh token is used
 to produce a new token, but the response containing the new refresh token is lost due to a network issue, the client