diff --git a/LANGS.md b/LANGS.md
new file mode 100644
index 0000000..6cc1b43
--- /dev/null
+++ b/LANGS.md
@@ -0,0 +1,4 @@
+# Languages
+
+* [English](en/)
+* [中国](ch/)
\ No newline at end of file
diff --git a/README.md b/README.md
index d2ab667..bce4d72 100644
--- a/README.md
+++ b/README.md
@@ -2,6 +2,8 @@
 description: 目前文档仍在陆续完善中！
 ---
 
+[English version](./en/README.md)
+
 # 欢迎
 
 ## Cloudreve 是什么？
diff --git a/ch/README.md b/ch/README.md
new file mode 100644
index 0000000..583156f
--- /dev/null
+++ b/ch/README.md
@@ -0,0 +1,31 @@
+---
+description: 目前文档仍在陆续完善中！
+---
+
+[English version](../en/README.md)
+
+# 欢迎
+
+## Cloudreve 是什么？
+
+Cloudreve 可以让您快速搭建起公私兼备的网盘系统。Cloudreve 在底层支持不同的云存储平台，用户在实际使用时无须关心物理存储方式。你可以使用 Cloudreve 搭建个人用网盘、文件分享系统，亦或是针对大小团体的公有云系统。
+
+## 问题反馈
+
+如果在使用过程中发现了什么缺陷，或是有新的需求提议，请先检查一下以前的文档、[issue](https://github.com/cloudreve/Cloudreve/issues) 、[讨论社区](https://forum.cloudreve.org/)是否提过。
+
+如果疑似 Bug 或是功能提议，请创建一个 [issue](https://github.com/cloudreve/Cloudreve/issues) 用于追踪问题；
+
+如果是日常使用上的疑问，请到 [讨论社区](https://forum.cloudreve.org/) 创建新的话题，并详细描述你遇到的问题。
+
+## 联系
+
+你可以加入以下群组与其他正在使用 Cloudreve 的用户交流：
+
+* [Telegram 群组](https://t.me/cloudreve_official)
+* [QQ 群组](https://jq.qq.com/?_wv=1027&k=5em9gwb)
+
+或是与开发者联系：
+
+ Email：[abslant@foxmail.com](mailto:abslant@foxmail.com)
+
diff --git a/SUMMARY.md b/ch/SUMMARY.md
similarity index 100%
rename from SUMMARY.md
rename to ch/SUMMARY.md
diff --git a/getting-started/build.md b/ch/getting-started/build.md
similarity index 100%
rename from getting-started/build.md
rename to ch/getting-started/build.md
diff --git a/getting-started/config.md b/ch/getting-started/config.md
similarity index 100%
rename from getting-started/config.md
rename to ch/getting-started/config.md
diff --git a/getting-started/install.md b/ch/getting-started/install.md
similarity index 100%
rename from getting-started/install.md
rename to ch/getting-started/install.md
diff --git a/manage/db-script.md b/ch/manage/db-script.md
similarity index 100%
rename from manage/db-script.md
rename to ch/manage/db-script.md
diff --git a/manage/update/README.md b/ch/manage/update/README.md
similarity index 100%
rename from manage/update/README.md
rename to ch/manage/update/README.md
diff --git a/manage/update/cong-3.x.x-sheng-ji.md b/ch/manage/update/cong-3.x.x-sheng-ji.md
similarity index 100%
rename from manage/update/cong-3.x.x-sheng-ji.md
rename to ch/manage/update/cong-3.x.x-sheng-ji.md
diff --git a/manage/update/update-from-os.md b/ch/manage/update/update-from-os.md
similarity index 100%
rename from manage/update/update-from-os.md
rename to ch/manage/update/update-from-os.md
diff --git a/manage/update/upgrade.md b/ch/manage/update/upgrade.md
similarity index 100%
rename from manage/update/upgrade.md
rename to ch/manage/update/upgrade.md
diff --git a/use/aria2.md b/ch/use/aria2.md
similarity index 100%
rename from use/aria2.md
rename to ch/use/aria2.md
diff --git a/use/policy/README.md b/ch/use/policy/README.md
similarity index 100%
rename from use/policy/README.md
rename to ch/use/policy/README.md
diff --git a/use/policy/compare.md b/ch/use/policy/compare.md
similarity index 100%
rename from use/policy/compare.md
rename to ch/use/policy/compare.md
diff --git a/use/pro/README.md b/ch/use/pro/README.md
similarity index 100%
rename from use/pro/README.md
rename to ch/use/pro/README.md
diff --git a/use/pro/cun-chu-ce-lve-qie-huan.md b/ch/use/pro/cun-chu-ce-lve-qie-huan.md
similarity index 100%
rename from use/pro/cun-chu-ce-lve-qie-huan.md
rename to ch/use/pro/cun-chu-ce-lve-qie-huan.md
diff --git a/use/pro/jie-shao.md b/ch/use/pro/jie-shao.md
similarity index 100%
rename from use/pro/jie-shao.md
rename to ch/use/pro/jie-shao.md
diff --git a/use/pro/pay.md b/ch/use/pro/pay.md
similarity index 100%
rename from use/pro/pay.md
rename to ch/use/pro/pay.md
diff --git a/use/pro/qq.md b/ch/use/pro/qq.md
similarity index 100%
rename from use/pro/qq.md
rename to ch/use/pro/qq.md
diff --git a/use/pro/shou-quan-guan-li.md b/ch/use/pro/shou-quan-guan-li.md
similarity index 100%
rename from use/pro/shou-quan-guan-li.md
rename to ch/use/pro/shou-quan-guan-li.md
diff --git a/use/webdav.md b/ch/use/webdav.md
similarity index 100%
rename from use/webdav.md
rename to ch/use/webdav.md
diff --git a/use/zi-ding-yi-qian-duan.md b/ch/use/zi-ding-yi-qian-duan.md
similarity index 100%
rename from use/zi-ding-yi-qian-duan.md
rename to ch/use/zi-ding-yi-qian-duan.md
diff --git a/en/README.md b/en/README.md
new file mode 100644
index 0000000..5054721
--- /dev/null
+++ b/en/README.md
@@ -0,0 +1,28 @@
+---
+description: The documentation is still being worked on!
+---
+
+## Welcome
+
+## What is Cloudreve?
+
+Cloudreve allows you to quickly set up both public and private drives. Cloudreve supports different cloud storage platforms under the hood, so you don't have to worry about the physical storage. You can use Cloudreve for personal use, for file sharing, or as a public cloud for small or large groups.
+
+## Feedback
+
+If you find any bugs or have a new requirement, please check the previous documentation, [issue](https://github.com/cloudreve/Cloudreve/issues), [discussion community](https://forum.cloudreve.org/) to see if it has been mentioned.
+
+If a bug or feature suggestion is suspected, create an [issue](https://github.com/cloudreve/Cloudreve/issues) to track the issue.
+
+If it is a question of daily use, please create a new topic in the [discussion community](https://forum.cloudreve.org/) and describe the problem you are having in detail.
+
+## Contact
+
+You can join the following groups to communicate with other users who are using Cloudreve.
+
+* [Telegram group](https://t.me/cloudreve_official)
+* [QQ group](https://jq.qq.com/?_wv=1027&k=5em9gwb)
+
+Or contact the developer at
+
+ Email: [abslant@foxmail.com](mailto:abslant@foxmail.com)
\ No newline at end of file
diff --git a/en/SUMMARY.md b/en/SUMMARY.md
new file mode 100644
index 0000000..6b136fb
--- /dev/null
+++ b/en/SUMMARY.md
@@ -0,0 +1,32 @@
+# Table of contents
+
+* [Welcome](README.md)
+
+## Getting Started <a id="getting-started"></a>
+
+* [Quick Start](getting-started/install.md)
+* [Configuration Files](getting-started/config.md)
+* [Build](getting-started/build.md)
+
+## Using <a id="use"></a>
+
+* [Storage Policies](use/policy/README.md)
+  * [Compare](use/policy/compare.md)
+* [WebDAV](use/webdav.md)
+* [Offline Download](use/aria2.md)
+* [Custom Frontends](use/zi-ding-yi-qian-duan.md)
+* [Donation Edition](use/pro/README.md)
+  * [Presentation](use/pro/jie-shao.md)
+  * [License Management](use/pro/shou-quan-guan-li.md)
+  * [Change Storage Policy](use/pro/cun-chu-ce-lve-qie-huan.md)
+  * [Payments](use/pro/pay.md)
+  * [QQ Connect](use/pro/qq.md)
+
+## Maintenance <a id="manage"></a>
+
+* [Database Scripts](manage/db-script.md)
+* [Updating](manage/update/README.md)
+  * [Updating from 3.x.x](manage/update/cong-3.x.x-sheng-ji.md)
+  * [Updating from 2.x.x](manage/update/upgrade.md)
+  * [Upgrade to donation version](manage/update/update-from-os.md)
+
diff --git a/en/getting-started/build.md b/en/getting-started/build.md
new file mode 100644
index 0000000..6e11989
--- /dev/null
+++ b/en/getting-started/build.md
@@ -0,0 +1,100 @@
+# Build
+
+The Cloudreve project consists of two main parts: the main backend repository [cloudreve/Cloudreve](https://github.com/cloudreve/Cloudreve), and the frontend repository [cloudreve/frontend](https://github.com/cloudreve/frontend). Before compiling the Cloudreve backend, you need to build the frontend submodules in the `assets` directory and embed them in the backend repository using [statik](https://github.com/rakyll/statik).
+
+## Environment preparation
+
+1. refer to [Getting Started - The Go Programming Language](https://golang.org/doc/install) to install and configure the Go language development environment.
+2. Refer to [Download \| Node.js](https://nodejs.org/download/) to install Node.js;
+3. Refer to [Install \| Yarn](https://classic.yarnpkg.com/docs/install#windows-stable) to install Yarn;
+4. run `go get github.com/rakyll/statik` to install the statik command line tool;
+
+## Start building
+
+### Clone the repository
+
+``bash
+## Clone the repository
+git clone --recurse-submodules https://github.com/cloudreve/Cloudreve.git
+
+# # Check out the version you want to compile
+git checkout 3.x.x
+```
+
+### Build static resources
+
+```bash
+# Access the front-end submodule
+cd assets
+# Install dependencies
+yarn install
+# Start building
+yarn run build
+```
+
+When finished, the static resource files are located in the `assets/build` directory.
+
+You can rename this directory to `statics`, place it in the same level as the main Cloudreve application and restart Cloudreve, which will use the static resource files in this directory instead of the built-in ones.
+
+### Embedding static resources
+
+```bash
+### Return to the project home directory
+cd ../
+
+# Install statik, for embedding static resources
+go get github.com/rakyll/statik
+
+# Start embedding
+statik -src=assets/build/ -include=*.html,*.js,*.json,*.css,*.png,*.svg,*.ico,*.ttf -f
+```
+
+{% hint style="info" %}
+If the `statik` command is not found when embedding, try executing.
+
+`export PATH=$PATH:$(go env GOPATH)/bin`
+{% endhint %}
+
+### Compile the project
+
+```bash
+### Get current version number, commit
+export COMMIT_SHA=$(git rev-parse --short HEAD)
+export VERSION=$(git describe --tags)
+
+# Start the build
+go build -a -o cloudreve -ldflags " -X 'github.com/cloudreve/Cloudreve/v3/pkg/conf.BackendVersion=$VERSION' -X 'github.com/cloudreve/ Cloudreve/v3/pkg/conf.LastCommit=$COMMIT_SHA'"
+```
+
+{% hint style="info" %}
+When first compiling, Go will download the relevant dependencies, which may cause this step to slow down or fail if you have a poor network. You can use [GOPROXY.IO](https://goproxy.io/zh/) to speed up the module download.
+{% endhint %}
+
+Once compiled, the final executable `cloudreve` will be generated in the project root directory.
+
+## Build Assistant
+
+You can quickly build, package etc. using the build script `build.sh` in the project root directory, which is used as follows
+
+```bash
+. /build.sh [-a] [-c] [-b] [-r]
+    a - build static resources
+    c - compile binaries
+    b - build front-end + compile binaries
+    r - cross-compile, build for release
+```
+
+## Cross-compiling
+
+Before cross-compiling, you need to enable `CGO`, properly install the GCC toolchain for the target platform and set the `CC` environment variable to the GCC compiler for the corresponding platform.
+
+For example, to cross-compile Windows/AMD64 on a Linux/AMD64 host platform.
+
+```bash
+export GOOS=windows
+export GOARCH=amd64
+export CC=x86_64-w64-mingw32-gcc
+export CGO_ENABLED=1
+
+go build
+```
\ No newline at end of file
diff --git a/en/getting-started/config.md b/en/getting-started/config.md
new file mode 100644
index 0000000..ae98e20
--- /dev/null
+++ b/en/getting-started/config.md
@@ -0,0 +1,165 @@
+# Configuration files
+
+## Configuration file
+
+When you start Cloudreve for the first time, Cloudreve creates a configuration file named `conf.ini` in the same level directory.
+
+You can also specify the path to the configuration file by adding the `-c` parameter at startup:
+
+```
+./cloudreve -c /path/to/conf.ini
+```
+
+An example of a complete configuration file is as follows.
+
+```d
+[System]
+; Run mode
+Mode = master
+; Listening port
+Listen = :5000
+; Whether to enable Debug
+Debug = false
+; Session key, usually generated automatically at first boot
+SessionSecret = 23333
+; Hash salt, usually generated automatically at first boot
+HashIDSalt = something really hard to guess
+
+; SSL related
+[SSL]
+; SSL listening port
+Listen = :443
+; Certificate path
+CertPath = C:\Users\i\Documents\fullchain.pem
+; private key path
+KeyPath = C:\Users\i\Documents\privkey.pem
+
+; Enable Unix Socket Listening
+[UnixSocket]
+Listen = /run/cloudreve/cloudreve.sock
+
+;If you only want to use the built-in SQLite database, just delete this section
+[Database]
+; Database type, currently supports sqlite/mysql/mssql/postgres
+Type = mysql
+MySQL port
+Port = 3306
+; Username
+User = root
+Password
+Password = root
+; Database address
+Host = 127.0.0.1
+; Database name
+Name = v3
+; Data table prefix
+TablePrefix = cd_
+; Character set
+Charset = utf8
+; SQLite database file path
+DBFile = cloudreve.db
+
+; Configuration in slave mode
+[Slave]
+; Communication key
+Secret = 1234567891234567123456789123456712345678912345671234567891234567
+; Callback request timeout (s)
+CallbackTimeout = 20
+; Signature validity
+SignatureTTL = 60
+
+; Cross-domain configuration
+[CORS]
+AllowOrigins = *
+AllowMethods = OPTIONS,GET,POST
+AllowHeaders = *
+AllowCredentials = false
+
+; Redis-related
+[Redis]
+Server = 127.0.0.1:6379
+Password =
+DB = 0
+
+; Thumbnail
+[Thumbnail]
+MaxWidth = 400
+MaxHeight = 300
+FileSuffix = ._thumb
+; Maximum number of thumbnails to be generated in parallel, filled with -1 will be determined automatically based on the number of CPU cores
+MaxTaskCount = -1
+; can be filled with jpg / png
+EncodeMethod = jpg
+; whether to garbage collect thumbnails immediately after they are generated
+GCAfterGen = false
+; Thumbnail quality
+EncodeQuality = 85
+```
+
+## Using MySQL
+
+By default, Cloudreve uses the built-in SQLite database and creates the database file `cloudreve.db` in the same directory. If you want to use MySQL, please add the following to the configuration file and restart Cloudreve.
+
+Note that Cloudreve only supports MySQL versions greater than or equal to 5.7.
+```
+[Database]
+; database type, currently sqlite/mysql/mssql/postgres is supported
+Type = mysql
+MySQL port
+Port = 3306
+; Username
+User = root
+; Password
+Password = root
+; Database address
+Host = 127.0.0.1
+; Database name
+Name = v3
+; Data table prefix
+TablePrefix = cd
+; Character set
+Charset = utf8
+```
+
+{% hint style="info" %}
+After changing the database configuration, Cloudreve will reinitialize the database and the old data will be lost.
+{% endhint %}
+
+## Using Redis
+
+You can add Redis-related settings to your configuration file.
+
+```
+[Redis]
+Server = 127.0.0.1:6379
+Password = your password
+DB = 0
+```
+
+{% hint style="info" %}
+Please specify a DB for Cloudreve that is not used by other services to avoid conflicts.
+{% endhint %}
+
+After restarting Cloudreve, you can note the console output to determine if Cloudreve successfully connected to the Redis server. When using Redis, the following will be taken over by Redis.
+
+* User sessions (no more lost login sessions after restarting Cloudreve)
+* Data table HF record query cache (e.g. storage policies, settings entries)
+* Callback sessions
+* OneDrive credentials
+
+## Enable HTTPS
+
+{% hint style="info" %}
+If you are using Cloudreve as a web server reverse proxy, it is recommended that you configure SSL in your web server, the how to described in this section is only valid if you are using Cloudreve's built-in web server.
+{% endhint %}
+
+In the configuration file add.
+
+```
+[SSL]
+Listen = :443
+CertPath = C:\Users\i\Documents\fullchain.pem
+KeyPath = C:\Users\i\Documents\privkey.pem
+```
+
+where `CertPath` and `KeyPath` are the SSL certificate and private key paths, respectively. Save and restart Cloudreve to take effect.
\ No newline at end of file
diff --git a/en/getting-started/install.md b/en/getting-started/install.md
new file mode 100644
index 0000000..c0e1224
--- /dev/null
+++ b/en/getting-started/install.md
@@ -0,0 +1,224 @@
+# Quick Start
+
+## Get Cloudreve
+
+You can get the packaged master on the [GitHub Release](https://github.com/cloudreve/Cloudreve/releases) page. Each of these releases provides the main program available on common system architectures with the naming convention `cloudreve_version_number_OS_CPU_architecture.tar.gz` . For example, to deploy version 3.0.0 on a common 64-bit Linux system, you should download `cloudreve_3.0.0_linux_amd64.tar.gz`.
+
+If you want to experience the latest features, you can download the development version built after each commit in [GitHub Actions](https://github.com/cloudreve/Cloudreve/actions). Note that development builds are not stable, cannot be used in production, and are not guaranteed to be fully available.
+
+If you want to build from source yourself, see the following sections.
+
+{% page-ref page="build.md" %}
+
+## Start Cloudreve
+
+{% tabs %}
+{% tab title="Linux" %}
+On Linux, just unpack and execute the main program directly as follows.
+
+```bash
+## Unzip the main program you got
+tar -zxvf cloudreve_VERSION_OS_ARCH.tar.gz
+
+# Give execute permission
+chmod +x . /cloudreve
+
+# Start Cloudreve
+. /cloudreve
+```
+{% endtab %}
+
+{% tab title="Windows" %}
+On Windows, unzip the zip archive and start `cloudreve.exe`.
+{% endtab %}
+{% endtabs %}
+
+When Cloudreve is first started, an initial administrator account will be created. Please keep the administrator password, which will only appear on first startup. If you forget the initial administrator password, you will need to delete `cloudreve.db` from the same directory and restart the main application to initialize a new administrator account.
+
+Cloudreve will listen on port `5212` by default. You can access Cloudreve by visiting `http://ServerIP:5212` in your browser.
+
+After the above steps, the simplest deployment is complete. You may need some more specific configuration to make Cloudreve work better, please refer to the following configuration process.
+
+## Optional Deployment Process
+
+### Reverse Proxy
+
+In a self-use or small-scale usage scenario, you can absolutely use Cloudreve's built-in web server. However, if you need to use HTTPS or need it to coexist with other web services on the server, you may need to use a mainstream web server to reverse proxy Cloudreve for richer extensions.
+
+You need to create a new virtual host on your web server, complete the required configuration (e.g. enable HTTPS) and then add the reverse proxy rules to your website configuration file:
+
+{% tabs %}
+{% tab title="NGINX" %}
+In the `server` field of the site add.
+
+```text
+location / {
+    proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
+    proxy_set_header Host $http_host;
+    proxy_redirect off;
+    proxy_pass http://127.0.0.1:5212;
+
+    # If you want to use the local storage policy, remove the comment character from the next line and change the size to the theoretical maximum file size
+    # client_max_body_size 20000m;
+}
+```
+{% endtab %}
+
+{% tab title="Apache" %}
+Add the reverse proxy configuration item `ProxyPass` under the `VirtualHost` field, e.g.
+
+```markup
+<VirtualHost *:80>
+    ServerName myapp.example.com
+    ServerAdmin webmaster@example.com
+    DocumentRoot /www/myapp/public
+
+    # Here are the key parts
+    AllowEncodedSlashes NoDecode
+    ProxyPass "/" "http://127.0.0.1:5212/" nocanon
+
+</VirtualHost
+```
+{% endtab %}
+{% endtabs %}
+
+### Process guarding
+
+Either of the following two methods can be used.
+
+#### Systemd
+
+```bash
+### Edit the configuration file
+vim /usr/lib/systemd/system/cloudreve.service
+```
+
+Replace the following ``PATH_TO_CLOUDREVE`` with the directory where the program is located.
+
+```bash
+[Unit]
+Description=Cloudreve
+Documentation=https://docs.cloudreve.org
+After=network.target
+After=mysqld.service
+Wants=network.target
+
+[Service]
+WorkingDirectory=/PATH_TO_CLOUDREVE
+ExecStart=/PATH_TO_CLOUDREVE/cloudreve
+Restart=on-abnormal
+RestartSec=5s
+KillMode=mixed
+
+StandardOutput=null
+StandardError=syslog
+
+[Install]
+WantedBy=multi-user.target
+```
+
+```bash
+# Update the configuration
+systemctl daemon-reload
+
+# Start the service
+systemctl start cloudreve
+
+# Set up bootup
+systemctl enable cloudreve
+```
+
+Management commands.
+
+```bash
+# Start the service
+systemctl start cloudreve
+
+# Stop the service
+systemctl stop cloudreve
+
+# Restart the service
+systemctl restart cloudreve
+
+# Check the status
+systemctl status cloudreve
+```
+
+#### Supervisor
+
+First install ``supervisor``, you can skip it if it is already installed.
+
+```bash
+# Install supervisor
+sudo yum install python-setuptools
+sudo easy_install supervisor
+
+# Initialize the global configuration file
+sudo touch /etc/supervisord.conf
+sudo echo_supervisord_conf > /etc/supervisord.conf
+```
+
+Edit the global configuration file.
+
+```bash
+sudo vim /etc/supervisord.conf
+```
+
+Remove the `[include]` partition comment symbol `;` from the bottom of the file and add the new configuration file include path:
+
+```bash
+[include]
+files = /etc/supervisor/conf/*.conf
+```
+
+Create the directory where the Cloudreve application configuration is located and create the open configuration file:
+
+```bash
+sudo mkdir -p /etc/supervisor/conf
+sudo vim /etc/supervisor/conf/cloudreve.conf
+```
+
+Fill in the following as appropriate and save.
+
+```bash
+[program:cloudreve]
+directory=/home/cloudreve
+command=/home/cloudreve/cloudreve
+autostart=true
+autorestart=true
+stderr_logfile=/var/log/cloudreve.err
+stdout_logfile=/var/log/cloudreve.log
+environment=CODENATION_ENV=prod
+```
+
+Where the following configuration items need to be changed as appropriate.
+
+* `directory`: the directory where the Clopudreve main program is located
+* `command`: absolute path to the Cloudreve main program
+* `stderr_logfile`: path to the error log
+* `stdout_logfile`: path to the usual log
+
+Start the supervisor via the global configuration file.
+
+```bash
+supervisord -c /etc/supervisord.conf
+```
+
+In the future you can manage the Cloudreve process with the following command.
+
+```bash
+# Start
+sudo supervisorctl start cloudreve
+
+# Stop
+sudo supervisorctl stop cloudreve
+
+# Check the status
+sudo supervisorctl status cloudreve
+```
+
+## Docker
+
+You can choose to deploy with the following images.
+
+* [xavierniu/cloudreve](https://hub.docker.com/r/xavierniu/cloudreve)
\ No newline at end of file
diff --git a/en/manage/db-script.md b/en/manage/db-script.md
new file mode 100644
index 0000000..acadc62
--- /dev/null
+++ b/en/manage/db-script.md
@@ -0,0 +1,23 @@
+# Database Scripts
+
+Cloudreve has some common database scripts built in for routine maintenance, versioning and other operations. You can execute each script by adding the command line parameter `-database-script <script name>` at startup.
+
+### Calibrating user capacity
+
+If the space used by users does not match the actual space used due to system failure or manual manipulation of database records, you can run the following database script and Cloudreve will recalibrate the capacity usage for all registered users.
+
+```text
+./cloudreve --database-script CalibrateUserStorage
+```
+
+### Upgrade donation version
+
+{% page-ref page="update/update-from-os.md" %}
+
+### Reset administrator password
+
+The following database script resets the password of the initial administrator (i.e. the user with UID 1). The new password will be output in the command line log, so please take care to save it.
+
+```text
+. /cloudreve --database-script ResetAdminPassword
+```
\ No newline at end of file
diff --git a/en/manage/update/README.md b/en/manage/update/README.md
new file mode 100644
index 0000000..02510ca
--- /dev/null
+++ b/en/manage/update/README.md
@@ -0,0 +1,2 @@
+# Upgrade
+
diff --git a/en/manage/update/cong-3.x.x-sheng-ji.md b/en/manage/update/cong-3.x.x-sheng-ji.md
new file mode 100644
index 0000000..eceaed1
--- /dev/null
+++ b/en/manage/update/cong-3.x.x-sheng-ji.md
@@ -0,0 +1,15 @@
+# Upgrade from 3.x.x
+
+The upgrade steps within the V3 release are relatively simple and the overall process is as follows.
+
+1. Back up the database.
+2. Download or build the latest version of Cloudreve.
+3. Stop the running Cloudreve.
+4. Replace the old version of Cloudreve main application with the new version.
+5. Start Cloudreve.
+6. Clear your browser cache.
+7. If you are using Cloudreve in slave mode, replace the Cloudreve on the slave node with the same version.
+
+{% hint style="info" %}
+If you used a self-built front-end static resource file in the old version, please rebuild it with the corresponding front-end repository code in the new version.
+{% endhint %}
diff --git a/en/manage/update/update-from-os.md b/en/manage/update/update-from-os.md
new file mode 100644
index 0000000..443f15b
--- /dev/null
+++ b/en/manage/update/update-from-os.md
@@ -0,0 +1,25 @@
+# Upgrade to Donation Edition
+
+If you were previously using the Community Edition of Cloudreve, you can upgrade to the Donation Edition after obtaining the Donation Edition while retaining your data.
+
+### Replace the main program
+
+Back up all data, upload and replace the main program and license files of the Donation Edition to the original Community Edition directory.
+
+### Execute the upgrade script
+
+Using Cloudreve's command line parameters, run the upgrade database script.
+
+{% tabs %}
+{% tab title="Linux" %}
+```
+./cloudreve --database-script OSSToPro
+```
+{% endtab %}
+
+{% tab title="Windows" %}
+```
+cloudreve.exe --database-script UpgradeToPro
+```
+{% endtab %}
+{% endtabs %}
diff --git a/en/manage/update/upgrade.md b/en/manage/update/upgrade.md
new file mode 100644
index 0000000..9ff3576
--- /dev/null
+++ b/en/manage/update/upgrade.md
@@ -0,0 +1,61 @@
+# Upgrade from 2.x.x
+
+Due to the large changes in the data table structure, upgrading from V2 to V3 requires the manual implementation of the Database Upgrade Assistant. Please be sure to back up your V2 version website data before upgrading to avoid data loss.
+
+## Upgrade Compatibility
+
+After upgrading from V2 to V3, the following data will be lost.
+
+* Offline download history
+* Timed task settings
+* User two-step verification settings
+
+## Check items before upgrading
+
+Before upgrading, please check the following list to ensure that all items are met and known before proceeding with the upgrade.
+
+* Make sure that the specific version number of Cloudreve for V2 is `2.0.0-Alpha1`, which you can see in the Admin Panel - About.
+* The V3 version does not support S3 type storage policies at the moment, if you are using S3 storage policies, please delete the storage policy and its subordinate files after backing up or transferring the files.
+* If you are using a remote storage policy, please delete the storage policy and its subordinate files after backing up or transferring the files, as upgrading a remote storage policy is not supported at this time.
+* Backing up V2 site files, databases.
+* If you are using the OneDrive task queue, stop it first.
+* stopping Crontab timed tasks that have been set.
+* You already know how to set up the V3 version and how to configure it to use MySQL, which you will use later, so I won't go over it again.
+
+## Starting the upgrade
+
+### Building the V3 version
+
+Start V3 in the V2 version of the Cloudreve web directory by referring to the following page.
+
+{% include "./../../getting-started/install.md" %}
+
+Specify the MySQL database for the V3 version in the configuration file by referring to the following page, and note that you can specify a different database for the V2 version, or use a data table prefix to distinguish it from the V2 version.
+
+{% include "./../../getting-started/config.md" %}
+
+Restart V3 and allow Cloudreve to initialise the V3 version of the data table, do not perform any actions once the initialisation is complete.
+
+### Run the upgrade assistant
+
+Download `upgrade_from_2.0.0-Alpha1.zip` from the [Release 3.0.0](https://github.com/cloudreve/Cloudreve/releases/tag/3.0.0) page \( Pro version users please download `upgrade_ffrom_2.0.0-Alpha1-pro.zip`\), unzip it and overwrite it to the V2 root directory.
+
+At the command line, switch the working directory to the V2 root directory and start the upgrade assistant by
+
+```bash
+# Switch to the V2 root directory
+cd /home/www/cloudreve.org
+
+# Start the upgrade
+php upgrade run
+```
+
+Follow the prompts and enter the database information for the V3 version, the database upgrade will start when you are done.
+
+### Follow up
+
+Once the upgrade assistant has been run, you will be able to use the V3 version. Please note that the `public` directory in the V2 website directory contains the user avatar and local policy files from the V2 version and will still be used by the V3 version, other files can be deleted as appropriate.
+
+### What to do if the upgrade fails
+
+If an exception occurs during the upgrade process and you need to retry, please restore the backed up V2 version database, delete the V3 version data table and restart the V3 main program before starting the Upgrade Assistant again. A thumbnail and avatar file upgrade error warning may appear during the upgrade process again and can be ignored.
\ No newline at end of file
diff --git a/en/use/aria2.md b/en/use/aria2.md
new file mode 100644
index 0000000..509d39f
--- /dev/null
+++ b/en/use/aria2.md
@@ -0,0 +1,106 @@
+# Offline Downloads
+
+Cloudreve's offline download core is driven by [Aria2](https://aria2.github.io). Once offline downloads are properly configured and enabled, users can create magnet, HTTP, and seed download tasks that are added to user files after the server completes the download.
+
+For cloud storage policy, Cloudreve will dump the downloaded files to the cloud storage side after the offline download task is completed, and users cannot download and manage the downloaded files until the dumping is finished. Users can view the progress of the dumped tasks in the task queue in the frontend.
+
+Cloudreve supports "slave offline download", which allows you to divert offline download tasks to multiple servers to avoid overloading the host with these tasks. Each node that handles offline downloads requires a set of Cloudreve and Aria2 instances to run. You can configure and add new nodes by following the Node Addition Wizard guidelines in the administration panel. A slave offline download node is essentially the same as the node used for a slave storage policy, and you can use a slave Cloudreve instance as both a storage node and an offline download node. If you do not need the slave node to handle offline download tasks and only want the current host Cloudreve to handle offline downloads, simply edit the host node and configure Aria2-related information. User-created offline download tasks will be rotated to all available offline download nodes for processing.
+
+## Enable Offline Downloads
+
+### Aria2 RPC Configuration
+
+The installation and startup process for Aria2 is beyond the scope of this article. You will need to start Aria2 on the same machine as Cloudreve.
+
+{% hint style="info" %}
+It is recommended that you start Aria2 before Cloudreve in your daily boot process, so that Cloudreve can subscribe to event notifications to Aria2 and download status changes are handled more promptly. Of course, if this process is not available, Cloudreve will also track the task status via polling.
+{% endhint %}
+
+When you start Aria2, you need to enable the RPC service in its configuration file and set the RPC Secret for subsequent use.
+
+```bash
+# Enable the RPC service
+enable-rpc=true
+# RPC listening port
+rpc-listen-port=6800
+# RPC authorization token, you can set it yourself
+rpc-secret=<your token>
+```
+
+### Accessing Cloudreve
+
+Go to Cloudreve's Admin Panel - Offline Download Node - Add/Edit Node - Offline Download, follow the instructions to fill in the information and test if you can communicate with Aria2 properly.
+
+The important parameters are explained as follows.
+
+**RPC server address**
+
+The address of the Aria2 RPC server, which can be filled in as `http://127.0.0.1:6800/`. Where `6800` is the listening port specified in the Aria2 configuration file above. You can use WebSocket communication, which is `ws://127.0.0.1:6800/`.
+
+**RPC Secret**
+
+The RPC authorization token you set in the Aria2 configuration file above
+
+**Temporary Download Directory**
+
+Cloudreve will specify that Aria2 download the files to this directory, and when the download is complete Cloudreve will copy to the specified storage policy and delete the files. This directory **must be an absolute path**, otherwise Cloudreve will not find the file after the task completes downloading. the absolute path specified under Windows should carry the disk letter, e.g. `G:\www\downloads`.
+
+**Status refresh interval (in seconds)**
+
+Specifies the interval at which Cloudreve polls Aria2 to update the task status for each task. The progress of the tasks that users see in the foreground is not updated in real time, but is automatically refreshed according to the interval set here.
+
+**Global Task Parameters**
+
+Specify additional parameters here that Cloudreve carries with it when creating Aria2 download tasks, or you can specify them in the Aria2 configuration file if Aria2 is not public with other services. The specific parameters available can be found in the [official documentation](https://aria2.github.io/manual/en/html/aria2c.html#options) and filled in here in JSON format. If the format is incorrect, the task may not be created. The following is a sample fill in specifying the maximum number of parallel tasks and the Tracker server list.
+
+```javascript
+{
+	"max-concurrent-downloads": 10,
+	"bt-tracker": [
+		"udp://tracker.coppersurfer.tk:6969/announce",
+		"udp://tracker.opentrackr.org:1337/announce",
+		"udp://tracker.leechers-paradise.org:6969/announce"
+	]
+}
+```
+
+You can also specify parameters specific to each user group in the user group configuration, such as limiting the maximum download speed. The format is the same as above and will not be repeated.
+
+### User group permissions
+
+For user groups that you want to allow offline downloading, please enable offline downloading permission on the user group edit page.
+
+## Frequently Asked Questions
+
+#### When testing an Aria2 connection, you are prompted with `Unable to request RPC service, Post "XXX": dial tcp XXX connect: connection refused`.
+
+Check if the address is incorrect, if Aria2 is running, and if the port is the same as the one specified in the Aria2 configuration file.
+
+#### When testing Aria2 connection, `Unable to request RPC service, invalid character '<' looking for beginning of value`.
+
+The RPC address filled in is incorrect, and you can connect, but it is not an Aria2 RPC service, so check if the address is incorrect and the port is correct. The reason for this error is usually that the RPC address is filled in as the address of a Web service.
+
+#### The status of tasks in the Cloudreve task list is not updated/is not updated in a timely manner
+
+Cloudreve polls the task status periodically. The task status is not updated in real time after it is created, so please be patient. You can also adjust the update frequency in Admin Panel - Parameter Settings - Offline Download - Status Refresh Interval (sec).
+
+#### BT download too slow/no speed
+
+Download tasks are processed by Aria2 and cannot be optimized via Cloudreve. One possible solution is to manually add a Tracker server. You can specify the Tracker in the Aria2 configuration file at
+
+```bash
+bt-tracker=udp://tracker.coppersurfer.tk:6969/announce,http://tracker.internetwarriors.net:1337/announce,udp://tracker.opentrackr.org:1337/announce
+```
+
+The Tracker list specified above is just an example, you need to fill it in yourself. You can use the best Tracker list from the [trackerslist](https://github.com/ngosang/trackerslist) project, which is updated daily.
+
+#### BT Tasks remain in the "in progress" list for a long time after 100% progress has been made
+
+By default, Aria2 seeds BT tasks that have completed downloading, and only after the seeding is complete will they be recognized as completed by Cloudreve and processed later. You can specify the seeding share rate or seeding time in the Aria2 configuration file, and seeding will stop when either of the following conditions is met.
+
+```bash
+# seed-ratio, 0 is always seeding, default:1.0
+seed-ratio=1.0
+# Stop seeding if seeding time is longer than 30 minutes
+seed-time=30
+```
\ No newline at end of file
diff --git a/en/use/policy/README.md b/en/use/policy/README.md
new file mode 100644
index 0000000..2c8231a
--- /dev/null
+++ b/en/use/policy/README.md
@@ -0,0 +1,2 @@
+# Storage Strategies
+
diff --git a/en/use/policy/compare.md b/en/use/policy/compare.md
new file mode 100644
index 0000000..ceeaaf3
--- /dev/null
+++ b/en/use/policy/compare.md
@@ -0,0 +1,45 @@
+# Compare and Contrast
+
+Cloudreve supports a variety of underlying storage policies, but due to various factors such as API limitations, Cloudreve does not support each policy to the same degree, and this section will detail the specific differences in support between different storage policies.
+
+## Basic Comparison
+
+|           |          Local          |          Slave          |          Qiniu          |          OSS         |          COS          |          Yubai Cloud         |       OneDrive       | S3                   |
+| --------- | :------------------: | :------------------: | :------------------: | :------------------: | :-------------------: | :------------------: | :------------------: | -------------------- |
+| Upload        | :white\_check\_mark: | :white\_check\_mark: | :white\_check\_mark: | :white\_check\_mark: |  :white\_check\_mark: | :white\_check\_mark: | :white\_check\_mark: | :white\_check\_mark: |
+| Download        | :white\_check\_mark: | :white\_check\_mark: | :white\_check\_mark: | :white\_check\_mark: |  :white\_check\_mark: | :white\_check\_mark: | :white\_check\_mark: | :white\_check\_mark: |
+| Copy        | :white\_check\_mark: | :white\_check\_mark: | :white\_check\_mark: | :white\_check\_mark: |  :white\_check\_mark: | :white\_check\_mark: | :white\_check\_mark: | :white\_check\_mark: |
+| Mobile        | :white\_check\_mark: | :white\_check\_mark: | :white\_check\_mark: | :white\_check\_mark: |  :white\_check\_mark: | :white\_check\_mark: | :white\_check\_mark: | :white\_check\_mark: |
+| General Preview      | :white\_check\_mark: | :white\_check\_mark: | :white\_check\_mark: | :white\_check\_mark: |  :white\_check\_mark: | :white\_check\_mark: | :white\_check\_mark: | :white\_check\_mark: |
+| Office Preview | :white\_check\_mark: | :white\_check\_mark: | :white\_check\_mark: | :white\_check\_mark: |  :white\_check\_mark: | :white\_check\_mark: | :white\_check\_mark: | :white\_check\_mark: |
+| Delete        | :white\_check\_mark: | :white\_check\_mark: | :white\_check\_mark: | :white\_check\_mark: |  :white\_check\_mark: | :white\_check\_mark: | :white\_check\_mark: | :white\_check\_mark: |
+| Thumbnails       | :white\_check\_mark: | :white\_check\_mark: | :white\_check\_mark: | :white\_check\_mark: |  :white\_check\_mark: | :white\_check\_mark: | :white\_check\_mark: | :x:                  |
+| Packed Downloads      | :white\_check\_mark: | :white\_check\_mark: | :white\_check\_mark: | :white\_check\_mark: |  :white\_check\_mark: | :white\_check\_mark: | :white\_check\_mark: | :white\_check\_mark: |
+| Real File Name Downloads   | :white\_check\_mark: | :white\_check\_mark: | :white\_check\_mark: | :white\_check\_mark: |  :white\_check\_mark: | :white\_check\_mark: |          :x:         | :white\_check\_mark: |
+| Theoretical maximum file size    |          Unlimited          |          Unlimited          |          Unlimited          |          5GB         |          5GB          |         150GB        |          Unknown          | Unknown                   |
+| Public Access Requirements    |           None          |           None          |          Required          |          Required          |           Required          |          Required          |          Required          | Required                   |
+
+## Advanced Features
+
+|      |          Local          |          Slave          |          Qiniu          |          OSS         |          COS         |          Yubai Cloud         |       OneDrive       | S3                   |
+| ---- | :------------------: | :------------------: | :------------------: | :------------------: | :------------------: | :------------------: | :------------------: | -------------------- |
+| Offline Download | :white\_check\_mark: | :white\_check\_mark: | :white\_check\_mark: | :white\_check\_mark: | :white\_check\_mark: | :white\_check\_mark: | :white\_check\_mark: | :white\_check\_mark: |
+| Download Speed Limit | :white\_check\_mark: | :white\_check\_mark: |          :x:         | :white\_check\_mark: | :white\_check\_mark: |          :x:         |          :x:         | :x:                  |
+| Get direct links | :white\_check\_mark: | :white\_check\_mark: | :white\_check\_mark: | :white\_check\_mark: | :white\_check\_mark: | :white\_check\_mark: | :white\_check\_mark: | :x:                  |
+| Decompression  | :white\_check\_mark: | :white\_check\_mark: | :white\_check\_mark: | :white\_check\_mark: | :white\_check\_mark: | :white\_check\_mark: | :white\_check\_mark: | :white\_check\_mark: |
+| Compression   | :white\_check\_mark: | :white\_check\_mark: | :white\_check\_mark: | :white\_check\_mark: | :white\_check\_mark: | :white\_check\_mark: | :white\_check\_mark: | :white\_check\_mark: |
+|      |                      |                      |                      |                      |                      |                      |                      |                      |
+
+## Traffic path
+
+|             | Local                   | Slave                   | Qiniu                   | OSS                  | COS                  | Yubai Cloud                  | OneDrive             | S3                   |
+| ----------- | -------------------- | -------------------- | -------------------- | -------------------- | -------------------- | -------------------- | -------------------- | -------------------- |
+| Web Upload Client Direct Transfer | :white\_check\_mark: | :white\_check\_mark: | :white\_check\_mark: | :white\_check\_mark: | :white\_check\_mark: | :white\_check\_mark: | >= 4MB when direct transfer           | :white\_check\_mark: |
+| Download Direct Transfer        | :white\_check\_mark: | :white\_check\_mark: | :white\_check\_mark: | :white\_check\_mark: | :white\_check\_mark: | :white\_check\_mark: | :white\_check\_mark: | :white\_check\_mark: |
+| download/zip/unzip | direct transfer                   | transfer                   | transfer                   | transfer                   | transfer                   | transfer                   | transfer                   | transfer                   |
+| Offline Download        | direct transfer                   | transfer                   | transfer                   | transfer                   | transfer                   | transfer                   | transfer                   | transfer                   |
+| Text Editor        | direct transfer                   | transfer                   | transfer                   | transfer                   | transfer                   | transfer                   | transfer                   | transfer                   |
+| WebDAV Upload Direct Transfer  | :white\_check\_mark: | :x:                  | :x:                  | :x:                  | :x:                  | :x:                  | :x:                  | :x:                  |
+| WebDAV Direct Download | :white\_check\_mark: | :white\_check\_mark: | :white\_check\_mark: | :white\_check\_mark: | :white\_check\_mark: | :white\_check\_mark: | :white\_check\_mark: | :white\_check\_mark: |
+
+
diff --git a/en/use/pro/README.md b/en/use/pro/README.md
new file mode 100644
index 0000000..2b0bad7
--- /dev/null
+++ b/en/use/pro/README.md
@@ -0,0 +1,2 @@
+# Donation Edition Related
+
diff --git a/en/use/pro/cun-chu-ce-lve-qie-huan.md b/en/use/pro/cun-chu-ce-lve-qie-huan.md
new file mode 100644
index 0000000..2e0d6f6
--- /dev/null
+++ b/en/use/pro/cun-chu-ce-lve-qie-huan.md
@@ -0,0 +1,2 @@
+# Storage Policy Switching
+
diff --git a/en/use/pro/jie-shao.md b/en/use/pro/jie-shao.md
new file mode 100644
index 0000000..d027a4e
--- /dev/null
+++ b/en/use/pro/jie-shao.md
@@ -0,0 +1,29 @@
+# Introduction
+
+You can choose to sponsor the development of Cloudreve and, in return, you will receive a feature-enhanced version of Cloudreve Pro.
+
+The Pro version currently has the following exclusive features, which you can experience at the [official demo site](https://demo.cloudreve.org).
+
+* Capacity Pack Purchase
+* User purchases
+* Points top-up
+* Activation codes (to redeem user groups, packs, points)
+* Creation of shares for paid credit downloads
+* Third party payment interfacing (PAYJS, Alipay in-person payment)
+* QQ Connect login
+* Save other users' shares to your own network drive
+* Bind multiple storage policies for the same user group, users can switch freely
+  * Support for transferring files between storage policies
+* Bind different storage policies for different directories under WebDAV
+* Share reporting and processing
+* Specify initial files for newly registered users
+* Site announcement module
+* Whitelisting/blacklisting of registered email suffixes
+* \(continuously updated... \)
+
+[Detailed Graphic Introduction and FAQ&gt;&gt;](https://forum.cloudreve.org/d/1587)
+
+The donation version is currently priced at ¥299 / domain name \*1 and supports authorizing multiple domains with the same root domain, e.g. www.abc.com,pan.abc.com.
+
+Sponsorship page: [https://pro.cloudreve.org/Buy](https://pro.cloudreve.org/Buy)
+
diff --git a/en/use/pro/pay.md b/en/use/pro/pay.md
new file mode 100644
index 0000000..daba587
--- /dev/null
+++ b/en/use/pro/pay.md
@@ -0,0 +1,2 @@
+# Payment
+
diff --git a/en/use/pro/qq.md b/en/use/pro/qq.md
new file mode 100644
index 0000000..e300e07
--- /dev/null
+++ b/en/use/pro/qq.md
@@ -0,0 +1,2 @@
+# QQ Connect
+
diff --git a/en/use/pro/shou-quan-guan-li.md b/en/use/pro/shou-quan-guan-li.md
new file mode 100644
index 0000000..f6e93d7
--- /dev/null
+++ b/en/use/pro/shou-quan-guan-li.md
@@ -0,0 +1,2 @@
+# Delegation Management
+
diff --git a/en/use/webdav.md b/en/use/webdav.md
new file mode 100644
index 0000000..baef316
--- /dev/null
+++ b/en/use/webdav.md
@@ -0,0 +1,25 @@
+# WebDAV
+
+WebDAV is an HTTP-based file transfer protocol. Many third-party file managers, video players, and other products now support accessing files in Cloudreve via the WebDAV protocol, allowing you to share and synchronize files across platforms.
+
+To use WebDAV, please go to the backend administration panel and enable WebDAV access for the corresponding user group; the account used for WebDAV is not interoperable with the Cloudreve account and needs to be created separately. Go to the frontend and navigate to the left side - WebDAV - Create New Account to create the account information for WebDAV. Once created, the system will automatically generate a password for this account. When using WebDAV, please use your registered email address as the account name and the password will be the one generated by the system above.
+
+When creating a WebDAV account, you can specify the relative root directory for this account, and this account can only access the directories and files under the specified relative root directory through WebDAV. For the donation version, users can also mount different storage policies for different directories, and the storage policy mounted for the directory will be used first when uploading new files under WebDAV.
+
+## Common client usage instructions
+
+### Using Windows Explorer (not recommended)
+
+{% hint style="info" %}
+Before using this method, make sure your Cloudreve site is HTTPS enabled. If you need to add it under a non-HTTPS protocol, you need to modify the registry `\HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\WebClient\ Parameters` change the value of `BasicAuthLevel` to `2`.
+{% endhint %}
+
+Right click in the "This computer" space and select "Add a network location":
+
+![](<../.gitbook/assets/image (3).png>)
+
+Enter the site WebDAV connection address, usually in the format of `https://ServerIP/dav`, and enter your Cloudreve account and system-generated account password when you are done.
+
+Known issue: The added WebDAV mount cannot be accessed after a reboot and the account password needs to be re-entered. This is because Windows no longer supports storing WebDAV account and password information under BasicAuth ([Related](https://docs.microsoft.com/en-us/troubleshoot/windows-client/networking/cannot-automatically-reconnect-dav-share)). Cloudreve will change the WebDAV authentication method in a future release to improve this issue.
+
+****
diff --git a/en/use/zi-ding-yi-qian-duan.md b/en/use/zi-ding-yi-qian-duan.md
new file mode 100644
index 0000000..d8c655a
--- /dev/null
+++ b/en/use/zi-ding-yi-qian-duan.md
@@ -0,0 +1,19 @@
+# Custom Front End
+
+By default, Cloudreve uses the built-in static resource files, including HTML documents, JS scripts, CSS, image resources, etc. If you need to use your own customised static resources, please rename the `build` directory from the [front-end repository](https://github.com/cloudreve/frontend) compilation to `statics` and place it in the same directory as Cloudreve, then restart Cloudreve to take effect.
+
+For the build process of the front-end repository, see the following section.
+
+{% page-ref page="../getting-started/build.md" %}
+
+{% hint style="warning" %}
+Please use a front-end repository build that matches the version of the main Cloudreve application. You can find the corresponding front-end repository version in the `assets` sub-module of the main Cloudreve repository you are using.
+
+Pro versions of front-end resources are not interoperable with community versions.
+{% endhint %}
+
+You can extract the built-in static resources to the `statics` directory by starting Cloudreve with the `eject` command line parameter.
+
+```bash
+./cloudreve -eject
+```