logto-io · charIeszhao · Oct 25, 2024 · Oct 24, 2024 · Oct 25, 2024
diff --git a/about/cloud-preview.mdx b/about/cloud-preview.mdx
@@ -1,5 +1,7 @@
 import './common.scss';
 
+{/* truncate */}
+
 # About Logto Cloud (Preview)
 
 Thank you for joining us in Logto Cloud (Preview), giving you a sneak peek into our current progress. Logto Cloud is built on top of Logto OSS, providing a seamless upgrade path without incurring heavy overhead.

diff --git a/babel.config.js b/babel.config.js
@@ -1,8 +1,11 @@
 module.exports = {
   presets: [require.resolve('@docusaurus/core/lib/babel/preset')],
   plugins: [
-    ['@babel/plugin-transform-react-jsx', {
-      runtime: 'automatic',
-    }],
+    [
+      '@babel/plugin-transform-react-jsx',
+      {
+        runtime: 'automatic',
+      },
+    ],
   ],
 };
diff --git a/blog/2022-08-07-typescript-all-in-one.md b/blog/2022-08-07-typescript-all-in-one.md
@@ -12,7 +12,7 @@ I always had a dream of monorepo.
 
 I saw the monorepo approach while working for Airbnb, but it was for the frontend only. With a deep love of the JavaScript ecosystem and the “happy” TypeScript developing experience, I started to align frontend and backend code in the same language from ~three years ago. It was great (for hiring) but not that great for developing since our projects were still scattered across multiple repos.
 
-<!--truncate-->
+{/* truncate */}
 
 :::info FYI
 There are quotes around the word “happy” since TypeScript did bring me a lot of fun and a-ha moments, but it also let me think “how could this doesn’t work” sometimes.

diff --git a/blog/2022-08-20-logto-x-hasura/index.mdx b/blog/2022-08-20-logto-x-hasura/index.mdx
@@ -15,7 +15,7 @@ When it comes to a new project, you usually cannot skip several things: APIs, au
 
 Also, most of the works are “repeating”. I mean, they are needed and similar for almost every project, with some tweaks.
 
-<!--truncate-->
+{/* truncate */}
 
 Sounds scary and tedious? Don’t panic. Today we have open source. With the two open-source projects below, things become not tricky :
 

diff --git a/blog/2022-11-15-design-for-seamless-sie-1/index.mdx b/blog/2022-11-15-design-for-seamless-sie-1/index.mdx
@@ -10,7 +10,7 @@ import architecture from './architecture.png';
 
 We are thrilled to announce the release of the newest version of the Sign-in Experience, which includes more ways to sign-in and sign-up, as well as a framework that is easier to understand and more flexible to configure in the Admin Console. When compared to Sign-in Experience V1, this version's capability was expanded so that it could support a greater variety of flexible use cases. We hope that this will be able to assist developers in delivering a successful sign-in flow, which will also be appreciated by the end users.
 
-<!--truncate-->
+{/* truncate */}
 
 In this article, we'll go over the history of Sign-in Experience, including its conception, design decisions, and product tradeoffs. You will also gain a better grasp of how to construct a successful and frictionless sign-in or sign-up experience.
 

diff --git a/blog/2022-11-28-ciam-101-authn-identity-sso/index.mdx b/blog/2022-11-28-ciam-101-authn-identity-sso/index.mdx
@@ -10,7 +10,7 @@ tags: [ciam, auth, authentication]
 
 I began the build Logto because I noticed that Identity and Access Management (IAM) had become increasingly complex and expansive over time. The concept of IAM is even large enough to give rise to new concepts, such as WIAM (Workforce IAM) and CIAM (Customer IAM).
 
-While WIAM and CIAM share the same foundation, they have distinct use cases: WIAM is typically used for internal users, while CIAM is used for external customers.<!--truncate--> Some examples:
+While WIAM and CIAM share the same foundation, they have distinct use cases: WIAM is typically used for internal users, while CIAM is used for external customers.{/* truncate */} Some examples:
 
 - **WIAM** Your company has a unified identity system for employees, thus every one can use the same account to access company resources, such as software subscriptions, cloud computing services, etc.
 - **CIAM** Your online bookstore requires a user identity system for customers and sellers. The sign-in experience is a critical part of onboarding, as it is located at the top of the conversion funnel.

diff --git a/blog/2022-12-05-design-for-seamless-sie-2/index.md b/blog/2022-12-05-design-for-seamless-sie-2/index.md
@@ -15,7 +15,7 @@ In the previous piece, we discussed the development of the Sign-in Experience, a
 
 In this article, we'll answer these questions and show you how the Logto Admin Console can help.
 
-<!--truncate-->
+{/* truncate */}
 
 ## Make Admin Console thoughtful and educational
 

diff --git a/blog/2023-02-05-ciam-102-authz-and-rbac/index.md b/blog/2023-02-05-ciam-102-authz-and-rbac/index.md
@@ -12,7 +12,7 @@ In the [previous article](../2022-11-28-ciam-101-authn-identity-sso/index.mdx),
 
 Organization and Tenant are great for grouping Identities, but they lead to an absolute democracy: everyone can do anything in this system. While utopia is still a mystery, let’s take a look at the governance of access: Authorization (AuthZ).
 
-<!--truncate-->
+{/* truncate */}
 
 ### Why do we need authorization?
 

diff --git a/blog/2023-02-16-do-you-need-to-build-auth/index.md b/blog/2023-02-16-do-you-need-to-build-auth/index.md
@@ -14,7 +14,7 @@ I would like to point out this first for a better reading experience.
 
 I’ve seen a lot of developers asking questions like “Should I build my own auth for my app?”. While the answer cannot be a simple "Yes" or "No", I’d like to write an article to breakdown the implementation and demonstrate the pros and cons to help you decide.
 
-<!--truncate-->
+{/* truncate */}
 
 > **TL;DR** If you're still learning, auth will be a good challenge. If you want full control, it's worth building your own auth system. Otherwise, it's necessary to find an existing solution that fits your needs.
 

diff --git a/blog/2023-03-20-announcing-logto-cloud-preview/index.md b/blog/2023-03-20-announcing-logto-cloud-preview/index.md
@@ -14,7 +14,7 @@ Hi there,
 
 I’m Gao, one of the creators of Logto. I remember feeling nervous last July - that’s the date we launched the first beta version of Logto OSS.
 
-<!-- truncate -->
+{/* truncate */}
 
 To our surprise, we had some deep conversations with the community from the outset. We talked about the terrible developer experience of building authentication, even with existing products, and the dramatic costs of current industry leaders. As developers ourselves, we feel you and that's why we started building Logto.
 

diff --git a/blog/releases/2023-feb-extended.md b/blog/releases/2023-feb-extended.md
@@ -19,7 +19,7 @@ Notable updates include:
 
 Let's take a look at what's inside!
 
-<!-- truncate -->
+{/* truncate */}
 
 ## 💥 BREAKING CHANGES 💥
 

diff --git a/blog/releases/2023-feb.md b/blog/releases/2023-feb.md
@@ -10,7 +10,7 @@ tags: [release]
 Please welcome our first release candidate! Logto is just a few steps away from general availability.
 :::
 
-<!-- truncate -->
+{/* truncate */}
 
 ## 💥 Breaking changes 💥
 

diff --git a/blog/releases/2023-jan.md b/blog/releases/2023-jan.md
@@ -18,7 +18,7 @@ For the first day of 2023, we shipped a few things for everybody:
 We are currently busy working on the general availability version which includes User profile, RBAC (Role-based access control), and much more!
 :::
 
-<!-- truncate -->
+{/* truncate */}
 
 ## 💥 Breaking change 💥
 

diff --git a/blog/releases/2023-mar.md b/blog/releases/2023-mar.md
@@ -11,7 +11,7 @@ tags: [release]
 
 We are grateful for your participation in testing Logto OSS, and we're excited to announce our first general availability version. In this version, we have delivered numerous improvements to the sign-in experience, making it more delightful for your end-users. This new release also includes several new practical features.
 
-<!-- truncate -->
+{/* truncate */}
 
 > **Note**
 > In case you missed it, please see the letter from Gao: [Announcing Logto Cloud (Preview) and OSS General Availability](https://docs.logto.io/blog/announcing-logto-cloud-preview).

diff --git a/commitlint.config.js b/commitlint.config.js
diff --git a/commitlint.config.ts b/commitlint.config.ts
@@ -0,0 +1,11 @@
+import conventional from '@commitlint/config-conventional';
+import type { UserConfig } from '@commitlint/types';
+
+const configs: UserConfig = {
+  extends: ['@commitlint/config-conventional'],
+  rules: {
+    'type-enum': [2, 'always', [...conventional.rules['type-enum'][2], 'blog']],
+  },
+};
+
+export default configs;