docs: add projects guide

website/docs/en/config/test/projects.mdx

@@ -17,10 +17,6 @@ Define multiple test projects. It can be an array of directories, configuration
 
 Rstest will run the tests for each project according to the configuration defined in each project, and the test results from all projects will be combined and displayed.
 
-You can filter the specified projects to run by using the [--project](/guide/basic/test-filter#filter-by-project-name) option.
-
-If there is no `projects` field, `rstest` will treat current directory as a single project.
-
 ```ts name='rstest.config.ts'
 import { defineConfig } from '@rstest/core';
 
@@ -52,67 +48,4 @@ export default defineConfig({
 });
 ```
 
-## Configuration notes
-
-- Project configuration does not inherit root configuration. If there is shared configuration between your sub-projects, you can extract the shared configuration and import it in the sub-project.
-- Some root-level options such as `reporters`, `pool`, and `isolate` are not valid in a project configuration.
-
-```ts title='packages/pkg-a/rstest.config.ts'
-import { defineConfig } from '@rstest/core';
-import sharedConfig from '../shared/rstest.config';
-
-export default defineConfig({
-  ...sharedConfig,
-});
-```
-
-## Inline configuration
-
-`rstest` supports configuring projects inline in the `projects` field. This lets you define multiple test projects in a single root without creating separate config files for each test project.
-
-```ts name='rstest.config.ts'
-import { defineConfig } from '@rstest/core';
-
-export default defineConfig({
-  projects: [
-    // inline project configs
-    {
-      name: 'node',
-      include: ['tests/node/**/*.{test,spec}.{js,cjs,mjs,ts,tsx}'],
-    },
-    {
-      name: 'react',
-      include: ['tests/react/**/*.{test,spec}.{js,cjs,mjs,ts,tsx}'],
-      testEnvironment: 'jsdom',
-    },
-  ],
-});
-```
-
-## Nested projects
-
-Rstest supports nested project definitions within the rstest config of sub-projects. This allows you to define more test projects in sub-projects without having to define all projects in the root project.
-
-This is especially useful when your sub-projects need to support multiple test environments or multiple configurations.
-
-### Example
-
-Define Node.js and browser test environments for `packages/pkg-a`:
-
-```ts title='packages/pkg-a/rstest.config.ts'
-import { defineConfig } from '@rstest/core';
-
-export default defineConfig({
-  projects: [
-    {
-      name: 'node',
-      include: ['tests/node/**/*.{test,spec}.?(c|m)[jt]s?(x)'],
-    },
-    {
-      name: 'react',
-      include: ['tests/react/**/*.{test,spec}.?(c|m)[jt]s?(x)'],
-      testEnvironment: 'jsdom',
-    },
-  ],
-});
-```
+More information about projects can be found in [Test projects](/guide/basic/projects).

website/docs/en/guide/advanced/debugging.mdx

@@ -2,7 +2,7 @@
 
 ## Debug mode
 
-Rstest provides a debug mode to troubleshoot problems, you can add the `DEBUG=rstest` environment variable when building to enable Rstest's debug mode.
+Rstest provides a debug mode to troubleshoot problems, you can add the `DEBUG=rstest` environment variable when testing to enable Rstest's debug mode.
 
 ```bash
 DEBUG=rstest pnpm test

website/docs/en/guide/basic/_meta.json

@@ -1 +1,8 @@
-["cli", "configure-rstest", "test-filter", "vscode-extension", "upgrade-rstest"]
+[
+  "cli",
+  "configure-rstest",
+  "test-filter",
+  "projects",
+  "vscode-extension",
+  "upgrade-rstest"
+]

website/docs/en/guide/basic/projects.mdx

@@ -0,0 +1,156 @@
+# Test projects
+
+Rstest supports running multiple test projects simultaneously within a single Rstest process. These projects can have different test configurations and test environments.
+
+## Use cases
+
+- **Monorepo projects**: When your codebase contains multiple sub-packages or modules, each sub-project might have different test configuration requirements.
+- **Different test environments**: Different sub-projects (or even the same sub-project) might need to run in different environments (e.g., Node environment and browser environment).
+- **File-specific testing**: You can specify different test or build configurations for specific test files/directories.
+
+## Example
+
+Define each sub-project in a monorepo as a project through the [projects](/config/test/projects) field, where each sub-project has its own test configuration.
+
+Rstest will automatically recognize each subdirectory under the `packages` directory as an independent test project and run tests according to the [rstest.config.ts](/guide/basic/configure-rstest#configuration-files) file (if present) in the subdirectory.
+
+```ts name='rstest.config.ts'
+import { defineConfig } from '@rstest/core';
+
+export default defineConfig({
+  projects: [
+    // A monorepo: each package directory is a project
+    'packages/*',
+  ],
+});
+```
+
+## Configuration description
+
+You can define multiple test projects through the [projects](/config/test/projects) field. Rstest will run the corresponding tests according to the configurations defined by each project, and all test results will be merged and displayed.
+
+If there is no `projects` field, `rstest` will treat the current directory as a single project.
+
+### Configuration syntax
+
+The `projects` field supports the following configuration methods:
+
+- **Directory path**: Specify a directory, and Rstest will automatically recognize all subdirectories under that directory as projects.
+- **Configuration file path**: Specify a configuration file path, and Rstest will run tests according to that file's configuration.
+- **Glob pattern**: Use glob patterns to match multiple directories or files, and Rstest will use the matching results as projects.
+- **Inline configuration object**: Directly define project configuration objects in the `projects` field. This allows you to define multiple test projects within a single project without creating separate configuration files for each test project.
+- **Nested projects**: Define projects nested within the rstest config of sub-projects.
+
+```ts name='rstest.config.ts'
+import { defineConfig } from '@rstest/core';
+
+export default defineConfig({
+  projects: [
+    // A monorepo: each package directory is a project
+    'packages/*',
+
+    // All projects under the apps directory that provide an rstest config file
+    'apps/**/rstest.config.ts',
+
+    // A specific project directory
+    '<rootDir>/services/auth',
+
+    // A specific project's config file
+    './projects/web/rstest.config.ts',
+
+    // inline project configs
+    {
+      name: 'node',
+      include: ['tests/node/**/*.{test,spec}.{js,cjs,mjs,ts,tsx}'],
+    },
+    {
+      name: 'react',
+      include: ['tests/react/**/*.{test,spec}.{js,cjs,mjs,ts,tsx}'],
+      testEnvironment: 'jsdom',
+    },
+  ],
+});
+```
+
+### Root configuration
+
+When the `projects` field exists in the root directory's rstest config file, Rstest will not treat it as a test project. In this case, the root directory's rstest.config file is only used to define `projects` and [global configuration](#global-configuration).
+
+If you want to treat the root directory as a project as well, you can define the test configuration for the root directory in `projects`.
+
+```ts name='rstest.config.ts'
+import { defineConfig } from '@rstest/core';
+
+export default defineConfig({
+  projects: [
+    {
+      name: 'root',
+      include: ['<rootDir>/tests/**/*.{test,spec}.{js,cjs,mjs,ts,tsx}'],
+    },
+    'packages/*',
+  ],
+});
+```
+
+#### Global configuration
+
+The following configurations are global configurations and are invalid when configured in projects. If you need to modify global configuration, you need to configure it in the root project's rstest config or override it through CLI options.
+
+- `reporters`: Global reporters configuration.
+- `pool`: Global pool configuration.
+- `isolate`: Global isolate configuration.
+- `coverage`: Global coverage configuration.
+- `bail`: Global bail configuration.
+
+### Project configuration
+
+Project configuration does not inherit the configuration from the root directory. Only the `projects` field and [global configuration](#global-configuration) in the root directory are effective.
+
+If there are reusable configuration items between your sub-projects, you can extract shared configurations and introduce them in sub-projects respectively:
+
+```ts title='packages/pkg-a/rstest.config.ts'
+import { defineConfig, mergeRstestConfig } from '@rstest/core';
+import sharedConfig from '../shared/rstest.config';
+
+export default mergeRstestConfig(sharedConfig, {
+  name: 'pkg-a',
+});
+```
+
+You can override all project configurations through [CLI options](/guide/basic/cli#cli-options).
+
+### Nested projects
+
+Rstest supports defining nested projects in sub-project rstest config files. This allows you to define more test projects in sub-projects without defining all projects in the root project.
+
+This is especially useful when your sub-projects need to support multiple test environments or multiple configurations.
+
+For example, define Node.js and browser test environments for `packages/pkg-a`:
+
+```ts title='packages/pkg-a/rstest.config.ts'
+import { defineConfig } from '@rstest/core';
+
+export default defineConfig({
+  projects: [
+    {
+      name: 'node',
+      include: ['tests/node/**/*.{test,spec}.?(c|m)[jt]s?(x)'],
+    },
+    {
+      name: 'react',
+      include: ['tests/react/**/*.{test,spec}.?(c|m)[jt]s?(x)'],
+      testEnvironment: 'jsdom',
+    },
+  ],
+});
+```
+
+### Inspect configuration
+
+If you want to view the final effective configuration of Rstest, you can enable [debug mode](/guide/advanced/debugging#enabling-debug-mode) through the `DEBUG=rstest` environment variable. Rstest will write the final effective Rstest configuration and build configuration to the output directory.
+
+## Filtering projects
+
+You can filter projects through the [--project](/guide/basic/test-filter#filtering-by-project-name) CLI option, or you can filter specific files under projects by directly filtering file names or file paths.
+
+For more information, please refer to the [Test Filtering](/guide/basic/test-filter) chapter.

website/docs/zh/config/test/projects.mdx

@@ -15,10 +15,6 @@ type Projects = (string | ProjectConfig)[];
 
 定义多个测试项目，可以是一个目录、配置文件或 glob 模式，也可以是一个对象。 Rstest 将会按照各个项目定义的配置运行对应的测试，所有项目的测试结果将会合并展示。
 
-你可以通过 [--project](/guide/basic/test-filter#根据项目名称过滤) 选项来过滤运行特定项目。
-
-如果没有 `projects` 字段，`rstest` 会将当前目录视为单个项目。
-
 ```ts name='rstest.config.ts'
 import { defineConfig } from '@rstest/core';
 
@@ -50,69 +46,4 @@ export default defineConfig({
 });
 ```
 
-## 配置说明
-
-需要注意的是：
-
-- project 配置并不会继承全局配置，如果你的子项目间存在共享配置，可以抽取 shared 配置，并在子项目中引入
-- 一些全局配置，如 `reporters`、`pool`、`isolate` 等，在 project 配置中是无效的
-
-```ts title='packages/pkg-a/rstest.config.ts'
-import { defineConfig } from '@rstest/core';
-import sharedConfig from '../shared/rstest.config';
-
-export default defineConfig({
-  ...sharedConfig,
-});
-```
-
-## 内联配置
-
-Rstest 支持在 `projects` 字段中直接通过内联的方式配置 project。这允许你在单个项目下定义多个测试项目，而无需为每个测试项目创建单独的配置文件。
-
-```ts name='rstest.config.ts'
-import { defineConfig } from '@rstest/core';
-
-export default defineConfig({
-  projects: [
-    // inline project configs
-    {
-      name: 'node',
-      include: ['tests/node/**/*.{test,spec}.{js,cjs,mjs,ts,tsx}'],
-    },
-    {
-      name: 'react',
-      include: ['tests/react/**/*.{test,spec}.{js,cjs,mjs,ts,tsx}'],
-      testEnvironment: 'jsdom',
-    },
-  ],
-});
-```
-
-## 嵌套 Projects
-
-Rstest 支持在子项目的 rstest config 中嵌套定义 projects。这允许你在子项目中定义更多的测试项目，而无需在根项目中定义所有项目。
-
-这尤其适用于你的子项目需要同时支持多个测试环境或多份配置的情况。
-
-### 示例
-
-为 `packages/pkg-a` 定义 Node.js 和浏览器两个测试环境：
-
-```ts title='packages/pkg-a/rstest.config.ts'
-import { defineConfig } from '@rstest/core';
-
-export default defineConfig({
-  projects: [
-    {
-      name: 'node',
-      include: ['tests/node/**/*.{test,spec}.?(c|m)[jt]s?(x)'],
-    },
-    {
-      name: 'react',
-      include: ['tests/react/**/*.{test,spec}.?(c|m)[jt]s?(x)'],
-      testEnvironment: 'jsdom',
-    },
-  ],
-});
-```
+更多关于项目配置的信息，请参考[多项目测试](/guide/basic/projects)。

website/docs/zh/guide/advanced/debugging.mdx

@@ -2,7 +2,7 @@
 
 ## 开启调试模式
 
-为了便于排查问题，Rstest 提供了调试模式，你可以在执行构建时添加 `DEBUG=rstest` 环境变量来开启 Rstest 的调试模式。
+为了便于排查问题，Rstest 提供了调试模式，你可以在执行测试时添加 `DEBUG=rstest` 环境变量来开启 Rstest 的调试模式。
 
 ```bash
 DEBUG=rstest pnpm test

website/docs/zh/guide/basic/_meta.json

@@ -1 +1,8 @@
-["cli", "configure-rstest", "test-filter", "vscode-extension", "upgrade-rstest"]
+[
+  "cli",
+  "configure-rstest",
+  "test-filter",
+  "projects",
+  "vscode-extension",
+  "upgrade-rstest"
+]