!3648 为适配上网要求修改节点链接，补充website缺失节点。不涉及翻译。

Merge pull request !3648 from liyan/master

!3648 为适配上网要求修改节点链接，补充website缺失节点。不涉及翻译。
Merge pull request !3648 from liyan/master
e8136c5e · openharmony_ci · Gitee · 5355677c · e18b9e17 · e8136c5e
9 changed file
--- a/en/device-dev/quick-start/quickstart-ide-lite-overview.md
+++ b/en/device-dev/quick-start/quickstart-ide-lite-overview.md
@@ -12,7 +12,7 @@ To accommodate different developer habits, OpenHarmony provides two modes for ge
 - Installation package mode: Dependency download and installation as well as building operations are performed using commands. Burning and running are performed in DevEco Device Tool.
  OpenHarmony also provides the [Docker environment](../get-code/gettools-acquire.md), which can significantly simplify the environment configuration before compilation. You can build your source code in the Docker environment if you are more accustomed to using the installation package mode.

-This document exemplifies how to use the IDE mode. For details about the installation package mode, see [Getting Started with Mini and Small Systems (Installation Package Mode)](../quick-start/quickstart-lite-package-directory.md).
+This document exemplifies how to use the IDE mode. For details about the installation package mode, see [Getting Started with Mini and Small Systems (Installation Package Mode)](../quick-start/quickstart-lite-overview.md).


 ## Development Environment
@@ -28,7 +28,7 @@ This document describes how to develop OpenHarmony in the Windows+Ubuntu environ

 ## Development Boards

-In this document, two development board models are used as examples: Hi3861 and Hi3516D V300. For details about these development boards, see [Appendix](../quick-start/quickstart-ide-lite-board-introduction.md). You can purchase the development board as required.
+In this document, two development board models are used as examples: Hi3861 and Hi3516D V300. For details about these development boards, see [Appendix](../quick-start/quickstart-ide-lite-introduction-hi3861.md). You can purchase the development board as required.


 ## Development Process

--- a/en/device-dev/quick-start/quickstart-lite-overview.md
+++ b/en/device-dev/quick-start/quickstart-lite-overview.md
@@ -15,7 +15,7 @@ To accommodate different developer habits, OpenHarmony provides two modes for ge
 - Installation package mode: Dependency download and installation as well as building operations are performed using commands. Burning and running are performed in DevEco Device Tool. OpenHarmony also provides the [Docker environment](../get-code/gettools-acquire.md), which can significantly simplify the environment configuration before compilation. You can build your source code in the Docker environment if you are more accustomed to using the installation package mode.


-This document exemplifies how to use the installation package mode. For details about the IDE mode, see [Getting Started with Mini and Small Systems (IDE Mode)](../quick-start/quickstart-lite-ide-directory.md).
+This document exemplifies how to use the installation package mode. For details about the IDE mode, see [Getting Started with Mini and Small Systems (IDE Mode)](../quick-start/quickstart-ide-lite-overview.md).


 ## Development Environment
@@ -31,7 +31,7 @@ This document describes how to develop OpenHarmony in the Windows+Ubuntu environ

 ## Development Boards

-In this document, two development board models are used as examples: Hi3861 and Hi3516D V300. For details about these development boards, see [Appendix](../quick-start/quickstart-lite-board-introduction.md). You can purchase the development board as required.
+In this document, two development board models are used as examples: Hi3861 and Hi3516D V300. For details about these development boards, see [Appendix](../quick-start/quickstart-lite-introduction-hi3861.md). You can purchase the development board as required.


 ## Development Process

--- a/en/device-dev/quick-start/quickstart-standard-overview.md
+++ b/en/device-dev/quick-start/quickstart-standard-overview.md
@@ -12,7 +12,7 @@ To accommodate different developer habits, OpenHarmony provides two modes for ge
 - Installation package mode: Dependency download and installation as well as building operations are performed using commands. Burning and running are performed in DevEco Device Tool.
  OpenHarmony also provides the [Docker environment](../get-code/gettools-acquire.md), which can significantly simplify the environment configuration before compilation. You can build your source code in the Docker environment if you are more accustomed to using the installation package mode.

-This document exemplifies how to use the installation package mode. For details about the IDE mode, see [Getting Started with Standard System (IDE Mode)](../quick-start/quickstart-standard-ide-directory.md).
+This document exemplifies how to use the installation package mode. For details about the IDE mode, see [Getting Started with Standard System (IDE Mode)](../quick-start/quickstart-ide-standard-overview.md).


 ## Development Environment
@@ -28,7 +28,7 @@ This document describes how to develop OpenHarmony in the Windows+Ubuntu environ

 ## Development Boards

-In this document, two development board models are used as examples: Hi3516D V300 and RK3516. For details about these development boards, see [Appendix](../quick-start/quickstart-standard-board-introduction.md). You can purchase the development board as required.
+In this document, two development board models are used as examples: Hi3516D V300 and RK3516. For details about these development boards, see [Appendix](../quick-start/quickstart-standard-board-introduction-hi3516.md). You can purchase the development board as required.


 ## Development Process

--- a/en/device-dev/website.md
+++ b/en/device-dev/website.md
@@ -21,7 +21,6 @@
            - [Burning](quick-start/quickstart-ide-lite-steps-hi3516-burn.md)
            - [Running](quick-start/quickstart-ide-lite-steps-hi3516-running.md)
    - Appendix
-        - Introduction to Development Boards
        - [Introduction to the Hi3861 Development Board](quick-start/quickstart-ide-lite-introduction-hi3861.md)
        - [Introduction to the Hi3516 Development Board](quick-start/quickstart-ide-lite-introduction-hi3516.md)
  - Getting Started with Mini and Small Systems (Installation Package Mode)
@@ -69,7 +68,6 @@
            - [Burning](quick-start/quickstart-ide-standard-running-rk3568-burning.md)
            - [Running](quick-start/quickstart-ide-standard-running-rk3568-running.md)
    - Appendix
-        - Introduction to Development Boards
        - [Introduction to the Hi3516 Development Board](quick-start/quickstart-ide-standard-board-introduction-hi3516.md)
        - [Introduction to the RK3568 Development Board](quick-start/quickstart-ide-standard-board-introduction-rk3568.md)
  - Getting Started with Standard System (Installation Package Mode)
@@ -329,40 +327,50 @@
      - [Driver Configuration Management](driver/driver-hdf-manage.md)
      - [HDF Development Example](driver/driver-hdf-sample.md)
    - Platform Driver Development
-      - [ADC](driver/driver-platform-adc-develop.md)
-      - [GPIO](driver/driver-platform-gpio-develop.md)
-      - [HDMI](driver/driver-platform-hdmi-develop.md)
-      - [I2C](driver/driver-platform-i2c-develop.md)
-      - [I3C](driver/driver-platform-i3c-develop.md)
-      - [MIPI DSI](driver/driver-platform-mipidsi-develop.md)
-      - [MMC](driver/driver-platform-mmc-develop.md)
-      - [PWM](driver/driver-platform-pwm-develop.md)
-      - [RTC](driver/driver-platform-rtc-develop.md)
-      - [SDIO](driver/driver-platform-sdio-develop.md)
-      - [SPI](driver/driver-platform-spi-develop.md)
-      - [UART](driver/driver-platform-uart-develop.md)
-      - [Watchdog](driver/driver-platform-watchdog-develop.md)
+      - [ADC](driver-platform-adc-develop.md)
+      - [DAC](driver-platform-dac-develop.md)
+      - [GPIO](driver-platform-gpio-develop.md)
+      - [HDMI](driver-platform-hdmi-develop.md)
+      - [I2C](driver-platform-i2c-develop.md)
+      - [I3C](driver-platform-i3c-develop.md)
+      - [MIPI CSI](driver-platform-mipicsi-develop.md)
+      - [MIPI DSI](driver-platform-mipidsi-develop.md)
+      - [MMC](driver-platform-mmc-develop.md)
+      - [PIN](driver-platform-pin-develop.md)
+      - [PWM](driver-platform-pwm-develop.md)
+      - [Regulator](driver-platform-regulator-develop.md)
+      - [RTC](driver-platform-rtc-develop.md)
+      - [SDIO](driver-platform-sdio-develop.md)
+      - [SPI](driver-platform-spi-develop.md)
+      - [UART](driver-platform-uart-develop.md)
+      - [WatchDog](driver-platform-watchdog-develop.md)
    - Platform Driver Usage
-      - [ADC](driver/driver-platform-adc-des.md)
-      - [GPIO](driver/driver-platform-gpio-des.md)
-      - [HDMI](driver/driver-platform-hdmi-des.md)
-      - [I2C](driver/driver-platform-i2c-des.md)
-      - [I3C](driver/driver-platform-i3c-des.md)
-      - [MIPI DSI](driver/driver-platform-mipidsi-des.md)
-      - [PWM](driver/driver-platform-pwm-des.md)
-      - [RTC](driver/driver-platform-rtc-des.md)
-      - [SDIO](driver/driver-platform-sdio-des.md)
-      - [SPI](driver/driver-platform-spi-des.md)
-      - [UART](driver/driver-platform-uart-des.md)
-      - [Watchdog](driver/driver-platform-watchdog-des.md)
+      - [ADC](driver-platform-adc-des.md)
+      - [DAC](driver-platform-dac-des.md)
+      - [GPIO](driver-platform-gpio-des.md)
+      - [HDMI](driver-platform-hdmi-des.md)
+      - [I2C](driver-platform-i2c-des.md)
+      - [I3C](driver-platform-i3c-des.md)
+      - [MIPI CSI](driver-platform-mipicsi-des.md)
+      - [MIPI DSI](driver-platform-mipidsi-des.md)
+      - [PIN](driver-platform-pin-des.md)
+      - [PWM](driver-platform-pwm-des.md)
+      - [Regulator](driver-platform-regulator-des.md)
+      - [RTC](driver-platform-rtc-des.md)
+      - [SDIO](driver-platform-sdio-des.md)
+      - [SPI](driver-platform-spi-des.md)
+      - [UART](driver-platform-uart-des.md)
+      - [WatchDog](driver-platform-watchdog-des.md)
    - Peripheral Driver Usage
      - [LCD](driver/driver-peripherals-lcd-des.md)
-      - [Touchscreen](driver/driver-peripherals-touch-des.md)
-      - [Sensor](driver/driver-peripherals-sensor-des.md)
+      - [TOUCHSCREEN](driver/driver-peripherals-touch-des.md)
+      - [SENSOR](driver/driver-peripherals-sensor-des.md)
      - [WLAN](driver/driver-peripherals-external-des.md)
-      - [Audio](driver/driver-peripherals-audio-des.md)
+      - [AUDIO](driver/driver-peripherals-audio-des.md)
      - [USB](driver/driver-peripherals-usb-des.md)
-      - [Camera](driver/driver-peripherals-camera-des.md)
+      - [CAMERA](driver/driver-peripherals-camera-des.md)
+      - [Vibrator](driver-peripherals-vibrator-des.md)
+      - [Light](driver-peripherals-light-des.md)
  - Compilation and Building
    - [Building Guidelines for Mini and Small Systems](subsystems/subsys-build-mini-lite.md)
    - [Building Guidelines for Standard Systems](subsystems/subsys-build-standard-large.md)

--- a/zh-cn/device-dev/quick-start/quickstart-ide-lite-overview.md
+++ b/zh-cn/device-dev/quick-start/quickstart-ide-lite-overview.md
@@ -12,7 +12,7 @@ OpenHarmony轻量和小型系统适用于内存较小的IOT设备（参考内存
 - 安装包方式：通过命令行进行编译依赖工具的下载安装，编译操作也通过命令实现。烧录、运行等操作使用IDE。
  OpenHarmony还为开发者提供了[Docker环境](../get-code/gettools-acquire.md)，在很大程度上简化了编译前的环境配置，习惯使用安装包方式的开发者也可以选择Docker环境进行编译 。

-本文采用Deveco Device Tool进行一站式开发介绍，习惯使用命令行的开发者可参考[轻量和小型系统快速入门（安装包方式）](../quick-start/quickstart-lite-package-directory.md)。
+本文采用Deveco Device Tool进行一站式开发介绍，习惯使用命令行的开发者可参考[轻量和小型系统快速入门（安装包方式）](../quick-start/quickstart-lite-overview.md)。


 ## 开发环境
@@ -28,7 +28,7 @@ OpenHarmony轻量和小型系统适用于内存较小的IOT设备（参考内存

 ## 开发板

-本文基于以下两款典型开发板进行开发介绍 ：Hi3861 WLAN模组、Hi3516DV300。开发板的具体外观和规格可参见[本文附录](../quick-start/quickstart-ide-lite-board-introduction.md)，开发者可根据需要自行购买开发板。
+本文基于以下两款典型开发板进行开发介绍 ：Hi3861 WLAN模组、Hi3516DV300。开发板的具体外观和规格可参见[本文附录](../quick-start/quickstart-ide-lite-introduction-hi3861.md)，开发者可根据需要自行购买开发板。


 ## 开发流程

--- a/zh-cn/device-dev/quick-start/quickstart-ide-standard-overview.md
+++ b/zh-cn/device-dev/quick-start/quickstart-ide-standard-overview.md
@@ -7,12 +7,12 @@ OpenHarmony标准系统适用于参考内存≥128MiB的设备。通过本文，

 考虑到开发者的开发习惯，OpenHarmony为开发者提供了以下两种入门指导：

- IDE方式：完全采用IDE（Deveco Device Tool）进行一站式开发，编译依赖工具的安装及编译、烧录、运行都通过IDE进行操作。
+- IDE方式：完全采用IDE（DevEco Device Tool）进行一站式开发，编译依赖工具的安装及编译、烧录、运行都通过IDE进行操作。

 - 安装包方式：通过命令行进行编译依赖工具的下载安装，编译操作也通过命令实现。烧录、运行等操作使用IDE。
  OpenHarmony还为开发者提供了[Docker环境](../get-code/gettools-acquire.md)，在很大程度上简化了编译前的环境配置，习惯使用安装包方式的开发者也可以选择Docker环境进行编译 。

-本文采用Deveco Device Tool进行一站式开发介绍，习惯使用命令行的开发者可参考[标准系统快速入门（安装包方式）](../quick-start/quickstart-standard-package-directory.md)。
+本文采用DevEco Device Tool进行一站式开发介绍，习惯使用命令行的开发者可参考[标准系统快速入门（安装包方式）](../quick-start/quickstart-standard-overview.md)。


 ## 开发环境
@@ -28,7 +28,7 @@ OpenHarmony标准系统适用于参考内存≥128MiB的设备。通过本文，

 ## 开发板

-本文选取了两款典型开发板：Hi3516DV300、RK3568，并基于上述两款开发板进行开发介绍。开发板的具体外观和规格可参见[本文附录](../quick-start/quickstart-standard-board-introduction.md)，开发者可根据需要自行购买开发板。
+本文选取了两款典型开发板：Hi3516DV300、RK3568，并基于上述两款开发板进行开发介绍。开发板的具体外观和规格可参见[本文附录](../quick-start/quickstart-ide-standard-board-introduction-hi3516.md)，开发者可根据需要自行购买开发板。


 ## 开发流程

--- a/zh-cn/device-dev/quick-start/quickstart-lite-overview.md
+++ b/zh-cn/device-dev/quick-start/quickstart-lite-overview.md
@@ -15,7 +15,7 @@ OpenHarmony轻量和小型系统适用于内存较小的IOT设备（参考内存
 - 安装包方式：通过命令行进行编译依赖工具的下载安装，编译操作也通过命令实现。烧录、运行等操作使用IDE。OpenHarmony还为开发者提供了[Docker环境](../get-code/gettools-acquire.md)，在很大程度上简化了编译前的环境配置，习惯使用安装包方式的开发者也可以选择Docker环境进行编译 。


-本文采用安装包方式进行介绍，习惯使用DevEco Device Tool的开发者可参考[轻量与小型系统快速入门（IDE方式）](../quick-start/quickstart-lite-ide-directory.md)。
+本文采用安装包方式进行介绍，习惯使用DevEco Device Tool的开发者可参考[轻量与小型系统快速入门（IDE方式）](../quick-start/quickstart-ide-lite-overview.md)。


 ## 开发环境
@@ -31,7 +31,7 @@ OpenHarmony轻量和小型系统适用于内存较小的IOT设备（参考内存

 ## 开发板

-本文基于以下两款典型开发板进行开发介绍 ：Hi3861 WLAN模组、Hi3516DV300。开发板的具体外观和规格可参见[本文附录](../quick-start/quickstart-lite-board-introduction.md)，开发者可根据需要自行购买开发板。
+本文基于以下两款典型开发板进行开发介绍 ：Hi3861 WLAN模组、Hi3516DV300。开发板的具体外观和规格可参见[本文附录](../quick-start/quickstart-lite-introduction-hi3861.md)，开发者可根据需要自行购买开发板。


 ## 开发流程

--- a/zh-cn/device-dev/quick-start/quickstart-standard-overview.md
+++ b/zh-cn/device-dev/quick-start/quickstart-standard-overview.md
@@ -12,7 +12,7 @@ OpenHarmony标准系统适用于参考内存≥128MiB的设备。通过本文，
 - 安装包方式：通过命令行进行编译依赖工具的下载安装，编译操作也通过命令实现。烧录、运行等操作使用IDE。
  OpenHarmony还为开发者提供了[Docker环境](../get-code/gettools-acquire.md)，在很大程度上简化了编译前的环境配置，习惯使用安装包方式的开发者也可以选择Docker环境进行编译 。

-本文采用安装包方式进行介绍，习惯使用DevEco Device Tool的开发者可参考[标准系统快速入门（IDE方式）](../quick-start/quickstart-standard-ide-directory.md)。
+本文采用安装包方式进行介绍，习惯使用DevEco Device Tool的开发者可参考[标准系统快速入门（IDE方式）](../quick-start/quickstart-ide-standard-overview.md)。


 ## 开发环境
@@ -28,7 +28,7 @@ OpenHarmony标准系统适用于参考内存≥128MiB的设备。通过本文，

 ## 开发板

-本文选取了两款典型开发板：Hi3516DV300、RK3516，并基于上述两款开发板进行开发介绍。开发板的具体外观和规格可参见[本文附录](../quick-start/quickstart-standard-board-introduction.md)，开发者可根据需要自行购买开发板。
+本文选取了两款典型开发板：Hi3516DV300、RK3516，并基于上述两款开发板进行开发介绍。开发板的具体外观和规格可参见[本文附录](../quick-start/quickstart-standard-board-introduction-hi3516.md)，开发者可根据需要自行购买开发板。


 ## 开发流程

--- a/zh-cn/device-dev/website.md
+++ b/zh-cn/device-dev/website.md
@@ -22,7 +22,6 @@
            - [烧录](quick-start/quickstart-ide-lite-steps-hi3516-burn.md)
            - [运行](quick-start/quickstart-ide-lite-steps-hi3516-running.md)
    - 附录
-        - 开发板介绍
        - [Hi3861开发板介绍](quick-start/quickstart-ide-lite-introduction-hi3861.md)
        - [Hi3516开发板介绍](quick-start/quickstart-ide-lite-introduction-hi3516.md)
  - 轻量和小型系统快速入门（安装包方式）
@@ -70,7 +69,6 @@
            - [烧录](quick-start/quickstart-ide-standard-running-rk3568-burning.md)
            - [运行](quick-start/quickstart-ide-standard-running-rk3568-running.md)
    - 附录
-        - 开发板介绍
        - [Hi3516开发板介绍](quick-start/quickstart-ide-standard-board-introduction-hi3516.md)
        - [RK3568开发板介绍](quick-start/quickstart-ide-standard-board-introduction-rk3568.md)
  - 标准系统快速入门（安装包方式）
@@ -95,6 +93,7 @@
        - 开发板介绍
            - [Hi3516开发板介绍](quick-start/quickstart-standard-board-introduction-hi3516.md)
            - [RK3568开发板介绍](quick-start/quickstart-standard-board-introduction-rk3568.md)
+        - [参考信息](quickstart-standard-reference.md)
  - [获取源码](get-code/sourcecode-acquire.md)

 - 兼容性与安全
@@ -343,37 +342,40 @@
      - [配置管理](driver/driver-hdf-manage.md)
      - [HDF开发实例](driver/driver-hdf-sample.md)
    - 平台驱动开发
-      - [ADC](driver/driver-platform-adc-develop.md)
-      - [GPIO](driver/driver-platform-gpio-develop.md)
-      - [HDMI](driver/driver-platform-hdmi-develop.md)
-      - [I2C](driver/driver-platform-i2c-develop.md)
-      - [I3C](driver/driver-platform-i3c-develop.md)
-      - [MIPI-CSI](driver/driver-platform-mipicsi-develop.md)
-      - [MIPI-DSI](driver/driver-platform-mipidsi-develop.md)
-      - [MMC](driver/driver-platform-mmc-develop.md)
-      - [PIN](driver/driver-platform-pin-develop.md)
-      - [PWM](driver/driver-platform-pwm-develop.md)
-      - [REGULATOR](driver/driver-platform-regulator-develop.md)
-      - [RTC](driver/driver-platform-rtc-develop.md)
-      - [SDIO](driver/driver-platform-sdio-develop.md)
-      - [SPI](driver/driver-platform-spi-develop.md)
-      - [UART](driver/driver-platform-uart-develop.md)
-      - [WatchDog](driver/driver-platform-watchdog-develop.md)
+      - [ADC](driver-platform-adc-develop.md)
+      - [DAC](driver-platform-dac-develop.md)
+      - [GPIO](driver-platform-gpio-develop.md)
+      - [HDMI](driver-platform-hdmi-develop.md)
+      - [I2C](driver-platform-i2c-develop.md)
+      - [I3C](driver-platform-i3c-develop.md)
+      - [MIPI CSI](driver-platform-mipicsi-develop.md)
+      - [MIPI DSI](driver-platform-mipidsi-develop.md)
+      - [MMC](driver-platform-mmc-develop.md)
+      - [PIN](driver-platform-pin-develop.md)
+      - [PWM](driver-platform-pwm-develop.md)
+      - [Regulator](driver-platform-regulator-develop.md)
+      - [RTC](driver-platform-rtc-develop.md)
+      - [SDIO](driver-platform-sdio-develop.md)
+      - [SPI](driver-platform-spi-develop.md)
+      - [UART](driver-platform-uart-develop.md)
+      - [WatchDog](driver-platform-watchdog-develop.md)
    - 平台驱动使用
-      - [ADC](driver/driver-platform-adc-des.md)
-      - [GPIO](driver/driver-platform-gpio-des.md)
-      - [HDMI](driver/driver-platform-hdmi-des.md)
-      - [I2C](driver/driver-platform-i2c-des.md)
-      - [I3C](driver/driver-platform-i3c-des.md)
-      - [MIPI-CSI](driver/driver-platform-mipicsi-des.md)
-      - [MIPI-DSI](driver/driver-platform-mipidsi-des.md)
-      - [PWM](driver/driver-platform-pwm-des.md)
-      - [REGULATOR](driver/driver-platform-regulator-des.md)
-      - [RTC](driver/driver-platform-rtc-des.md)
-      - [SDIO](driver/driver-platform-sdio-des.md)
-      - [SPI](driver/driver-platform-spi-des.md)
-      - [UART](driver/driver-platform-uart-des.md)
-      - [WATCHDOG](driver/driver-platform-watchdog-des.md)
+      - [ADC](driver-platform-adc-des.md)
+      - [DAC](driver-platform-dac-des.md)
+      - [GPIO](driver-platform-gpio-des.md)
+      - [HDMI](driver-platform-hdmi-des.md)
+      - [I2C](driver-platform-i2c-des.md)
+      - [I3C](driver-platform-i3c-des.md)
+      - [MIPI CSI](driver-platform-mipicsi-des.md)
+      - [MIPI DSI](driver-platform-mipidsi-des.md)
+      - [PIN](driver-platform-pin-des.md)
+      - [PWM](driver-platform-pwm-des.md)
+      - [Regulator](driver-platform-regulator-des.md)
+      - [RTC](driver-platform-rtc-des.md)
+      - [SDIO](driver-platform-sdio-des.md)
+      - [SPI](driver-platform-spi-des.md)
+      - [UART](driver-platform-uart-des.md)
+      - [WatchDog](driver-platform-watchdog-des.md)
    - 外设驱动使用
      - [LCD](driver/driver-peripherals-lcd-des.md)
      - [TOUCHSCREEN](driver/driver-peripherals-touch-des.md)
@@ -382,6 +384,8 @@
      - [AUDIO](driver/driver-peripherals-audio-des.md)
      - [USB](driver/driver-peripherals-usb-des.md)
      - [CAMERA](driver/driver-peripherals-camera-des.md)
+      - [Vibrator](driver-peripherals-vibrator-des.md)
+      - [Light](driver-peripherals-light-des.md)
  - 编译构建
    - [轻量和小型系统编译构建指导](subsystems/subsys-build-mini-lite.md)
    - [标准系统编译构建指导](subsystems/subsys-build-standard-large.md)