chore: sync lastest docs to 1.x (#404)

Author: gao-sun

versioned_docs/version-1.x/docs/README.mdx

@@ -32,4 +32,5 @@ import basicConcepts from './assets/basic-concepts.png';
 <img src={basicConcepts} alt="Basic concepts" width="600px" />
 
 :::info
-Admin Console is the easiest way to customize and manage Sign-in Experience and Core Service, and we'll use it across the tutorial. And it is available in both Logto Cloud and Logto Opensource.:::
+Admin Console is the easiest way to customize and manage Sign-in Experience and Core Service, and we'll use it across the tutorial. And it is available in both [Logto Cloud](https://cloud.logto.io/) and Logto Open-Source.
+:::

versioned_docs/version-1.x/docs/recipes/configure-connectors/configure-social-connector.md

@@ -34,7 +34,7 @@ Follow the README to compose the connector config with little effort.
 - **Naver** [Universal connector](https://github.com/logto-io/connectors/tree/master/packages/connector-naver)
 - **Microsoft Azure AD** [Universal connector](https://github.com/logto-io/connectors/tree/master/packages/connector-azuread)
 
-:::About the platform of Social connector
+:::info About the platform of Social connector
 You may find that some connectors do not have a secondary choice of platform, such as Google, Facebook, and GitHub. These connectors' _platform_ are _Universal_. Explore _[platform_ description](https://docs.logto.io/docs/references/connectors/#platform) to know more.
 
 Choose a proper _platform_ from either _Web_ or _Native_ for connectors to fit your use case. You can set up a single _Native_ connector w/o adding a _Web_ connector if you only provide native mobile apps and vice versa.

versioned_docs/version-1.x/docs/recipes/create-your-connector/connector-implementation-guide.mdx

@@ -100,31 +100,6 @@ The interface is defined as `GetUserInfo` in [`@logto/connector-kit`](https://gi
 
 For sign-in purposes, you can retrieve necessary information using the `getSession` function.
 
-:::tip
-To handle sign-in related data that needs to be shared across multiple APIs, you can use the `getSession` and `setSession` functions. On the other hand, if you need to store and retrieve key-value data to the database for longer-term use, you can use the `get` and `set` methods.
-
-It's important to understand the purpose of `getSession` and `setSession`. These functions are primarily used for manipulating sign-in related information for cross-API pass. For example, when sending an authorization request, you may need to attach essential information such as `nonce`. As the `getAuthorizationUri` and `getUserInfo` methods are separated and located in different APIs within Logto core, it's necessary to pass this information across APIs. Since the API is stateless, the `getSession` and `setSession` functions can be used to persist the data throughout the user's session.
-
-On the other hand, the `get` and `set` methods are used to store and retrieve key-value information in the database for long-term use. For example, you might use these methods to save and load an application-level access token and refresh token, which should not be requested frequently.
-
-Here is an example of how to use the `set` and `get` methods (suppose that we start with an empty DB):
-
-```typescript
-// Set a value
-const key = 'userPreferences';
-const value = { theme: 'dark', language: 'en' };
-await set(key, value);
-
-// Get a value
-const retrievedValue = await get(key);
-console.log(retrievedValue); // { theme: 'dark', language: 'en' }
-const valueOfUnknownKey = await get('unknownKey');
-console.log(valueOfUnknownKey); // null
-```
-
-It is important to note that we do not add constraints to the type of `value` to bring more flexibility to developers. However, it is the responsibility of developers to ensure that the data is clear and well-organized. We also do not provide advanced operations such as "list keys" or "clear," so it is strongly recommended to reuse keys when possible.
-:::
-
 `userInfoEndpoint` is the endpoint which is used to get user information.
 
 You may check official documents to find specific user information that can be accessed at user info endpoint and corresponding scope.

versioned_docs/version-1.x/docs/recipes/customize-sie/README.md

@@ -14,10 +14,18 @@ Logto covers the tedious part, so you can have fun with customization to define
 
 In Admin Console, click the "Sign-in Experience" tab on the left, and you'll see a two-column page.
 
-The left column is the customization section with three tabs: Branding, Sign-in Methods, and Others.
+The left column is the customization section with three tabs: **Branding**, **Sign-in and sign-up**, and **Others**.
+
+1. Configure sign-in methods: Whether you prefer **password-based or passwordless sign-in/sign-up** options, you can easily configure them straight out of the box or customize them to align with your company's unique requirements.
+2. Match your brand: Quickly customize the sign-in page to match your product brand with options to set your **brand color**, **logo**, **favicon**, and **dark mode** usage.
+3. Custom CSS: Tailor the UI of all pages with **Custom CSS**. The orderly and concise design system of styles and components makes customization a breeze.
+4. Terms & Policy: Link your website's **Terms of Use** and **Privacy Policy** to the sign-in page. Users will be prompted to agree to these policies when they register.
+5. Language (i18n): Create a localized experience by selecting your language mode to **enable auto-detect** or **choose a default language**. Edit **i18n translations** for tailored content.
 
 The right column is a live preview that will immediately update to synchronize the change when you update things on the left.
 
+![Sign-in Experience homepage](./assets/sie-set-homepage.png)
+
 :::tip Use preview to save your time
 
 - Click the tab "Mobile" or "Web" to see what the homepage looks like on different platforms.