fix: broken external links

docs/integrations/social/oidc/README.mdx

@@ -107,4 +107,4 @@ Each social identity provider could have their own variant on OIDC standard prot
 | subject                              | string                             | False    |
 | typ                                  | string                             | False    |
 
-See [here](https://github.com/panva/jose/blob/main/docs/interfaces/jwt_verify.JWTVerifyOptions.md) to find more details about `IdTokenVerificationConfig`.
+See [here](https://github.com/panva/jose/blob/main/docs/jwt/verify/interfaces/JWTVerifyOptions.md) to find more details about `IdTokenVerificationConfig`.

docs/logto-oss/develop-your-connector/implement-connectors.mdx

@@ -49,7 +49,7 @@ In order to accomplish the flow, we need to have following three methods:
 
 `getAuthorizationUri` generates a redirect URL that can direct end-users to the page need users' authentication.
 
-The interface is defined as `GetAuthorizationUri` in [`@logto/connector-kit`](https://github.com/logto-io/logto/blob/master/packages/toolkit/connector-kit/src/types.ts).
+The interface is defined as `GetAuthorizationUri` in [`@logto/connector-kit`](https://github.com/logto-io/logto/blob/master/packages/toolkit/connector-kit/src/types/social.ts).
 
 You are allowed to store sign-in-related essential information using `setSession` (the second input parameter of `GetAuthorizationUri`) for the sake of `getUserInfo` method.
 
@@ -113,7 +113,7 @@ const getAccessToken = async (config: GithubConfig, code: string) => {
 
 `getUserInfo` fetches user information with access token got in previous step.
 
-The interface is defined as `GetUserInfo` in [`@logto/connector-kit`](https://github.com/logto-io/logto/blob/master/packages/toolkit/connector-kit/src/types.ts).
+The interface is defined as `GetUserInfo` in [`@logto/connector-kit`](https://github.com/logto-io/logto/blob/master/packages/toolkit/connector-kit/src/types/social.ts).
 
 For sign-in purposes, you can retrieve necessary information using the `getSession` function.
 

docs/quick-starts/framework/next/_integration.mdx

@@ -30,7 +30,7 @@ export const logtoClient = new LogtoClient({
 
 ### Prepare API routes
 
-Prepare [API routes](https://nextjs.org/docs/api-routes/introduction) to connect with Logto.
+Prepare [API routes](https://nextjs.org/docs/pages/building-your-application/routing/api-routes) to connect with Logto.
 
 Go back to your IDE/editor, use the following code to implement the API routes first:
 

docs/quick-starts/framework/webflow/_guide-tip.mdx

@@ -1,5 +1,5 @@
 :::tip
 
-- The sample project is available at [Webflow project preview](https://preview.webflow.com/preview/charless-trendy-site-f191c0?utm_medium=preview_link&utm_source=designer&utm_content=charless-trendy-site-f191c0&preview=0eae5f73661a8a5791787f0438bc29de&workflow=preview).
-- A live demo is deployed at https://charless-trendy-site-f191c0.webflow.io/.
-  :::
+The sample project is available at [Webflow project preview](https://preview.webflow.com/preview/charless-trendy-site-f191c0?utm_medium=preview_link&utm_source=designer&utm_content=charless-trendy-site-f191c0&preview=0eae5f73661a8a5791787f0438bc29de&workflow=preview).
+
+:::

i18n/de/docusaurus-plugin-content-docs/current/integrations/social/oidc/README.mdx

@@ -103,4 +103,4 @@ Du fragst dich vielleicht, warum ein standardmäßiges OIDC-Protokoll sowohl die
 | subject                                 | string                             | Nein         |
 | typ                                     | string                             | Nein         |
 
-Siehe [hier](https://github.com/panva/jose/blob/main/docs/interfaces/jwt_verify.JWTVerifyOptions.md) für weitere Details zu `IdTokenVerificationConfig`.
+Siehe [hier](https://github.com/panva/jose/blob/main/docs/jwt/verify/interfaces/JWTVerifyOptions.md) für weitere Details zu `IdTokenVerificationConfig`.

i18n/de/docusaurus-plugin-content-docs/current/logto-oss/develop-your-connector/implement-connectors.mdx

@@ -49,7 +49,7 @@ Um den Fluss zu vervollständigen, benötigen wir die folgenden drei Methoden:
 
 `getAuthorizationUri` generiert eine Umleitungs-URL, die Endbenutzer zur Seite leiten kann, die die Authentifizierung der Benutzer erfordert.
 
-Die Schnittstelle ist als `GetAuthorizationUri` in [`@logto/connector-kit`](https://github.com/logto-io/logto/blob/master/packages/toolkit/connector-kit/src/types.ts) definiert.
+Die Schnittstelle ist als `GetAuthorizationUri` in [`@logto/connector-kit`](https://github.com/logto-io/logto/blob/master/packages/toolkit/connector-kit/src/types/social.ts) definiert.
 
 Sie dürfen wesentliche Informationen zur Anmeldung mit `setSession` (dem zweiten Eingabeparameter von `GetAuthorizationUri`) speichern, um der `getUserInfo`-Methode zu dienen.
 
@@ -113,7 +113,7 @@ const getAccessToken = async (config: GithubConfig, code: string) => {
 
 `getUserInfo` ruft Benutzerinformationen mit dem in den vorherigen Schritten erhaltenen Zugangstoken ab.
 
-Die Schnittstelle ist als `GetUserInfo` in [`@logto/connector-kit`](https://github.com/logto-io/logto/blob/master/packages/toolkit/connector-kit/src/types.ts) definiert.
+Die Schnittstelle ist als `GetUserInfo` in [`@logto/connector-kit`](https://github.com/logto-io/logto/blob/master/packages/toolkit/connector-kit/src/types/social.ts) definiert.
 
 Für Anmeldezwecke können Sie notwendige Informationen mit der Funktion `getSession` abrufen.
 

i18n/de/docusaurus-plugin-content-docs/current/quick-starts/framework/next/_integration.mdx

@@ -30,7 +30,7 @@ export const logtoClient = new LogtoClient({
 
 ### API-Routen vorbereiten
 
-Bereite [API-Routen](https://nextjs.org/docs/api-routes/introduction) vor, um eine Verbindung mit Logto herzustellen.
+Bereite [API-Routen](https://nextjs.org/docs/pages/building-your-application/routing/api-routes) vor, um eine Verbindung mit Logto herzustellen.
 
 Gehe zurück zu deinem IDE/Editor und verwende den folgenden Code, um die API-Routen zuerst zu implementieren:
 

i18n/de/docusaurus-plugin-content-docs/current/quick-starts/framework/webflow/_guide-tip.mdx

@@ -1,5 +1,5 @@
 :::tip
 
-- Das Beispielprojekt ist verfügbar unter [Webflow-Projektvorschau](https://preview.webflow.com/preview/charless-trendy-site-f191c0?utm_medium=preview_link&utm_source=designer&utm_content=charless-trendy-site-f191c0&preview=0eae5f73661a8a5791787f0438bc29de&workflow=preview).
-- Eine Live-Demo ist bereitgestellt unter https://charless-trendy-site-f191c0.webflow.io/.
-  :::
+Das Beispielprojekt ist verfügbar unter [Webflow-Projektvorschau](https://preview.webflow.com/preview/charless-trendy-site-f191c0?utm_medium=preview_link&utm_source=designer&utm_content=charless-trendy-site-f191c0&preview=0eae5f73661a8a5791787f0438bc29de&workflow=preview).
+
+:::

i18n/es/docusaurus-plugin-content-docs/current/integrations/social/oidc/README.mdx

@@ -103,4 +103,4 @@ Puede que te preguntes por qué un protocolo OIDC estándar admite tanto los flu
 | subject                                  | string                             | False     |
 | typ                                      | string                             | False     |
 
-Consulta [aquí](https://github.com/panva/jose/blob/main/docs/interfaces/jwt_verify.JWTVerifyOptions.md) para encontrar más detalles sobre `IdTokenVerificationConfig`.
+Consulta [aquí](https://github.com/panva/jose/blob/main/docs/jwt/verify/interfaces/JWTVerifyOptions.md) para encontrar más detalles sobre `IdTokenVerificationConfig`.

i18n/es/docusaurus-plugin-content-docs/current/logto-oss/develop-your-connector/implement-connectors.mdx

@@ -49,7 +49,7 @@ Para completar el flujo, necesitamos tener los siguientes tres métodos:
 
 `getAuthorizationUri` genera una URL de redirección que puede dirigir a los usuarios finales a la página que necesita la autenticación de los usuarios.
 
-La interfaz está definida como `GetAuthorizationUri` en [`@logto/connector-kit`](https://github.com/logto-io/logto/blob/master/packages/toolkit/connector-kit/src/types.ts).
+La interfaz está definida como `GetAuthorizationUri` en [`@logto/connector-kit`](https://github.com/logto-io/logto/blob/master/packages/toolkit/connector-kit/src/types/social.ts).
 
 Se te permite almacenar información esencial relacionada con el inicio de sesión usando `setSession` (el segundo parámetro de entrada de `GetAuthorizationUri`) para el método `getUserInfo`.
 
@@ -113,7 +113,7 @@ const getAccessToken = async (config: GithubConfig, code: string) => {
 
 `getUserInfo` obtiene información del usuario con el token de acceso obtenido en el paso anterior.
 
-La interfaz está definida como `GetUserInfo` en [`@logto/connector-kit`](https://github.com/logto-io/logto/blob/master/packages/toolkit/connector-kit/src/types.ts).
+La interfaz está definida como `GetUserInfo` en [`@logto/connector-kit`](https://github.com/logto-io/logto/blob/master/packages/toolkit/connector-kit/src/types/social.ts).
 
 Para propósitos de inicio de sesión, puedes recuperar la información necesaria usando la función `getSession`.
 

i18n/es/docusaurus-plugin-content-docs/current/quick-starts/framework/next/_integration.mdx

@@ -30,7 +30,7 @@ export const logtoClient = new LogtoClient({
 
 ### Preparar rutas de API
 
-Prepara [rutas de API](https://nextjs.org/docs/api-routes/introduction) para conectar con Logto.
+Prepara [rutas de API](https://nextjs.org/docs/pages/building-your-application/routing/api-routes) para conectar con Logto.
 
 Regresa a tu IDE/editor, utiliza el siguiente código para implementar primero las rutas de API:
 

i18n/es/docusaurus-plugin-content-docs/current/quick-starts/framework/webflow/_guide-tip.mdx

@@ -1,5 +1,5 @@
 :::tip
 
-- El proyecto de ejemplo está disponible en [vista previa del proyecto Webflow](https://preview.webflow.com/preview/charless-trendy-site-f191c0?utm_medium=preview_link&utm_source=designer&utm_content=charless-trendy-site-f191c0&preview=0eae5f73661a8a5791787f0438bc29de&workflow=preview).
-- Una demostración en vivo está desplegada en https://charless-trendy-site-f191c0.webflow.io/.
-  :::
+El proyecto de ejemplo está disponible en [vista previa del proyecto Webflow](https://preview.webflow.com/preview/charless-trendy-site-f191c0?utm_medium=preview_link&utm_source=designer&utm_content=charless-trendy-site-f191c0&preview=0eae5f73661a8a5791787f0438bc29de&workflow=preview).
+
+:::

i18n/fr/docusaurus-plugin-content-docs/current/integrations/social/oidc/README.mdx

@@ -103,4 +103,4 @@ Vous vous demandez peut-être pourquoi un protocole OIDC standard prend en charg
 | subject                              | string                             | Faux   |
 | typ                                  | string                             | Faux   |
 
-Voir [ici](https://github.com/panva/jose/blob/main/docs/interfaces/jwt_verify.JWTVerifyOptions.md) pour plus de détails sur `IdTokenVerificationConfig`.
+Voir [ici](https://github.com/panva/jose/blob/main/docs/jwt/verify/interfaces/JWTVerifyOptions.md) pour plus de détails sur `IdTokenVerificationConfig`.

i18n/fr/docusaurus-plugin-content-docs/current/logto-oss/develop-your-connector/implement-connectors.mdx

@@ -49,7 +49,7 @@ Pour accomplir le flux, nous devons avoir les trois méthodes suivantes :
 
 `getAuthorizationUri` génère une URL de redirection qui peut diriger les utilisateurs finaux vers la page nécessitant l'Authentification des utilisateurs.
 
-L'interface est définie comme `GetAuthorizationUri` dans [`@logto/connector-kit`](https://github.com/logto-io/logto/blob/master/packages/toolkit/connector-kit/src/types.ts).
+L'interface est définie comme `GetAuthorizationUri` dans [`@logto/connector-kit`](https://github.com/logto-io/logto/blob/master/packages/toolkit/connector-kit/src/types/social.ts).
 
 Vous êtes autorisé à stocker des informations essentielles liées à la connexion en utilisant `setSession` (le deuxième paramètre d'entrée de `GetAuthorizationUri`) pour le bien de la méthode `getUserInfo`.
 
@@ -113,7 +113,7 @@ const getAccessToken = async (config: GithubConfig, code: string) => {
 
 `getUserInfo` récupère les informations utilisateur avec le jeton d’accès obtenu à l'étape précédente.
 
-L'interface est définie comme `GetUserInfo` dans [`@logto/connector-kit`](https://github.com/logto-io/logto/blob/master/packages/toolkit/connector-kit/src/types.ts).
+L'interface est définie comme `GetUserInfo` dans [`@logto/connector-kit`](https://github.com/logto-io/logto/blob/master/packages/toolkit/connector-kit/src/types/social.ts).
 
 À des fins de connexion, vous pouvez récupérer les informations nécessaires en utilisant la fonction `getSession`.
 

i18n/fr/docusaurus-plugin-content-docs/current/quick-starts/framework/next/_integration.mdx

@@ -30,7 +30,7 @@ export const logtoClient = new LogtoClient({
 
 ### Préparer les routes API
 
-Préparez les [routes API](https://nextjs.org/docs/api-routes/introduction) pour se connecter avec Logto.
+Préparez les [routes API](https://nextjs.org/docs/pages/building-your-application/routing/api-routes) pour se connecter avec Logto.
 
 Retournez à votre IDE / éditeur, utilisez le code suivant pour implémenter d'abord les routes API :
 

i18n/fr/docusaurus-plugin-content-docs/current/quick-starts/framework/webflow/_guide-tip.mdx

@@ -1,5 +1,5 @@
 :::tip
 
-- Le projet d'exemple est disponible sur [aperçu du projet Webflow](https://preview.webflow.com/preview/charless-trendy-site-f191c0?utm_medium=preview_link&utm_source=designer&utm_content=charless-trendy-site-f191c0&preview=0eae5f73661a8a5791787f0438bc29de&workflow=preview).
-- Une démonstration en direct est déployée à l'adresse https://charless-trendy-site-f191c0.webflow.io/.
-  :::
+Le projet d'exemple est disponible sur [aperçu du projet Webflow](https://preview.webflow.com/preview/charless-trendy-site-f191c0?utm_medium=preview_link&utm_source=designer&utm_content=charless-trendy-site-f191c0&preview=0eae5f73661a8a5791787f0438bc29de&workflow=preview).
+
+:::

i18n/ja/docusaurus-plugin-content-docs/current/integrations/social/oidc/README.mdx

@@ -103,4 +103,4 @@ _issuer_: これは、RP が IdP から受け取った JWT を検証するため
 | subject                              | string                             | False |
 | typ                                  | string                             | False |
 
-`IdTokenVerificationConfig` の詳細については [こちら](https://github.com/panva/jose/blob/main/docs/interfaces/jwt_verify.JWTVerifyOptions.md) を参照してください。
+`IdTokenVerificationConfig` の詳細については [こちら](https://github.com/panva/jose/blob/main/docs/jwt/verify/interfaces/JWTVerifyOptions.md) を参照してください。

i18n/ja/docusaurus-plugin-content-docs/current/logto-oss/develop-your-connector/implement-connectors.mdx

@@ -49,7 +49,7 @@ sequenceDiagram
 
 `getAuthorizationUri` は、エンドユーザーを認証が必要なページにリダイレクトする URL を生成します。
 
-インターフェースは [`@logto/connector-kit`](https://github.com/logto-io/logto/blob/master/packages/toolkit/connector-kit/src/types.ts) の `GetAuthorizationUri` として定義されています。
+インターフェースは [`@logto/connector-kit`](https://github.com/logto-io/logto/blob/master/packages/toolkit/connector-kit/src/types/social.ts) の `GetAuthorizationUri` として定義されています。
 
 `getUserInfo` メソッドのために、サインインに関連する重要な情報を `setSession`（`GetAuthorizationUri` の第 2 引数）を使用して保存することが許可されています。
 
@@ -113,7 +113,7 @@ const getAccessToken = async (config: GithubConfig, code: string) => {
 
 `getUserInfo` は、前のステップで取得したアクセス トークンでユーザー情報を取得します。
 
-インターフェースは [`@logto/connector-kit`](https://github.com/logto-io/logto/blob/master/packages/toolkit/connector-kit/src/types.ts) の `GetUserInfo` として定義されています。
+インターフェースは [`@logto/connector-kit`](https://github.com/logto-io/logto/blob/master/packages/toolkit/connector-kit/src/types/social.ts) の `GetUserInfo` として定義されています。
 
 サインインの目的で、`getSession` 関数を使用して必要な情報を取得できます。
 

i18n/ja/docusaurus-plugin-content-docs/current/quick-starts/framework/next/_integration.mdx

@@ -30,7 +30,7 @@ export const logtoClient = new LogtoClient({
 
 ### API ルートを準備する
 
-Logto と接続するための [API ルート](https://nextjs.org/docs/api-routes/introduction) を準備します。
+Logto と接続するための [API ルート](https://nextjs.org/docs/pages/building-your-application/routing/api-routes) を準備します。
 
 IDE / エディタに戻り、まず次のコードを使用して API ルートを実装します：
 

i18n/ja/docusaurus-plugin-content-docs/current/quick-starts/framework/webflow/_guide-tip.mdx

@@ -1,6 +1,5 @@
 :::tip
 
-- サンプルプロジェクトは [Webflow プロジェクトプレビュー](https://preview.webflow.com/preview/charless-trendy-site-f191c0?utm_medium=preview_link&utm_source=designer&utm_content=charless-trendy-site-f191c0&preview=0eae5f73661a8a5791787f0438bc29de&workflow=preview) で利用可能です。
-- ライブデモは https://charless-trendy-site-f191c0.webflow.io/ にデプロイされています。
+サンプルプロジェクトは [Webflow プロジェクトプレビュー](https://preview.webflow.com/preview/charless-trendy-site-f191c0?utm_medium=preview_link&utm_source=designer&utm_content=charless-trendy-site-f191c0&preview=0eae5f73661a8a5791787f0438bc29de&workflow=preview) で利用可能です。
 
 :::

i18n/pt-BR/docusaurus-plugin-content-docs/current/integrations/social/oidc/README.mdx

@@ -103,4 +103,4 @@ Você pode estar curioso sobre por que um protocolo OIDC padrão suporta tanto o
 | subject                                   | string                             | False       |
 | typ                                       | string                             | False       |
 
-Veja [aqui](https://github.com/panva/jose/blob/main/docs/interfaces/jwt_verify.JWTVerifyOptions.md) para encontrar mais detalhes sobre `IdTokenVerificationConfig`.
+Veja [aqui](https://github.com/panva/jose/blob/main/docs/jwt/verify/interfaces/JWTVerifyOptions.md) para encontrar mais detalhes sobre `IdTokenVerificationConfig`.

i18n/pt-BR/docusaurus-plugin-content-docs/current/logto-oss/develop-your-connector/implement-connectors.mdx

@@ -49,7 +49,7 @@ Para realizar o fluxo, precisamos ter os seguintes três métodos:
 
 `getAuthorizationUri` gera uma URL de redirecionamento que pode direcionar os usuários finais para a página que requer a autenticação dos usuários.
 
-A interface é definida como `GetAuthorizationUri` em [`@logto/connector-kit`](https://github.com/logto-io/logto/blob/master/packages/toolkit/connector-kit/src/types.ts).
+A interface é definida como `GetAuthorizationUri` em [`@logto/connector-kit`](https://github.com/logto-io/logto/blob/master/packages/toolkit/connector-kit/src/types/social.ts).
 
 Você pode armazenar informações essenciais relacionadas ao login usando `setSession` (o segundo parâmetro de entrada de `GetAuthorizationUri`) para o método `getUserInfo`.
 
@@ -113,7 +113,7 @@ const getAccessToken = async (config: GithubConfig, code: string) => {
 
 `getUserInfo` busca informações do usuário com o token de acesso obtido na etapa anterior.
 
-A interface é definida como `GetUserInfo` em [`@logto/connector-kit`](https://github.com/logto-io/logto/blob/master/packages/toolkit/connector-kit/src/types.ts).
+A interface é definida como `GetUserInfo` em [`@logto/connector-kit`](https://github.com/logto-io/logto/blob/master/packages/toolkit/connector-kit/src/types/social.ts).
 
 Para fins de login, você pode recuperar informações necessárias usando a função `getSession`.
 

i18n/pt-BR/docusaurus-plugin-content-docs/current/quick-starts/framework/next/_integration.mdx

@@ -30,7 +30,7 @@ export const logtoClient = new LogtoClient({
 
 ### Preparar rotas de API
 
-Prepare [rotas de API](https://nextjs.org/docs/api-routes/introduction) para conectar com Logto.
+Prepare [rotas de API](https://nextjs.org/docs/pages/building-your-application/routing/api-routes) para conectar com Logto.
 
 Volte para o seu IDE/editor, use o seguinte código para implementar as rotas de API primeiro:
 

i18n/pt-BR/docusaurus-plugin-content-docs/current/quick-starts/framework/webflow/_guide-tip.mdx

@@ -1,5 +1,5 @@
 :::tip
 
-- O projeto de exemplo está disponível em [Webflow project preview](https://preview.webflow.com/preview/charless-trendy-site-f191c0?utm_medium=preview_link&utm_source=designer&utm_content=charless-trendy-site-f191c0&preview=0eae5f73661a8a5791787f0438bc29de&workflow=preview).
-- Uma demonstração ao vivo está implantada em https://charless-trendy-site-f191c0.webflow.io/.
-  :::
+O projeto de exemplo está disponível em [Webflow project preview](https://preview.webflow.com/preview/charless-trendy-site-f191c0?utm_medium=preview_link&utm_source=designer&utm_content=charless-trendy-site-f191c0&preview=0eae5f73661a8a5791787f0438bc29de&workflow=preview).
+
+:::

i18n/zh-CN/docusaurus-plugin-content-docs/current/integrations/social/oidc/README.mdx

@@ -103,4 +103,4 @@ _issuer_：这是 IdP 的唯一标识符，RP 用于验证从 IdP 接收到的 J
 | subject                        | string                             | 否   |
 | typ                            | string                             | 否   |
 
-在 [这里](https://github.com/panva/jose/blob/main/docs/interfaces/jwt_verify.JWTVerifyOptions.md) 查看有关 `IdTokenVerificationConfig` 的更多详细信息。
+在 [这里](https://github.com/panva/jose/blob/main/docs/jwt/verify/interfaces/JWTVerifyOptions.md) 查看有关 `IdTokenVerificationConfig` 的更多详细信息。