diff --git a/docs/integrations/email/mailgun/README.mdx b/docs/integrations/email/mailgun/README.mdx index 9706f596246..576762aef1e 100644 --- a/docs/integrations/email/mailgun/README.mdx +++ b/docs/integrations/email/mailgun/README.mdx @@ -48,8 +48,9 @@ The following usage types are supported: - `ForgotPassword`: The email to be sent when a user is resetting their password. - `Generic`: The email to be sent when a user is performing a generic action, for example, testing the email connector. -> **Note** -> If the usage type is not specified in the deliveries config, the generic email will be sent. If the generic email is not specified, the connector will return an error. +:::note +If the usage type is not specified in the deliveries config, the generic email will be sent. If the generic email is not specified, the connector will return an error. +::: ### Content config diff --git a/docs/integrations/email/smtp/README.mdx b/docs/integrations/email/smtp/README.mdx index 474897b5089..775c223efb9 100644 --- a/docs/integrations/email/smtp/README.mdx +++ b/docs/integrations/email/smtp/README.mdx @@ -52,11 +52,11 @@ You can go to [SMTP service address page](https://www.alibabacloud.com/help/en/d To check "Sender Addresses", you can find the entrance on the left-side navigation pane on [DirectMail console](https://dm.console.aliyun.com/). You should see `Sender address` and `SMTP Password` here. -> ℹ️ **Note** -> -> Only one sample template is provided in the previous cases to keep things simple. You should add more templates for other use cases. -> You should change values wrapped with "\<" and ">" according to your Gmail, SendGrid or Aliyun account settings and choose to keep other fields w/o "\<" and ">". -> Add `{{code}}` as a placeholder in templates' content to show random verification code in sending emails. +:::note +Only one sample template is provided in the previous cases to keep things simple. You should add more templates for other use cases. +You should change values wrapped with "\<" and ">" according to your Gmail, SendGrid or Aliyun account settings and choose to keep other fields w/o "\<" and ">". +Add `{{code}}` as a placeholder in templates' content to show random verification code in sending emails. +::: ### Test SMTP connector diff --git a/docs/integrations/sms/aliyun-sms/README.mdx b/docs/integrations/sms/aliyun-sms/README.mdx index c1e7c82177d..168cabda8bc 100644 --- a/docs/integrations/sms/aliyun-sms/README.mdx +++ b/docs/integrations/sms/aliyun-sms/README.mdx @@ -71,4 +71,4 @@ That's it. Don't forget to [Enable connector in sign-in experience](/connectors/ ## References -- [Aliyun SMS - Quick Start](https://dysms.console.aliyun.com/quickstart) +Aliyun SMS - Quick Start diff --git a/docs/integrations/sms/tencent-sms/README.mdx b/docs/integrations/sms/tencent-sms/README.mdx index 3ef6473ebfe..d06b8e8f844 100644 --- a/docs/integrations/sms/tencent-sms/README.mdx +++ b/docs/integrations/sms/tencent-sms/README.mdx @@ -84,4 +84,6 @@ That's it. Don't forget to [Enable connector in sign-in experience](/connectors/ ## References -- [How to implement SMS verification code function?](https://cloud.tencent.com/document/product/382/43070) + + How to implement SMS verification code function? + diff --git a/docs/integrations/sms/twilio-sms/README.mdx b/docs/integrations/sms/twilio-sms/README.mdx index a31ca92228a..f71d885bbb3 100644 --- a/docs/integrations/sms/twilio-sms/README.mdx +++ b/docs/integrations/sms/twilio-sms/README.mdx @@ -28,18 +28,18 @@ Go to the [Twilio console page](https://console.twilio.com/) and sign in with yo Purchase a phone number under "Phone Numbers" -> "Manage" -> "Buy a number". -> ℹ️ **Tip** -> -> Sometimes you may encounter the situation that SMS service is not supported in specific countries or areas. Pick a number from other regions to bypass. +:::tip +Sometimes you may encounter the situation that SMS service is not supported in specific countries or areas. Pick a number from other regions to bypass. +::: Once we have a valid number claimed, nav to the "Messaging" -> "Services". Create a new Message Service by clicking on the button. Give a friendly service name and choose _Notify my users_ as our service purpose. Following the next step, choose `Phone Number` as _Sender Type_, and add the phone number we just claimed to this service as a sender. -> ℹ️ **Note** -> -> Each phone number can only be linked with one messaging service. +:::note +Each phone number can only be linked with one messaging service. +::: ## Get account credentials @@ -80,4 +80,4 @@ That's it. Don't forget to [Enable connector in sign-in experience](/connectors/ ## Reference -- [Twilio - Error and Warning Dictionary](https://www.twilio.com/docs/api/errors) +Twilio - Error and Warning Dictionary diff --git a/docs/integrations/social/alipay-native/README.mdx b/docs/integrations/social/alipay-native/README.mdx index 93373c1060a..f6fd8e239b9 100644 --- a/docs/integrations/social/alipay-native/README.mdx +++ b/docs/integrations/social/alipay-native/README.mdx @@ -35,16 +35,17 @@ Alipay Native connector works closely with Logto SDK on mobile platforms. It tak 9. Set up "Authorization Redirect URI" (授权回调地址) by clicking "set up" (设置) button on the bottom of the Alipay console page. `${your_logto_origin}/callback/${connector_id}` is the default redirect URI used in Logto core. The `connector_id` can be found on the top bar of the Logto Admin Console connector details page. 10. After finishing all these steps, go back to the top right corner of Alipay console page, and click "Submit for review" (提交审核). Once the review is approved, you are good to go with a smooth Alipay sign-in flow. -> ℹ️ **Note** -> -> You can use _openssl_ to generate key pairs on your local machine by executing following code snippet in terminal. -> -> ```bash -> openssl genrsa -out private.pem 2048 -> openssl rsa -in private.pem -outform PEM -pubout -out public.pem -> ``` -> -> When filling in the public key on the Alipay app setup website, you need to remove the header and footer of `public.pem`, delete all newline characters, and paste the rest of the contents into the text input box for "public key". +:::note + +You can use _openssl_ to generate key pairs on your local machine by executing following code snippet in terminal. + +```bash +openssl genrsa -out private.pem 2048 +openssl rsa -in private.pem -outform PEM -pubout -out public.pem +``` + +When filling in the public key on the Alipay app setup website, you need to remove the header and footer of `public.pem`, delete all newline characters, and paste the rest of the contents into the text input box for "public key". +::: ## Set up the Logto Alipay Native connector settings @@ -75,9 +76,11 @@ Add the framework: ![Add framework](./assets/add-framework.png) -> ℹ️ **Note** -> -> The plugin includes Alipay "minimalist SDK" (极简版 SDK). You can directly use `import AFServiceSDK` once imported the plugin. +:::note + +The plugin includes Alipay "minimalist SDK" (极简版 SDK). You can directly use `import AFServiceSDK` once imported the plugin. + +::: **2. Add the plugin to your `LogtoClient` init options** @@ -129,5 +132,10 @@ Once Alipay native connector is enabled, you can build and run your app to see i ## References -- [Alipay Docs - Access Preparation - How to create an app](https://opendocs.alipay.com/support/01rau6) -- [Alipay Docs - Web & Mobile Apps - Create an app](https://opendocs.alipay.com/open/200/105310) + + Alipay Docs - Access Preparation - How to create an app + + + + Alipay Docs - Web & Mobile Apps - Create an app + diff --git a/docs/integrations/social/alipay-web/README.mdx b/docs/integrations/social/alipay-web/README.mdx index cdd5eb4fbee..1d2cf8b1dc3 100644 --- a/docs/integrations/social/alipay-web/README.mdx +++ b/docs/integrations/social/alipay-web/README.mdx @@ -35,16 +35,17 @@ Alipay Web connector is designed for desktop Web applications. It takes advantag 9. Set up "Authorization Redirect URI" (授权回调地址) by clicking "set up" (设置) button on the bottom of the Alipay console page. `${your_logto_origin}/callback/${connector_id}` is the default redirect URI used in Logto core. The `connector_id` can be found on the top bar of the Logto Admin Console connector details page. 10. After finishing all these steps, go back to the top right corner of Alipay console page, and click "Submit for review" (提交审核). Once the review is approved, you are good to go with a smooth Alipay sign-in flow. -> ℹ️ **Note** -> -> You can use _openssl_ to generate key pairs on your local machine by executing following code snippet in terminal. -> -> ```bash -> openssl genrsa -out private.pem 2048 -> openssl rsa -in private.pem -outform PEM -pubout -out public.pem -> ``` -> -> When filling in the public key on the Alipay app setup website, you need to remove the header and footer of `public.pem`, delete all newline characters, and paste the rest of the contents into the text input box for "public key". +:::note +You can use _openssl_ to generate key pairs on your local machine by executing following code snippet in terminal. + +```bash +openssl genrsa -out private.pem 2048 +openssl rsa -in private.pem -outform PEM -pubout -out public.pem +``` + +When filling in the public key on the Alipay app setup website, you need to remove the header and footer of `public.pem`, delete all newline characters, and paste the rest of the contents into the text input box for "public key". + +::: ## Set up the Logto Alipay Web connector settings @@ -75,5 +76,10 @@ Once Alipay web connector is enabled, you can build and run your web app to see ## References -- [Alipay Docs - Access Preparation - How to create an app](https://opendocs.alipay.com/support/01rau6) -- [Alipay Docs - Web & Mobile Apps - Create an app](https://opendocs.alipay.com/open/200/105310) + + Alipay Docs - Access Preparation - How to create an app + + + + Alipay Docs - Web & Mobile Apps - Create an app + diff --git a/docs/integrations/social/apple/README.mdx b/docs/integrations/social/apple/README.mdx index 61164a08eb2..89489b80b39 100644 --- a/docs/integrations/social/apple/README.mdx +++ b/docs/integrations/social/apple/README.mdx @@ -18,18 +18,22 @@ The official Logto connector for Apple social sign-in. If you don't know the concept of the connector or don't know how to add this connector to your Sign-in experience, please see [Logto tutorial](/connectors/social-connectors). -> ℹ️ **Note** -> -> Apple sign-in is required for AppStore if you have other social sign-in methods in your app. -> Having Apple sign-in on Android devices is great if you also provide an Android app. +:::note + +Apple sign-in is required for AppStore if you have other social sign-in methods in your app. +Having Apple sign-in on Android devices is great if you also provide an Android app. + +::: You need to enroll [Apple Developer Program](https://developer.apple.com/programs/) before continuing. ### Enable Sign in with Apple for your app -> ⚠️ **Caution** -> -> Even if you want to implement Sign in with Apple on a web app only, you still need to have an existing app that embraces the AppStore ecosystem (i.e., have a valid App ID). +:::caution + +Even if you want to implement Sign in with Apple on a web app only, you still need to have an existing app that embraces the AppStore ecosystem (i.e., have a valid App ID). + +::: You can do it via Xcode -> Project settings -> Signing & Capabilities, or visit [Certificates, Identifiers & Profiles](https://developer.apple.com/account/resources/identifiers/list/bundleId). @@ -58,19 +62,23 @@ Enter the domain of your Logto instance without protocol and port, e.g., `your.l Click "Next" then "Done" to close the modal. Click "Continue" on the top-right corner, then click "Save" to save your configuration. -> ⚠️ **Caution** -> -> Apple does NOT allow Return URLs with HTTP protocol and `localhost` domain. -> -> If you want to test locally, you need to edit `/etc/hosts` file to map localhost to a custom domain and set up a local HTTPS environment. [mkcert](https://github.com/FiloSottile/mkcert) can help you for setting up local HTTPS. +:::caution + +Apple does NOT allow Return URLs with HTTP protocol and `localhost` domain. + +If you want to test locally, you need to edit `/etc/hosts` file to map localhost to a custom domain and set up a local HTTPS environment. [mkcert](https://github.com/FiloSottile/mkcert) can help you for setting up local HTTPS. + +::: ## Configure scope To get user's email from Apple, you need to configure the scope to include `email`. For both email and name, you can use `name email` as the scope. See [Apple official docs](https://developer.apple.com/documentation/sign_in_with_apple/sign_in_with_apple_js/incorporating_sign_in_with_apple_into_other_platforms#3332113) for more info. -> ℹ️ **Note** -> -> The user may choose to hide their email address from your app. In this case, you will not be able to retrieve the real email address. An email address like `random@privaterelay.appleid.com` will be returned instead. +:::note + +The user may choose to hide their email address from your app. In this case, you will not be able to retrieve the real email address. An email address like `random@privaterelay.appleid.com` will be returned instead. + +::: ### Pitfalls of configuring scope diff --git a/docs/integrations/social/azuread/README.mdx b/docs/integrations/social/azuread/README.mdx index 384be9da8a3..e142705ad49 100644 --- a/docs/integrations/social/azuread/README.mdx +++ b/docs/integrations/social/azuread/README.mdx @@ -17,8 +17,7 @@ The Microsoft Azure AD connector provides a succinct way for your application to - Visit the [Azure Portal](https://portal.azure.com/#home) and sign in with your Azure account. You need to have an active subscription to access Microsoft Azure AD. - Click the **Azure Active Directory** from the services they offer, and click the **App Registrations** from the left menu. -- Click **New Registration** at the top, enter a description, select your **access type** and add your **Redirect URI**, which will redirect the user to the application after logging in. In our case, this will be `${your_logto_endpoint}/callback/${connector_id}`. e.g. `https://foo.logto.app/callback/${connector_id}`. (The `connector_id` can be also found on the top bar of the Logto Admin Console connector details page) - > You can copy the `Callback URI` in the configuration section. +- Click **New Registration** at the top, enter a description, select your **access type** and add your **Redirect URI**, which will redirect the user to the application after logging in. In our case, this will be `${your_logto_endpoint}/callback/${connector_id}`. e.g. `https://foo.logto.app/callback/${connector_id}`. The `connector_id` can be also found on the top bar of the Logto Admin Console connector details page. You can copy the `Callback URI` in the configuration section. - Select Web as Platform. ## Fill in the configuration in Logto @@ -55,4 +54,6 @@ Logto will use this field to construct the authorization endpoints. This value i ## References -- [Web app that signs in users](https://docs.microsoft.com/en-us/azure/active-directory/develop/scenario-web-app-sign-user-overview) + + Web app that signs in users + diff --git a/docs/integrations/social/github/README.mdx b/docs/integrations/social/github/README.mdx index 1d94d75ad79..39c026469d4 100644 --- a/docs/integrations/social/github/README.mdx +++ b/docs/integrations/social/github/README.mdx @@ -29,7 +29,11 @@ Follow the [creating an OAuth App](https://docs.github.com/en/developers/apps/bu Name your new OAuth application in **Application name** and fill up **Homepage URL** of the app. You can leave **Application description** field blank and customize **Authorization callback URL** as `${your_logto_origin}/callback/${connector_id}`. The `connector_id` can be found on the top bar of the Logto Admin Console connector details page. -> Note: If you encounter the error message "The redirect_uri MUST match the registered callback URL for this application." when logging in, try aligning the Authorization Callback URL of your GitHub OAuth App and your Logto App's redirect URL (of course, including the protocol) to resolve the issue. +:::note + +If you encounter the error message "The redirect_uri MUST match the registered callback URL for this application." when logging in, try aligning the Authorization Callback URL of your GitHub OAuth App and your Logto App's redirect URL (of course, including the protocol) to resolve the issue. + +::: We suggest not to check the box before **Enable Device Flow**, or users who sign in with GitHub on mobile devices must confirm the initial sign-in action in the GitHub app. Many GitHub users do not install the GitHub mobile app on their phones, which could block the sign-in flow. Please ignore our suggestion if you are expecting end-users to confirm their sign-in flow. See details of [device flow](https://docs.github.com/en/developers/apps/building-oauth-apps/authorizing-oauth-apps#device-flow). @@ -58,5 +62,10 @@ That's it. The GitHub connector should be available now. Don't forget to [Enable ## Reference -- [GitHub - Developers - Apps](https://docs.github.com/en/developers/apps/getting-started-with-apps/about-apps) -- [GitHub - Developers - Apps - Creating an OAuth App](https://docs.github.com/en/developers/apps/building-oauth-apps/creating-an-oauth-app) + + GitHub - Developers - Apps + + + + GitHub - Developers - Apps - Creating an OAuth App + diff --git a/docs/integrations/social/google/README.mdx b/docs/integrations/social/google/README.mdx index 66447c8b5f7..9a2ae47fe9d 100644 --- a/docs/integrations/social/google/README.mdx +++ b/docs/integrations/social/google/README.mdx @@ -99,4 +99,6 @@ To enable Google One Tap in your website (beyond the Logto sign-in experience), ## References -- [Google Identity: Setting up OAuth 2.0](https://developers.google.com/identity/protocols/oauth2/openid-connect#appsetup) + + Google Identity: Setting up OAuth 2.0 + diff --git a/docs/integrations/social/huggingface/README.mdx b/docs/integrations/social/huggingface/README.mdx index 4732a760443..9a3ce046009 100644 --- a/docs/integrations/social/huggingface/README.mdx +++ b/docs/integrations/social/huggingface/README.mdx @@ -58,4 +58,6 @@ That's it. The Hugging Face connector should be available now. Don't forget to [ ## Reference -- [Hugging Face - Sign in with Hugging Face](https://huggingface.co/docs/hub/en/oauth#sign-in-with-hugging-face) + + Hugging Face - Sign in with Hugging Face + diff --git a/docs/integrations/social/naver/README.mdx b/docs/integrations/social/naver/README.mdx index 9288c07a392..cf7f05264c1 100644 --- a/docs/integrations/social/naver/README.mdx +++ b/docs/integrations/social/naver/README.mdx @@ -54,9 +54,11 @@ Currently `Naver Developers` site only supports Korean. Please consider use a tr - For `서비스 URL(Service URL)`, type `http(s)://YOUR_URL` (ex. https://logto.io) - For `네이버 로그인(Naver Login) Callback URL`, type `http(s)://YOUR_URL/callback/${connector_id}` (e.g. https://logto.io/callback/${connector_id}) -> ⚠️ **Caution** -> -> The `connector_id` can be found on the top bar of the Logto Admin Console connector details page. +:::caution + +The `connector_id` can be found on the top bar of the Logto Admin Console connector details page. + +::: ## Configure Logto diff --git a/docs/integrations/social/oauth2/README.mdx b/docs/integrations/social/oauth2/README.mdx index 9cdee477599..278af6ec21b 100644 --- a/docs/integrations/social/oauth2/README.mdx +++ b/docs/integrations/social/oauth2/README.mdx @@ -18,9 +18,11 @@ The official Logto connector for OAuth 2.0 protocol. The OAuth connector enables Logto's connection to an arbitrary social identity provider that supports OAuth 2.0 protocol. -> ℹ️ **Note** -> -> OAuth connector is a special kind of connector in Logto, you can add a few OAuth-protocol-based connectors. +:::note + +OAuth connector is a special kind of connector in Logto, you can add a few OAuth-protocol-based connectors. + +::: ## Create your OAuth app @@ -63,10 +65,12 @@ For example, you can find [Google user profile response](https://developers.goog } ``` -> ℹ️ **Note** -> -> We provided an OPTIONAL `customConfig` key to put your customize parameters. -> Each social identity provider could have their own variant on OAuth standard protocol. If your desired social identity provider strictly stick to OAuth standard protocol, the you do not need to care about `customConfig`. +:::note + +We provided an OPTIONAL `customConfig` key to put your customize parameters. +Each social identity provider could have their own variant on OAuth standard protocol. If your desired social identity provider strictly stick to OAuth standard protocol, the you do not need to care about `customConfig`. + +::: ## Config types @@ -94,4 +98,4 @@ For example, you can find [Google user profile response](https://developers.goog ## Reference -- [The OAuth 2.0 Authorization Framework](https://www.rfc-editor.org/rfc/rfc6749) +The OAuth 2.0 Authorization Framework diff --git a/docs/integrations/social/oidc/README.mdx b/docs/integrations/social/oidc/README.mdx index 286e53ba79a..9ca23a81bdd 100644 --- a/docs/integrations/social/oidc/README.mdx +++ b/docs/integrations/social/oidc/README.mdx @@ -17,9 +17,11 @@ The official Logto connector for OpenID Connect (OIDC) protocol. The OIDC connector enables Logto's connection to an arbitrary social identity provider that supports OIDC protocol. -> ℹ️ **Note** -> -> OIDC connector is a special kind of connector in Logto, you can add a few OIDC-based connector. +:::note + +OIDC connector is a special kind of connector in Logto, you can add a few OIDC-based connector. + +::: ## Create your OIDC app @@ -59,10 +61,12 @@ You may be curious as to why a standard OIDC protocol supports both the implicit `responseType` and `grantType` can ONLY be FIXED values with "Authorization Code" flow, so we make them optional and default values will be automatically filled. -> ℹ️ **Note** -> -> For all flow types, we provided an OPTIONAL `customConfig` key to put your customize parameters. -> Each social identity provider could have their own variant on OIDC standard protocol. If your desired social identity provider strictly stick to OIDC standard protocol, the you do not need to care about `customConfig`. +:::note + +For all flow types, we provided an OPTIONAL `customConfig` key to put your customize parameters. +Each social identity provider could have their own variant on OIDC standard protocol. If your desired social identity provider strictly stick to OIDC standard protocol, the you do not need to care about `customConfig`. + +::: ## Config types diff --git a/docs/integrations/social/wechat-native/README.mdx b/docs/integrations/social/wechat-native/README.mdx index c2ba785c8ab..e0d60727dad 100644 --- a/docs/integrations/social/wechat-native/README.mdx +++ b/docs/integrations/social/wechat-native/README.mdx @@ -24,9 +24,11 @@ We know it sounds scary, but don't worry. We'll handle it easily in this tutoria ## Create a mobile app in the WeChat Open Platform -> 💡 **Tip** -> -> You can skip some sections if you have already finished. +:::tip + +You can skip some sections if you have already finished. + +::: ### Create an account @@ -65,13 +67,17 @@ If you chose "No" for the App Store availability, you cloud skip filling out the Fill out _Bundle ID_, _Test version Bundle ID_, and _Universal Links_ (actually, only one link is needed 😂). -> ℹ️ **Note** -> -> _Bundle ID_ and _Test version Bundle ID_ can be the same value. +:::note + +_Bundle ID_ and _Test version Bundle ID_ can be the same value. + +::: -> 💡 **Tip** -> -> WeChat requires universal link for native sign-in. If you haven't set up or don't know it, please refer to the [Apple official doc](https://developer.apple.com/ios/universal-links/). +:::tip + +WeChat requires universal link for native sign-in. If you haven't set up or don't know it, please refer to the [Apple official doc](https://developer.apple.com/ios/universal-links/). + +::: **Android app** @@ -81,9 +87,11 @@ Check "Android app" (Android 应用). Fill out _Application Signing Signature_ (应用签名) and _Application Package Name_ (应用包名). -> ℹ️ **Note** -> -> You need to sign your app to get a signature. Refer to the [Sign your app](https://developer.android.com/studio/publish/app-signing) for more info. +:::note + +You need to sign your app to get a signature. Refer to the [Sign your app](https://developer.android.com/studio/publish/app-signing) for more info. + +::: After finish signing, you can execute the `signingReport` task to get the signing signature. @@ -121,9 +129,11 @@ Finally open your `Info.plist`, add `weixinULAPI` and `weixin` under `LSApplicat ![Plist](./assets/plist.png) -> 🤦 **Note** -> -> We know these actions are not very reasonable, but this is the minimum workable solution we found. See the [magical official guide](https://developers.weixin.qq.com/doc/oplatform/en/Mobile_App/Access_Guide/iOS.html) for more info. +:::note + +We know these actions are not very reasonable, but this is the minimum workable solution we found. See the [magical official guide](https://developers.weixin.qq.com/doc/oplatform/en/Mobile_App/Access_Guide/iOS.html) for more info. + +::: **2. Add `LogtoSocialPluginWechat` to your Xcode project** @@ -135,9 +145,11 @@ And add `-ObjC` to your Build Settings > Linking > Other Linker Flags: ![Linker flags](./assets/linker-flags.png) -> ℹ️ **Note** -> -> The plugin includes WeChat Open SDK 1.9.2. You can directly use `import WechatOpenSDK` once imported the plugin. +:::note + +The plugin includes WeChat Open SDK 1.9.2. You can directly use `import WechatOpenSDK` once imported the plugin. + +::: **3. Add the plugin to your `LogtoClient` init options** @@ -150,9 +162,11 @@ let logtoClient = LogtoClient( **4. Handle `onOpenURL` properly** -> ℹ️ **Note** -> -> The function `LogtoClient.handle(url:)` will handle all the native connectors you enabled. You only need to call it once. +:::note + +The function `LogtoClient.handle(url:)` will handle all the native connectors you enabled. You only need to call it once. + +::: ```swift // SwiftUI @@ -244,6 +258,8 @@ That's it. Don't forget to [Enable social connector in sign-in experience](/conn Once WeChat native connector is enabled, you can build and run your app to see if it works. -> ⚠️ **Caution** -> -> WeChat doesn't have a plan for those devices without the WeChat app installed. Logto will hide this connector during sign-in if so (which is the recommended way from the [official development guide](https://developers.weixin.qq.com/doc/oplatform/en/Mobile_App/WeChat_Login/Development_Guide.html)). +:::caution + +WeChat doesn't have a plan for those devices without the WeChat app installed. Logto will hide this connector during sign-in if so (which is the recommended way from the [official development guide](https://developers.weixin.qq.com/doc/oplatform/en/Mobile_App/WeChat_Login/Development_Guide.html)). + +::: diff --git a/docs/integrations/social/wechat-web/README.mdx b/docs/integrations/social/wechat-web/README.mdx index 9fa0628f156..fa0d4894048 100644 --- a/docs/integrations/social/wechat-web/README.mdx +++ b/docs/integrations/social/wechat-web/README.mdx @@ -18,15 +18,19 @@ The official Logto connector for WeChat social sign-in in web apps. If you don't know the concept of the connector or don't know how to add this connector to your Sign-in experience, please see [Logto tutorial](/connectors/social-connectors). -> **⚠️ Caution** -> -> This connector is for web apps only. If you are looking for the method for signing in with WeChat in native apps, please see [WeChat native connector](/integrations/wechat-native). +:::caution + +This connector is for web apps only. If you are looking for the method for signing in with WeChat in native apps, please see [WeChat native connector](/integrations/wechat-native). + +::: ## Create a web app in the WeChat Open Platform -> 💡 **Tip** -> -> You can skip some sections if you have already finished. +:::tip + +You can skip some sections if you have already finished. + +::: ### Create an account diff --git a/docs/introduction/README.mdx b/docs/introduction/README.mdx index 8a9af05e843..f5a23062d29 100644 --- a/docs/introduction/README.mdx +++ b/docs/introduction/README.mdx @@ -25,8 +25,6 @@ Welcome to Logto documentation! Logto is an identity and access management (IAM) ## Explore by features -Logto provides a robust suite of features, including authentication, authorization, and user and organization management, tailored for modern identity needs. Our strong CIAM (Customer Identity and Access Management) support gives it a clear advantage in the field. -