add launch system page

Signed-off-by: ismetatabay <ismet@leodrive.ai>

docs/how-to-guides/integrating-autoware/launch-autoware/.pages

@@ -1,6 +1,7 @@
 nav:
   - index.md
   - Launch vehicle: vehicle
+  - Launch system: system
   - Launch sensing: sensing
   - Launch localization: localization
   - Launch perception: perception

docs/how-to-guides/integrating-autoware/launch-autoware/index.md

@@ -3,8 +3,8 @@
 This section explains how to run your vehicle with Autoware.
 We will explain how to run and launch autoware with these modules:
 
-- Vehicle
-- System
+- [Vehicle](./vehicle)
+- [System](./system)
 - Map
 - [Sensing](./sensing)
 - [Localization](./localization)

docs/how-to-guides/integrating-autoware/launch-autoware/system/index.md

@@ -0,0 +1,57 @@
+# System Launch Files
+
+## Overview
+
+The Autoware system stacks start
+launching at `autoware_launch.xml` as we mentioned at [Launch Autoware](../index.md) page.
+The `autoware_launch` package includes `tier4_system_component.launch.xml`
+for starting system launch files invocation from `autoware_launch.xml`.
+This diagram describes some of the Autoware system launch files flow at `autoware_launch` and `autoware.universe` packages.
+
+<figure markdown>
+  ![system-launch-flow](images/system_launch_flow.svg){ align=center }
+  <figcaption>
+    Autoware system launch flow diagram
+  </figcaption>
+</figure>
+
+!!! note
+
+    The Autoware project is a large project.
+    Therefore, as we manage the Autoware project, we utilize specific
+    arguments in the launch files.
+    ROS 2 offers an argument-overriding feature for these launch files.
+    Please refer to [the official ROS 2 launch documentation](https://docs.ros.org/en/humble/Tutorials/Intermediate/Launch/Using-ROS2-Launch-For-Large-Projects.html#parameter-overrides) for further information.
+    For instance,
+    if we define an argument at the top-level launch,
+    it will override the value on lower-level launches.
+
+As described in the flow diagram of the system launch pipeline,
+the `system.launch.xml` from the `tier4_system_launch` package directly launches the following packages:
+
+- [system_monitor](https://autowarefoundation.github.io/autoware.universe/main/system/system_monitor/)
+- [component_interface_tools](https://autowarefoundation.github.io/autoware.universe/main/common/component_interface_tools/)
+- [component_state_monitor](https://autowarefoundation.github.io/autoware.universe/main/system/component_state_monitor/)
+- [system_error_monitor](https://autowarefoundation.github.io/autoware.universe/main/system/system_error_monitor/)
+- [emergency_handler](https://autowarefoundation.github.io/autoware.universe/main/system/emergency_handler/)
+- [duplicated_node_checker](https://autowarefoundation.github.io/autoware.universe/main/system/duplicated_node_checker/)
+- [mrm_comfortable_stop_operator](https://autowarefoundation.github.io/autoware.universe/main/system/mrm_comfortable_stop_operator/)
+- [mrm_emergency_stop_operator](https://autowarefoundation.github.io/autoware.universe/main/system/mrm_emergency_stop_operator/)
+- [dummy_diag_publisher](https://autowarefoundation.github.io/autoware.universe/main/system/dummy_diag_publisher/)
+
+We don't have many modification options here,
+but you can change your system_error_monitor parameter file path.
+For example,
+you can run autoware with the following command line arguments
+if you want to change your system_error_monitor.param.yaml file path:
+
+```bash
+ros2 launch autoware_launch autoware.launch.xml ... system_error_monitor_param_path:=<YOUR-SYSTEM-ERROR-PARAM-PATH> ...
+```
+
+Or you can change it on your `tier4_system_component.launch.xml` launch file:
+
+```diff
+- <arg name="system_error_monitor_param_path" default="$(find-pkg-share autoware_launch)/config/..."/>
++ <arg name="system_error_monitor_param_path" default="<YOUR-SYSTEM-ERROR-PARAM-PATH>"/>
+```

docs/how-to-guides/integrating-autoware/launch-autoware/vehicle/index.md

@@ -25,7 +25,7 @@ the Autoware vehicle launch file flow within the `autoware_launch` and `autoware
     if we define an argument at the top-level launch,
     it will override the value on lower-level launches.
 
-We don't have many modification options here, you can disable vehicle_interface launching.
+We don't have many modification options here, but you can disable vehicle_interface launching.
 For example,
 if you want
 to run robot_state_publisher but not `vehicle_interface` you can run autoware with the following command line arguments:
@@ -37,6 +37,6 @@ ros2 launch autoware_launch autoware.launch.xml ... launch_vehicle_interface:=fa
 Or you can change it on your `autoware.launch.xml` launch file:
 
 ```diff
-- <arg name="launch_vehicle_interface" default="true" description="launch sensing driver"/>
-+ <arg name="launch_vehicle_interface" default="false" description="launch sensing driver"/>
+- <arg name="launch_vehicle_interface" default="true" description="launch vehicle interface"/>
++ <arg name="launch_vehicle_interface" default="false" description="launch vehicle interface"/>
 ```