doc: v3 GA (#531)

* doc: v3 GA

* update nestjs guide

* update homepage

* update

* update

* update

* update

* update docs

* update

* update

Author: ymc9

blog/better-auth/index.mdx

@@ -204,7 +204,7 @@ The initial dashboard UI looks like:
 
 ## Setting up ZenStack
 
-In the following sections, we'll use ZenStack to implement the access control requirements. ZenStack uses its own DSL called [ZModel](/docs/the-complete-guide/part1/zmodel) to define data models and access policy rules. ZModel is a superset of the Prisma schema language. The ZenStack CLI can generate a Prisma schema from a ZModel file so that downstream Prisma consumers (like better-auth) will continue to work seamlessly.
+In the following sections, we'll use ZenStack to implement the access control requirements. ZenStack uses its own DSL called [ZModel](/docs/2.x/the-complete-guide/part1/zmodel) to define data models and access policy rules. ZModel is a superset of the Prisma schema language. The ZenStack CLI can generate a Prisma schema from a ZModel file so that downstream Prisma consumers (like better-auth) will continue to work seamlessly.
 
 Let's initialize the project with ZenStack:
 
@@ -346,9 +346,9 @@ export {
 };
 ```
 
-This will expose a set of CRUD endpoints like `/api/model/TodoList/findMany`, `/api/model/TodoList/create`, etc. You can find more details [here](https://zenstack.dev/docs/reference/server-adapters/api-handlers/rpc).
+This will expose a set of CRUD endpoints like `/api/model/TodoList/findMany`, `/api/model/TodoList/create`, etc. You can find more details [here](https://zenstack.dev/docs/2.x/reference/server-adapters/api-handlers/rpc).
 
-Although we can call these APIs with `fetch` directly, a much easier way is to leverage ZenStack's [TanStack Query plugin](https://zenstack.dev/docs/reference/plugins/tanstack-query) to generate client-side hooks.
+Although we can call these APIs with `fetch` directly, a much easier way is to leverage ZenStack's [TanStack Query plugin](https://zenstack.dev/docs/2.x/reference/plugins/tanstack-query) to generate client-side hooks.
 
 ```bash
 npm install @zenstackhq/tanstack-query
@@ -434,7 +434,7 @@ type Auth {
 }
 ```
 
-Now, we're ready to write the policy rules. You can find more information about access policies [here](https://zenstack.dev/docs/the-complete-guide/part1/access-policy/).
+Now, we're ready to write the policy rules. You can find more information about access policies [here](https://zenstack.dev/docs/2.x/the-complete-guide/part1/access-policy/).
 
 #### 1. Tenant segregation
 

blog/check-function/index.md

@@ -181,7 +181,7 @@ There are two possible ways to add such support:
   }
   ```
 
-- B: make it work with [collection predicate expressions](../docs/reference/zmodel-language#collection-predicate-expressions)
+- B: make it work with [collection predicate expressions](../docs/2.x/reference/zmodel-language#collection-predicate-expressions)
 
   ```zmodel
 

blog/clerk-multitenancy/index.mdx

@@ -105,7 +105,7 @@ npm install --save-dev prisma zenstack
 npm install @prisma/client @zenstackhq/runtime
 ```
 
-Then we can create the database schema. Please note that we're creating a **schema.zmodel** file (as a replacement of "schema.prisma"). The [ZModel language](/docs/the-complete-guide/part1/zmodel) is a superset of Prisma schema language, allowing you to model both the data schema and access control policies. In this section, we'll only focus on the data modeling part.
+Then we can create the database schema. Please note that we're creating a **schema.zmodel** file (as a replacement of "schema.prisma"). The [ZModel language](/docs/2.x/the-complete-guide/part1/zmodel) is a superset of Prisma schema language, allowing you to model both the data schema and access control policies. In this section, we'll only focus on the data modeling part.
 
 ```zmodel title="/schema.zmodel"
 datasource db {

blog/code-as-doc/index.md

@@ -105,7 +105,7 @@ I will walk you through the steps of how to create this tool.
 
 Like many wonderful tools in the web development world, ZenStack adopts a plugin-based architecture. At the core of the system is the ZModel schema, around which features are implemented as plugins.   Let's create a plugin to generate a markdown for a ZModel so it can be easily adopted by others. 
 
-> For brevity, we'll focus on core parts. See the [ZenStack documentation](https://zenstack.dev/docs/the-complete-guide/part2/writing-plugins) for complete plugin development details.
+> For brevity, we'll focus on core parts. See the [ZenStack documentation](https://zenstack.dev/docs/2.x/the-complete-guide/part2/writing-plugins) for complete plugin development details.
 > 
 
 A plugin is simply a Node.js module that has the two parts:

blog/custom-attributes.mdx

@@ -196,7 +196,7 @@ So as Dan Abramov said in the [React Documentary](https://youtu.be/8pDqJVdNa44?t
 
 # Custom attributes of ZenStack
 
-[ZenStack](https://zenstack.dev/?utm_campaign=devto&utm_medium=organic&utm_content=custom_attribute) is the toolkit that supercharges Prisma with a powerful access control layer and unleashes its full potential for full-stack development. Its schema file [ZModel](https://zenstack.dev/docs/reference/zmodel-language) is a superset of Prisma schema.
+[ZenStack](https://zenstack.dev/?utm_campaign=devto&utm_medium=organic&utm_content=custom_attribute) is the toolkit that supercharges Prisma with a powerful access control layer and unleashes its full potential for full-stack development. Its schema file [ZModel](https://zenstack.dev/docs/2.x/reference/zmodel-language) is a superset of Prisma schema.
 
 Regardless of ZenStack, the above Prisma file is supposed to be looks like below ideally:
 
@@ -212,7 +212,7 @@ model User {
 
 Actually, that’s exactly what the ZModel would be. You can find it in our example code:
 
-[https://zenstack.dev/docs/category/quick-start/nextjs#3-preparing-the-user-model-for-authentication](https://zenstack.dev/docs/category/quick-start/nextjs#3-preparing-the-user-model-for-authentication)
+[https://zenstack.dev/docs/2.x/category/quick-start/nextjs#3-preparing-the-user-model-for-authentication](https://zenstack.dev/docs/2.x/category/quick-start/nextjs#3-preparing-the-user-model-for-authentication)
 
 The above attributes are already predefined in our standard library as below:
 

blog/form-validation/index.md

@@ -81,7 +81,7 @@ model Signup {
 A few quick notes:
 - We used attributes like `@email` and `@endsWith` to attach validation rules to fields.
 - We also used the model-level attribute `@@validate` to express validation rules involving multiple fields and conditions.
-- The `@@allow` attribute grants "create" and "read" access to the table. By default, all operations are denied. Access control is not a focus of this post, but you can learn more [here](https://zenstack.dev/docs/the-complete-guide/part1/access-policy/) if interested.
+- The `@@allow` attribute grants "create" and "read" access to the table. By default, all operations are denied. Access control is not a focus of this post, but you can learn more [here](https://zenstack.dev/docs/2.x/the-complete-guide/part1/access-policy/) if interested.
 
 Run the following commands to generate a Prisma schema and synchronize it to the database:
 

blog/json-typing/index.md

@@ -166,4 +166,4 @@ const images = await db.image.findMany({
 });
 ```
 
-Is it useful, or can it be confusing (as it looks the same as relation filters)? Let us know by leaving a comment below. You can also learn more about this feature in the [official guide](https://zenstack.dev/docs/guides/typing-json).
+Is it useful, or can it be confusing (as it looks the same as relation filters)? Let us know by leaving a comment below. You can also learn more about this feature in the [official guide](https://zenstack.dev/docs/2.x/guides/typing-json).

blog/modern-sql-dx/index.md

@@ -34,7 +34,7 @@ There have been many security concerns about using cloud-based databases directl
 
 Beneath the simple surface, cloud database providers have been working hard to automate many things for you:
 
-- Scaling up and down? Don’t worry about it. When idle, the services can shrink to [literally zero CPU usage](https://neon.tech/docs/reference/glossary#scale-to-zero) and rapidly scale up as traffic surges.
+- Scaling up and down? Don’t worry about it. When idle, the services can shrink to [literally zero CPU usage](https://neon.tech/docs/2.x/reference/glossary#scale-to-zero) and rapidly scale up as traffic surges.
 - Bottomless storage, so running out of disk space is never a worry anymore.
 - Sharding has always been a headache to manage and used to require lots of application code changes. Now, it can be achieved in a [much less intrusive way](https://planetscale.com/docs/concepts/sharding).
 - Not proficient with managing indexes? The services monitor query patterns and auto-tune indexes for you.

blog/multi-tenant/index.md

@@ -277,7 +277,7 @@ Then whenever the place you use the Prisma client, just wrap it with the `enhanc
 
 If you feel interested in the access policy, you can find more detail below:
 
-**[Understanding Access Policies](https://zenstack.dev/docs/the-complete-guide/part1/access-policy/)**
+**[Understanding Access Policies](https://zenstack.dev/docs/2.x/the-complete-guide/part1/access-policy/)**
 
 There is also a tutorial for how to create the project step by step:
 

blog/nest-api/index.md

@@ -325,7 +325,7 @@ export class AppModule implements NestModule {
 }
 ```
 
-That's it! Now we have a complete set of RESTful CRUD APIs at "/api/zen" that conforms to the [JSON:API](https://jsonapi.org/) specification, and the access policies fully protect the APIs. The API provides rich filtering and relation-fetching capabilities. The following are some examples; you can find more details [here](https://zenstack.dev/docs/reference/server-adapters/api-handlers/rest#endpoints-and-features).
+That's it! Now we have a complete set of RESTful CRUD APIs at "/api/zen" that conforms to the [JSON:API](https://jsonapi.org/) specification, and the access policies fully protect the APIs. The API provides rich filtering and relation-fetching capabilities. The following are some examples; you can find more details [here](https://zenstack.dev/docs/2.x/reference/server-adapters/api-handlers/rest#endpoints-and-features).
 
 ```bash
 # Fetch posts together with their authors