chore: Fix documentation links to ensure correct file extensions and improve clarity

- Updated links in alerts_troubleshooting.md, alert.md, and other files to include the correct .md extension for consistency.
- Adjusted API endpoint formatting in proposals and howtos for better readability.
- Ensured all references to configuration steps and troubleshooting guides are accurate and up-to-date.

Signed-off-by: Gabryel Nóbrega <[email protected]>

Author: see7e

.github/workflows/docs-test.yml

@@ -44,7 +44,7 @@ jobs:
       - name: Verify build output
         run: |
           cd docusaurus/
-          test -d build-test && echo "✅ Build successful"
+          test -d build && echo "✅ Build successful"
 
   markdown-lint:
     name: Markdown Format Check

docusaurus/package.json

@@ -13,8 +13,8 @@
     "write-translations": "docusaurus write-translations",
     "write-heading-ids": "docusaurus write-heading-ids",
     "test": "node test.js",
-    "build:test": "docusaurus build --dev --no-minify --out-dir ./build-test",
-    "check-links": "lychee ./build_test/**/*.html --exclude-mail --exclude './**/proposal/**'"
+    "build:test": "docusaurus build --dev --no-minify --out-dir ./build",
+    "check-links": "lychee ./build/**/*.html --exclude-mail --exclude './**/proposal/**'"
   },
   "dependencies": {
     "@docusaurus/core": "3.7.0",

docusaurus/sidebars.js

@@ -14,7 +14,7 @@
 /** @type {import('@docusaurus/plugin-content-docs').SidebarsConfig} */
 const sidebars = {
   // By default, Docusaurus generates a sidebar from the docs folder structure
-  tutorialSidebar: [{type: 'autogenerated', dirName: '.'}],
+  versionSidebar: [{type: 'autogenerated', dirName: '.'}],
 
   // But you can create a sidebar manually
   /*

docusaurus/versioned_docs/version-1.0.0/lte/config_agw.md

@@ -11,10 +11,10 @@ original_id: config_agw
 Before beginning to configure your Magma Access Gateway, you will need to make
 sure that it is running all services without crashing. You will also need a
 working Orchestrator setup. Please follow the instructions in
-"[Deploying Orchestrator](../orc8r/deploy_intro)" for a
+"[Deploying Orchestrator](../orc8r/deploy_intro.md)" for a
 successful Orchestrator installation.
 
-You also should have completed all the steps in "[Access Gateway Setup (On Bare Metal)](setup_deb)".
+You also should have completed all the steps in "[Access Gateway Setup (On Bare Metal)](setup_deb.md)".
 For this part, we strongly recommend that you SSH into the AGW box from a host
 machine instead of using the AGW directly.
 

docusaurus/versioned_docs/version-1.0.0/lte/enodebd.md

@@ -7,8 +7,8 @@ original_id: enodebd
 # eNodeB Configuration
 ## Prerequisites
 
-Make sure you follow the instructions in "[Deploying Orchestrator](../orc8r/deploy_intro)" for successful
-installation of Orchestrator and the instructions in "[AGW Configuration](config_agw)" to provision and
+Make sure you follow the instructions in "[Deploying Orchestrator](../orc8r/deploy_intro.md)" for successful
+installation of Orchestrator and the instructions in "[AGW Configuration](config_agw.md)" to provision and
 configure your Access Gateway (AGW).
 
 ## S1 interface

docusaurus/versioned_docs/version-1.0.X/lte/config_agw.md

@@ -11,10 +11,10 @@ original_id: config_agw
 Before beginning to configure your Magma Access Gateway, you will need to make
 sure that it is running all services without crashing. You will also need a
 working Orchestrator setup. Please follow the instructions in
-"[Deploying Orchestrator](../orc8r/deploy_intro)" for a
+"[Deploying Orchestrator](../orc8r/deploy_intro.md)" for a
 successful Orchestrator installation.
 
-You also should have completed all the steps in "[Access Gateway Setup (On Bare Metal)](setup_deb)".
+You also should have completed all the steps in "[Access Gateway Setup (On Bare Metal)](setup_deb.md)".
 For this part, we strongly recommend that you SSH into the AGW box from a host
 machine instead of using the AGW directly.
 

docusaurus/versioned_docs/version-1.0.X/lte/enodebd.md

@@ -7,8 +7,8 @@ original_id: enodebd
 # eNodeB Configuration
 ## Prerequisites
 
-Make sure you follow the instructions in "[Deploying Orchestrator](../orc8r/deploy_intro)" for successful
-installation of Orchestrator and the instructions in "[AGW Configuration](config_agw)" to provision and
+Make sure you follow the instructions in "[Deploying Orchestrator](../orc8r/deploy_intro.md)" for successful
+installation of Orchestrator and the instructions in "[AGW Configuration](config_agw.md)" to provision and
 configure your Access Gateway (AGW).
 
 ## S1 interface

docusaurus/versioned_docs/version-1.1.X/faq/magma_faq.md

@@ -76,7 +76,7 @@ This section lists some of the commonly asked questions related to Magma operati
   - Login to Gateway, then run `sudo checkin_cli.py`.
 
 ### Where can I find API endpoint?
-  - If you have followed the [install guide](../orc8r/deploy_install), it'll be at `https://api.youdomain.com/apidocs/v1/` (the trailing slash is important).
+  - If you have followed the [install guide](../orc8r/deploy_install.md), it'll be at `https://api.youdomain.com/apidocs/v1/` (the trailing slash is important).
   - You will need to load the `admin_operator.pfx` certificate into your keychain/browser, otherwise, API access will be blocked.
 
 ### How can I use Swagger UI to trigger API request?

docusaurus/versioned_docs/version-1.1.X/lte/config_agw.md

@@ -11,10 +11,10 @@ original_id: config_agw
 Before beginning to configure your Magma Access Gateway, you will need to make
 sure that it is running all services without crashing. You will also need a
 working Orchestrator setup. Please follow the instructions in
-"[Deploying Orchestrator](../orc8r/deploy_intro)" for a
+"[Deploying Orchestrator](../orc8r/deploy_intro.md)" for a
 successful Orchestrator installation.
 
-You also should have completed all the steps in "[Access Gateway Setup (On Bare Metal)](setup_deb)".
+You also should have completed all the steps in "[Access Gateway Setup (On Bare Metal)](setup_deb.md)".
 For this part, we strongly recommend that you SSH into the AGW box from a host
 machine instead of using the AGW directly.
 

docusaurus/versioned_docs/version-1.1.X/lte/dev_notes.md

@@ -14,7 +14,7 @@ continues to grow.
 ## Configuration/system settings
 
 If you have a gateway running in a VM (as described in the [Quick Start
-Guide](../basics/quick_start_guide)), the `magma` directory is shared between
+Guide](../basics/quick_start_guide.md)), the `magma` directory is shared between
 the guest and host machine, so changes made on either system reflect on the
 other.  Exceptions to this rule are the systemd unit files and python scripts.
 Changes to these files on the guest or host need to be manually synced.
@@ -73,7 +73,7 @@ To connect a physical eNodeB to the gateway VM:
 3. In gateway VM, modify the `nat_iface` in `/etc/magma/pipelined.yml` from
 `eth2` to `eth0`. Restart all services.
 4. In the gateway VM, follow the steps in [EnodeB
-Configuration](enodebd#basic-troubleshooting). Make sure the `earfcn` set in the
+Configuration](./enodebd.md#basic-troubleshooting). Make sure the `earfcn` set in the
 enodebd section of `gateway.mconfig` is the one that is supported by the eNodeB
 under consideration.
 
@@ -113,7 +113,7 @@ created by the MME service. The Mme service creates a new log file with name
 
 Many services have a command line interface (CLI) that can be used for
 debugging and configuration. Check the [AGW
-Readme](readme_agw.md#command-line-interfaces) for more details.
+Readme]((./readme_agw.md#command-line-interfaces) for more details.
 
 ### Analyzing raw network packets
 
@@ -166,7 +166,7 @@ dependent on are already running. Follow the steps below:
 ### Checking Redis entries for stateless services
 
 When the services are running in stateless mode, as described in [Testing
-stateless Access Gateway](s1ap_tests#testing-stateless-access-gateway), you can
+stateless Access Gateway](./s1ap_tests.md#testing-stateless-access-gateway), you can
 connect to the redis service with `redis-cli -p 6380`. Then on the shell, you
 can list all the keys with `KEYS *`. The keys for state follow the pattern
 `<IMSI>:<Service/MME task>`. For example: