Hello
-}
-
-// first argument is `name` of route, second argument is `RouteObject`
-app.router.add('root', {
- path: '/',
- element:
- Home
- about
-
-
-}
-
-const Home = () => {
- return Home
-}
-
-const About = () => {
- return About
-}
-
-app.router.add('root', {
- element: hello
,
- })
-
- // remove route
- this.app.router.remove('world');
- }
-}
-```
-
-## Example
-
-```tsx
-/**
- * defaultShowCode: true
- */
-import React from 'react';
-import { Link, Outlet } from 'react-router-dom';
-import { Application } from '@nocobase/client';
-
-const Home = () => Home
; -const About = () =>About
; - -const Layout = () => { - return
-
-}
-
-const app = new Application({
- router: {
- type: 'memory',
- initialEntries: ['/']
- }
-})
-
-app.router.add('root', {
- element: Home, About
-
-
- );
-}
-```
-
-The template method `'{{t({t('World')}
-{compile(title)}
- );
-}
-```
-
-## Suggested configuration
-
-With English text as the key and translation as the value, the benefit of this, even if multiple languages are missing, it will be displayed in English and will not cause reading barriers, e.g.
-
-```ts
-i18n.addResources('zh-CN', 'my-plugin', {
- 'Show dialog': '显示对话框',
- 'Hide dialog': '隐藏对话框'
-});
-```
-
-To make it easier to manage multilingual files, it is recommended to create a `locale` folder in the plugin and place all the corresponding language files in it for easy management.
-
-```bash
-|- /my-plugin
- |- /src
- |- /client
- |- locale # Multilingual folder
- |- zh-CN.ts
- |- en-US.ts
-```
-
-## Example
-
-### Client-side components with multiple languages
-
-For example, the order status component, with different text displays depending on the value.
-
-```tsx | pure
-import React from 'react';
-import { Select } from 'antd';
-import { i18n } from '@nocobase/client';
-import { useTranslation } from 'react-i18next';
-
-i18n.addResources('zh-CN', 'sample-shop-i18n', {
- Pending: '已下单',
- Paid: '已支付',
- Delivered: '已发货',
- Received: '已签收'
-});
-
-const ORDER_STATUS_LIST = [
- { value: -1, label: 'Canceled (untranslated)' },
- { value: 0, label: 'Pending' },
- { value: 1, label: 'Paid' },
- { value: 2, label: 'Delivered' },
- { value: 3, label: 'Received' },
-]
-
-function OrderStatusSelect() {
- const { t } = useTranslation('sample-shop-i18n');
-
- return (
-
- );
-}
-
-export default function () {
- return (
- Hello world!
- }
- return <>{props.children}
-});
-HelloProvider.displayName = 'HelloProvider'
-
-app.use(HelloProvider);
-```
-
-## Client-side of plugins
-
-Directory structure of the client-side of an empty plugin is as follows
-
-```bash
-|- /my-plugin
- |- /src
- |- /client
- |- index.tsx
- |- client.d.ts
- |- client.js
-```
-
-``client/index.tsx`` reads as follows.
-
-```tsx | pure
-import React from 'react';
-
-// This is an empty Provider, only children are passed, no custom Context is provided
-export default React.memo((props) => {
- return <>{props.children};
-});
-```
-
-After the plugin pm.add, it writes the `my-plugin.ts` file to the `packages/app/client/src/plugins` directory.
diff --git a/docs/en-US/development/client/m.svg b/docs/en-US/development/client/m.svg
deleted file mode 100644
index 932d4de2b..000000000
--- a/docs/en-US/development/client/m.svg
+++ /dev/null
@@ -1 +0,0 @@
-
\ No newline at end of file
diff --git a/docs/en-US/development/client/plugin-settings.md b/docs/en-US/development/client/plugin-settings.md
deleted file mode 100644
index f938bbec3..000000000
--- a/docs/en-US/development/client/plugin-settings.md
+++ /dev/null
@@ -1,75 +0,0 @@
-# Plugin Settings Manager
-
-
-
-## Example
-
-### Basic Usage
-
-```tsx | pure
-import { Plugin } from '@nocobase/client';
-import React from 'react';
-
-const HelloSettingPage = () => Hello Setting page
;
-
-export class HelloPlugin extends Plugin {
- async load() {
- this.app.pluginSettingsManager.add('hello', {
- title: 'Hello', // menu title and page title
- icon: 'ApiOutlined', // menu icon
- Component: HelloSettingPage,
- })
- }
-}
-```
-
-### Multiple Level Routes
-
-```tsx | pure
-import { Outlet } from 'react-router-dom'
-const SettingPageLayout = () => This
public part, the following is the outlet of the sub-route: Demo1 Page Content
- })
-
- this.app.pluginSettingsManager.add('hello.demo2', {
- title: 'Demo2 Page',
- Component: () => Demo2 Page Content
- })
- }
-}
-```
-
-### Get Route Path
-
-If you want to get the jump link of the setting page, you can get it through the `getRoutePath` method.
-
-```tsx | pure
-import { useApp } from '@nocobase/client'
-
-const app = useApp();
-app.pluginSettingsManager.getRoutePath('hello'); // /admin/settings/hello
-app.pluginSettingsManager.getRoutePath('hello.demo1'); // /admin/settings/hello/demo1
-```
-
-### Get Config
-
-If you want to get the added configuration (already filtered by permissions), you can get it through the `get` method.
-
-```tsx | pure
-const app = useApp();
-app.pluginSettingsManager.get('hello'); // { title: 'HelloWorld', icon: '', Component: HelloSettingPage, children: [{...}] }
-```
-
-
-See [samples/hello](https://github.com/nocobase/nocobase/blob/main/packages/plugins/%40nocobase/plugin-sample-hello/src/client/index.tsx) for full examples.
diff --git a/docs/en-US/development/client/plugin-settings/settings-tab.jpg b/docs/en-US/development/client/plugin-settings/settings-tab.jpg
deleted file mode 100644
index 34a8da116..000000000
Binary files a/docs/en-US/development/client/plugin-settings/settings-tab.jpg and /dev/null differ
diff --git a/docs/en-US/development/client/test.md b/docs/en-US/development/client/test.md
deleted file mode 100644
index a6c082f9f..000000000
--- a/docs/en-US/development/client/test.md
+++ /dev/null
@@ -1,40 +0,0 @@
-# Testing
-
-Testing is based on the [Jest](https://jestjs.io/) testing framework. Also included are common React testing libraries such as [@testing-library/react](https://testing-library.com/docs/react-testing-library/intro/)
-
-## Example
-
-```tsx | pure
-import { render } from '@testing-library/react';
-import React from 'react';
-import { MemoryRouter } from 'react-router-dom';
-import { RouteSwitch } from '../RouteSwitch';
-import { RouteSwitchProvider } from '../RouteSwitchProvider';
-
-const Home = () => Home
; -const About = () =>About
; - -describe('route-switch', () => { - it('case 1', () => { - const App = () => { - return ( -Home
; -const About = () =>About
; - -const Layout = () => { - return
-
-}
-
-const app = new Application({
- router: {
- type: 'memory',
- initialEntries: ['/']
- }
-})
-
-app.router.add('root', {
- element: Home, About
- hello
,
- })
-
- // remove
- this.app.router.remove('hello');
- }
-}
-```
-
-See [packages/samples/custom-page](https://github.com/nocobase/nocobase/tree/develop/packages/samples/custom-page) for the full example
diff --git a/docs/en-US/development/client/ui-schema-designer/acl.md b/docs/en-US/development/client/ui-schema-designer/acl.md
deleted file mode 100644
index d1c6127f6..000000000
--- a/docs/en-US/development/client/ui-schema-designer/acl.md
+++ /dev/null
@@ -1,2 +0,0 @@
-# ACL
-
diff --git a/docs/en-US/development/client/ui-schema-designer/block-provider.md b/docs/en-US/development/client/ui-schema-designer/block-provider.md
deleted file mode 100644
index 42fa25421..000000000
--- a/docs/en-US/development/client/ui-schema-designer/block-provider.md
+++ /dev/null
@@ -1,2 +0,0 @@
-# 区块
-
diff --git a/docs/en-US/development/client/ui-schema-designer/collection-manager.md b/docs/en-US/development/client/ui-schema-designer/collection-manager.md
deleted file mode 100644
index e4154eb14..000000000
--- a/docs/en-US/development/client/ui-schema-designer/collection-manager.md
+++ /dev/null
@@ -1,127 +0,0 @@
-# Collection Manager
-
-```tsx
-import React from 'react';
-import { observer, ISchema, useForm } from '@formily/react';
-import {
- SchemaComponent,
- SchemaComponentProvider,
- Form,
- Action,
- CollectionProvider,
- CollectionField,
-} from '@nocobase/client';
-import { FormItem, Input } from '@formily/antd-v5';
-
-export default observer(() => {
- const collection = {
- name: 'tests',
- fields: [
- {
- type: 'string',
- name: 'title1',
- interface: 'input',
- uiSchema: {
- title: 'Title1',
- type: 'string',
- 'x-component': 'Input',
- required: true,
- description: 'description1',
- } as ISchema,
- },
- {
- type: 'string',
- name: 'title2',
- interface: 'input',
- uiSchema: {
- title: 'Title2',
- type: 'string',
- 'x-component': 'Input',
- description: 'description',
- default: 'ttt',
- },
- },
- {
- type: 'string',
- name: 'title3',
- },
- ],
- };
-
- const schema: ISchema = {
- type: 'object',
- properties: {
- form1: {
- type: 'void',
- 'x-component': 'Form',
- properties: {
- // 字段 title1 直接使用全局提供的 uiSchema
- title1: {
- 'x-component': 'CollectionField',
- 'x-decorator': 'FormItem',
- default: '111',
- },
- // 等同于
- // title1: {
- // type: 'string',
- // title: 'Title',
- // required: true,
- // 'x-component': 'Input',
- // 'x-decorator': 'FormItem',
- // },
- title2: {
- 'x-component': 'CollectionField',
- 'x-decorator': 'FormItem',
- title: 'Title4', // 覆盖全局已定义的 Title2
- required: true, // 扩展的配置参数
- description: 'description4',
- },
- // 等同于
- // title2: {
- // type: 'string',
- // title: 'Title22',
- // required: true,
- // 'x-component': 'Input',
- // 'x-decorator': 'FormItem',
- // },
- // 字段 title3 没有提供 uiSchema，自行处理
- title3: {
- 'x-component': 'Input',
- 'x-decorator': 'FormItem',
- title: 'Title3',
- required: true,
- },
- action1: {
- // type: 'void',
- 'x-component': 'Action',
- title: 'Submit',
- 'x-component-props': {
- type: 'primary',
- useAction: '{{ useSubmit }}',
- },
- },
- },
- },
- },
- };
-
- const useSubmit = () => {
- const form = useForm();
- return {
- async run() {
- form.submit(() => {
- console.log(form.values);
- });
- },
- };
- };
-
- return (
-
-
-
-
-
-
-
-
- );
-}, { displayName: 'Hello' });
-
-const Page = observer((props) => {
- return {fieldSchema.name}
-{props.children}
- {props.children}
;
-}, { displayName: 'Page' });
-
-export default () => {
- return (
-
- {props.children}
-
- );
-}
-
-const Block = observer((props) => {
- const field = useField();
- const fieldSchema = useFieldSchema();
- return (
-
- Block {fieldSchema.name}{' '}
-
- Drag
-
-
- Hello, world!
; - -const schema = { - type: 'void', - name: 'hello', - 'x-component': 'Hello', -}; - -export default () => { - return ( -{props.value}
-};
-
-const SingleText = connect(
- Input,
- mapProps((props, field) => {
- return {
- ...props,
- suffix: '后缀',
- }
- }),
- mapReadPretty(ReadPretty),
-);
-
-const schema = {
- type: 'object',
- properties: {
- t1: {
- type: 'string',
- default: 'hello t1',
- 'x-component': 'SingleText',
- },
- t2: {
- type: 'string',
- default: 'hello t2',
- 'x-component': 'SingleText',
- 'x-pattern': 'readPretty',
- },
- }
-};
-
-export default () => {
- return (
- UsedObserver: {form.values.t1}
-}, { displayName: 'UsedObserver' });
-
-const NotUsedObserver = (props) => {
- const form = useForm();
- return NotUsedObserver: {form.values.t1}
-};
-
-const schema = {
- type: 'object',
- properties: {
- t1: {
- type: 'string',
- 'x-component': 'SingleText',
- },
- t2: {
- type: 'string',
- 'x-component': 'UsedObserver',
- },
- t3: {
- type: 'string',
- 'x-component': 'NotUsedObserver',
- },
- }
-};
-
-const components = {
- SingleText,
- UsedObserver,
- NotUsedObserver
-};
-
-export default () => {
- return (
- Hello, {props.children}!
; -const World = () => world; - -const schema = { - type: 'object', - name: 'hello', - 'x-component': 'Hello', - properties: { - world: { - type: 'string', - 'x-component': 'World', - }, - }, -}; - -export default () => { - return ( -Hello, {props.children}!
; -const World = () => world; - -const schema = { - type: 'object', - properties: { - title1: { - type: 'void', - 'x-content': 'Void schema，渲染 properties', - }, - void: { - type: 'void', - name: 'hello', - 'x-component': 'Hello', - properties: { - world: { - type: 'void', - 'x-component': 'World', - }, - }, - }, - title2: { - type: 'void', - 'x-content': 'Object schema，渲染 properties', - }, - object: { - type: 'object', - name: 'hello', - 'x-component': 'Hello', - properties: { - world: { - type: 'string', - 'x-component': 'World', - }, - }, - }, - title3: { - type: 'void', - 'x-content': 'Array schema，不渲染 properties', - }, - array: { - type: 'array', - name: 'hello', - 'x-component': 'Hello', - properties: { - world: { - type: 'string', - 'x-component': 'World', - }, - }, - }, - title4: { - type: 'void', - 'x-content': 'String schema，不渲染 properties', - }, - string: { - type: 'string', - name: 'hello', - 'x-component': 'Hello', - properties: { - world: { - type: 'string', - 'x-component': 'World', - }, - }, - }, - } -}; - -export default () => { - return ( --
- {field.value?.map((item, index) => {
- // Only one element
- return
-
- {field.value?.map((item, index) => {
- // When the Array element is an Object
- return (
-
-
-
-
-
-
-
-
- );
-}, { displayName: 'Hello' });
-
-const Page = observer((props) => {
- return {fieldSchema.name}
-{props.children}
- {props.children}
;
-}, { displayName: 'Page' });
-
-export default () => {
- return (
- Hello, world!
-``` - -## children components can be written in properties - -```ts -{ - type: 'void', - 'x-component': 'div', - 'x-component-props': { className: 'form-item' }, - properties: { - title: { - type: 'string', - 'x-component': 'input', - }, - }, -} -``` - -JSX is equivalent to - -```tsx | pure -
-
-
-```
-
-## The clever use of Decorator
-
-The combination of decorator + component allows you to put two components in a single schema node, reducing the complexity of the schema structure and increasing the reusability of the components.
-
-For example, in a form scenario, you can combine a FormItem component with any field component, where the FormItem is the Decorator.
-
-```ts
-{
- type: 'void',
- ['x-component']: 'div',
- properties: {
- title: {
- type: 'string',
- 'x-decorator': 'FormItem',
- 'x-component': 'Input',
- },
- content: {
- type: 'string',
- 'x-decorator': 'FormItem',
- 'x-component': 'Input.TextArea',
- },
- },
-}
-```
-
-JSX is equivalent to
-
-```tsx | pure
-
-
-
-
-
-
-
-```
-
-It is also possible to provide a CardItem component that wraps all blocks, so that all blocks are Card wrapped.
-
-```ts
-{
- type: 'void',
- ['x-component']: 'div',
- properties: {
- title: {
- type: 'string',
- 'x-decorator': 'CardItem',
- 'x-component': 'Table',
- },
- content: {
- type: 'string',
- 'x-decorator': 'CardItem',
- 'x-component': 'Kanban',
- },
- },
-}
-```
-
-JSX is equivalent to
-
-```tsx | pure
-
-
-
-
-
-
-
-```
-
-## Display state of the component
-
-- `'x-display': 'visible'`: the component is displayed
-- `'x-display': 'hidden'`: component is hidden, data is not hidden
-- `'x-display': 'none'`: component is hidden, data is also hidden
-
-### `'x-display': 'visible'`
-
-```ts
-{
- type: 'void',
- 'x-component': 'div',
- 'x-component-props': { className: 'form-item' },
- properties: {
- title: {
- type: 'string',
- 'x-component': 'input',
- 'x-display': 'visible'
- },
- },
-}
-```
-
-JSX is equivalent to
-
-```tsx | pure
-
-
-
-```
-
-### `'x-display': 'hidden'`
-
-```ts
-{
- type: 'void',
- 'x-component': 'div',
- 'x-component-props': { className: 'form-item' },
- properties: {
- title: {
- type: 'string',
- 'x-component': 'input',
- 'x-display': 'hidden'
- },
- },
-}
-```
-
-JSX is equivalent to
-
-```tsx | pure
-
- {/* The input component is not output here, the corresponding field model with name=title still exists */}
-
-```
-
-### `'x-display': 'none'`
-
-```ts
-{
- type: 'void',
- 'x-component': 'div',
- 'x-component-props': { className: 'form-item' },
- properties: {
- title: {
- type: 'string',
- 'x-component': 'input',
- 'x-display': 'none'
- },
- },
-}
-```
-
-JSX is equivalent to
-
-```tsx | pure
-
- {/* The input component is not output here, and the corresponding field model with name=title does not exist anymore */}
-
-```
-
-## Display modes for components
-
-For field components, there are three display modes:
-
-- `'x-pattern': 'editable'` Editable
-- `'x-pattern': 'disabled'` Non-editable
-- `'x-pattern': 'readPretty'` Friendly reading
-
-As in the case of the `
-
-
-```
-
-### `'x-pattern': 'disabled'`
-
-```ts
-const schema = {
- name: 'test',
- type: 'void',
- 'x-component': 'div',
- 'x-component-props': { className: 'form-item' },
- properties: {
- title: {
- type: 'string',
- default: 'Hello',
- 'x-component': 'SingleText',
- 'x-pattern': 'disabled'
- },
- },
-};
-```
-
-JSX is equivalent to
-
-```tsx | pure
-
-
-
-```
-
-### `'x-pattern': 'readPretty'`
-
-```ts
-const schema = {
- name: 'test',
- type: 'void',
- 'x-component': 'div',
- 'x-component-props': { className: 'form-item' },
- properties: {
- title: {
- type: 'string',
- default: 'Hello',
- 'x-component': 'SingleText',
- 'x-pattern': 'readPretty',
- },
- },
-};
-```
-
-JSX is equivalent to
-
-```tsx | pure
-
-
-```
diff --git a/docs/en-US/development/client/ui-schema-designer/x-designer.md b/docs/en-US/development/client/ui-schema-designer/x-designer.md
deleted file mode 100644
index 7ee74ef75..000000000
--- a/docs/en-US/development/client/ui-schema-designer/x-designer.md
+++ /dev/null
@@ -1,61 +0,0 @@
-# x-designer
-
-## Built-in x-designer component
-
-- Action.Designer
-- Calendar.Designer
-- Filter.Action.Designer
-- Form.Designer
-- FormItem.Designer
-- FormV2.Designer
-- FormV2.ReadPrettyDesigner
-- DetailsDesigner
-- G2Plot.Designer
-- Kanban.Designer
-- Kanban.Card.Designer
-- Markdown.Void.Designer
-- Menu.Designer
-- TableV2.Column.Designer
-- TableV2.ActionColumnDesigner
-- TableBlockDesigner
-- TableSelectorDesigner
-- Tabs.Designer
-
-## Replacement
-
-```tsx | pure
-import React, { useContext } from 'react';
-import { useFieldSchema } from '@formily/react';
-import {
- SchemaComponentOptions,
- GeneralSchemaDesigner,
- SchemaSettings,
- useCollection
-} from '@nocobase/client';
-import React from 'react';
-
-const CustomActionDesigner = () => {
- const { name, title } = useCollection();
- const fieldSchema = useFieldSchema();
- return (
- Hello
-
-
-The pluggable design reduces the coupling between modules and increases the reuse rate. As the plugin library continues to expand, common scenarios require only a combination of plugins to complete the base build. NocoBase's no-code platform, for example, is a combination of various plugins.
-
-
-
-## Plugin Manager
-
-NocoBase provides a powerful plugin manager for managing plugins. The flow of the plugin manager is as follows
-
-
-
-No-code Users can manage the activation and deactivation of local plugins through the interface at
-
-
-
-Developers can also manage the complete plugin process by way of the CLI:
-
-```bash
-# Create the plugin
-yarn pm create hello
-# Register the plugin
-yarn pm add hello
-# Activate the plugin
-yarn pm enable hello
-# Disable the plugin
-yarn pm disable hello
-# Remove the plugin
-yarn pm remove hello
-```
-
-For more plugin examples, see [packages/samples](https://github.com/nocobase/nocobase/tree/main/packages/samples).
-
-## Extensibility
-
-Whether it is generic functionality or personalization, it is recommended to write it as a plugin. NocoBase is extensible in all aspects.
-
-- It can be user-intuitive interface-related page modules, block types, action types, field types, etc.
-- Filters, validators, access restrictions, etc. for enhancing or restricting the HTTP API
-- It can also be enhancements to underlying data tables, migrations, events, command lines, etc.
-
-
-Distribution of modules.
-
-- Server
- - Collections & Fields: mainly used for system table configuration. Business tables are recommended to be configured in "Plugin Settings Manager - Collection manager".
- - Resources & Actions: Mainly used to extend the Action API
- - Middleware: Middleware
- - Events: Events
- - I18n: server-side internationalization
- - Commands: Custom command lines
- - Migrations: Migration scripts
-- Client
- - UI Schema Designer: Page Designer
- - UI Router: When there is a need for custom pages
- - Plugin Settings Manager: Provides configuration pages for plugins
- - I18n: Client side internationalization
diff --git a/docs/en-US/development/index/app-flow.svg b/docs/en-US/development/index/app-flow.svg
deleted file mode 100644
index e167cda39..000000000
--- a/docs/en-US/development/index/app-flow.svg
+++ /dev/null
@@ -1 +0,0 @@
-
\ No newline at end of file
diff --git a/docs/en-US/development/index/pm-built-in.jpg b/docs/en-US/development/index/pm-built-in.jpg
deleted file mode 100644
index 2fe60fdac..000000000
Binary files a/docs/en-US/development/index/pm-built-in.jpg and /dev/null differ
diff --git a/docs/en-US/development/index/pm-flow.svg b/docs/en-US/development/index/pm-flow.svg
deleted file mode 100644
index 23a738cfc..000000000
--- a/docs/en-US/development/index/pm-flow.svg
+++ /dev/null
@@ -1 +0,0 @@
-
\ No newline at end of file
diff --git a/docs/en-US/development/index/pm-ui.jpg b/docs/en-US/development/index/pm-ui.jpg
deleted file mode 100644
index 4c8fdd3c1..000000000
Binary files a/docs/en-US/development/index/pm-ui.jpg and /dev/null differ
diff --git a/docs/en-US/development/learning-guide.md b/docs/en-US/development/learning-guide.md
deleted file mode 100644
index 115402259..000000000
--- a/docs/en-US/development/learning-guide.md
+++ /dev/null
@@ -1,125 +0,0 @@
-# 学习路线指南
-
-## 1. 从安装运行 NocoBase 开始
-
-**相关文档：快速开始**
-
-主要命令包括：
-
-下载
-
-```bash
-yarn create/git clone
-yarn install
-```
-
-安装
-
-```bash
-yarn nocobase install
-```
-
-运行
-
-```bash
-# for development
-yarn dev
-
-# for production
-yarn build
-yarn start
-```
-
-## 2. 了解 NocoBase 平台提供的核心功能
-
-**相关文档：使用手册**
-
-主要的三部分包括：
-
-- UI 设计器：主要包括区块、字段和操作
-- 插件管理器：功能需求扩展
-- 配置中心：已激活插件提供的配置功能
-
-## 3. 进一步了解插件管理器的使用
-
-**相关文档：插件开发**
-
-NocoBase 提供了简易的插件管理器界面，但是在界面上只能处理本地插件的 enable、disable 和 remove，完整的操作需要通过 CLI
-
-```bash
-# 创建插件
-yarn pm create hello
-# 注册插件
-yarn pm add hello
-# 激活插件
-yarn pm enable hello
-# 禁用插件
-yarn pm disable hello
-# 删除插件
-yarn pm remove hello
-```
-
-更多插件示例，查看 packages/samples，通过 samples 插件能够了解插件的基本用法，就可以进一步开发插件了。
-
-## 4. 开发新插件，了解模块分布
-
-**相关文档：扩展指南**
-
-[编写第一个插件](/development/your-fisrt-plugin) 章节，虽然简单的讲述了插件的主要开发流程，但是为了更快速的介入插件细节，你可能需要进一步了解 NocoBase 框架的模块分布：
-
-- Server
- - Collections & Fields：主要用于系统表配置，业务表建议在「配置中心 - 数据表配置」里配置
- - Resources & Actions：主要用于扩展 Action API
- - Middleware：中间件
- - Events：事件
- - I18n：服务端国际化
-- Client
- - UI Schema Designer：页面设计器
- - UI Router：有自定义页面需求时
- - Plugin Settings Manager：为插件提供配置页面
- - I18n：客户端国际化
-- Devtools
- - Commands：自定义命令行
- - Migrations：迁移脚本
-
-## 5. 查阅各模块主要 API
-
-**相关文档：API 参考**
-
-查看各模块的 packages/samples，进一步了解模块主要 API 的用法
-
-- Server
- - Collections & Fields
- - db.collection
- - db.import
- - Resources & Actions
- - app.resourcer.define
- - app.resourcer.registerActions
- - Middleware
- - app.use
- - app.acl.use
- - app.resourcer.use
- - Events
- - app.on
- - app.db.on
- - I18n
- - app.i18n
- - ctx.i18n
-- Client
- - UI Schema Designer
- - SchemaComponent
- - SchemaInitializer
- - SchemaSettings
- - UI Router
- - RouteSwitchProvider
- - RouteSwitch
- - I18n
- - app.i18n
- - useTranslation
-- Devtools
- - Commands
- - app.command
- - app.findCommand
- - Migrations
- - app.db.addMigration
- - app.db.addMigrations
diff --git a/docs/en-US/development/life-cycle.md b/docs/en-US/development/life-cycle.md
deleted file mode 100644
index f250b26a9..000000000
--- a/docs/en-US/development/life-cycle.md
+++ /dev/null
@@ -1,41 +0,0 @@
-# Life cycle
-
-## Lifecycle of applications
-
-
-
-## Lifecycle of plugins
-
-
-
-## Lifecycle methods for plugins
-
-```ts
-import { InstallOptions, Plugin } from '@nocobase/server';
-
-export class MyPlugin extends Plugin {
- afterAdd() {
- // After the plugin pm.add is registered. Mainly used to place the app.beforeLoad event.
- beforeLoad() { }
- beforeLoad() {
- // Before all plugins are loaded. Generally used for registering classes and event listeners
- }
- async load() {
- // Load configuration
- }
- async install(options?: InstallOptions) {
- // Logic for installing
- }
- async afterEnable() {
- // After activation
- }
- async afterDisable() {
- // After disable
- }
- async remove() {
- // Logic for removing
- }
-}
-
-export default MyPlugin;
-```
diff --git a/docs/en-US/development/others/build.md b/docs/en-US/development/others/build.md
deleted file mode 100644
index 1294b9a65..000000000
--- a/docs/en-US/development/others/build.md
+++ /dev/null
@@ -1 +0,0 @@
-# Building
\ No newline at end of file
diff --git a/docs/en-US/development/others/testing.md b/docs/en-US/development/others/testing.md
deleted file mode 100644
index 1f37805b5..000000000
--- a/docs/en-US/development/others/testing.md
+++ /dev/null
@@ -1,163 +0,0 @@
-# 单元测试
-
-## 介绍
-
-NocoBase 的测试基于 [Jest](https://jestjs.io/) 测试框架。同时，为了方便的编写测试，我们提供了两个工具类，在测试环境模拟正常的数据库和应用的服务端。
-
-### MockDatabase
-
-模拟数据库类继承自 [`Database`](/api/database) 类，大部分内容没有区别，主要在构造函数默认内置了随机表前缀，在每个测试用例初始化数据库时相关数据表都通过前缀名称与其他用例进行隔离，在运行测试用例时互不影响。
-
-```ts
-import { MockDatabase } from '@nocobase/test';
-
-describe('my suite', () => {
- let db;
-
- beforeEach(async () => {
- db = new MockDatabase();
-
- db.collection({
- name: 'posts',
- fields: [
- {
- type: 'string',
- name: 'title',
- }
- ]
- });
-
- await db.sync();
- });
-
- test('my case', async () => {
- const postRepository = db.getRepository('posts');
- const p1 = await postRepository.create({
- values: {
- title: 'hello'
- }
- });
-
- expect(p1.get('title')).toEqual('hello');
- });
-});
-```
-
-### MockServer
-
-模拟服务器也继承自 [Application](/api/server/application) 类，除了内置的数据库实例是通过模拟数据库类生成的以外，还提供了比较方便的生成基于 [superagent](https://www.npmjs.com/package/superagent) 请求代理功能，针对从发送请求到获取响应的写法也集成了 `.resource('posts').create()`，比较简化。
-
-```ts
-import { mockServer } from '@nocobase/test';
-
-describe('my suite', () => {
- let app;
- let agent;
- let db;
-
- beforeEach(async () => {
- app = mockServer();
- agent = app.agent();
-
- db.collection({
- name: 'posts',
- fields: [
- {
- type: 'string',
- name: 'title',
- }
- ]
- });
-
- await db.sync();
- await app.load();
- });
-
- test('my case', async () => {
- const { body } = await agent.resource('posts').create({
- values: {
- title: 'hello'
- }
- });
-
- expect(body.data.title).toEqual('hello');
- });
-});
-```
-
-## 示例
-
-我们以之前在 [资源与操作](development/guide/resources-actions) 章节的功能为例，来写一个插件的测试：
-
-```ts
-import { mockServer } from '@nocobase/test';
-import Plugin from '../../src/server';
-
-describe('shop actions', () => {
- let app;
- let agent;
- let db;
-
- beforeEach(async () => {
- app = mockServer();
- app.plugin(Plugin);
- agent = app.agent();
- db = app.db;
-
- await app.load();
- await db.sync();
- });
-
- afterEach(async () => {
- await app.destroy();
- });
-
- test('product order case', async () => {
- const { body: product } = await agent.resource('products').create({
- values: {
- title: 'iPhone 14 Pro',
- price: 7999,
- enabled: true,
- inventory: 1
- }
- });
- expect(product.data.price).toEqual(7999);
-
- const { body: order } = await agent.resource('orders').create({
- values: {
- productId: product.data.id
- }
- });
- expect(order.data.totalPrice).toEqual(7999);
- expect(order.data.status).toEqual(0);
-
- const { body: deliveredOrder } = await agent.resource('orders').deliver({
- filterByTk: order.data.id,
- values: {
- provider: 'SF',
- trackingNumber: '123456789'
- }
- });
- expect(deliveredOrder.data.status).toBe(2);
- expect(deliveredOrder.data.delivery.trackingNumber).toBe('123456789');
- });
-});
-```
-
-编写完成后，在命令行中允许测试命令：
-
-```bash
-yarn test packages/samples/shop-actions
-```
-
-该测试将验证：
-
-1. 商品可以创建成功；
-2. 订单可以创建成功；
-3. 订单可以发货成功；
-
-当然这只是个最基本的例子，从业务上来说并不完善，但作为示例已经可以说明整个测试的流程。
-
-## 小结
-
-本章涉及的示例代码整合在对应的包 [packages/samples/shop-actions](https://github.com/nocobase/nocobase/tree/main/packages/samples/shop-actions) 中，可以直接在本地运行，查看效果。
diff --git a/docs/en-US/development/plugin-ds.md b/docs/en-US/development/plugin-ds.md
deleted file mode 100644
index 6c05646a9..000000000
--- a/docs/en-US/development/plugin-ds.md
+++ /dev/null
@@ -1,45 +0,0 @@
-# Plugin directory structure
-
-An empty plugin can be created quickly with `yarn pm create my-plugin`, with the following directory structure.
-
-```bash
-|- /my-plugin
- |- /src
- |- /client # client-side of the plugin
- |- /server # server-side of the plugin
- |- client.d.ts
- |- client.js
- |- package.json # plugin package information
- |- server.d.ts
- |- server.js
- |- build.config.ts # or `build.config.js`, modify configuration
-```
-
-The tutorial for `/src/server` refers to the [server](./server) section, and the tutorial for `/src/client` refers to the [client](./client) section.
-
-If you want to customize the packaging configuration, you can create a `config.js` file in the root directory, with the following content:
-
-```js
-import { defineConfig } from '@nocobase/build';
-
-export default defineConfig({
- modifyViteConfig: (config) => {
- // vite is used to package the `src/client` side code
-
- // Modify the Vite configuration, for more information, please refer to: https://vitejs.dev/guide/
- return config
- },
- modifyTsupConfig: (config) => {
- // tsup is used to package the `src/server` side code
-
- // Modify the tsup configuration, for more information, please refer to: https://tsup.egoist.dev/#using-custom-configuration
- return config
- },
- beforeBuild: (log) => {
- // The callback function before the build starts, you can do some operations before the build starts
- },
- afterBuild: (log: PkgLog) => {
- // The callback function after the build is completed, you can do some operations after the build is completed
- };
-})
-```
diff --git a/docs/en-US/development/server/collections-fields.md b/docs/en-US/development/server/collections-fields.md
deleted file mode 100644
index e5570aba8..000000000
--- a/docs/en-US/development/server/collections-fields.md
+++ /dev/null
@@ -1,319 +0,0 @@
-## Collections and Fields
-
-## Basic Concepts
-
-Data modeling is the lowest level foundation of an application. In NocoBase applications we model data through data tables (Collection) and fields (Field), and the modeling is also mapped to database tables for persistence.
-
-### Collection
-
-Collection is a collection of all similar data, which corresponds to the concept of database tables in NocoBase. Such as orders, products, users, comments, etc. can form a collection definition. Different collections are distinguished by name and contain fields defined by `fields`, such as
-
-```ts
-db.collection({
- name: 'posts',
- fields: [
- { name: 'title', type: 'string' }
- { name: 'content', type: 'text' },
- // ...
- ]
-});
-```
-
-The collection is only in memory after the definition, you need to call the [``db.sync()`'' (/api/database#sync) method to synchronize it to the database.
-
-### Field
-
-Corresponding to the concept of database table "fields", each data table (Collection) can have a number of Fields, for example.
-
-```ts
-db.collection({
- name: 'users',
- fields: [
- { type: 'string', name: 'name' }
- { type: 'integer', name: 'age' }
- // Other fields
- ],
-});
-```
-
-The field name (`name`) and field type (`type`) are required, and different fields are distinguished by the field name (`name`). All field types and their configurations are described in the [List of built-in field types](/api/database/field#List of built-in field types) section of the API reference.
-
-## Example
-
-For developers, we usually build functional collections that are different from normal collections and solidify these collections as part of the plugin and combine them with other data processing processes to form a complete functionality.
-
-Let's take a simple online store plugin as an example to show how to model and manage the collections of the plugin. Assuming you have already learned about [Develop your first plugin](/development/your-first-plugin), we continue to build on the previous plugin code, except that the name of the plugin is changed from `hello` to `shop-modeling`.
-
-### Define and create collections in the plugin
-
-For a store, you first need to create a collection of products, named `products`. Instead of calling [`db.collection()`](/api/database#collection) directly, in the plugin we will use a more convenient method to import multiple files of defined data tables at once. So let's start by creating a file for the product collection definition named ``collections/products.ts`` and fill it with the following content.
-
-```ts
-export default {
- name: 'products',
- fields: [
- {
- type: 'string',
- name: 'title'
- },
- {
- type: 'integer',
- name: 'price'
- },
- {
- type: 'boolean',
- name: 'enabled'
- },
- {
- type: 'integer',
- name: 'inventory'
- }
- ]
-};
-```
-
-As you can see, the collections structure definition can be used directly in standard JSON format, where `name` and `fields` are required representing the collection's name and the field definitions in the collection. Field definitions similar to Sequelize create system fields such as primary key (`id`), data creation time (`createdAt`) and data update time (`updatedAt`) by default, which can be overridden by a configuration with the same name if there is a special need.
-
-The data table defined in this file we can introduce and complete the definition in the `load()` cycle of the main plugin class using `db.import()`. This is shown below.
-
-```ts
-import path from 'path';
-import { Plugin } from '@nocobase/server';
-
-export default class ShopPlugin extends Plugin {
- async load() {
- await this.db.import({
- directory: path.resolve(__dirname, 'collections'),
- });
-
- this.app.acl.allow('products', '*');
- this.app.acl.allow('categories', '*');
- this.app.acl.allow('orders', '*');
- }
-}
-```
-
-In the meantime, for testing purposes, we will temporarily allow all access permissions for the data in these collections, and later we will detail how to manage data permissions in [Permissions Management](/development/guide/acl).
-
-This way, when the plugin is loaded by the main application, the `products` collection we defined is also loaded into the memory of the database management instance. At the same time, the NocoBase constraint-based resource mapping of the collections automatically generates the corresponding CRUD HTTP API after the application's service is started.
-
-When the following URLs are requested from the client, the corresponding responses are obtained.
-
-* `GET /api/products:list`: Get a list of all product data
-* `GET /api/products:get?filterByTk=
-
-## Configuring collections through the interface
-
-Business data is generally recommended to be configured using the interface, and the NocoBase platform provides two interfaces to configure collections.
-
-### Regular table interface
-
-
-
-### Graphical configuration interface
-
-
-
-## Defined in the plugin code
-
-Generally used to configure plugin functions or system configuration tables where users can read and write data, but cannot modify the data structure.
-
-```ts
-export class MyPlugin extends Plugin {
- load() {
- this.db.collection();
- this.db.import();
- }
-}
-```
-
-Related API Reference
-
-- [db.collection()](/api/database#collection)
-- [db.import()](/api/database#import)
-
-The collection configured in the plugin is automatically synchronized with the database when the plugin is activated, giving birth to the corresponding data tables and fields.
-
-## Managing data tables via REST API
-
-Third parties can also manage data tables via the HTTP interface (permissions required)
-
-### Collections
-
-```bash
-GET /api/collections
-POST /api/collections
-GET /api/collections/
-
-## Extend Field Type
-
-For example, to extend the password type field ``type: 'password'`
-
-```ts
-export class MyPlugin extends Plugin {
- beforeLoad() {
- this.db.registerFieldTypes({
- password: PasswordField
- });
- }
-}
-
-export class PasswordField extends Field {
- get dataType() {
- return DataTypes.STRING;
- }
-}
-```
-
-- [More implementations of the built-in field types can be found here](https://github.com/nocobase/nocobase/tree/main/packages/core/database/src/fields)
-- Also see the full samples plugin [packages/samples/shop-modeling](https://github.com/nocobase/nocobase/tree/main/packages/samples/shop-modeling)
-
-## Extend Field Component
-
-Related extension documentation can be found at
-
-- [Extending Schema Components](/development/client/ui-schema-designer/extending-schema-components)
-- [Schema component library](/development/client/ui-schema-designer/component-library)
-
-## Extend Field Interface
-
-- [Built-in field interfaces view here](https://github.com/nocobase/nocobase/tree/main/packages/core/client/src/collection-manager/interfaces)
diff --git a/docs/en-US/development/server/collections/graph.jpg b/docs/en-US/development/server/collections/graph.jpg
deleted file mode 100644
index 16c2f95d1..000000000
Binary files a/docs/en-US/development/server/collections/graph.jpg and /dev/null differ
diff --git a/docs/en-US/development/server/collections/index.md b/docs/en-US/development/server/collections/index.md
deleted file mode 100644
index 27e7d7dd9..000000000
--- a/docs/en-US/development/server/collections/index.md
+++ /dev/null
@@ -1,194 +0,0 @@
-# Core concepts
-
-## Collection
-
-Collection is a collection of all kinds of data, such as orders, products, users, comments, etc. Different collections are distinguished by name, e.g.
-
-```ts
-// Orders
-{
- name: 'orders',
-}
-// Products
-{
- name: 'products',
-}
-// Users
-{
- name: 'users',
-}
-// Comments
-{
- name: 'comments',
-}
-```
-
-## Collection Field
-
-Each Collection has a number of Fields.
-
-```ts
-// Collection configuration
-{
- name: 'users',
- fields: [
- { type: 'string', name: 'name' },
- { type: 'integer', name: 'age' },
- // Other fields
- ],
-}
-// sample data
-[
- {
- name: 'Jason',
- age: 20,
- },
- { {
- name: 'Li Si',
- age: 18,
- }
-];
-```
-
-The composition of a Collection Field in NocoBase consists of
-
-
-
-### Field Type
-
-Different fields are distinguished by name, and type indicates the data type of the field, which is divided into Attribute Type and Association Type, e.g.
-
-**Attribute - Attribute Type**
-
-- string
-- text
-- date
-- boolean
-- time
-- float
-- json
-- location
-- password
-- virtual
-- ...
-
-**Relationship - Association Type**
-
-- hasOne
-- hasMany
-- belongsTo
-- belongsToMany
-- ...
-
-### Field Component
-
-The field has a data type, the IO of the field value is fine, but it is not enough, if you need to display the field on the interface, you need another dimension of configuration -- `uiSchema`, e.g.
-
-```tsx | pure
-// Email field, displayed with Input component, using email validation rules
-{
- type: 'string',
- name: 'email',
- uiSchema: {
- 'x-component': 'Input',
- 'x-component-props': { size: 'large' },
- 'x-validator': 'email',
- 'x-pattern': 'editable', // editable state, and readonly state, read-pretty state
- },
-}
-
-// Example data
-{
- email: 'admin@nocobase.com',
-}
-
-// Component example
-
-```
-
-The uiSchema is used to configure the components of the field to be displayed on the interface, each field component will correspond to a value and includes several maintained configurations:
-
-- The component of the field
-- The parameters of the component
-- The field's validation rules
-- The mode of the field (editable, readonly, read-pretty)
-- The default value of the field
-- Other
-
-[see the UI Schema chapter for more information](/development/client/ui-schema-designer/what-is-ui-schema).
-
-The built-in field components of NocoBase are
-
-- Input
-- InputNumber
-- Select
-- Radio
-- Checkbox
-- ...
-
-### Field Interface
-
-With Field Type and Field Component you can freely combine several fields, we call this combined template Field Interface, e.g.
-
-```ts
-// email field, string + input, email validation rules
-{
- type: 'string',
- name: 'email',
- uiSchema: {
- 'x-component': 'Input',
- 'x-component-props': {},
- 'x-validator': 'email',
- },
-}
-
-// phone field, string + input, phone validation rules
-{
- type: 'string',
- name: 'phone',
- uiSchema: {
- 'x-component': 'Input',
- 'x-component-props': {},
- 'x-validator': 'phone',
- },
-}
-```
-
-The above email and phone require a full uiSchema to be configured each time which is very tedious. To simplify the configuration, another concept Field interface is introduced, which can template some parameters, e.g.
-
-```ts
-// Template for the email field
-interface email {
- type: 'string';
- uiSchema: {
- 'x-component': 'Input',
- 'x-component-props': {},
- 'x-validator': 'email',
- };
-}
-
-// Template for the phone field
-interface phone {
- type: 'string';
- uiSchema: {
- 'x-component': 'Input',
- 'x-component-props': {},
- 'x-validator': 'phone',
- };
-}
-
-// Simplified field configuration
-// email
-{
- interface: 'email',
- name: 'email',
-}
-
-// phone
-{
- interface: 'phone',
- name: 'phone',
-}
-```
-
-[More Field Interface here](https://github.com/nocobase/nocobase/tree/main/packages/core/client/src/collection-manager/interfaces)
diff --git a/docs/en-US/development/server/collections/options.md b/docs/en-US/development/server/collections/options.md
deleted file mode 100644
index 319edf654..000000000
--- a/docs/en-US/development/server/collections/options.md
+++ /dev/null
@@ -1,137 +0,0 @@
-# Collection protocol
-
-Collection is the backbone of NocoBase, a protocol for describing data structures (collections and fields), very close to the concept of a relational database, but not limited to relational databases, but can also be a data source for NoSQL databases, HTTP APIs, etc.
-
-
-
-At this stage, the Collection protocol is based on the relational database interface (db.collections), and data sources such as NoSQL databases and HTTP APIs will be implemented gradually in the future.
-
-Collection protocol mainly includes two parts: CollectionOptions and FieldOptions. Because Field is extensible, the parameters of FieldOptions are very flexible.
-
-## CollectionOptions
-
-```ts
-interface CollectionOptions {
- name: string;
- title?: string;
- // Tree structure table, TreeRepository
- tree?: 'adjacency-list' | 'closure-table' | 'materialized-path' | 'nested-set';
- // parent-child inheritance
- inherits?: string | string[];
- fields?: FieldOptions[];
- timestamps?: boolean;
- paranoid?: boolean;
- sortable?: CollectionSortable;
- model?: string;
- repository?: string;
- [key: string]: any;
-}
-
-type CollectionSortable = string | boolean | { name?: string; scopeKey?: string };
-```
-
-## FieldOptions
-
-Generic field parameters
-
-```ts
-interface FieldOptions {
- name: string;
- type: string;
- hidden?: boolean;
- index?: boolean;
- interface?: string;
- uiSchema?: ISchema;
-```
-
-[Introduction to UI Schema here](/development/client/ui-schema-designer/what-is-ui-schema)
-
-### Field Type
-
-Field Type includes Attribute Type and Association Type.
-
-**Attribute Type**
-
-- 'boolean'
-- 'integer'
-- 'bigInt'
-- 'double'
-- 'real'
-- 'decimal'
-- 'string'
-- 'text'
-- 'password'
-- 'date'
-- 'time'
-- 'array'
-- 'json'
-- 'jsonb'
-- 'uuid'
-- 'uid'
-- 'formula'
-- 'radio'
-- 'sort'
-- 'virtual'
-
-**Association Type**
-
-- 'belongsTo'
-- 'hasOne'
-- 'hasMany'
-- 'belongsToMany'
-
-### Field Interface
-
-**Basic**
-
-- input
-- textarea
-- phone
-- email
-- integer
-- number
-- percent
-- password
-- icon
-
-**Choices**
-
-- checkbox
-- select
-- multipleSelect
-- radioGroup
-- checkboxGroup
-- chinaRegion
-
-**Media**
-
-- attachment
-- markdown
-- richText
-
-**Date & Time**
-
-- datetime
-- time
-
-**Relation**
-
-- linkTo - `type: 'believesToMany'`
-- oho - `type: 'hasOne'`
-- obo - `type: 'believesTo'`
-- o2m - `type: 'hasMany'`
-- m2o - `type: 'believesTo'`
-- m2m - `type: 'believesToMany'`
-
-**Advanced**
-
-- formula
-- sequence
-
-**System info**
-
-- id
-- createdAt
-- createdBy
-- updatedAt
-- updatedBy
diff --git a/docs/en-US/development/server/collections/schema.svg b/docs/en-US/development/server/collections/schema.svg
deleted file mode 100644
index 230a9bbca..000000000
--- a/docs/en-US/development/server/collections/schema.svg
+++ /dev/null
@@ -1 +0,0 @@
-
\ No newline at end of file
diff --git a/docs/en-US/development/server/collections/table.jpg b/docs/en-US/development/server/collections/table.jpg
deleted file mode 100644
index 55fe4c183..000000000
Binary files a/docs/en-US/development/server/collections/table.jpg and /dev/null differ
diff --git a/docs/en-US/development/server/commands.md b/docs/en-US/development/server/commands.md
deleted file mode 100644
index 069e1f354..000000000
--- a/docs/en-US/development/server/commands.md
+++ /dev/null
@@ -1,100 +0,0 @@
-# Commands
-
-NocoBase Server Application is a powerful and extensible CLI tool in addition to being used as a WEB server.
-
-Create a new `app.js` file with the following code.
-
-```ts
-const Application = require('@nocobase/server');
-
-// omit the specific configuration here
-const app = new Application({/*... */});
-
-app.runAsCLI();
-```
-
-app.js run as ``runAsCLI()`` is a CLI, it will work like this in the command line tool.
-
-```bash
-node app.js install # install
-node app.js start # start
-```
-
-To better develop, build and deploy NocoBase applications, NocoBase has many built-in commands, see the [NocoBase CLI](/api/cli) section for details.
-
-## How to customize Command?
-
-NocoBase CLI is designed to be very similar to [Laravel Artisan](https://laravel.com/docs/9.x/artisan), both are extensible. NocoBase CLI is based on [commander](https://www.npmjs.com/ package/commander) implementation, which extends Command like this
-
-```ts
-export class MyPlugin extends Plugin {
- load() {
- this.app
- .command('echo')
- .option('--v, --version');
- .action(async ([options]) => {
- console.log('Hello World!');
- if (options.version) {
- console.log('Current version:', app.getVersion());
- }
- });
- }
-}
-```
-
-This method defines the following command.
-
-```bash
-yarn nocobase echo
-# Hello World!
-yarn nocobase echo -v
-# Hello World!
-# Current version: 0.8.0-alpha.1
-```
-
-More API details can be found in the [Application.command()](/api/server/application#command) section.
-
-## Example
-
-### Defining a command for exporting collections
-
-If we want to export the data in the application's collections to a JSON file, we can define a subcommand as follows.
-
-```ts
-import path from 'path';
-import * as fs from 'fs/promises';
-
-class MyPlugin extends Plugin {
- load() {
- this.app
- .command('export')
- .option('-o, --output-dir')
- .action(async (options, . .collections) => {
- const { outputDir = path.join(process.env.PWD, 'storage') } = options;
- await collections.reduce((promise, collection) => promise.then(async () => {
- if (!this.db.hasCollection(collection)) {
- console.warn('No such collection:', collection);
- return;
- }
-
- const repo = this.db.getRepository(collection);
- const data = repo.find();
- await fs.writeFile(path.join(outputDir, `${collection}.json`), JSON.stringify(data), { mode: 0o644 });
- }), Promise.resolve());
- });
- }
-}
-```
-
-After registering and activating the plugin call from the command line.
-
-```bash
-mkdir -p . /storage/backups
-yarn nocobase export -o . /storage/backups users
-```
-
-After execution, it will generate `. /storage/backups/users.json` file containing the data from the collections.
-
-## Summary
-
-The sample code covered in this chapter is integrated in the [packages/samples/command](https://github.com/nocobase/nocobase/tree/main/packages/samples/command) package and can be run directly locally to see the results.
diff --git a/docs/en-US/development/server/events.md b/docs/en-US/development/server/events.md
deleted file mode 100644
index 15e2a6a96..000000000
--- a/docs/en-US/development/server/events.md
+++ /dev/null
@@ -1,168 +0,0 @@
-# Events
-
-NocoBase provides a very large number of event listeners in the lifecycle of applications, plugins, and database, and these methods will only be executed when an event is triggered.
-
-## How to add event listeners?
-
-The registration of events is usually placed in afterAdd or beforeLoad
-
-```ts
-export class MyPlugin extends Plugin {
- // After the plugin is added, afterAdd() is executed with or without activation
- afterAdd() {
- this.app.on();
- this.db.on();
- }
-
- // beforeLoad() will only be executed after the plugin is activated
- beforeLoad() {
- this.app.on();
- this.db.on();
- }
-}
-```
-
-### `db.on`
-
-Database related events are related to Collection configuration, CRUD of Repository, including:
-
-- 'beforeSync' / 'afterSync'
-- 'beforeValidate' / 'afterValidate'
-- 'beforeCreate' / 'afterCreate'
-- 'beforeUpdate' / 'afterUpdate'
-- 'beforeSave' / 'afterSave'
-- 'beforeDestroy' / 'afterDestroy'
-- 'afterCreateWithAssociations'
-- 'afterUpdateWithAssociations'
-- 'afterSaveWithAssociations'
-- 'beforeDefineCollection'
-- 'afterDefineCollection'
-- 'beforeRemoveCollection' / 'afterRemoveCollection'
-
-See [Database API](/api/database) for more details.
-
-### `app.on()`
-
-The app's events are related to the application's lifecycle, and the relevant events are:
-
-- 'beforeLoad' / 'afterLoad'
-- 'beforeInstall' / 'afterInstall'
-- 'beforeUpgrade' / 'afterUpgrade'
-- 'beforeStart' / 'afterStart'
-- 'beforeStop' / 'afterStop'
-- 'beforeDestroy' / 'afterDestroy'
-
-Refer to [Application API](/api/server/application#Events) for more details.
-
-## Example
-
-Let's continue with a simple online store as an example, the related collections modeling can be reviewed in the [Collections and Fields](/development/) section for examples.
-
-### Deducting product inventory after creating an order
-
-Usually we have different collections for products and orders. The problem of overselling can be solved by subtracting the inventory of the item after the customer has placed the order. At this point we can define the corresponding event for the action of Creating Order and solve the inventory modification problem at this time together with:
-
-```ts
-class ShopPlugin extends Plugin {
- beforeLoad() {
- this.db.on('orders.afterCreate', async (order, options) => {
- const product = await order.getProduct({
- transaction: options.transaction
- });
-
- await product.update({
- inventory: product.inventory - order.quantity
- }, {
- transaction: options.transaction
- });
- });
- }
-}
-```
-
-Since the default Sequelize event carries information about the transaction, we can use transaction directly to ensure that both data actions are performed in the same transaction.
-
-Similarly, you can change the order status to shipped after creating the shipping record: ```ts
-
-```ts
-class ShopPlugin extends Plugin {
- load() {
- this.db.on('deliveries.afterCreate', async (delivery, options) => {
- const orderRepo = this.db.getRepository('orders');
- await orderRepo.update({
- filterByTk: delivery.orderId,
- value: {
- status: 2
- }
- transaction: options.transaction
- });
- });
- }
-}
-```
-
-### Timed tasks that exist alongside the application
-
-Without considering complex cases such as using workflow plugins, we can also implement a simple timed task mechanism via application-level events, and it can be bound to the application's process and stop when it exits. For example, if we want to scan all orders at regular intervals and automatically sign them after the sign-off time.
-
-```ts
-class ShopPlugin extends Plugin {
- timer = null;
- orderReceiveExpires = 86400 * 7;
-
- checkOrder = async () => {
- const expiredDate = new Date(Date.now() - this.orderReceiveExpires);
- const deliveryRepo = this.db.getRepository('deliveries');
- const expiredDeliveries = await deliveryRepo.find({
- fields: ['id', 'orderId'],
- filter: {
- status: 0,
- createdAt: {
- $lt: expiredDate
- }
- }
- });
- await deliveryRepo.update({
- filter: {
- id: expiredDeliveries.map(item => item.get('id')),
- },
- values: {
- status: 1
- }
- });
- const orderRepo = this.db.getRepository('orders');
- const [updated] = await orderRepo.update({
- filter: {
- status: 2,
- id: expiredDeliveries.map(item => item.get('orderId'))
- },
- values: {
- status: 3
- }
- });
-
- console.log('%d orders expired', updated);
- };
-
- load() {
- this.app.on('beforeStart', () => {
- // execute every minute
- this.timer = setInterval(this.checkOrder, 1000 * 60);
- });
-
- this.app.on('beforeStop', () => {
- clearInterval(this.timer);
- this.timer = null;
- });
- }
-}
-```
-
-## Summary
-
-The above example gives us a basic understanding of what events do and the ways they can be used to extend.
-
-* Database related events
-* Application related events
-
-The sample code covered in this chapter is integrated in the corresponding package [packages/samples/shop-events](https://github.com/nocobase/nocobase/tree/main/packages/samples/shop-events), which can be run directly in run locally to see the results.
diff --git a/docs/en-US/development/server/i18n.md b/docs/en-US/development/server/i18n.md
deleted file mode 100644
index e0b68cc59..000000000
--- a/docs/en-US/development/server/i18n.md
+++ /dev/null
@@ -1,134 +0,0 @@
-# Internationalization
-
-Internationalization in NocoBase is implemented based on [i18next](https://npmjs.com/package/i18next).
-
-## How to register a multilingual package?
-
-```ts
-export class MyPlugin extends Plugin {
- load() {
- this.app.i18n.addResources('zh-CN', 'test', {
- Hello: '你好',
- World: '世界',
- });
- this.app.i18n.addResources('en-US', 'test', {
- Hello: 'Hello',
- World: 'World',
- });
- }
-}
-```
-
-## Two i18n instances
-
-### app.i18n
-
-Global i18n instance, typically used in the CLI.
-
-```ts
-app.i18n.t('World') // "世界" or "World"
-```
-
-### ctx.i18n
-
-CloneInstance of global i18n with a completely independent context for each request, typically used to respond to multilingual messages based on the client language.
-
-```ts
-app.use(async (ctx, next) => {
- ctx.body = `${ctx.i18n.t('Hello')} ${ctx.i18n.t('World')}`;
- await next();
-});
-```
-
-The client request parameters can be placed in the query string
-
-```bash
-GET /?locale=en-US HTTP/1.1
-Host: localhost:13000
-```
-
-or in the request headers
-
-```bash
-GET / HTTP/1.1
-Host: localhost:13000
-X-Locale: en-US
-```
-
-## Suggested configuration
-
-With English text as the key and translation as the value, this has the advantage that even if multiple languages are missing, it will be displayed in English and will not cause reading barriers, e.g.
-
-```ts
-i18n.addResources('zh-CN', 'your-namespace', {
- 'Show dialog': '显示对话框',
- 'Hide dialog': '隐藏对话框'
-});
-```
-
-To make it easier to manage multilingual files, it is recommended to create a `locale` folder in the plugin and place all the corresponding language files in it:
-
-```bash
-|- /my-plugin
- |- /src
- |- /server
- |- locale # Multi-language folder
- |- en-cn.ts
- |- en-US.ts
-```
-
-## Example
-
-### Server-side error alert
-
-For example, when a user places an order for a product in the store, if the product is not in stock, or not on the shelf, then the order interface should return the appropriate error when it is called.
-
-```ts
-const namespace = 'shop';
-
-export default class ShopPlugin extends Plugin {
- async load() {
- this.app.i18n.addResources('zh-CN', namespace, {
- 'No such product': '商品不存在',
- 'Product not on sale': '商品已下架',
- 'Out of stock': '库存不足',
- });
-
- this.app.resource({
- name: 'orders',
- actions: {
- async create(ctx, next) {
- const productRepo = ctx.db.getRepository('products');
- const product = await productRepo.findOne({
- filterByTk: ctx.action.params.values.productId
- productId });
-
- if (!product) {
- return ctx.throw(404, ctx.t('No such product'));
- }
-
- if (!product.enabled) {
- return ctx.throw(400, ctx.t('Product not on sale'));
- }
-
- if (!product.inventory) {
- return ctx.throw(400, ctx.t('Out of stock'));
- }
-
- const orderRepo = ctx.db.getRepository('orders');
- ctx.body = await orderRepo.create({
- values: {
- productId: product.id,
- quantity: 1,
- totalPrice: product.price,
- userId: ctx.state.currentUser.id
- }
- });
-
- next();
- }
- }
- });
- }
-}
-```
diff --git a/docs/en-US/development/server/index.md b/docs/en-US/development/server/index.md
deleted file mode 100644
index b220c425d..000000000
--- a/docs/en-US/development/server/index.md
+++ /dev/null
@@ -1,72 +0,0 @@
-# Overview
-
-The server-side for an initialized, empty plugin has the following directory structure.
-
-```bash
-|- /my-plugin
- |- /src
- |- /server # Server-side code of the plugin
- |- plugin.ts # Classes of the plugin
- |- index.ts # server-side entry
- |- server.d.ts
- |- server.js
-```
-
-`plugin.ts` provides calls to various methods of the plugin lifecycle
-
-```ts
-import { InstallOptions, Plugin } from '@nocobase/server';
-
-export class MyPlugin extends Plugin {
- afterAdd() {
- // After the plugin pm.add is registered. This is mainly used to place a listener for the app beforeLoad event
- this.app.on('beforeLoad');
- }
- beforeLoad() {
- // Custom classes or methods
- this.db.registerFieldTypes()
- this.db.registerModels()
- this.db.registerRepositories()
- this.db.registerOperators()
- // Event Listening
- this.app.on();
- this.db.on();
- }
- async load() {
- // Define collection
- this.db.collection();
- // Import collection
- this.db.import();
- this.db.addMigrations();
-
- // Define resource
- this.resourcer.define();
- // resource action
- this.resourcer.registerActions();
-
- // Register middleware
- this.resourcer.use();
- this.acl.use();
- this.app.use();
-
- // Customize the multilingual package
- this.app.i18n.addResources();
- // Customize command line
- this.app.command();
- }
- async install(options?: InstallOptions) {
- // Logic for installing
- }
- async afterEnable() {
- // After activation
- }
- async afterDisable() {
- // After disable
- }
- async remove() {
- // Logic for removing
- }
-}
-
-export default MyPlugin;
-```
diff --git a/docs/en-US/development/server/middleware.md b/docs/en-US/development/server/middleware.md
deleted file mode 100644
index 80f156b53..000000000
--- a/docs/en-US/development/server/middleware.md
+++ /dev/null
@@ -1,160 +0,0 @@
-# Middleware
-
-## How to register middleware?
-
-The registration method for middleware is usually written in the load method
-
-```ts
-export class MyPlugin extends Plugin {
- load() {
- this.app.acl.use();
- this.app.resourcer.use();
- this.app.use();
- }
-}
-```
-
-Notes.
-
-1. `app.acl.use()` Add a resource-permission-level middleware to be executed before permission determination
-2. `app.resourcer.use()` Adds a resource-level middleware that is executed only when a defined resource is requested
-3. `app.use()` Add an application-level middleware to be executed on every request
-
-## Onion Circle Model
-
-```ts
-app.use(async (ctx, next) => {
- ctx.body = ctx.body || [];
- ctx.body.push(1);
- await next();
- ctx.body.push(2);
-});
-
-app.use(async (ctx, next) => {
- ctx.body = ctx.body || [];
- ctx.body.push(3);
- await next();
- ctx.body.push(4);
-});
-```
-
-Visit http://localhost:13000/api/hello to see that the browser responds with the following data
-
-```js
-{"data": [1,3,4,2]}
-```
-
-## Built-in middlewares and execution order
-
-1. `cors`
-2. `bodyParser`
-3. `i18n`
-4. `dataWrapping`
-5. `db2resource` 6.
-6. `restApi` 1.
- 1. `parseToken` 2.
- 2. `checkRole`
- 3. `acl` 1.
- 1. `acl.use()` Additional middleware added
- 4. `resourcer.use()` Additional middleware added
- 5. `action handler`
-7. `app.use()` Additional middleware added
-
-You can also use `before` or `after` to insert the middleware into the location of one of the preceding `tag`, e.g.
-
-```ts
-app.use(m1, { tag: 'restApi' });
-app.resourcer.use(m2, { tag: 'parseToken' });
-app.resourcer.use(m3, { tag: 'checkRole' });
-// m4 will come before m1
-app.use(m4, { before: 'restApi' });
-// m5 will be inserted between m2 and m3
-app.resourcer.use(m5, { after: 'parseToken', before: 'checkRole' });
-```
-
-If no location is specifically specified, the order of execution of the added middlewares is
-
-1. middlewares added by `acl.use` will be executed first
-2. then the ones added by `resourcer.use`, including the middleware handler and action handler
-3. and finally the ones added by `app.use`
-
-```ts
-app.use(async (ctx, next) => {
- ctx.body = ctx.body || [];
- ctx.body.push(1);
- await next();
- ctx.body.push(2);
-});
-
-app.resourcer.use(async (ctx, next) => {
- ctx.body = ctx.body || [];
- ctx.body.push(3);
- await next();
- ctx.body.push(4);
-});
-
-app.acl.use(async (ctx, next) => {
- ctx.body = ctx.body || [];
- ctx.body.push(5);
- await next();
- ctx.body.push(6);
-});
-
-app.resourcer.define({
- name: 'test',
- actions: {
- async list(ctx, next) {
- ctx.body = ctx.body || [];
- ctx.body.push(7);
- await next();
- ctx.body.push(8);
- },
- },
-});
-```
-
-Visit http://localhost:13000/api/hello to see that the browser responds with the data
-
-```js
-{"data": [1,2]}
-```
-
-Visiting http://localhost:13000/api/test:list to see, the browser responds with the following data
-
-```js
-{"data": [5,3,7,1,2,8,4,6]}
-```
-
-### Resource undefined, middlewares added by resourcer.use() will not be executed
-
-```ts
-app.use(async (ctx, next) => {
- ctx.body = ctx.body || [];
- ctx.body.push(1);
- await next();
- ctx.body.push(2);
-});
-
-app.resourcer.use(async (ctx, next) => {
- ctx.body = ctx.body || [];
- ctx.body.push(3);
- await next();
- ctx.body.push(4);
-});
-```
-
-Visit http://localhost:13000/api/hello to see that the browser responds with the following data
-
-```js
-{"data": [1,2]}
-```
-
-In the above example, the hello resource is not defined and will not enter the resourcer, so the middleware in the resourcer will not be executed
-
-## Middleware Usage
-
-TODO
-
-## Example
-
-- [samples/ratelimit](https://github.com/nocobase/nocobase/blob/main/packages/samples/ratelimit/) IP rate-limiting
diff --git a/docs/en-US/development/server/migration.md b/docs/en-US/development/server/migration.md
deleted file mode 100644
index eb7b3e341..000000000
--- a/docs/en-US/development/server/migration.md
+++ /dev/null
@@ -1,50 +0,0 @@
-# Database Migration
-
-There may be some incompatible changes during the plugin update iteration, these incompatible upgrade scripts can be handled by writing migration files.
-
-## How to add a migration file?
-
-```ts
-export class MyPlugin extends Plugin {
- load() {
- // Load a single Migration file
- this.db.addMigration();
- // Load multiple Migration files
- this.db.addMigrations();
- }
-}
-```
-
-API reference.
-
-- [db.addMigration()](/api/database#addmigration)
-- [db.addMigrations()](/api/database#addmigrations)
-
-## When to execute?
-
-```bash
-## When the app is upgraded, migrator.up() and db.sync() are executed
-yarn nocobase upgrade
-# Trigger migration separately
-yarn nocobase migrator up
-```
-
-## When do I need to write a migration file?
-
-It is usually used to update the system configuration stored in the database during the upgrade process. If it is just a collection configuration change, you don't need to configure migration, just execute ``yarn nocobase db:sync`` to synchronize to the database.
-
-## Migration file
-
-```ts
-import { Migration } from '@nocobase/server';
-
-export default class CustomMigration extends Migration {
- async up() {
- //
- }
-
- async down() {
- //
- }
-}
-```
diff --git a/docs/en-US/development/server/resources-actions.md b/docs/en-US/development/server/resources-actions.md
deleted file mode 100644
index 1d79b0718..000000000
--- a/docs/en-US/development/server/resources-actions.md
+++ /dev/null
@@ -1,464 +0,0 @@
-# Resources and Actions
-
-In the web development world, you may have heard of the concept of RESTful, and NocoBase borrows this concept of resources to map various entities in the system, such as data in a database, a file in a file system or a service. However, NocoBase does not fully follow the RESTful conventions based on practical considerations, but rather extends the specifications from the [Google Cloud API Design Guide](https://cloud.google.com/apis/design) to fit more scenarios.
-
-## Basic concepts
-
-The same concept as resources in RESTful, which are externally available objects in the system that can be manipulated, such as data tables, files, and other custom objects.
-
-Actions refer to reading and writing to resources, usually for accessing data, creating data, updating data, deleting data, etc. NocoBase implements access to resources by defining actions, the core of which is actually a Koa-compatible middleware function for handling requests.
-
-### Automatic mapping of collections to resources
-
-NocoBase automatically maps collections to resources by default, and also provides a server-side data interface. So by default, as long as a collection is defined using `db.collection()`, you can access the data resources of this collection via NocoBase HTTP API. The name of the automatically generated resource is the same as the collection name, for example, the collection defined by `db.collection({ name: 'users' })` has the corresponding resource name `users`.
-
-Also, there are built-in common CRUD actions for these data resources, and built-in actions methods for associative data for relational data resources.
-
-The default actions for a simple data resource:
-
-* [`list`](/api/actions#list): Query the list of data in the collection
-* [`get`](/api/actions#get): Query a single record in the collection
-* [`create`](/api/actions#create): Create a single record to the collection
-* [`update`](/api/actions#update): Update a single record on the collection
-* [`destroy`](/api/actions#destroy): Delete a single record from the collection
-
-In addition to simple CRUD actions, relational resources have default relational actions:
-
-* [`add`](/api/actions#add): Add a association to the data
-* [`remove`](/api/actions#remove): Removes an association from the data
-* [`set`](/api/actions#set): Set the association to the data
-* [`toggle`](/api/actions#toggle): Add or remove associations to data
-
-For example, to define an article collection and synchronize it to the database.
-
-```ts
-app.db.collection({
- name: 'posts',
- fields: [
- { type: 'string', name: 'title' }
- ]
-});
-
-await app.db.sync();
-```
-
-All CRUD methods for the `posts` data resource can then be called directly via the HTTP API: ```bash
-
-```bash
-# create
-curl -X POST -H "Content-Type: application/json" -d '{"title": "first"}' http://localhost:13000/api/posts:create
-# list
-curl http://localhost:13000/api/posts:list
-# update
-curl -X PUT -H "Content-Type: application/json" -d '{"title": "second"}' http://localhost:13000/api/posts:update
-# destroy
-curl -X DELETE http://localhost:13000/api/posts:destroy?filterByTk=1
-```
-
-### Customize Actions
-
-It is also possible to extend specific resources with more actions when the default provided actions such as CRUD do not satisfy the business scenario. For example, additional processing of built-in actions, or the need to set default parameters.
-
-Custom actions for specific resources, such as overriding the `create` action in the article collection.
-
-```ts
-// Equivalent to app.resourcer.registerActions()
-// Register the create action method for article resources
-app.actions({
- async ['posts:create'](ctx, next) {
- const postRepo = ctx.db.getRepository('posts');
- await postRepo.create({
- values: {
- ... . ctx.action.params.values,
- // restrict the current user to be the creator of the post
- userId: ctx.state.currentUserId
- }
- });
-
- await next();
- }
-});
-```
-
-This adds a reasonable restriction in the business that users cannot create articles as other users.
-
-Custom operations for all global resources, such as adding `export` action to all collections.
-
-```ts
-app.actions({
- // Add export method to all resources for exporting data
- async export(ctx, next) {
- const repo = ctx.db.getRepository(ctx.action.resource);
- const results = await repo.find({
- filter: ctx.action.params.filter
- });
- ctx.type = 'text/csv';
- // Splice to CSV format
- ctx.body = results
- .map(row => Object.keys(row)
- .reduce((arr, col) => [... . arr, row[col]], []).join(',')
- ).join('\n');
-
- next();
- }
-});
-```
-
-The data in CSV format can then be exported as follows from the HTTP API.
-
-```bash
-curl http://localhost:13000/api/
-
-If the plugin is not shown in the plugin manager, you can add it manually with the `pm add` command.
-
-```bash
-yarn pm add @my-project/plugin-hello
-```
-
-## Code the plugin
-
-Look at the `packages/plugins/@my-project/plugin-hello/src/server/plugin.ts` file and modify it to
-
-```ts
-import { InstallOptions, Plugin } from '@nocobase/server';
-
-export class PluginHelloServer extends Plugin {
- afterAdd() {}
-
- beforeLoad() {}
-
- async load() {
- this.db.collection({
- name: 'hello',
- fields: [{ type: 'string', name: 'name' }],
- });
- this.app.acl.allow('hello', '*');
- }
-
- async install(options?: InstallOptions) {}
-
- async afterEnable() {}
-
- async afterDisable() {}
-
- async remove() {}
-}
-
-export default PluginHelloServer;
-```
-
-## Activate the plugin
-
-**Operated by command**
-
-```bash
-yarn pm enable @my-project/plugin-hello
-```
-
-**Operated by UI**
-
-Visit the Plugin Manager to view the plugin you just added and click enable.
-The Plugin Manager page defaults to http://localhost:13000/admin/pm/list/local/
-
-
-
-Node: When the plugin is activated, the hello collection that you just configured is automatically created.
-
-## Debug the Plugin
-
-If the app is not started, you need to start the app first
-
-```bash
-# for development
-yarn dev
-
-# for production
-yarn build
-yarn start
-```
-
-Insert data into the hello collection of the plugin
-
-```bash
-curl --location --request POST 'http://localhost:13000/api/hello:create' \
---header 'Content-Type: application/json' \
---data-raw '{
- "name": "Hello world"
-}'
-```
-
-View the data
-
-```bash
-curl --location --request GET 'http://localhost:13000/api/hello:list'
-```
-
-## Build the plugin
-
-```bash
-yarn build plugins/@my-project/plugin-hello --tar
-
-# step-by-step
-yarn build plugins/@my-project/plugin-hello
-yarn nocobase tar plugins/@my-project/plugin-hello
-```
-
-The default saved path for the plugin tar is `storage/tar/@my-project/plugin-hello.tar.gz`
-
-## Upload to other NocoBase applications
-
-Only supported in v0.14 and above
-
-
diff --git a/docs/en-US/index.md b/docs/en-US/index.md
deleted file mode 100644
index 49a1e7610..000000000
--- a/docs/en-US/index.md
+++ /dev/null
@@ -1,3 +0,0 @@
-# Index
-
-
-
-The following table lists the Language Culture Name, Locale File Name, Display Name.
-
-| Language Culture Name | Locale File Name | Display Name |
-| :-------------------- | :--------------- | :---------------------------- |
-| af-ZA | af_ZA.ts | Afrikaans - South Africa |
-| sq-AL | sq_AL.ts | Albanian - Albania |
-| ar-DZ | ar_DZ.ts | Arabic - Algeria |
-| ar-BH | ar_BH.ts | Arabic - Bahrain |
-| ar-EG | ar_EG.ts | Arabic - Egypt |
-| ar-IQ | ar_IQ.ts | Arabic - Iraq |
-| ar-JO | ar_JO.ts | Arabic - Jordan |
-| ar-KW | ar_KW.ts | Arabic - Kuwait |
-| ar-LB | ar_LB.ts | Arabic - Lebanon |
-| ar-LY | ar_LY.ts | Arabic - Libya |
-| ar-MA | ar_MA.ts | Arabic - Morocco |
-| ar-OM | ar_OM.ts | Arabic - Oman |
-| ar-QA | ar_QA.ts | Arabic - Qatar |
-| ar-SA | ar_SA.ts | Arabic - Saudi Arabia |
-| ar-SY | ar_SY.ts | Arabic - Syria |
-| ar-TN | ar_TN.ts | Arabic - Tunisia |
-| ar-AE | ar_AE.ts | Arabic - United Arab Emirates |
-| ar-YE | ar_YE.ts | Arabic - Yemen |
-| hy-AM | hy_AM.ts | Armenian - Armenia |
-| Cy-az-AZ | Cy_az_AZ.ts | Azeri (Cyrillic) - Azerbaijan |
-| Lt-az-AZ | Lt_az_AZ.ts | Azeri (Latin) - Azerbaijan |
-| eu-ES | eu_ES.ts | Basque - Basque |
-| be-BY | be_BY.ts | Belarusian - Belarus |
-| bg-BG | bg_BG.ts | Bulgarian - Bulgaria |
-| ca-ES | ca_ES.ts | Catalan - Catalan |
-| zh-CN | zh_CN.ts | Chinese - China |
-| zh-HK | zh_HK.ts | Chinese - Hong Kong SAR |
-| zh-MO | zh_MO.ts | Chinese - Macau SAR |
-| zh-SG | zh_SG.ts | Chinese - Singapore |
-| zh-TW | zh_TW.ts | Chinese - Taiwan |
-| zh-CHS | zh_CHS.ts | Chinese (Simplified) |
-| zh-CHT | zh_CHT.ts | Chinese (Traditional) |
-| hr-HR | hr_HR.ts | Croatian - Croatia |
-| cs-CZ | cs_CZ.ts | Czech - Czech Republic |
-| da-DK | da_DK.ts | Danish - Denmark |
-| div-MV | div_MV.ts | Dhivehi - Maldives |
-| nl-BE | nl_BE.ts | Dutch - Belgium |
-| nl-NL | nl_NL.ts | Dutch - The Netherlands |
-| en-AU | en_AU.ts | English - Australia |
-| en-BZ | en_BZ.ts | English - Belize |
-| en-CA | en_CA.ts | English - Canada |
-| en-CB | en_CB.ts | English - Caribbean |
-| en-IE | en_IE.ts | English - Ireland |
-| en-JM | en_JM.ts | English - Jamaica |
-| en-NZ | en_NZ.ts | English - New Zealand |
-| en-PH | en_PH.ts | English - Philippines |
-| en-ZA | en_ZA.ts | English - South Africa |
-| en-TT | en_TT.ts | English - Trinidad and Tobago |
-| en-GB | en_GB.ts | English - United Kingdom |
-| en-US | en_US.ts | English - United States |
-| en-ZW | en_ZW.ts | English - Zimbabwe |
-| et-EE | et_EE.ts | Estonian - Estonia |
-| fo-FO | fo_FO.ts | Faroese - Faroe Islands |
-| fa-IR | fa_IR.ts | Farsi - Iran |
-| fi-FI | fi_FI.ts | Finnish - Finland |
-| fr-BE | fr_BE.ts | French - Belgium |
-| fr-CA | fr_CA.ts | French - Canada |
-| fr-FR | fr_FR.ts | French - France |
-| fr-LU | fr_LU.ts | French - Luxembourg |
-| fr-MC | fr_MC.ts | French - Monaco |
-| fr-CH | fr_CH.ts | French - Switzerland |
-| gl-ES | gl_ES.ts | Galician - Galician |
-| ka-GE | ka_GE.ts | Georgian - Georgia |
-| de-AT | de_AT.ts | German - Austria |
-| de-DE | de_DE.ts | German - Germany |
-| de-LI | de_LI.ts | German - Liechtenstein |
-| de-LU | de_LU.ts | German - Luxembourg |
-| de-CH | de_CH.ts | German - Switzerland |
-| el-GR | el_GR.ts | Greek - Greece |
-| gu-IN | gu_IN.ts | Gujarati - India |
-| he-IL | he_IL.ts | Hebrew - Israel |
-| hi-IN | hi_IN.ts | Hindi - India |
-| hu-HU | hu_HU.ts | Hungarian - Hungary |
-| is-IS | is_IS.ts | Icelandic - Iceland |
-| id-ID | id_ID.ts | Indonesian - Indonesia |
-| it-IT | it_IT.ts | Italian - Italy |
-| it-CH | it_CH.ts | Italian - Switzerland |
-| ja-JP | ja_JP.ts | Japanese - Japan |
-| kn-IN | kn_IN.ts | Kannada - India |
-| kk-KZ | kk_KZ.ts | Kazakh - Kazakhstan |
-| kok-IN | kok_IN.ts | Konkani - India |
-| ko-KR | ko_KR.ts | Korean - Korea |
-| ky-KZ | ky_KZ.ts | Kyrgyz - Kazakhstan |
-| lv-LV | lv_LV.ts | Latvian - Latvia |
-| lt-LT | lt_LT.ts | Lithuanian - Lithuania |
-| mk-MK | mk_MK.ts | Macedonian (FYROM) |
-| ms-BN | ms_BN.ts | Malay - Brunei |
-| ms-MY | ms_MY.ts | Malay - Malaysia |
-| mr-IN | mr_IN.ts | Marathi - India |
-| mn-MN | mn_MN.ts | Mongolian - Mongolia |
-| nb-NO | nb_NO.ts | Norwegian (Bokmål) - Norway |
-| nn-NO | nn_NO.ts | Norwegian (Nynorsk) - Norway |
-| pl-PL | pl_PL.ts | Polish - Poland |
-| pt-BR | pt_BR.ts | Portuguese - Brazil |
-| pt-PT | pt_PT.ts | Portuguese - Portugal |
-| pa-IN | pa_IN.ts | Punjabi - India |
-| ro-RO | ro_RO.ts | Romanian - Romania |
-| ru-RU | ru_RU.ts | Russian - Russia |
-| sa-IN | sa_IN.ts | Sanskrit - India |
-| Cy-sr-SP | Cy_sr_SP.ts | Serbian (Cyrillic) - Serbia |
-| Lt-sr-SP | Lt_sr_SP.ts | Serbian (Latin) - Serbia |
-| sk-SK | sk_SK.ts | Slovak - Slovakia |
-| sl-SI | sl_SI.ts | Slovenian - Slovenia |
-| es-AR | es_AR.ts | Spanish - Argentina |
-| es-BO | es_BO.ts | Spanish - Bolivia |
-| es-CL | es_CL.ts | Spanish - Chile |
-| es-CO | es_CO.ts | Spanish - Colombia |
-| es-CR | es_CR.ts | Spanish - Costa Rica |
-| es-DO | es_DO.ts | Spanish - Dominican Republic |
-| es-EC | es_EC.ts | Spanish - Ecuador |
-| es-SV | es_SV.ts | Spanish - El Salvador |
-| es-GT | es_GT.ts | Spanish - Guatemala |
-| es-HN | es_HN.ts | Spanish - Honduras |
-| es-MX | es_MX.ts | Spanish - Mexico |
-| es-NI | es_NI.ts | Spanish - Nicaragua |
-| es-PA | es_PA.ts | Spanish - Panama |
-| es-PY | es_PY.ts | Spanish - Paraguay |
-| es-PE | es_PE.ts | Spanish - Peru |
-| es-PR | es_PR.ts | Spanish - Puerto Rico |
-| es-ES | es_ES.ts | Spanish - Spain |
-| es-UY | es_UY.ts | Spanish - Uruguay |
-| es-VE | es_VE.ts | Spanish - Venezuela |
-| sw-KE | sw_KE.ts | Swahili - Kenya |
-| sv-FI | sv_FI.ts | Swedish - Finland |
-| sv-SE | sv_SE.ts | Swedish - Sweden |
-| syr-SY | syr_SY.ts | Syriac - Syria |
-| ta-IN | ta_IN.ts | Tamil - India |
-| tt-RU | tt_RU.ts | Tatar - Russia |
-| te-IN | te_IN.ts | Telugu - India |
-| th-TH | th_TH.ts | Thai - Thailand |
-| tr-TR | tr_TR.ts | Turkish - Turkey |
-| uk-UA | uk_UA.ts | Ukrainian - Ukraine |
-| ur-PK | ur_PK.ts | Urdu - Pakistan |
-| Cy-uz-UZ | Cy_uz_UZ.ts | Uzbek (Cyrillic) - Uzbekistan |
-| Lt-uz-UZ | Lt_uz_UZ.ts | Uzbek (Latin) - Uzbekistan |
-| vi-VN | vi_VN.ts | Vietnamese - Vietnam |
diff --git a/docs/en-US/welcome/community/translations/enabled-languages.jpg b/docs/en-US/welcome/community/translations/enabled-languages.jpg
deleted file mode 100644
index fcf326305..000000000
Binary files a/docs/en-US/welcome/community/translations/enabled-languages.jpg and /dev/null differ
diff --git a/docs/en-US/welcome/community/translations/language-settings-1.jpg b/docs/en-US/welcome/community/translations/language-settings-1.jpg
deleted file mode 100644
index eb352a0f8..000000000
Binary files a/docs/en-US/welcome/community/translations/language-settings-1.jpg and /dev/null differ
diff --git a/docs/en-US/welcome/community/translations/language-settings-2.jpg b/docs/en-US/welcome/community/translations/language-settings-2.jpg
deleted file mode 100644
index 3e9f7b08e..000000000
Binary files a/docs/en-US/welcome/community/translations/language-settings-2.jpg and /dev/null differ
diff --git a/docs/en-US/welcome/getting-started/deployment.md b/docs/en-US/welcome/getting-started/deployment.md
deleted file mode 100644
index ed3c9a4c8..000000000
--- a/docs/en-US/welcome/getting-started/deployment.md
+++ /dev/null
@@ -1,2 +0,0 @@
-# Deployment
-
diff --git a/docs/en-US/welcome/getting-started/installation/create-nocobase-app.md b/docs/en-US/welcome/getting-started/installation/create-nocobase-app.md
deleted file mode 100644
index 92a834865..000000000
--- a/docs/en-US/welcome/getting-started/installation/create-nocobase-app.md
+++ /dev/null
@@ -1,86 +0,0 @@
-# `create-nocobase-app`
-
-## 0. Prerequisites
-
-Make sure you have:
-
-- Installed Node.js 16+, Yarn 1.22.x
-- Configured and started one of the required database SQLite 3.x, MySQL 8.x, PostgreSQL 10.x
-
-Please make sure you have Node.js 16.x or above installed. You can download and install the latest LTS version from the official website. It is recommended to use nvm (or nvm-windows for Win systems) to manage Node.js versions if you plan to work with Node.js for a long time.
-
-```bash
-$ node -v
-
-v16.13.2
-```
-
-Install yarn package manager
-
-```bash
-$ npm install --global yarn
-$ yarn -v
-
-1.22.10
-```
-
-## 1. Create a NocoBase project
-
-```bash
-# SQLite
-yarn create nocobase-app my-nocobase-app -d sqlite
-# MySQL
-yarn create nocobase-app my-nocobase-app -d mysql \
- -e DB_HOST=localhost \
- -e DB_PORT=3306 \
- -e DB_DATABASE=nocobase \
- -e DB_USER=nocobase \
- -e DB_PASSWORD=nocobase
-# PostgreSQL
-yarn create nocobase-app my-nocobase-app -d postgres \
- -e DB_HOST=localhost \
- -e DB_PORT=5432 \
- -e DB_DATABASE=nocobase \
- -e DB_USER=nocobase \
- -e DB_PASSWORD=nocobase
-```
-
-## 2. Switch to the project directory
-
-```bash
-cd my-nocobase-app
-```
-
-## 3. Install dependencies
-
-📢 This next step may take more than ten minutes due to network environment, system configuration, and other factors.
-
-```bash
-yarn install
-```
-
-## 4. Install NocoBase
-
-```bash
-yarn nocobase install --lang=zh-CN
-```
-
-## 5. Start NocoBase
-
-Development
-
-```bash
-yarn dev
-```
-
-Production
-
-```bash
-yarn start
-```
-
-Note: For production, if the code has been modified, you need to execute `yarn build` and restart NocoBase.
-
-## 6. Log in to NocoBase
-
-Open [http://localhost:13000](http://localhost:13000) in a web browser. The initial account and password are `admin@nocobase.com` and `admin123`.
diff --git a/docs/en-US/welcome/getting-started/installation/docker-compose.md b/docs/en-US/welcome/getting-started/installation/docker-compose.md
deleted file mode 100644
index 5b788504f..000000000
--- a/docs/en-US/welcome/getting-started/installation/docker-compose.md
+++ /dev/null
@@ -1,142 +0,0 @@
-# Docker (👍 Recommended)
-
-## 0. Prerequisites
-
-⚡⚡ Please make sure you have installed [Docker](https://docs.docker.com/get-docker/)
-
-## 1. Download NocoBase
-
-Download with Git (or Download Zip，and extract it to the nocobase directory)
-
-```bash
-git clone https://github.com/nocobase/nocobase.git nocobase
-```
-
-## 2. Select database (choose one)
-
-Change the directory to the folder downloaded in the first step.
-
-```bash
-# MacOS, Linux...
-cd /your/path/nocobase
-# Windows
-cd C:\your\path\nocobase
-```
-
-The docker configuration of different databases is slightly different, please choose to switch to the corresponding directory.
-
-### SQLite
-
-```bash
-cd docker/app-sqlite
-```
-
-### MySQL
-
-```bash
-cd docker/app-mysql
-```
-
-### PostgreSQL
-
-```bash
-cd docker/app-postgres
-```
-
-## 3. Configure docker-compose.yml (optional)
-
-
-
-## 为什么需要 Collection 模板？
-
-待补充
-
-## 配置参数说明
-
-```ts
-interface ICollectionTemplate {
- name: string;
- title?: string;
- /** 排序 */
- order?: number;
- /** 默认配置 */
- default?: CollectionOptions;
- /** UI 可配置的 CollectionOptions 参数（添加或编辑的 Collection 表单的字段） */
- configurableProperties?: Record
-
-## Excel Formula
-
-基于 [Formula.js](https://formulajs.info/) 实现，详细用法参考 [Formula.js functions](https://formulajs.info/functions/)。
-
-```ts
-SUM(-5, 15, 32) // 42
-IF(true, 'Hello!', 'Goodbye!') // Hello!
-```
-
-
diff --git a/docs/en-US/welcome/release/formulas/excel-form.jpg b/docs/en-US/welcome/release/formulas/excel-form.jpg
deleted file mode 100644
index 41413a0c4..000000000
Binary files a/docs/en-US/welcome/release/formulas/excel-form.jpg and /dev/null differ
diff --git a/docs/en-US/welcome/release/formulas/math-form.jpg b/docs/en-US/welcome/release/formulas/math-form.jpg
deleted file mode 100644
index ecf54c476..000000000
Binary files a/docs/en-US/welcome/release/formulas/math-form.jpg and /dev/null differ
diff --git a/docs/en-US/welcome/release/gantt/introduction.md b/docs/en-US/welcome/release/gantt/introduction.md
deleted file mode 100644
index 484eff651..000000000
--- a/docs/en-US/welcome/release/gantt/introduction.md
+++ /dev/null
@@ -1,21 +0,0 @@
-# Gantt block
-
-## Create gantt block
-
-
-
-## Gantt block (No data)
-
-
-
-## Block settings
-
-
-
-## General tasks
-
-
-
-## Tree tasks
-
-
diff --git a/docs/en-US/welcome/release/gantt/static/IwJzb9PsFovXwZxNqJnc6HaFnyg.png b/docs/en-US/welcome/release/gantt/static/IwJzb9PsFovXwZxNqJnc6HaFnyg.png
deleted file mode 100644
index a8893aa82..000000000
Binary files a/docs/en-US/welcome/release/gantt/static/IwJzb9PsFovXwZxNqJnc6HaFnyg.png and /dev/null differ
diff --git a/docs/en-US/welcome/release/gantt/static/UxT7b8mVCo1isIxrsjtcZ8hpnlf.png b/docs/en-US/welcome/release/gantt/static/UxT7b8mVCo1isIxrsjtcZ8hpnlf.png
deleted file mode 100644
index 2d309ad42..000000000
Binary files a/docs/en-US/welcome/release/gantt/static/UxT7b8mVCo1isIxrsjtcZ8hpnlf.png and /dev/null differ
diff --git a/docs/en-US/welcome/release/gantt/static/V9w1b43YsoIRYpxtFdscpf2MnQf.png b/docs/en-US/welcome/release/gantt/static/V9w1b43YsoIRYpxtFdscpf2MnQf.png
deleted file mode 100644
index c454d0c43..000000000
Binary files a/docs/en-US/welcome/release/gantt/static/V9w1b43YsoIRYpxtFdscpf2MnQf.png and /dev/null differ
diff --git a/docs/en-US/welcome/release/gantt/static/VGTZbOs38obgyqxm5YfcGS1Vnhb.png b/docs/en-US/welcome/release/gantt/static/VGTZbOs38obgyqxm5YfcGS1Vnhb.png
deleted file mode 100644
index 4e93257fd..000000000
Binary files a/docs/en-US/welcome/release/gantt/static/VGTZbOs38obgyqxm5YfcGS1Vnhb.png and /dev/null differ
diff --git a/docs/en-US/welcome/release/gantt/static/VM3qbBhLeoEcKwxwAZkcRHBynOd.png b/docs/en-US/welcome/release/gantt/static/VM3qbBhLeoEcKwxwAZkcRHBynOd.png
deleted file mode 100644
index 901010eff..000000000
Binary files a/docs/en-US/welcome/release/gantt/static/VM3qbBhLeoEcKwxwAZkcRHBynOd.png and /dev/null differ
diff --git a/docs/en-US/welcome/release/gantt/static/YJZZb0aO3oG9n6x4aZwcAB07nng.png b/docs/en-US/welcome/release/gantt/static/YJZZb0aO3oG9n6x4aZwcAB07nng.png
deleted file mode 100644
index a603d847c..000000000
Binary files a/docs/en-US/welcome/release/gantt/static/YJZZb0aO3oG9n6x4aZwcAB07nng.png and /dev/null differ
diff --git a/docs/en-US/welcome/release/index.md b/docs/en-US/welcome/release/index.md
deleted file mode 100644
index 0b9215d36..000000000
--- a/docs/en-US/welcome/release/index.md
+++ /dev/null
@@ -1,3 +0,0 @@
-# Changelog
-
-Visit: https://github.com/nocobase/nocobase/blob/main/CHANGELOG.md
\ No newline at end of file
diff --git a/docs/en-US/welcome/release/inherits.md b/docs/en-US/welcome/release/inherits.md
deleted file mode 100644
index aee2c72e7..000000000
--- a/docs/en-US/welcome/release/inherits.md
+++ /dev/null
@@ -1,74 +0,0 @@
-# v0.9.0: 数据表继承
-
-数据表继承基于 [PostgreSQL 的 INHERITS 语法](https://www.postgresql.org/docs/current/tutorial-inheritance.html) 实现，仅限于 PostgreSQL 数据库安装的 NocoBase 时才会提供。
-
-## 示例
-
-我们从一个例子开始，假设要做一个教学系统，有三类用户：学生、家长和老师。
-
-如果没有继承，要分别为三类用户建表：
-
-- 学生：姓名、年龄、性别、身份证
-- 家长：姓名、年龄、性别、职业、学历
-- 老师：姓名、年龄、性别、教龄、已婚
-
-有了数据表继承之后，共同的信息就可以提炼出来：
-
-- 用户：姓名、年龄、性别
-- 学生：身份证
-- 家长：职业、学历
-- 老师：教龄、已婚
-
-ER 图如下：
-
-
-
-注：子表 ID 和父表 ID 共享序列
-
-## 配置数据表继承
-
-Inherits 字段选择需要继承的数据表
-
-
-
-通过代码配置如下：
-
-```ts
-db.collection({
- name: 'users',
-});
-
-db.collection({
- name: 'students',
- inherits: 'users',
-});
-```
-
-注意：
-
-- 继承的表并不能随意选择，主键必须是唯一序列，比如 uuid 或者所有继承线路上的表的 id 自增序列都用同一个
-- Inherits 参数不能被编辑
-- 如果有继承关系，被继承的父表不能被删除
-
-## 数据表字段列表
-
-字段列表里同步显示继承的父表字段，父表字段不可以修改，但可以重写（Override）
-
-
-
-重写父表字段的注意事项：
-- 子表字段标识与父表字段一样时为重写
-- 重写字段的类型必须保持一致
-- 关系字段除了 target collection 以外的其他参数需要保持一致
-
-## 父表的子表区块
-
-在父表区块里可以配置子表的区块
-
-
-
-## 新增继承的父表字段的配置
-
-当有继承的父表时，配置字段时，会提供从父表继承的字段的配置
-
-
diff --git a/docs/en-US/welcome/release/inherits/configure-fields.jpg b/docs/en-US/welcome/release/inherits/configure-fields.jpg
deleted file mode 100644
index adf256da3..000000000
Binary files a/docs/en-US/welcome/release/inherits/configure-fields.jpg and /dev/null differ
diff --git a/docs/en-US/welcome/release/inherits/er.svg b/docs/en-US/welcome/release/inherits/er.svg
deleted file mode 100644
index f1ba5c251..000000000
--- a/docs/en-US/welcome/release/inherits/er.svg
+++ /dev/null
@@ -1,4 +0,0 @@
-
-
-
-
\ No newline at end of file
diff --git a/docs/en-US/welcome/release/inherits/form.jpg b/docs/en-US/welcome/release/inherits/form.jpg
deleted file mode 100644
index 2de047cd5..000000000
Binary files a/docs/en-US/welcome/release/inherits/form.jpg and /dev/null differ
diff --git a/docs/en-US/welcome/release/inherits/inherit-fields.jpg b/docs/en-US/welcome/release/inherits/inherit-fields.jpg
deleted file mode 100644
index acdaddda9..000000000
Binary files a/docs/en-US/welcome/release/inherits/inherit-fields.jpg and /dev/null differ
diff --git a/docs/en-US/welcome/release/inherits/inherit.jpg b/docs/en-US/welcome/release/inherits/inherit.jpg
deleted file mode 100644
index ecc419daa..000000000
Binary files a/docs/en-US/welcome/release/inherits/inherit.jpg and /dev/null differ
diff --git a/docs/en-US/welcome/release/inherits/inherited-blocks.jpg b/docs/en-US/welcome/release/inherits/inherited-blocks.jpg
deleted file mode 100644
index e95928c20..000000000
Binary files a/docs/en-US/welcome/release/inherits/inherited-blocks.jpg and /dev/null differ
diff --git a/docs/en-US/welcome/release/logger.md b/docs/en-US/welcome/release/logger.md
deleted file mode 100644
index 34214734f..000000000
--- a/docs/en-US/welcome/release/logger.md
+++ /dev/null
@@ -1,67 +0,0 @@
-# v0.9.0：NocoBase 的 Logging 系统
-
-## `@nocobase/logger`
-
-基于 Winston 实现，提供了便捷的创建 logger 实例的方法。
-
-```ts
-const logger = createLogger();
-logger.info('Hello distributed log files!');
-
-const { instance, middleware } = createAppLogger(); // 用于 @nocobase/server
-app.logger = instance;
-app.use(middleware);
-```
-
-## 新增的环境变量
-
-logger 相关环境变量有：
-
-- [LOGGER_TRANSPORT](/api/env#logger_transport)
-- [LOGGER_BASE_PATH](/api/env#logger_base_path)
-
-## Application 的 logger 配置
-
-```ts
-const app = new Application({
- logger: {
- async skip(ctx) {
- return false;
- },
- requestWhitelist: [],
- responseWhitelist: [],
- transports: ['console', 'dailyRotateFile'],
- },
-})
-```
-
-更多配置项参考 [Winston 文档](https://github.com/winstonjs/winston#table-of-contents)
-
-## app.logger & ctx.logger
-
-ctx.logger 带有 reqId，整个 ctx 周期里都是一个 reqId
-
-```ts
-ctx.logger = app.logger.child({ reqId: ctx.reqId });
-```
-
-`app.logger` 和 `ctx.logger` 都是 Winston 实例，详细用法参考 [Winston 文档](https://github.com/winstonjs/winston#table-of-contents)
-
-
-## 自定义 Transports
-
-除了 Winston 的方式以外，NocoBase 还提供了一种更便捷的方式
-
-```ts
-import { Transports } from '@nocobase/logger';
-
-Transports['custom'] = () => {
- return new winston.transports.Console();
-};
-
-const app = new Application({
- logger: {
- transports: ['custom'],
- },
-})
-```
diff --git a/docs/en-US/welcome/release/tree-collection.md b/docs/en-US/welcome/release/tree-collection.md
deleted file mode 100644
index 5b17858f7..000000000
--- a/docs/en-US/welcome/release/tree-collection.md
+++ /dev/null
@@ -1,45 +0,0 @@
-# Tree collection
-
-## Collection options
-
-```ts
-{
- name: 'categories',
- tree: 'adjacency-list',
- fields: [
- {
- type: 'belongsTo',
- name: 'parent',
- treeParent: true,
- },
- {
- type: 'hasMany',
- name: 'children',
- treeChildren: true,
- },
- ],
-}
-```
-
-## UI
-
-### Create tree collection
-
-
-
-
-### Default fields
-
-
-
-### Table block
-
-
-
-### Add child
-
-
-
-### Expend/Collapse
-
-
diff --git a/docs/en-US/welcome/release/tree-collection/add-child.jpg b/docs/en-US/welcome/release/tree-collection/add-child.jpg
deleted file mode 100644
index 0c1285d5d..000000000
Binary files a/docs/en-US/welcome/release/tree-collection/add-child.jpg and /dev/null differ
diff --git a/docs/en-US/welcome/release/tree-collection/expend-collapse.jpg b/docs/en-US/welcome/release/tree-collection/expend-collapse.jpg
deleted file mode 100644
index de703b86b..000000000
Binary files a/docs/en-US/welcome/release/tree-collection/expend-collapse.jpg and /dev/null differ
diff --git a/docs/en-US/welcome/release/tree-collection/init.jpg b/docs/en-US/welcome/release/tree-collection/init.jpg
deleted file mode 100644
index 86b4d5b42..000000000
Binary files a/docs/en-US/welcome/release/tree-collection/init.jpg and /dev/null differ
diff --git a/docs/en-US/welcome/release/tree-collection/tree-collection.jpg b/docs/en-US/welcome/release/tree-collection/tree-collection.jpg
deleted file mode 100644
index 1733aca53..000000000
Binary files a/docs/en-US/welcome/release/tree-collection/tree-collection.jpg and /dev/null differ
diff --git a/docs/en-US/welcome/release/tree-collection/tree-table.jpg b/docs/en-US/welcome/release/tree-collection/tree-table.jpg
deleted file mode 100644
index 4eeb1e6f2..000000000
Binary files a/docs/en-US/welcome/release/tree-collection/tree-table.jpg and /dev/null differ
diff --git a/docs/en-US/welcome/release/v08-1-collection-templates/v08-1-collection-templates.jpg b/docs/en-US/welcome/release/v08-1-collection-templates/v08-1-collection-templates.jpg
deleted file mode 100644
index dd0a99af8..000000000
Binary files a/docs/en-US/welcome/release/v08-1-collection-templates/v08-1-collection-templates.jpg and /dev/null differ
diff --git a/docs/en-US/welcome/release/v08-changelog.md b/docs/en-US/welcome/release/v08-changelog.md
deleted file mode 100644
index 1d302a59a..000000000
--- a/docs/en-US/welcome/release/v08-changelog.md
+++ /dev/null
@@ -1,222 +0,0 @@
-# v0.8：Plugin manager & docs
-
-Starting with v0.8, NocoBase begins to provide an available plugin manager and development documentation. Here are the main changes in v0.8.
-
-## Tweaks to the top right corner of the interface
-
-- UI Editor
-- Plugin Manager
-- Plugin Settings Manager
-- Personal Center
-
-
-
-## The new plugin manager
-
-v0.8 provides a powerful plugin manager for managing plugins in a no-code way.
-
-### Plugin manager flow
-
-
-
-### Plugin Manager interface
-
-Currently it is mainly used for disabling, activating and deleting local plugins. Built-in plugins cannot be deleted.
-
-
-
-### Plugin Manager command
-
-In addition to being able to activate and disable plugins from the no-code interface, you can also manage plugins more completely from the command line.
-
-```
-# Create a plugin
-yarn pm create hello
-# Register the plugin
-yarn pm add hello
-# Activate the plugin
-yarn pm enable hello
-# Disable the plugin
-yarn pm disable hello
-# Remove the plugin
-yarn pm remove hello
-
-```
-
-Note: Releases and upgrades for plugins will be supported in subsequent releases.
-
-```
-# Publish the plugin
-yarn pm publish hello
-# Publish the plugin
-yarn pm upgrade hello
-
-```
-
-For more plugin examples, see [packages/samples](https://github.com/nocobase/nocobase/tree/main/packages/samples).
-
-## Changes of plugin
-
-### Plugin’s directory structure
-
-```
-|- /hello
- |- /src
- |- /client # Plugin client
- |- /server # Plugin server
- |- client.d.ts
- |- client.js
- |- package.json # Plugin package information
- |- server.d.ts
- |- server.js
-
-```
-
-### Plugin’s name specification
-
-NocoBase plugin is also an NPM package, the correspondence rule between plugin name and NPM package name is `${PLUGIN_PACKAGE_PREFIX}-${pluginName}`.
-
-`PLUGIN_PACKAGE_PREFIX` is the plugin package prefix, which can be customized in .env, [click here for PLUGIN_PACKAGE_PREFIX description](https://www.notion.so/api/env#plugin_package_prefix).
-
-For example, a project named `my-nocobase-app` adds the `hello` plugin with package name `@my-nocobase-app/plugin-hello`.
-
-`PLUGIN_PACKAGE_PREFIX` is configured as follows.
-
-```
-PLUGIN_PACKAGE_PREFIX=@nocobase/plugin-,@nocobase/preset-,@my-nocobase-app/plugin-
-
-```
-
-The correspondence between plugin names and package names is
-
-- `users` plugin package name is `@nocobase/plugin-users`
-- `nocobase` plugin package name is `@nocobase/preset-nocobase`
-- `hello` plugin package named `@my-nocobase-app/plugin-hello`
-
-### Plugin’s lifecycle
-
-v0.8 provides a more complete approach to the plugin lifecycle.
-
-```
-import { InstallOptions, Plugin } from '@nocobase/server';
-
-export class HelloPlugin extends Plugin {
- afterAdd() {
- // After the plugin has been added via pm.add
- }
-
- beforeLoad() {
- // Before all plugins are loaded, generally used to register classes and event listeners
- }
-
- async load() {
- // Load configuration
- }
-
- async install(options?: InstallOptions) {
- // Install logic
- }
-
- async afterEnable() {
- // After activation
- }
-
- async afterDisable() {
- // After disable
- }
-
- async remove() {
- // Remove logic
- }
-}
-
-export default HelloPlugin;
-
-```
-
-### Front- and back-end entrance for plugins
-
-The lifecycle of the plugin is controlled by the server
-
-```
-import { Application } from '@nocobase/server';
-
-const app = new Application({
- // ...
-});
-
-class MyPlugin extends Plugin {
- afterAdd() {}
- beforeLoad() {}
- load() {}
- install() {}
- afterEnable() {}
- afterDisable() {}
- remove() {}
-}
-
-app.plugin(MyPlugin, { name: 'my-plugin' });
-
-```
-
-The client side of the plugin exists as Context.Provider (similar to Middleware on the server side)
-
-```
-import React from 'react';
-import { Application } from '@nocobase/client';
-
-const app = new Application({
- apiClient: {
- baseURL: process.env.API_BASE_URL,
- },
- dynamicImport: (name: string) => {
- return import(`../plugins/${name}`);
- },
-});
-
-// When you visit the /hello page, it displays Hello world!
-const HelloProvider = React.memo((props) => {
- const location = useLocation();
- if (location.pathname === '/hello') {
- return Hello world!
- }
- return <>{props.children}
-});
-HelloProvider.displayName = 'HelloProvider'
-
-app.use(HelloProvider);
-
-```
-
-## Custom business code
-
-v0.7 plugins are not complete, custom business code may be scattered in `packages/app/client` and `packages/app/server`, which is not conducive to upgrade and maintenance. v0.8 recommends organizing as a plugin package and using `yarn pm` to manage plugins.
-
-## More complete documentation is provided
-
-- **Welcome**: a quick look at NocoBase
-- **Manual**: learn more about the core features provided by the NocoBase platform
-- **Plugin Development Tutorial**: Advanced dive into plugin development
-- **API Reference**: Check the API usage during plugin development
-- **Client Components Library** (in preparation): provides examples and usage of NocoBase components
-
-## More plugin examples are provided
-
-- [command](https://github.com/nocobase/nocobase/tree/develop/packages/samples/command)
-- [custom-block](https://github.com/nocobase/nocobase/tree/develop/packages/samples/custom-block)
-- [custom-page](https://github.com/nocobase/nocobase/tree/develop/packages/samples/custom-page)
-- [custom-signup-page](https://github.com/nocobase/nocobase/tree/develop/packages/samples/custom-signup-page)
-- [hello](https://github.com/nocobase/nocobase/tree/develop/packages/samples/hello)
-- [ratelimit](https://github.com/nocobase/nocobase/tree/develop/packages/samples/ratelimit)
-- [shop-actions](https://github.com/nocobase/nocobase/tree/develop/packages/samples/shop-actions)
-- [shop-events](https://github.com/nocobase/nocobase/tree/develop/packages/samples/shop-events)
-- [shop-i18n](https://github.com/nocobase/nocobase/tree/develop/packages/samples/shop-i18n)
-- [shop-modeling](https://github.com/nocobase/nocobase/tree/develop/packages/samples/shop-modeling)
-
-## Other new features and functionality
-
-- Import from Excel
-- Bulk Update & Edit
-- Graphical collection
-- Workflow support for viewing execution history
-- JSON field
diff --git a/docs/en-US/welcome/release/v08-changelog/pm-flow.svg b/docs/en-US/welcome/release/v08-changelog/pm-flow.svg
deleted file mode 100644
index d15cf800c..000000000
--- a/docs/en-US/welcome/release/v08-changelog/pm-flow.svg
+++ /dev/null
@@ -1 +0,0 @@
-
\ No newline at end of file
diff --git a/docs/en-US/welcome/release/v08-changelog/pm-ui.jpg b/docs/en-US/welcome/release/v08-changelog/pm-ui.jpg
deleted file mode 100644
index 4c8fdd3c1..000000000
Binary files a/docs/en-US/welcome/release/v08-changelog/pm-ui.jpg and /dev/null differ
diff --git a/docs/en-US/welcome/release/v08-changelog/topright.jpg b/docs/en-US/welcome/release/v08-changelog/topright.jpg
deleted file mode 100644
index 8ce510973..000000000
Binary files a/docs/en-US/welcome/release/v08-changelog/topright.jpg and /dev/null differ
diff --git a/docs/en-US/welcome/release/v10-changelog.md b/docs/en-US/welcome/release/v10-changelog.md
deleted file mode 100644
index c05f3f1da..000000000
--- a/docs/en-US/welcome/release/v10-changelog.md
+++ /dev/null
@@ -1,233 +0,0 @@
-# v0.10: Update instructions
-
-## New features in the second quarter
-
-- Association field component improvements, support for multiple component switching
- - Select
- - Record picker
- - Sub-form/Sub-details
- - Sub-table
- - File manager
- - Title(read only)
-- Quick creation of relational data, supports two quick creation modes
- - Add in drop-down menu to quickly create a new record based on the title field
- - Add in pop-up window to configure complex add forms
-- Duplicate action, supports two modes
- - Direct duplicate
- - Copy into the form and continue to fill in
-- Form data templates
-- Filter data scope support variables
-- List block
-- Grid card block
-- Mobile client plugin
-- User authentication plugin, support for different authentication methods
- - Email/Password
- - SMS
- - OIDC
- - SAML
-- Workflow nodes
- - Manual node upgrade, support for adding and editing from existing collections
- - Loop node
- - Aggregate node
-- File manager
- - Provide file collection template
- - Provide file manager component
-
-## Upgrading applications
-
-### Upgrading for Docker compose
-
-No change, upgrade reference [Upgrading for Docker compose](/welcome/getting-started/upgrading/docker-compose)
-
-### Upgrading for Git source code
-
-v0.10 has a major upgrade of dependencies, so to prevent errors when upgrading the source code, you need to delete the following directories before upgrading
-
-```bash
-# Remove .umi cache
-yarn rimraf -rf "./**/{.umi,.umi-production}"
-# Delete compiled files
-yarn rimraf -rf "./packages/*/*/{lib,esm,es,dist,node_modules}"
-# Remove dependencies
-yarn rimraf -rf node_modules
-```
-
-See [Upgrading for Git source code](/welcome/getting-started/upgrading/git-clone) for more details
-
-### Upgrading for create-nocobase-app
-
-It is recommended that `yarn create` re-download the new version and modify the `.env` configuration, for more details refer to [major version upgrade guide](/welcome/getting-started/upgrading/create-nocobase-app#major-upgrade)
-
-## Upcoming deprecated and potentially incompatible changes
-
-### Sub-table field component
-
-Not compatible with new version, block fields need to be removed and reassigned (UI reassignment only)
-
-### Attachment upload api changes
-
-In addition to the built-in attachments table, users can also custom file collection, the upload api for attachments has been changed from `/api/attachments:upload` to `/api/
-- { props.children }
-+
- );
-}
-```
-
-if you use `React.cloneElement` to render the route component, you need to change it like this:
-
-```diff
-import React from 'react';
-+ import { Outlet } from 'react-router-dom';
-
-export default function RouteComponent(props) {
- return (
-
-- { React.cloneElement(props.children, { someProp: 'p1' }) }
-+
- );
-}
-```
-
-Change the route component to get the value from `useOutletContext`
-
-```diff
-import React from 'react';
-+ import { useOutletContext } from 'react-router-dom';
-
-- export function Comp(props){
-+ export function Comp() {
-+ const props = useOutletContext();
- return props.someProp;
-}
-```
-
-### Redirect
-
-`
- {props.children}
-
;
-}
-
-export default HelloProvider
-```
-
-now you need to change to the plugin way, for example:
-
-```diff | pure
-+import { Plugin } from '@nocobase/client'
-
-const HelloProvider = (props) => {
- // do something logic
- return
- {props.children}
-
;
-}
-
-+ export class HelloPlugin extends Plugin {
-+ async load() {
-+ this.app.addProvider(HelloProvider);
-+ }
-+ }
-
-- export default HelloProvider;
-+ export default HelloPlugin;
-```
-
-plugins are very powerful and can do a lot of things in the `load` phase:
-
-- modify routes
-- add Components
-- add Providers
-- add Scopes
-- load other plugins
-
-#### Routing changes
-
-if you used `RouteSwitchContext` to modify the route before, you now need to replace it with a plugin:
-
-```tsx | pure
-import { RouteSwitchContext } from '@nocobase/client';
-
-const HelloProvider = () => {
- const { routes, ...others } = useContext(RouteSwitchContext);
- routes[1].routes.unshift({
- path: '/hello',
- component: Hello,
- });
-
- return
-
- {props.children}
-
-
-}
-```
-
-now you need to change to the plugin way, for example:
-
-```diff | pure
-- import { RouteSwitchContext } from '@nocobase/client';
-+ import { Plugin } from '@nocobase/client';
-
-const HelloProvider = (props) => {
-- const { routes, ...others } = useContext(RouteSwitchContext);
-- routes[1].routes.unshift({
-- path: '/hello',
-- component: Hello,
-- });
-
- return
--
- {props.children}
--
-
-}
-
-+ export class HelloPlugin extends Plugin {
-+ async load() {
-+ this.app.router.add('admin.hello', {
-+ path: '/hello',
-+ Component: Hello,
-+ });
-+ this.app.addProvider(HelloProvider);
-+ }
-+ }
-+ export default HelloPlugin;
-```
-
-more details can be found in [packages/core/client/src/application/index.md](https://github.com/nocobase/nocobase/blob/main/packages/core/client/src/application/index.md)
-
-### antd upgrade to v5
-
-- antd related details view the official website [V4 to V5](https://ant.design/docs/react/migration-v5)
-- `@formily/antd` replace with `@formily/antd-v5`
diff --git a/docs/en-US/welcome/release/v12-changelog.md b/docs/en-US/welcome/release/v12-changelog.md
deleted file mode 100644
index 3cf30b1d0..000000000
--- a/docs/en-US/welcome/release/v12-changelog.md
+++ /dev/null
@@ -1,181 +0,0 @@
-# v0.12: New plugin build tool
-
-## New Features
-
-- New plugin build tool. The built plugins will be able to be used directly on the production environment without the need for a second build.
-
-## Application upgrades
-
-### Upgrade of Docker installation
-
-No change, refer to [Docker Image Upgrade Guide](/welcome/getting-started/upgrading/docker-compose) for upgrade.
-
-### Upgrading source code installation
-
-The plugin build tool has been freshly upgraded, and the cache needs to be cleared after pulling new sources.
-
-```bash
-git pull # Pull the new source code.
-yarn clean # Clear the cache.
-```
-
-For more details, see [Git source upgrade guide](/welcome/getting-started/upgrading/git-clone).
-
-### Upgrading a create-nocobase-app installation
-
-Redownload the new version via `yarn create` and update the .env configuration, see [major version upgrade guide](/welcome/getting-started/upgrading/create-nocobase-app#Major version upgrade) for more details.
-
-## Incompatible changes
-
-### @nocobase/app-client and @nocobase/app-server merged into @nocobase-app
-
-Apps installed via create-nocobase-app no longer have a packages/app directory, and custom code in packages/app needs to be moved to the custom plugin.
-
-### The dist/client path of the app has changed.
-
-If you are configuring nginx yourself, you will need to make a similar adjustment
-
-```diff
-server {
-- root /app/nocobase/packages/app/client/dist;
-+ root /app/nocobase/node_modules/@nocobase/app/dist/client;
-
- location / {
-- root /app/nocobase/packages/app/client/dist;
-+ root /app/nocobase/node_modules/@nocobase/app/dist/client;
- try_files $uri $uri/ /index.html;
- add_header Last-Modified $date_gmt;
- add_header Cache-Control 'no-store, no-cache';
- if_modified_since off;
- expires off;
- etag off;
- }
-}
-```
-
-### Third party plugins need to be rebuilt
-
-Refer to the third-party plugin upgrade guide below
-
-## Third-party plugin upgrade guide
-
-### The plugin directory must have both `src/client` and `src/server` directories.
-
-```js
-// src/client/index.ts
-import { Plugin } from '@nocobase/client';
-
-class MyPlugin extends Plugin {
- async load() {
- // ...
- }
-}
-
-export default MyPlugin;
-```
-
-```js
-// src/server/index.ts
-import { Plugin } from '@nocobase/server';
-
-class MyPlugin extends Plugin {
- async load() {
- // ...
- }
-}
-
-export default MyPlugin;
-```
-
-Specific demo code can be referred to: [sample-hello](https://github.com/nocobase/nocobase/tree/main/packages/samples/hello)
-
-### Plugin's multilingual placement `src/locale` directory
-
-Both frontend and backend, multi-language translation files are placed in the `src/locale` directory, so the plugin doesn't need to load multi-language packages by itself.
-
-### Adjustment of plugin dependencies
-
-The dependencies of the plugin are divided into its own dependencies and global dependencies. Global dependencies are directly used globally and will not be packaged into the plugin product, while its own dependencies will be packaged into the product. After the plug-in is built, the production environment is plug-and-play, and there is no need to install dependencies or build twice. Adjustments to plugin dependencies include:
-
-- Put `@nocobase/*` related packages into `peerDependencies` and specify the version number as `0.x`;
-- Place other dependencies in `devDependencies`, not `dependencies`, as the plugin will extract all the dependencies required by the production environment after packaging.
-
-
-```diff
-{
- "devDependencies": {
- "@formily/react": "2.x",
- "@formily/shared": "2.x",
- "ahooks": "3.x",
- "antd": "5.x",
- "dayjs": "1.x",
- "i18next": "22.x",
- "react": "18.x",
- "react-dom": "18.x",
- "react-i18next": "11.x"
- },
- "peerDependencies": {
- "@nocobase/actions": "0.x",
- "@nocobase/client": "0.x",
- "@nocobase/database": "0.x",
- "@nocobase/resourcer": "0.x",
- "@nocobase/server": "0.x",
- "@nocobase/test": "0.x",
- "@nocobase/utils": "0.x"
- }
-}
-```
-
-### The output path of the plugin has been changed from `lib` to `dist`
-
-dist directory structure
-
-```bash
-|- dist
- |- client # Client-side, umd
- |- index.js
- |- index.d.ts
- |- server # Server-side, cjs
- |- index.js
- |- index.d.ts
- |- others
- |- locale # multilingual package
- |- node_modules # server dependencies
-```
-
-Other related adjustments include:
-
-Adjustment of the main parameter of package.json
-
-```diff
-{
- - "main": "./lib/server/index.js",
- + "main": "./dist/server/index.js",
-}
-```
-
-client.d.ts
-
-```ts
-export * from './dist/client';
-export { default } from './dist/client';
-```
-
-client.js
-
-```js
-module.exports = require('./dist/client/index.js');
-```
-
-server.d.ts
-
-```ts
-export * from './dist/server';
-export { default } from './dist/server';
-```
-
-server.js
-
-```js
-module.exports = require('./dist/server/index.js');
-```
diff --git a/docs/en-US/welcome/release/v13-changelog.md b/docs/en-US/welcome/release/v13-changelog.md
deleted file mode 100644
index 166f7e5e4..000000000
--- a/docs/en-US/welcome/release/v13-changelog.md
+++ /dev/null
@@ -1,19 +0,0 @@
-# v0.13: New application status flow
-
-## New Features
-
-### Application status flow
-
-
-
-### Demo video
-
-
-
-## Upgrading
-
-- [Upgrading for Docker compose](/welcome/getting-started/upgrading/docker-compose)
-- [Upgrading for create-nocobase-app](/welcome/getting-started/upgrading/create-nocobase-app)
-- [Upgrading for Git source code](/welcome/getting-started/upgrading/git-clone)
diff --git a/docs/en-US/welcome/release/v14-changelog.md b/docs/en-US/welcome/release/v14-changelog.md
deleted file mode 100644
index a81dcac9c..000000000
--- a/docs/en-US/welcome/release/v14-changelog.md
+++ /dev/null
@@ -1,82 +0,0 @@
-# v0.14: New plugin manager, supports adding plugins through UI
-
-This release enables plug-and-play plugins in production environments. You can now add plugins directly through the UI, and support downloading from the npm registry (which can be private), local uploads, and URL downloads.
-
-## New features
-
-### New plugin manager interface
-
-
-
-### Uploaded plugins are located in the storage/plugins directory.
-
-The storage/plugins directory is used to upload plugins, and is organized as npm packages.
-
-```bash
-|- /storage/
- |- /plugins/
- |- /@nocobase/
- |- /plugin-hello1/
- |- /plugin-hello2/
- |- /@foo/
- |- /bar/
- |- /my-nocobase-plugin-hello/
-```
-
-### Plugin updates
-
-Currently, only plugins under storage/plugins can be updated, as shown here:
-
-
-
-Note: In order to facilitate maintenance and upgrading, and to avoid unavailability of the storage plugins due to upgrading, you can put the new plugin directly into storage/plugins and then perform the upgrade operation.
-
-## Incompatible changes
-
-### Changes to plugin names
-
-- PLUGIN_PACKAGE_PREFIX environment variable is no longer provided.
-- Plugin names and package names are unified, old plugin names can still exist as aliases.
-
-### Improvements to pm.add
-
-```bash
-# Use packageName instead of pluginName, lookup locally, error if not found
-pm add packageName
-
-# Download from remote only if registry is provided, can also specify version
-pm add packageName --registry=xx --auth-token=yy --version=zz
-
-# You can also provide a local zip, add multiple times and replace it with the last one
-pm add /a/plugin.zip
-
-# Remote zip, replace it with the same name
-pm add http://url/plugin.zip
-```
-
-### Nginx configuration changes
-
-Add `/static/plugins/` location
-
-```conf
-server {
- location ^~ /static/plugins/ {
- proxy_pass http://127.0.0.1:13000/static/plugins/;
- proxy_http_version 1.1;
- proxy_set_header Upgrade $http_upgrade;
- proxy_set_header Connection 'upgrade';
- proxy_set_header Host $host;
- proxy_cache_bypass $http_upgrade;
- proxy_connect_timeout 600;
- proxy_send_timeout 600;
- proxy_read_timeout 600;
- send_timeout 600;
- }
-}
-```
-
-More see full version of [nocobase.conf](https://github.com/nocobase/nocobase/blob/main/docker/nocobase/nocobase.conf)
-
-## Plugin development guide
-
-[Develop the first plugin](/development/your-fisrt-plugin)
diff --git a/docs/zh-CN/api/acl/acl-resource.md b/docs/zh-CN/api/acl/acl-resource.md
deleted file mode 100644
index 305b80bed..000000000
--- a/docs/zh-CN/api/acl/acl-resource.md
+++ /dev/null
@@ -1,57 +0,0 @@
-# ACLResource
-
-ACLResource，ACL 系统中的资源类。在 ACL 系统中，为用户授予权限时会自动创建对应的资源。
-
-
-## 类方法
-
-### `constructor()`
-构造函数
-
-**签名**
-* `constructor(options: AclResourceOptions)`
-
-**类型**
-```typescript
-type ResourceActions = { [key: string]: RoleActionParams };
-
-interface AclResourceOptions {
- name: string; // 资源名称
- role: ACLRole; // 资源所属角色
- actions?: ResourceActions;
-}
-```
-
-**详细信息**
-
-`RoleActionParams`详见 [`aclRole.grantAction`](./acl-role.md#grantaction)
-
-### `getActions()`
-
-获取资源的所有 Action，返回结果为 `ResourceActions` 对象。
-
-### `getAction()`
-根据名称返回 Action 的参数配置，返回结果为 `RoleActionParams` 对象。
-
-**详细信息**
-
-`RoleActionParams`详见 [`aclRole.grantAction`](./acl-role.md#grantaction)
-
-### `setAction()`
-
-在资源内部设置一个 Action 的参数配置，返回结果为 `RoleActionParams` 对象。
-
-**签名**
-* `setAction(name: string, params: RoleActionParams)`
-
-**详细信息**
-
-* name - 要设置的 action 名称
-* `RoleActionParams`详见 [`aclRole.grantAction`](./acl-role.md#grantaction)
-
-### `setActions()`
-
-**签名**
-* `setActions(actions: ResourceActions)`
-
-批量调用 `setAction` 的便捷方法
diff --git a/docs/zh-CN/api/acl/acl-role.md b/docs/zh-CN/api/acl/acl-role.md
deleted file mode 100644
index c6d8a1bbe..000000000
--- a/docs/zh-CN/api/acl/acl-role.md
+++ /dev/null
@@ -1,87 +0,0 @@
-# ACLRole
-
-ACLRole，ACL 系统中的用户角色类。在 ACL 系统中，通常使用 `acl.define` 定义角色。
-
-## 类方法
-
-### `constructor()`
-构造函数
-
-**签名**
-* `constructor(public acl: ACL, public name: string)`
-
-**详细信息**
-* acl - ACL 实例
-* name - 角色名称
-
-### `grantAction()`
-
-为角色授予 Action 权限
-
-**签名**
-* `grantAction(path: string, options?: RoleActionParams)`
-
-**类型**
-```typescript
-interface RoleActionParams {
- fields?: string[];
- filter?: any;
- own?: boolean;
- whitelist?: string[];
- blacklist?: string[];
- [key: string]: any;
-}
-```
-
-**详细信息**
-
-* path - 资源Action路径，如 `posts:edit`，表示 `posts` 资源的 `edit` Action, 资源名称和 Action 之间使用 `:` 冒号分隔。
-
-RoleActionParams 为授权时，对应 action 的可配置参数，用以实现更细粒度的权限控制。
-
-* fields - 可访问的字段
- ```typescript
- acl.define({
- role: 'admin',
- actions: {
- 'posts:view': {
- // admin 用户可以请求 posts:view action，但是只有 fields 配置的字段权限
- fields: ["id", "title", "content"],
- },
- },
- });
- ```
-* filter - 权限资源过滤配置
- ```typescript
- acl.define({
- role: 'admin',
- actions: {
- 'posts:view': {
- // admin 用户可以请求 posts:view action，但是列出的结果必须满足 filter 设置的条件。
- filter: {
- createdById: '{{ ctx.state.currentUser.id }}', // 支持模板语法，可以取 ctx 中的值，将在权限判断时替换
- },
- },
- },
- });
- ```
-* own - 是否只能访问自己的数据
- ```typescript
- const actionsWithOwn = {
- 'posts:view': {
- "own": true //
- }
- }
-
- // 等价于
- const actionsWithFilter = {
- 'posts:view': {
- "filter": {
- "createdById": "{{ ctx.state.currentUser.id }}"
- }
- }
- }
- ```
-* whitelist - 白名单，只有在白名单中的字段才能被访问
-* blacklist - 黑名单，黑名单中的字段不能被访问
-
diff --git a/docs/zh-CN/api/acl/acl.md b/docs/zh-CN/api/acl/acl.md
deleted file mode 100644
index 720c905f5..000000000
--- a/docs/zh-CN/api/acl/acl.md
+++ /dev/null
@@ -1,253 +0,0 @@
-# ACL
-
-## 概览
-
-ACL 为 Nocobase 中的权限控制模块。在 ACL 中注册角色、资源以及配置相应权限之后，即可对角色进行权限判断。
-
-### 基本使用
-
-```javascript
-const { ACL } = require('@nocobase/acl');
-
-const acl = new ACL();
-
-// 定义一个名称为 member 的角色
-const memberRole = acl.define({
- role: 'member',
-});
-
-// 使 member 角色拥有 posts 资源的 list 权限
-memberRole.grantAction('posts:list');
-
-acl.can('member', 'posts:list'); // true
-acl.can('member', 'posts:edit'); // null
-```
-
-### 概念解释
-
-* 角色 (`ACLRole`)：权限判断的对象
-* 资源 (`ACLResource`)：在 Nocobase ACL 中，资源通常对应一个数据库表，概念上可类比为 Restful API 中的 Resource。
-* Action：对资源的操作，如 `create`、`read`、`update`、`delete` 等。
-* 策略 (`ACLAvailableStrategy`): 通常每个角色都有自己的权限策略，策略中定义了默认情况下的用户权限。
-* 授权：在 `ACLRole` 实例中调用 `grantAction` 函数，为角色授予 `Action` 的访问权限。
-* 鉴权：在 `ACL` 实例中调用 `can` 函数，函数返回结果即为用户的鉴权结果。
-
-
-## 类方法
-
-### `constructor()`
-
-构造函数，创建一个 `ACL` 实例。
-
-```typescript
-import { ACL } from '@nocobase/database';
-
-const acl = new ACL();
-```
-
-### `define()`
-
-定义一个 ACL 角色
-
-**签名**
-* `define(options: DefineOptions): ACLRole`
-
-**类型**
-
-```typescript
-interface DefineOptions {
- role: string;
- allowConfigure?: boolean;
- strategy?: string | AvailableStrategyOptions;
- actions?: ResourceActionsOptions;
- routes?: any;
-}
-```
-
-**详细信息**
-
-* `role` - 角色名称
-
-```typescript
-// 定义一个名称为 admin 的角色
-acl.define({
- role: 'admin',
-});
-```
-
-* `allowConfigure` - 是否允许配置权限
-* `strategy` - 角色的权限策略
- * 可以为 `string`，为要使用的策略名，表示使用已定义的策略。
- * 可以为 `AvailableStrategyOptions`，为该角色定义一个新的策略，参考[`setAvailableActions()`](#setavailableactions)。
-* `actions` - 定义角色时，可传入角色可访问的 `actions` 对象，
- 之后会依次调用 `aclRole.grantAction` 授予资源权限。详见 [`aclRole.grantAction`](./acl-role.md#grantaction)
-
-```typescript
-acl.define({
- role: 'admin',
- actions: {
- 'posts:edit': {}
- },
-});
-// 等同于
-const role = acl.define({
- role: 'admin',
-});
-
-role.grantAction('posts:edit', {});
-```
-
-### `getRole()`
-
-根据角色名称返回已注册的角色对象
-
-**签名**
-* `getRole(name: string): ACLRole`
-
-### `removeRole()`
-
-根据角色名称移除角色
-
-**签名**
-* `removeRole(name: string)`
-
-### `can()`
-鉴权函数
-
-**签名**
-* `can(options: CanArgs): CanResult | null`
-
-**类型**
-
-```typescript
-interface CanArgs {
- role: string; // 角色名称
- resource: string; // 资源名称
- action: string; //操作名称
-}
-
-interface CanResult {
- role: string; // 角色名称
- resource: string; // 资源名称
- action: string; // 操作名称
- params?: any; // 注册权限时传入的参数
-}
-
-```
-
-**详细信息**
-
-`can` 方法首先会判断角色是否有注册对应的 `Action` 权限，如果没有则会去判断角色的 `strategy` 是否匹配。
-调用返回为`null`时，表示角色无权限，反之返回 `CanResult`对象，表示角色有权限。
-
-**示例**
-```typescript
-// 定义角色，注册权限
-acl.define({
- role: 'admin',
- actions: {
- 'posts:edit': {
- fields: ['title', 'content'],
- },
- },
-});
-
-const canResult = acl.can({
- role: 'admin',
- resource: 'posts',
- action: 'edit',
-});
-/**
- * canResult = {
- * role: 'admin',
- * resource: 'posts',
- * action: 'edit',
- * params: {
- * fields: ['title', 'content'],
- * }
- * }
- */
-
-acl.can({
- role: 'admin',
- resource: 'posts',
- action: 'destroy',
-}); // null
-```
-### `use()`
-
-**签名**
-* `use(fn: any)`
-向 middlewares 中添加中间件函数。
-
-### `middleware()`
-
-返回一个中间件函数，用于在 `@nocobase/server` 中使用。使用此 `middleware` 之后，`@nocobase/server` 在每次请求处理之前都会进行权限判断。
-
-### `allow()`
-
-设置资源为可公开访问
-
-**签名**
-* `allow(resourceName: string, actionNames: string[] | string, condition?: string | ConditionFunc)`
-
-**类型**
-```typescript
-type ConditionFunc = (ctx: any) => PromiseHello
-}
-
-// 第一个参数是名称, 第二个参数是 `RouteObject`
-app.router.add('root', {
- path: '/',
- element:
- Home
- about
-
-
-}
-
-const Home = () => {
- return Home
-}
-
-const About = () => {
- return About
-}
-
-app.router.add('root', {
- element: hello
,
- })
-
- // remove route
- this.app.router.remove('world');
- }
-}
-```
-
-## 示例
-
-```tsx
-/**
- * defaultShowCode: true
- */
-import React from 'react';
-import { Link, Outlet } from 'react-router-dom';
-import { Application } from '@nocobase/client';
-
-const Home = () => Home
; -const About = () =>About
; - -const Layout = () => { - return
-
-}
-
-const app = new Application({
- router: {
- type: 'memory',
- initialEntries: ['/']
- }
-})
-
-app.router.add('root', {
- element: Home, About
-