[docs] chore(workflows): Check MkDocs URIs

Author: RomuDeuxfois

.github/workflows/check-mkdocs-uris.yml

@@ -0,0 +1,45 @@
+name: Check MkDocs URIs
+
+on:
+  pull_request:
+  push:
+    branches:
+      - main
+
+jobs:
+  check-mkdocs-uris:
+    name: Validate MkDocs URIs
+    runs-on: ubuntu-latest
+
+    steps:
+      - name: Checkout repository
+        uses: actions/checkout@v4
+
+      - name: Install dependencies
+        run: |
+          python -m pip install --upgrade pip
+          pip install -r requirements.txt
+
+      - name: Disable git-committers plugin in CI
+        # The git-committers plugin is not CI-safe:
+        # it performs GitHub API calls even without an explicit token,
+        # which causes 403 rate-limit errors in GitHub Actions.
+        # We remove the plugin block entirely for CI builds.
+        run: |
+          sed -i '/- git-committers:/,/^[[:space:]]*-[[:space:]]/d' mkdocs.yml
+
+      - name: Check for underscores in MkDocs URIs
+        run: |
+          echo "Checking mkdocs.yml for URIs (use '-' instead of '_')"
+
+          INVALID_PATHS=$(grep '.md' mkdocs.yml | grep '_' | grep -Ev 'pymdownx\.superfences|md_in_html' || true)          
+          
+          if [ -n "$INVALID_PATHS" ]; then
+            echo "❌ Invalid MkDocs URIs detected (use '-' instead of '_'):"
+            echo "$INVALID_PATHS" | sed 's/^/ - /'
+            echo "Required format:"
+            echo "usage/scenarios_and_simulations.md -> usage/scenarios-and-simulations.md"
+            exit 1
+          else
+            echo "✅ All MkDocs URIs are clean (no underscores)."
+          fi

docs/administration/users_and_rbac.md docs/administration/users-and-rbac.mddocs/administration/users_and_rbac.md renamed to docs/administration/users-and-rbac.md

@@ -88,7 +88,7 @@ docker compose up -d
 
 This section provides instructions to install and run a pre-built OpenAEV server with its dependencies. Note that this
 does not cover building from source,
-which you will find in the [Development section](../development/build_from_source.md) instead.
+which you will find in the [Development section](../development/build-from-source.md) instead.
 
 ### Prepare the installation
 

docs/deployment/installation.md

@@ -3,8 +3,8 @@
     Ensure you have followed the steps for installing prerequisites according to your development
     platform of choice:
 
-    * [Linux (Ubuntu used as example)](environment_ubuntu.md)
-    * [Windows](environment_windows.md)
+    * [Linux (Ubuntu used as example)](environment-ubuntu.md)
+    * [Windows](environment-windows.md)
     * MacOS (TBD)
 
 # Building and running from source

docs/development/build_from_source.md docs/development/build-from-source.mddocs/development/build_from_source.md renamed to docs/development/build-from-source.md

@@ -1,6 +1,6 @@
 # Channels
 
-In OpenAEV, Channels represent communication medias with a particular look. They are used to present [web articles or other media contents](media_pressure.md) to Players in a specific way.
+In OpenAEV, Channels represent communication medias with a particular look. They are used to present [web articles or other media contents](media-pressure.md) to Players in a specific way.
 
 It helps give shape to your Scenario context and events.
 
@@ -20,6 +20,6 @@ On the right, a mock up of the overview is displayed to give you the look and fi
 
 A Channel will then be used in Scenario and in Simulation definition. When you create an Article, you have to choose the Channel that will give it an adequate shape.
 
-See [Media pressure](media_pressure.md) page to know how to create and add Articles to your Scenarios.
+See [Media pressure](media-pressure.md) page to know how to create and add Articles to your Scenarios.
 
 ![Channel selection during Article creation](../assets/channel_selection_during_creation.png)

docs/development/environment_ubuntu.md docs/development/environment-ubuntu.mddocs/development/environment_ubuntu.md renamed to docs/development/environment-ubuntu.md

@@ -67,7 +67,7 @@ You can:
 Once defined, a scenario can be turned into a [simulation](simulation.md): a live execution in your environment, either
 one-shot or scheduled regularly.
 
-During simulations, [expectations](injects_and_expectations.md) are validated:
+During simulations, [expectations](injects-and-expectations.md) are validated:
 
 - **Automatically**, via integrations with your stack
 - **Manually**, by observers validating human reactions