Fix links

SimonDarksideJ · web-flow · commit f3c151ec449e · 2024-08-03T14:58:30.000+01:00
diff --git a/articles/getting_started/1_setting_up_your_development_environment_windows.md b/articles/getting_started/1_setting_up_your_development_environment_windows.md
@@ -15,7 +15,7 @@ Alternatively, you can use [JetBrains Rider](https://www.jetbrains.com/rider/) o
 
 Before using MonoGame, you will need to install [Visual Studio 2022](https://visualstudio.microsoft.com/vs/)
 
-When installing Visual Studio, the following workloads are required depending on your desired [target platform(s)](../platforms.md):
+When installing Visual Studio, the following workloads are required depending on your desired [target platform(s)](./platforms.md):
 
 * Mandatory for all platforms:
   * **.Net desktop development**
diff --git a/articles/getting_started/2_creating_a_new_project_netcore.md b/articles/getting_started/2_creating_a_new_project_netcore.md
@@ -27,14 +27,14 @@ For example:
 dotnet new mgdesktopgl -o MyGame
 ```
 
-> To know which platform identifier (short name) to use for your project, please refer to [Target Platforms](../platforms.md), or type the following command into the command prompt to list the installed templates and their corresponding short names:
+> To know which platform identifier (short name) to use for your project, please refer to [Target Platforms](./platforms.md), or type the following command into the command prompt to list the installed templates and their corresponding short names:
 > 
 > ```
 > dotnet new -l
 > ```
 
 Once created, you can open your code editor of choice in the new folder and begin editing.
 
-> To run your project, check the instructions for [packaging your game](../packaging_games.md) to build the executable using the .NET tooling.
+> To run your project, check the instructions for [packaging your game](./packaging_games.md) to build the executable using the .NET tooling.
 
 **Next up:** [Understanding the code](3_understanding_the_code.md)
diff --git a/articles/getting_started/4_adding_content.md b/articles/getting_started/4_adding_content.md
@@ -11,7 +11,7 @@ This tutorial will go over adding content such as images or sounds to your game.
 
 ## MonoGame Content Builder Tool (MGCB Editor)
 
-This tutorial assumes that you are using Visual Studio 2022 with its MonoGame extension installed. If you are not using the extension, you will need to manually install and use the [MGCB Editor](../tools/mgcb_editor.md).
+This tutorial assumes that you are using Visual Studio 2022 with its MonoGame extension installed. If you are not using the extension, you will need to manually install and use the [MGCB Editor](./tools/mgcb_editor.md).
 
 > This is technically optional, since you can edit the .mgcb files manually if you wish, but the editor is highly recommended for ease of use.
 
@@ -29,7 +29,7 @@ Now open up your game project and look at the Solution Explorer window. Expand t
 
 You should now see the MGCB Editor window open up. If a text file opens instead, then right-click on **Content.mgcb** and select **Open With**, then select **MGCB Editor** in the list, click **Set as Default** and then click **OK**, then try again.
 
-> If you do not see the **MGCB Editor** option when you right-click and select **Open With**, then please review the [Tools documentation](../tools/index.md) for installing the MGCB Editor tool for your operating system.
+> If you do not see the **MGCB Editor** option when you right-click and select **Open With**, then please review the [Tools documentation](./tools/index.md) for installing the MGCB Editor tool for your operating system.
 
 ![MGCB Editor](images/3_mgcb_editor_tool.png)
 
diff --git a/articles/getting_started/content_pipeline/using_mgcb_editor.md b/articles/getting_started/content_pipeline/using_mgcb_editor.md
@@ -5,7 +5,7 @@ description: Learn how to use the MGCB Editor to organize and build content for
 
 # Using MGCB Editor
 
-The [MGCB Editor](../tools/mgcb_editor.md) is used to organize and build content for use with MonoGame. It is accessed by double-clicking a "**.mgcb**" file from within the Visual Studio solution explorer (providing that you installed [MonoGame's Visual Studio extension](../getting_started/1_setting_up_your_development_environment_windows.md)).
+The [MGCB Editor](../tools/mgcb_editor.md) is used to organize and build content for use with MonoGame. It is accessed by double-clicking a "**.mgcb**" file from within the Visual Studio solution explorer (providing that you installed [MonoGame's Visual Studio extension](../1_setting_up_your_development_environment_windows.md)).
 
 Alternatively, you can build it [directly from source](https://github.com/MonoGame/MonoGame/tree/develop/Tools/MonoGame.Content.Builder.Editor) if needed.
 
diff --git a/articles/migration/migrate_38.md b/articles/migration/migrate_38.md
@@ -7,7 +7,7 @@ description: A guide on migrating a MonoGame v3.8.0 project to the current versi
 
 Migrating from 3.8.0 should be straightforward for most platforms.
 
-The major difference is that 3.8.1 now requires .NET 6 and Visual Studio 2022. You can follow the [environment setup tutorial](getting_started/index.md) to make sure that you are not missing any components.
+The major difference is that 3.8.1 now requires .NET 6 and Visual Studio 2022. You can follow the [environment setup tutorial](../getting_started/index.md) to make sure that you are not missing any components.
 
 The MGCB Editor is no longer a global .NET tool and we recommend that you use the new Visual Studio 2022 extension which helps with accessing it without the need of CLI commands.
 
diff --git a/articles/migration/migrate_xna.md b/articles/migration/migrate_xna.md
@@ -22,7 +22,7 @@ MonoGame is API compatible with [XNA 4.0](https://docs.microsoft.com/en-us/previ
 MonoGame does not use the legacy fxc compiler for effects that XNA used. Instead, MonoGame uses the DX11 compiler.
 The way MonoGame handles shaders imposes some restrictions and causes some caveats in what is and is not supported.
 
-This is all documented in the [custom effects](content_pipeline/custom_effects.md) documentation page.
+This is all documented in the [custom effects](../getting_started/content_pipeline/custom_effects.md) documentation page.
 
 ## Half pixel offset
 
diff --git a/articles/toc.yml b/articles/toc.yml
@@ -37,35 +37,35 @@
   - name: Tools
     items:
     - name: Introduction
-      href: tools/index.md
+      href: getting_started/tools/index.md
     - name: MGCB
-      href: tools/mgcb.md
+      href: getting_started/tools/mgcb.md
     - name: MGCB Editor
-      href: tools/mgcb_editor.md
+      href: getting_started/tools/mgcb_editor.md
     - name: MGFXC
-      href: tools/mgfxc.md
+      href: getting_started/tools/mgfxc.md
   - name: Content Pipeline
     items:
     - name: Introduction
-      href: content_pipeline/index.md
+      href: getting_started/content_pipeline/index.md
     - name: Why use the Content Pipeline
-      href: content_pipeline/why_content_pipeline.md
+      href: getting_started/content_pipeline/why_content_pipeline.md
     - name: Using MGCB Editor
-      href: content_pipeline/using_mgcb_editor.md
+      href: getting_started/content_pipeline/using_mgcb_editor.md
     - name: Custom Effects
-      href: content_pipeline/custom_effects.md
+      href: getting_started/content_pipeline/custom_effects.md
     - name: TrueType fonts
-      href: content_pipeline/adding_ttf_fonts.md
+      href: getting_started/content_pipeline/adding_ttf_fonts.md
     - name: Localization
-      href: content_pipeline/localization.md
+      href: getting_started/content_pipeline/localization.md
 - name: Migration
   items:
   - name: Migrating from XNA
-    href: migrate_xna.md
+    href: migration/migrate_xna.md
   - name: Migrating from 3.7
-    href: migrate_37.md
+    href: migration/migrate_37.md
   - name: Migrating from 3.8.0
-    href: migrate_38.md
+    href: migration/migrate_38.md
 - name: Samples and Demos
   href: samples.md
 - name: Community Tutorials
diff --git a/articles/whats_new.md b/articles/whats_new.md
@@ -16,11 +16,11 @@ We now support [.NET 6](https://docs.microsoft.com/en-us/dotnet/core/introductio
 
 ## Visual Studio 2022 extension
 
-MonoGame 3.8.1 now comes with an optional Visual Studio extension which will install all the MonoGame project templates and will allow for quick access to the [MGCB Editor](./tools/mgcb_editor.md).
+MonoGame 3.8.1 now comes with an optional Visual Studio extension which will install all the MonoGame project templates and will allow for quick access to the [MGCB Editor](./getting_started/tools/mgcb_editor.md).
 
 This extension is available for Visual Studio 2022, and Visual Studio 2022 for Mac.
 
-If you are migrating from 3.8.0 it is recommended to uninstall the existing global MGCB .NET tools. It would be a good idea to review the [Migrating from 3.8.0](migrate_38.md) documentation, as there are changes to how 3.8.1 works with the .NET tools and the new extension.
+If you are migrating from 3.8.0 it is recommended to uninstall the existing global MGCB .NET tools. It would be a good idea to review the [Migrating from 3.8.0](./migration/migrate_38.md) documentation, as there are changes to how 3.8.1 works with the .NET tools and the new extension.
 
 ## Visual Studio 2019 and prior are no longer supported
 
@@ -40,6 +40,6 @@ This is motivated by the fact that 32bit players are nearly extinct (less than 0
 
 ## Apple silicon (M1+) support
 
-Games built using the ```DesktopGL``` [platform](./platforms.md) and targeting ```osx-arm64``` will now run natively on Apple silicon without Rosetta emulation.
+Games built using the ```DesktopGL``` [platform](./getting_started/platforms.md) and targeting ```osx-arm64``` will now run natively on Apple silicon without Rosetta emulation.
 
-**However**, it is not yet possible to use the [MGCB](./tools/mgcb.md) or the [MGCB Editor](./tools/mgcb_editor.md) on Apple silicon, unless you are running the ```osx-x64``` variant of the .NET SDK (and therefore using Rosetta emulation). We are working toward resolving this inconvenience.
+**However**, it is not yet possible to use the [MGCB](./getting_started/tools/mgcb.md) or the [MGCB Editor](./getting_started/tools/mgcb_editor.md) on Apple silicon, unless you are running the ```osx-x64``` variant of the .NET SDK (and therefore using Rosetta emulation). We are working toward resolving this inconvenience.
