autowarefoundation · xmfcx · Dec 11, 2025 · Dec 11, 2025
diff --git a/docs/.pages b/docs/.pages
@@ -10,5 +10,4 @@ nav:
   - Reference HW: reference-hw
   - contributing
   - datasets
-  - support
-  - Competitions: autoware-competitions
+  - community
diff --git a/docs/community/.pages b/docs/community/.pages
@@ -0,0 +1,3 @@
+nav:
+  - support
+  - Competitions: autoware-competitions
diff --git a/docs/autoware-competitions/.pages → docs/community/autoware-competitions/.pages b/docs/autoware-competitions/.pages → docs/community/autoware-competitions/.pages
diff --git a/...itions/images/ai_challenge2023-racing.jpg → ...itions/images/ai_challenge2023-racing.jpg b/...itions/images/ai_challenge2023-racing.jpg → ...itions/images/ai_challenge2023-racing.jpg
diff --git a/...competitions/images/ai_challenge_2023.png → ...competitions/images/ai_challenge_2023.png b/...competitions/images/ai_challenge_2023.png → ...competitions/images/ai_challenge_2023.png
diff --git a/...itions/images/autoware_challenge_2023.png → ...itions/images/autoware_challenge_2023.png b/...itions/images/autoware_challenge_2023.png → ...itions/images/autoware_challenge_2023.png
diff --git a/docs/autoware-competitions/index.md → .../community/autoware-competitions/index.md b/docs/autoware-competitions/index.md → .../community/autoware-competitions/index.md
diff --git a/docs/support/.pages → docs/community/support/.pages b/docs/support/.pages → docs/community/support/.pages
diff --git a/docs/support/docs-guide.md → docs/community/support/docs-guide.md b/docs/support/docs-guide.md → docs/community/support/docs-guide.md
diff --git a/docs/support/index.md → docs/community/support/index.md b/docs/support/index.md → docs/community/support/index.md
diff --git a/docs/support/support-guidelines.md → docs/community/support/support-guidelines.md b/docs/support/support-guidelines.md → docs/community/support/support-guidelines.md
@@ -5,7 +5,7 @@ This page explains the support mechanisms we provide.
 !!! warning
 
     Before asking for help, search and read this documentation site carefully.
-    Also, follow the [discussion guidelines](../contributing/discussion-guidelines/index.md) for discussions.
+    Also, follow the [discussion guidelines](../../contributing/discussion-guidelines/index.md) for discussions.
 
 Choose appropriate resources depending on what kind of help you need and read the detailed description in the sections below.
 
@@ -63,7 +63,7 @@ If you are unsure how to create a discussion, refer to the [GitHub Docs on creat
 Visit them and see if there is any information related to your problem.
 
 Note that the documentation sites aren't always up-to-date and perfect.
-If you find out that some information is wrong, unclear, or missing in Autoware docs, feel free to submit a pull request following the [contribution guidelines](../contributing/index.md).
+If you find out that some information is wrong, unclear, or missing in Autoware docs, feel free to submit a pull request following the [contribution guidelines](../../contributing/index.md).
 
 ## GitHub Discussions
 
@@ -120,7 +120,7 @@ When creating a new issue, use the following guidelines:
 When you start working on an issue, link the related pull request to the issue by mentioning the issue number.
 This helps maintain a clear and traceable development history.
 
-For more details, see the [Pull Request Guidelines page](../contributing/pull-request-guidelines/index.md).
+For more details, see the [Pull Request Guidelines page](../../contributing/pull-request-guidelines/index.md).
 
 !!! warning
 

diff --git a/docs/support/troubleshooting/.pages → .../community/support/troubleshooting/.pages b/docs/support/troubleshooting/.pages → .../community/support/troubleshooting/.pages
diff --git a/docs/support/troubleshooting/index.md → ...ommunity/support/troubleshooting/index.md b/docs/support/troubleshooting/index.md → ...ommunity/support/troubleshooting/index.md
@@ -112,7 +112,7 @@
 colcon build --symlink-install --cmake-args -DCMAKE_BUILD_TYPE=Release
 ```
 
-If the error is not resolved, remove `src/` and update your workspace according to installation type ([Docker](../../installation/autoware/docker-installation.md#update-the-workspace) / [source](../../installation/autoware/source-installation.md#how-to-update-a-workspace)).
+If the error is not resolved, remove `src/` and update your workspace according to installation type ([Docker](../../../installation/autoware/docker-installation.md#update-the-workspace) / [source](../../../installation/autoware/source-installation.md#how-to-update-a-workspace)).
 
 !!! Warning
 
@@ -192,7 +192,7 @@
 
 ### Map does not display when running the Planning Simulator
 
-When running the Planning Simulator, the most common reason for the map not being displayed in RViz is because [the map path has not been specified correctly in the launch command](../../demos/planning-simulation.md#lane-driving-scenario). You can confirm if this is the case by searching for `Could not find lanelet map under {path-to-map-dir}/lanelet2_map.osm` errors in the log.
+When running the Planning Simulator, the most common reason for the map not being displayed in RViz is because [the map path has not been specified correctly in the launch command](../../../demos/planning-simulation.md#lane-driving-scenario). You can confirm if this is the case by searching for `Could not find lanelet map under {path-to-map-dir}/lanelet2_map.osm` errors in the log.
 
 Another possible reason is that map loading is taking a long time due to poor DDS performance. For this, please visit the [Performance Troubleshooting](performance-troubleshooting.md) page.
 
@@ -208,7 +208,7 @@
 ```

 In this state, when a died process occurs when you run the autoware again, a core file will be created.
 Remeber to remove the size limit of the core file.

 ```bash
 ulimit -c unlimited

diff --git a/...leshooting/performance-troubleshooting.md → ...leshooting/performance-troubleshooting.md b/...leshooting/performance-troubleshooting.md → ...leshooting/performance-troubleshooting.md
@@ -32,9 +32,9 @@ If you get the error message `selected interface "{your-interface-name}" is not
 
 #### Solution
 
-Follow [DDS settings for ROS 2 and Autoware](../../installation/additional-settings-for-developers/network-configuration/dds-settings.md)
+Follow [DDS settings for ROS 2 and Autoware](../../../installation/additional-settings-for-developers/network-configuration/dds-settings.md)
 
-Especially the [Enable `multicast` on `lo`](../../installation/additional-settings-for-developers/network-configuration/enable-multicast-for-lo.md) section.
+Especially the [Enable `multicast` on `lo`](../../../installation/additional-settings-for-developers/network-configuration/enable-multicast-for-lo.md) section.
 
 ### Check the compilation flags
 
@@ -93,7 +93,7 @@ If you are using a different DDS middleware, we might not have official support
 
 Add `export RMW_IMPLEMENTATION=rmw_cyclonedds_cpp` as a separate line in you `~/.bashrc` file.
 
-More details in: [CycloneDDS Configuration](../../installation/additional-settings-for-developers/network-configuration/dds-settings.md#cyclonedds-configuration)
+More details in: [CycloneDDS Configuration](../../../installation/additional-settings-for-developers/network-configuration/dds-settings.md#cyclonedds-configuration)
 
 #### Check if the CycloneDDS is configured correctly
 
@@ -117,7 +117,7 @@ This should print the `.xml` file on the terminal.
 
 ##### Solution
 
-Follow [CycloneDDS Configuration](../../installation/additional-settings-for-developers/network-configuration/dds-settings.md#cyclonedds-configuration) and make sure:
+Follow [CycloneDDS Configuration](../../../installation/additional-settings-for-developers/network-configuration/dds-settings.md#cyclonedds-configuration) and make sure:
 
 - you have `export CYCLONEDDS_URI=file:///absolute_path_to_your/cyclonedds.xml` as a line on your `~/.bashrc` file.
 - you have the `cyclonedds.xml` with the configuration provided in the documentation.
@@ -126,11 +126,11 @@ Follow [CycloneDDS Configuration](../../installation/additional-settings-for-dev
 
 ##### Diagnosis
 
-[Validate the sysctl settings](../../installation/additional-settings-for-developers/network-configuration/dds-settings.md#validate-the-sysctl-settings)
+[Validate the sysctl settings](../../../installation/additional-settings-for-developers/network-configuration/dds-settings.md#validate-the-sysctl-settings)
 
 ##### Solution
 
-[Tune system-wide network settings](../../installation/additional-settings-for-developers/network-configuration/dds-settings.md#tune-system-wide-network-settings)
+[Tune system-wide network settings](../../../installation/additional-settings-for-developers/network-configuration/dds-settings.md#tune-system-wide-network-settings)
 
 ### Check if localhost only communication for DDS is enabled
 
@@ -154,11 +154,11 @@ Run:
 cat ${CYCLONEDDS_URI#file://}
 ```
 
-And it should return [DDS settings for ROS 2 and Autoware: CycloneDDS Configuration](../../installation/additional-settings-for-developers/network-configuration/dds-settings.md#cyclonedds-configuration) this file.
+And it should return [DDS settings for ROS 2 and Autoware: CycloneDDS Configuration](../../../installation/additional-settings-for-developers/network-configuration/dds-settings.md#cyclonedds-configuration) this file.
 
 #### Solution
 
-Follow [DDS settings for ROS 2 and Autoware: Enable localhost-only communication](../../installation/additional-settings-for-developers/network-configuration/dds-settings.md#enable-localhost-only-communication).
+Follow [DDS settings for ROS 2 and Autoware: Enable localhost-only communication](../../../installation/additional-settings-for-developers/network-configuration/dds-settings.md#enable-localhost-only-communication).
 
 Also make sure the following returns an empty line:
 

diff --git a/docs/contributing/documentation-guidelines/index.md b/docs/contributing/documentation-guidelines/index.md
@@ -8,7 +8,7 @@ Examples of small changes include:
 
 - Fixing spelling or grammatical mistakes
 - Fixing broken links
-- Making an addition to an existing, well-defined page, such as the [Troubleshooting](../../support/troubleshooting/index.md) guide.
+- Making an addition to an existing, well-defined page, such as the [Troubleshooting](../../community/support/troubleshooting/index.md) guide.
 
 Examples of larger changes include:
 

diff --git a/docs/contributing/index.md b/docs/contributing/index.md
@@ -40,7 +40,7 @@ If you are new to open source projects, we recommend reading GitHub's [How to Co
 
 ## How can I get help?
 
-Do not open issues for general support questions as we want to keep GitHub issues for confirmed bug reports. Instead, open a discussion in the Q&A category. For more details on the support mechanisms for Autoware, refer to the [Support guidelines](../support/index.md).
+Do not open issues for general support questions as we want to keep GitHub issues for confirmed bug reports. Instead, open a discussion in the Q&A category. For more details on the support mechanisms for Autoware, refer to the [Support guidelines](../community/support/index.md).
 
 !!! note
 

diff --git a/docs/contributing/pull-request-guidelines/code-owners.md b/docs/contributing/pull-request-guidelines/code-owners.md
@@ -44,7 +44,7 @@ If your PR hasn't been reviewed:
 
 - 🏹 **Directly Address Code Owners**: Comment on the PR to alert the owners.
 - ⏳ **Follow Up After a Week**: If unreviewed after a week, add a comment under the PR and tag the `@autoware-maintainers`.
-- 📢 **Escalate if Necessary**: If your requests continue to go unanswered, you may escalate the issue by posting a message in the [Autoware Discord channel](../../support/support-guidelines.md#discord) 🚨. Remember, maintainers often juggle numerous responsibilities, so patience is appreciated🙇.
+- 📢 **Escalate if Necessary**: If your requests continue to go unanswered, you may escalate the issue by posting a message in the [Autoware Discord channel](../../community/support/support-guidelines.md#discord) 🚨. Remember, maintainers often juggle numerous responsibilities, so patience is appreciated🙇.
 
 ### PR author is the only code owner
 

diff --git a/docs/contributing/pull-request-guidelines/index.md b/docs/contributing/pull-request-guidelines/index.md
@@ -10,7 +10,7 @@ Use this workflow as a reference when you contribute to Autoware.
 
 1. Create an issue.
    - Discuss the approaches to the issue with maintainers.
-   - Confirm the [support guidelines](../../support/support-guidelines.md) before creating an issue.
+   - Confirm the [support guidelines](../../community/support/support-guidelines.md) before creating an issue.
    - Follow the [discussion guidelines](../discussion-guidelines/index.md) when you discuss with other contributors.
 2. Create a fork repository. (for the first time only)
 3. Write code in your fork repository according to the approach agreed upon in the issue.

diff --git a/docs/index.md b/docs/index.md
@@ -32,9 +32,9 @@ Autoware is the world’s leading open-source project dedicated to autonomous dr
 
 **Datasets**: The [Datasets](datasets/index.md) pages are a crucial resource for anyone working with Autoware. Here, you'll find a collection of datasets that are compatible with Autoware, providing real-world scenarios and data to test and refine your autonomous driving solutions.
 
-**Support**: As you dive deeper into Autoware, you might encounter challenges or have questions. The [Support](support/index.md) section is designed to assist you in these moments. This area includes FAQs, community forums, and contact information for getting help with Autoware. It's also a great place to connect with other Autoware users and contributors, sharing experiences and solutions.
+**Support**: As you dive deeper into Autoware, you might encounter challenges or have questions. The [Support](community/support/index.md) section is designed to assist you in these moments. This area includes FAQs, community forums, and contact information for getting help with Autoware. It's also a great place to connect with other Autoware users and contributors, sharing experiences and solutions.
 
-**Competitions**: The [Competitions](autoware-competitions/index.md) pages are where excitement meets innovation. Autoware regularly hosts or participates in various competitions and challenges, providing a platform for users to test their skills, showcase their work, and contribute to the community. These competitions range from local to global scale, offering opportunities for both beginners and experts to engage and excel. Stay updated with upcoming events and take part in the advancement of autonomous driving technologies.
+**Competitions**: The [Competitions](community/autoware-competitions/index.md) pages are where excitement meets innovation. Autoware regularly hosts or participates in various competitions and challenges, providing a platform for users to test their skills, showcase their work, and contribute to the community. These competitions range from local to global scale, offering opportunities for both beginners and experts to engage and excel. Stay updated with upcoming events and take part in the advancement of autonomous driving technologies.
 
 ### Contribute and Collaborate
 

diff --git a/docs/installation/autoware/docker-installation.md b/docs/installation/autoware/docker-installation.md
@@ -133,7 +133,7 @@ Open AD Kit provides different deployment options for Autoware, so that you can
    colcon build --symlink-install --cmake-args -DCMAKE_BUILD_TYPE=Release
    ```
 
-   If there is any build issue, refer to [Troubleshooting](../../support/troubleshooting/index.md#build-issues).
+   If there is any build issue, refer to [Troubleshooting](../../community/support/troubleshooting/index.md#build-issues).
 
 ### Update the Workspace
 

diff --git a/docs/installation/autoware/source-installation.md b/docs/installation/autoware/source-installation.md
@@ -33,7 +33,7 @@ sudo apt-get -y install git
    ./setup-dev-env.sh
    ```
 
-   If you encounter any build issues, please consult the [Troubleshooting](../../support/troubleshooting/index.md#build-issues) section for assistance.
+   If you encounter any build issues, please consult the [Troubleshooting](../../community/support/troubleshooting/index.md#build-issues) section for assistance.
 
 !!! info
 
@@ -119,7 +119,7 @@ sudo apt-get -y install git
    colcon build --symlink-install --cmake-args -DCMAKE_BUILD_TYPE=Release
    ```
 
-   If there is any build issue, refer to [Troubleshooting](../../support/troubleshooting/index.md#build-issues).
+   If there is any build issue, refer to [Troubleshooting](../../community/support/troubleshooting/index.md#build-issues).
 
 5. Follow the steps in [Network Configuration](../../installation/additional-settings-for-developers/network-configuration/index.md) before running Autoware.
 

diff --git a/docs/installation/index.md b/docs/installation/index.md
@@ -33,7 +33,7 @@ For details of how to enable object detection and traffic light detection/classi
 ## Installing Autoware
 
 There are five ways to set up Autoware. Choose one according to your preference. Autoware Core contains only the essential Autoware packages, and Autoware Universe contains the full Autoware stack.
-For installation types, see the subsections below. If any issues occur during installation, refer to the [Support page](../support/index.md).
+For installation types, see the subsections below. If any issues occur during installation, refer to the [Support page](../community/support/index.md).
 
 - [Autoware Core Docker installation](autoware/core-docker-installation.md)
 - [Autoware Core source installation](autoware/core-source-installation.md)