lots of broken links restored

en/contributors/documentation/content.md

@@ -19,7 +19,7 @@
 
 If you want to contribute and update the website, please follow the instructions below.
 
-Small updates can be done directly in the GitHub web interface, for bigger updates the local development environment is required, which is described in the [Installation](Installation) section.
+Small updates can be done directly in the GitHub web interface, for bigger updates the local development environment is required, which is described in the [Installation](installation.md) section.
 
 You can use any text editor to make changes. If you are using **Visual Studio**, you can open `Stride.Docs.sln` solution file in the root of the repository and start making your updates directly from this IDE.
 
@@ -60,7 +60,7 @@ We can define bigger updates as changes to the design of the website, where you
 - Update docfx version
 - Update layouts
 
-You would start with the local development environment, which is described in the [Installation](Installation) section.
+You would start with the local development environment, which is described in the [Installation](installation.md) section.
 
 Then you would make your changes and test them locally. Once you are happy with the result, you can create a pull request to merge your changes into the `master` branch.
 

en/contributors/documentation/deployment.md

@@ -46,7 +46,7 @@ The `web.config` file is used to configure IIS, including:
 
 The GitHub action `stride-website-staging-azure` builds the website and deploys it to Azure Web Apps.
 
-[Step-by-Step Deployment Guide for Azure Web Apps (Windows) with IIS and Stride Website](Deployment-Azure).
+[Step-by-Step Deployment Guide for Azure Web Apps (Windows) with IIS and Stride Website](deployment-azure.md).
 
 **Recommendation**
 

en/contributors/documentation/docfx.md

@@ -1,5 +1,5 @@
 # DocFX
-[docfx](https://www.11ty.dev/) is a static site generator that uses JavaScript as its templating language. It is a very powerful tool that allows us to create a website with a lot of flexibility and customization. It is also very easy to use and learn. This section will cover the basics of Eleventy configuration on the Stride website. Creating and updating the content is described in our [Content](Content) section.
+[docfx](https://www.11ty.dev/) is a static site generator that uses JavaScript as its templating language. It is a very powerful tool that allows us to create a website with a lot of flexibility and customization. It is also very easy to use and learn. This section will cover the basics of Eleventy configuration on the Stride website. Creating and updating the content is described in our [Content](content.md) section.
 
 We used to use **Jekyll** as our static site generator, but we decided to switch to Eleventy because of its flexibility and ease of use. We also wanted to use a tool that is more widely used and supported, which is why we decided to switch to Eleventy.
 
@@ -14,7 +14,7 @@ We used to use **Jekyll** as our static site generator, but we decided to switch
   - [Creating Custom Shortcodes and Includes](#creating-custom-shortcodes-and-includes)
   
 # Packages and Dependencies
-Eleventy is a **Node.js** application. Please follow our [Installation](Installation) guide to install Node.js and all the required dependencies.
+Eleventy is a **Node.js** application. Please follow our [installation](installation.md) guide to install Node.js and all the required dependencies.
 
 Packages we currently use:
 
@@ -40,7 +40,7 @@ The Eleventy configuration is located in the `.eleventy.js` file at the root of
 - pass through files - Files that are copied to the output folder without any processing
 - custom collections - Custom collections used in the templates like `tagList` and `yearList`
 - filters - Custom filters used in the templates
-- custom shortcodes - Custom [shortcodes](Content#shortcodes-and-includes) used in the templates, pages or blog posts.
+- custom shortcodes - Custom [shortcodes](content.md#shortcodes-and-includes) used in the templates, pages or blog posts.
 
 The file is well-commented and should be self-explanatory. If you need to add a new configuration, please follow the existing structure and include a comment to explain the new configuration.
 
@@ -107,7 +107,7 @@ The folder structure is crucial for Eleventy, as it determines the output of the
 - `web.Release.config` - Configuration file for Windows ASP.NET Core deployment
 
 
-**Note:** This project includes ASP.NET Core solution and files, as they can be used seamlessly with Eleventy. Read more about this in our [Installation](Installation#asp-net-core) section.
+**Note:** This project includes ASP.NET Core solution and files, as they can be used seamlessly with Eleventy. Read more about this in our [Installation](installation.md#asp-net-core.md) section.
 
 
 # Layouts
@@ -129,7 +129,7 @@ Some includes are used solely by the layouts, while others are used by the conte
 
 ## Creating Custom Shortcodes and Includes
 
-If you need to create a custom shortcode or include, please follow the existing structure and [include a comment](Content#shortcodes-and-includes) to explain the new shortcode or include.
+If you need to create a custom shortcode or include, please follow the existing structure and [include a comment](content.md#shortcodes-and-includes) to explain the new shortcode or include.
 
 The shortcodes are defined in the `.eleventy.js` file, while the includes are located in the `/_includes` folder.
 

en/contributors/documentation/index.md

@@ -1,7 +1,7 @@
 # Contributing to documentation
 This documentation serves as a comprehensive guide to help you navigate and contribute to the **Stride Docs** website.
 
-If you're looking to make minor changes, such as adding or updating a manual, tutorial or page, or fixing a typo, feel free to jump straight to the [Content Updates](content#content-updates) section.
+If you're looking to make minor changes, such as adding or updating a manual, tutorial or page, or fixing a typo, feel free to jump straight to the [Content Updates](content.md#content-updates) section.
 
 For more extensive updates 🤯🤦‍♂️ or for a deeper understanding of the docs website project, we recommend exploring all the sections provided. Happy browsing and contributing!
 
@@ -46,14 +46,14 @@ Here are the technologies we use to build our website:
     - [Adding a New Language](new-language.md#adding-a-new-language)
 - [Roadmap](roadmap.md)
 - [DocFX](docfx.md)
-    - [Packages and Dependencies](eleventy.md#packages-and-dependencies)
-    - [Configuration](eleventy.md#configuration)
-    - [Global Data](eleventy.md#global-data)
-    - [Folder Structure](eleventy.md#folder-structure)
-    - [Layouts](eleventy.md#layouts)
-    - [Includes](eleventy.md#includes)
-    - [Advanced Topics](eleventy.md#advanced-topics)
-        - [Creating Custom Shortcodes and Includes](eleventy.md#creating-custom-shortcodes-and-includes)
+    - [Packages and Dependencies](docfx.md#packages-and-dependencies)
+    - [Configuration](docfx.md#configuration)
+    - [Global Data](docfx.md#global-data)
+    - [Folder Structure](docfx.md#folder-structure)
+    - [Layouts](docfx.md#layouts)
+    - [Includes](docfx.md#includes)
+    - [Advanced Topics](docfx.md#advanced-topics)
+        - [Creating Custom Shortcodes and Includes](docfx.md#creating-custom-shortcodes-and-includes)
 - [Deployment](deployment.md)
     - [GitHub Pages](deployment.md#github-pages)
     - [Azure Web Apps](deployment.md#azure-web-apps)

en/contributors/documentation/installation.md

@@ -1,7 +1,7 @@
 # Local installation
 This guide will walk you through the steps to install the Stride Docs website on your local machine for development purposes. Although we use the Windows operating system for development, the steps should be similar for other operating systems.
 
-[Minor updates](Content#small-updates) can be made directly on GitHub. However, for [more significant updates](Content#major-updates) that affect multiple pages, we recommend using a local development environment so you can see the impact of your changes beforehand. This is because we use the **docfx** static site generator, and in some cases, all pages need to be regenerated. This approach helps you assess your changes before submitting a pull request.
+[Minor updates](content.md#small-updates) can be made directly on GitHub. However, for [more significant updates](content.md#major-updates) that affect multiple pages, we recommend using a local development environment so you can see the impact of your changes beforehand. This is because we use the **docfx** static site generator, and in some cases, all pages need to be regenerated. This approach helps you assess your changes before submitting a pull request.
 
 This guide assumes you have a basic understanding of the technologies used in the Stride docs website.
 
@@ -90,4 +90,4 @@ We've created a PowerShell script [BuildDocs.ps1](https://github.com/stride3d/st
 1. 🔄 After saving the updated file, you will need to rebuild the documentation by running the script again
 1. 😃 Happy coding!
 
-Let's [update the content](Content) now!
+Let's [update the content](content.md) now!

en/contributors/documentation/troubleshooting-and-faq.md

@@ -16,6 +16,6 @@ Any issue should be added to Stride Website [GitHub issues](https://github.com/s
 
 **Q:** I just want to fix a typo in a post. Do I need to follow your installation steps?
 
-**A:** *No, you can fix the typo directly on the GitHub website. However, you will still need to fork the repo, make your update on the main branch or a new branch, and then create a pull request. You can follow this guide for [minor updates](Content#small-updates).*
+**A:** *No, you can fix the typo directly on the GitHub website. However, you will still need to fork the repo, make your update on the main branch or a new branch, and then create a pull request. You can follow this guide for [minor updates](content.md#small-updates).*
 
 

en/contributors/donate.md

@@ -8,24 +8,3 @@ We gather funding through a website called [OpenCollective](https://opencollecti
 Stride's Open Collective hosts different '[Projects](https://opencollective.com/stride3d/projects)' — think of them as funding goals for specific features or contributions. Each project typically has a related Github ticket for more details on what's required for its development. If you're interested in working on or contributing to a particular feature, please reply in the thread and mention @stride3d/stride-contributors.
 
 
-## Bug bounties
-If you are a developer with experience in C#, rendering techniques, or game development, we want to hire you! We have allocated funds from supporters on [OpenCollective](https://opencollective.com/stride3d) and will pay you for your work on certain issues.
-
-You can find [issues with bounties here](https://github.com/stride3d/stride/labels/bounty)
-
-If you are interested in tackling one of those issues:
-- Reply in the thread and tag @stride3d/stride-contributors
-- We'll get back to you and reserve that issue to your name.
-- You can then create a new pull request and we'll review it.
-- Once merged in you will receive 60% of the bounty and the other 40% on the next official release of the engine.
-
-
-### Payment info
-Stride uses the [Open source collective](https://opencollective.com/opensource) as our Fiscal host which approves the payments. They process payouts twice weekly, once they have been approved by the admins of the Collective. They make payments via PayPal and Wise, and can only make payouts to countries served by these payment processors.
-
-You can go to the specific bug bounty on Stride's [Open Collective](https://opencollective.com/stride3d) for payment:
-
-![getting-paid-bounty](https://user-images.githubusercontent.com/3499539/158011382-732c2448-8368-418f-9eae-7713ea7b349d.gif)
-
-
-

en/contributors/engine/architecture/build-details.md

@@ -19,7 +19,7 @@ Also, we use `RuntimeIdentifiers` to select graphics platform. [MSBuild.Sdk.Extr
 
 Since we want to package tools (i.e. GameStudio, ConnectionRouter, CompilerApp) with a package that contains only the executable with proper dependencies to other NuGet runtime packages, we use NuGet API to resolve assemblies at runtime.
 
-The code responsible for this is located in [Stride.NuGetResolver](../sources/shared/Stride.NuGetResolver).
+The code responsible for this is located in [Stride.NuGetResolver](../../../sources/shared/Stride.NuGetResolver).
 
 Later, we might want to take advantage of .NET Core dependency resolving to do that natively. Also, we might want to use actual project information/dependencies to resolve to different runtime assemblies and better support plugins.
 
@@ -38,12 +38,12 @@ For example, assuming version `4.1.3.135+gfa0f5cc4`:
 Assembly processor is run by both Game and Stride targets.
 
 It performs various transforms to the compiled assemblies:
-* Generate [DataSerializer](../sources/common/core/Stride.Core/Serialization/DataSerializer.cs) serialization code (and merge it back in assembly using IL-Repack)
-* Generate [UpdateEngine](../sources/engine/Stride.Engine/Updater/UpdateEngine.cs) code
+* Generate [DataSerializer](../../../../../stride/sources/core/Stride.Core/Serialization/DataSerializer.cs) serialization code (and merge it back in assembly using IL-Repack)
+* Generate [UpdateEngine](../../../../../stride/sources/engine/Stride.Engine/Updater/UpdateEngine.cs) code
 * Scan for types or attributes with `[ScanAssembly]` to quickly enumerate them without needing `Assembly.GetTypes()`
-* Optimize calls to [Stride.Core.Utilities](../sources/common/core/Stride.Core/Utilities.cs)
-* Automatically call methods tagged with [ModuleInitializer](../sources/common/core/Stride.Core/ModuleInitializerAttribute.cs)
-* Cache lambdas and various other code generation related to [Dispatcher](../sources/common/core/Stride.Core/Threading/Dispatcher.cs)
+* Optimize calls to [Stride.Core.Utilities](../../../../../stride/sources/core/Stride.Core/Utilities.cs)
+* Automatically call methods tagged with [ModuleInitializer](../../../../../stride/sources/core/Stride.Core/ModuleInitializerAttribute.cs)
+* Cache lambdas and various other code generation related to [Dispatcher](../../../../../stride/sources/core/Stride.Core/Threading/Dispatcher.cs)
 * A few other internal tasks
 
 For performance reasons, it is run as a MSBuild Task (avoid reload/JIT-ing). If you wish to make it run the executable directly, set `StrideAssemblyProcessorDev` to `true`.
@@ -66,7 +66,7 @@ By adding a reference to `Stride.Native.targets`, it is easy to build some C/C++
 
 ### Limitations
 
-It seems that using those optimization don't work well with shadow copying and [probing privatePath](https://msdn.microsoft.com/en-us/library/823z9h8w(v=vs.110).aspx). This forces us to copy the `Direct3D11` specific assemblies to the top level `Windows` folder at startup of some tools. This is little bit unfortunate as it seems to disturb the MSBuild assembly searching (happens before `$(AssemblySearchPaths)`). As a result, inside Stride solution it is necessary to explicitely add `<ProjectReference>` to the graphics specific assemblies otherwise wrong ones might be picked up.
+It seems that using those optimization don't work well with shadow copying and [probing privatePath](https://msdn.microsoft.com/en-us/library/823z9h8w(v=vs.110).aspx). This forces us to copy the `Direct3D11` specific assemblies to the top level `Windows` folder at startup of some tools. This is little bit unfortunate as it seems to disturb the MSBuild assembly searching (happens before `$(AssemblySearchPaths)`). As a result, inside Stride solution it is necessary to explicitly add `<ProjectReference>` to the graphics specific assemblies otherwise wrong ones might be picked up.
 
 This will require further investigation to avoid this copying at all.
 

en/contributors/engine/bug-bounties.md

@@ -1,10 +1,12 @@
 # Bug bounties
 If you are a developer with solid experience in C#, rendering techniques, or game development, we want to hire you! We have allocated funds from supporters on [OpenCollective](https://opencollective.com/stride3d) and will pay you for your work on certain issues.
 
-You can find [issues with bounties here](https://github.com/stride3d/stride/labels/bounty). If you see a different bug that you would like to tackle and you want to know if it is eligible for a bug bounty, you are also more than welcome to reach out to the core contributors on [Discord](https://discord.gg/f6aerfE) and [Github Discussion](https://github.com/stride3d/stride/discussions).
+You can find [issues with bounties here](https://github.com/stride3d/stride/labels/bounty). 
+
+If the issue you want to work on doesn't have a bounty associated to it, feel free to get in touch with us by creating a new issue or adding your message to an existing one, tagging us with `@stride3d`/`@stride-contributors` and sharing your email address or Discord handle. You can also do it directly through Discord by sending a message in `#github-pr-and-issues` with the `@Developer` tag.
 
 If you are interested in tackling one of those issues:
-- Reply in the thread and tag @stride3d/stride-contributors
+- Reply in the thread and tag `@stride3d`/`@stride-contributors`
 - We'll get back to you and reserve that issue to your name.
 - You can then create a new pull request and we'll review it.
 - Once merged in you will receive 60% of the bounty and the other 40% on the next official release of the engine.

en/contributors/engine/index.md

@@ -1,10 +1,10 @@
 # Contribute to Stride engine
 Here you can find various pages describing building the source locally for different systems. You can also find information about stride's architecture.
 
-### [Contribute code](contribute-engine.md)
+### [Contribute code](contribute-code.md)
 Want to help out fixing bugs or making new features? Check out how you can do so.
 
-### [Bug bounties](contribute-engine.md)
+### [Bug bounties](bug-bounties.md)
 Here you can learn about the process on our bug bounty process.
 
 ### [Building on Windows](building-source-windows.md)

en/contributors/toc.yml

@@ -13,8 +13,6 @@
     href: engine/bug-bounties.md
   - name: Building source on Windows
     href: engine/building-source-windows.md
-#  - name: Building source on Linux
-#    href: engine/building-source-linux.md
   - name: Localization
     href: engine/localization.md
   - name: Hot reloading editor shaders
@@ -60,6 +58,7 @@
 - name: 🌐️ Contribute to the website
   expanded: false
   href: website/index.md
+  items:
     - name: Installation
       href: website/installation.md
     - name: Website Content

en/contributors/website/content.md

@@ -24,7 +24,7 @@
 
 If you want to contribute and update the website, please follow the instructions below.
 
-Small updates can be done directly in the GitHub web interface, for bigger updates the local development environment is required, which is described in the [Installation](Installation) section.
+Small updates can be done directly in the GitHub web interface, for bigger updates the local development environment is required, which is described in the [Installation](installation.md) section.
 
 You can use any text editor to make changes. If you are using **Visual Studio**, you can open `Stride.Web.sln` solution file in the root of the repository and start making your updates directly from this IDE.
 
@@ -69,7 +69,7 @@ We can define bigger updates as changes to the design of the website, where you
 - Update Bootstrap library or other libraries
 - Update layouts
 
-You would start with the local development environment, which is described in the [Installation](Installation) section.
+You would start with the local development environment, which is described in the [Installation](installation.md) section.
 
 Then you would make your changes and test them locally. Once you are happy with the result, you can create a pull request to merge your changes into the `master` branch.
 

en/contributors/website/deployment.md

@@ -24,7 +24,7 @@ The [web.config](https://github.com/stride3d/stride-website/blob/master/web.conf
 
 The GitHub action [stride-website-release-azure.yml](https://github.com/stride3d/stride-website/blob/master/.github/workflows/stride-website-release-azure.yml) builds the website and deploys it to Azure Web Apps.
 
-[Step-by-Step Deployment Guide for Azure Web Apps (Windows) with IIS and Stride Website](Deployment-Azure).
+[Step-by-Step Deployment Guide for Azure Web Apps (Windows) with IIS and Stride Website](deployment-azure.md).
 
 # Deployment To Wiki
 

en/contributors/website/eleventy.md

@@ -1,5 +1,5 @@
 # Eleventy site generator
-[Eleventy](https://www.11ty.dev/) is a static site generator that uses JavaScript as its templating language. It is a very powerful tool that allows us to create a website with a lot of flexibility and customization. It is also very easy to use and learn. This section will cover the basics of Eleventy configuration on the Stride website. Creating and updating the content is described in our [Content](Content) section.
+[Eleventy](https://www.11ty.dev/) is a static site generator that uses JavaScript as its templating language. It is a very powerful tool that allows us to create a website with a lot of flexibility and customization. It is also very easy to use and learn. This section will cover the basics of Eleventy configuration on the Stride website. Creating and updating the content is described in our [Content](content.md) section.
 
 We used to use **Jekyll** as our static site generator, but we decided to switch to Eleventy because of its flexibility and ease of use. We also wanted to use a tool that is more widely used and supported, which is why we decided to switch to Eleventy.
 
@@ -16,7 +16,7 @@ We used to use **Jekyll** as our static site generator, but we decided to switch
   
 # Packages and Dependencies
 
-Eleventy is a **Node.js** application. Please follow our [Installation](Installation) guide to install Node.js and all the required dependencies.
+Eleventy is a **Node.js** application. Please follow our [Installation](installation.md) guide to install Node.js and all the required dependencies.
 
 Packages we currently use:
 
@@ -43,7 +43,7 @@ The Eleventy configuration is located in the `.eleventy.js` file at the root of
 - pass through files - Files that are copied to the output folder without any processing
 - custom collections - Custom collections used in the templates like `tagList` and `yearList`
 - filters - Custom filters used in the templates
-- custom shortcodes - Custom [shortcodes](Content#shortcodes-and-includes) used in the templates, pages or blog posts.
+- custom shortcodes - Custom [shortcodes](content.md#shortcodes-and-includes) used in the templates, pages or blog posts.
 
 The file is well-commented and should be self-explanatory. If you need to add a new configuration, please follow the existing structure and include a comment to explain the new configuration.
 
@@ -111,7 +111,7 @@ The folder structure is crucial for Eleventy, as it determines the output of the
 - `web.Release.config` - Configuration file for Windows ASP.NET Core deployment
 
 
-**Note:** This project includes ASP.NET Core solution and files, as they can be used seamlessly with Eleventy. Read more about this in our [Installation](Installation#asp-net-core) section.
+**Note:** This project includes ASP.NET Core solution and files, as they can be used seamlessly with Eleventy. Read more about this in our [Installation](installation.md#aspnet-core) section.
 
 
 # Layouts
@@ -133,7 +133,7 @@ Some includes are used solely by the layouts, while others are used by the conte
 
 ## Creating Custom Shortcodes and Includes
 
-If you need to create a custom shortcode or include, please follow the existing structure and [include a comment](Content#shortcodes-and-includes) to explain the new shortcode or include.
+If you need to create a custom shortcode or include, please follow the existing structure and [include a comment](content.md#shortcodes-and-includes) to explain the new shortcode or include.
 
 The shortcodes are defined in the `.eleventy.js` file, while the includes are located in the `/_includes` folder.
 

en/contributors/website/index.md

@@ -1,7 +1,7 @@
 # Contributing to the Stride website
 This documentation serves as a comprehensive guide to help you navigate and contribute to the **Stride website**.
 
-If you're looking to make minor changes, such as adding or updating a post or page, or fixing a typo, you can jump straight to the [Content Updates](content#content-updates) section.
+If you're looking to make minor changes, such as adding or updating a post or page, or fixing a typo, you can jump straight to the [Content Updates](content.md#content-updates) section.
 
 For more extensive updates 🤯🤦‍♂️ and a deeper understanding of the website project, we recommend exploring all the sections provided. Happy browsing and contributing!
 
@@ -33,7 +33,6 @@ Technologies we use to build our website:
     - [Content Updates](content.md#content-updates)
         - [Small Updates](content.md#small-updates)
         - [Major Updates](content.md#major-updates)
-        - [Updating Wiki](content.md#updating-wiki)
     - [Creating New Post](content.md#creating-new-post)
         - [Post Naming Convention](content.md#post-naming-convention)
         - [Post Front Matter](content.md#post-front-matter)

en/contributors/website/installation.md

@@ -1,7 +1,7 @@
 # Local installation
 This guide will walk you through the steps to install the Stride website on your local machine for development purposes. Although we use the Windows operating system for development, the steps should be similar for other operating systems.
 
-[Minor updates](Content#small-updates) can be made directly on GitHub. However, for [more significant updates](Content#major-updates) that affect multiple pages, we recommend using a local development environment so you can see the impact of your changes beforehand. This is because we use the **Eleventy** static site generator, and in some cases, all pages need to be regenerated. This approach helps you assess your changes before submitting a pull request.
+[Minor updates](content.md#small-updates) can be made directly on GitHub. However, for [more significant updates](content.md#major-updates) that affect multiple pages, we recommend using a local development environment so you can see the impact of your changes beforehand. This is because we use the **Eleventy** static site generator, and in some cases, all pages need to be regenerated. This approach helps you assess your changes before submitting a pull request.
 
 This guide assumes you have a basic understanding of the technologies used in the Stride website.
 
@@ -42,7 +42,7 @@ Before updating the Stride website, ensure you are familiar with the following p
 
 *ToDo: Attach a screenshot of the command line output*
 
-Let's [update the content](Content) now!
+Let's [update the content](content.md) now!
 
 # ASP.NET Core
 

en/contributors/website/troubleshooting-and-faq.md

@@ -16,6 +16,6 @@ Any issue should be added to Stride Website [GitHub issues](https://github.com/s
 
 **Q:** I just want to fix a typo in a post. Do I need to follow your installation steps?
 
-**A:** *No, you can fix the typo directly on the GitHub website. However, you will still need to fork the repo, make your update on the main branch or a new branch, and then create a pull request. You can follow this guide for [minor updates](Content#small-updates).*
+**A:** *No, you can fix the typo directly on the GitHub website. However, you will still need to fork the repo, make your update on the main branch or a new branch, and then create a pull request. You can follow this guide for [minor updates](content.md#small-updates).*
 
 

wiki/Content.md

@@ -30,7 +30,7 @@
 
 If you want to contribute and update the website, please follow the instructions below.
 
-Small updates can be done directly in the GitHub web interface, for bigger updates the local development environment is required, which is described in the [Installation](Installation) section.
+Small updates can be done directly in the GitHub web interface, for bigger updates the local development environment is required, which is described in the [Installation](installation.md) section.
 
 You can use any text editor to make changes. If you are using **Visual Studio**, you can open `Stride.Docs.sln` solution file in the root of the repository and start making your updates directly from this IDE.
 
@@ -71,7 +71,7 @@ We can define bigger updates as changes to the design of the website, where you
 - Update docfx version
 - Update layouts
 
-You would start with the local development environment, which is described in the [Installation](Installation) section.
+You would start with the local development environment, which is described in the [Installation](installation.md) section.
 
 Then you would make your changes and test them locally. Once you are happy with the result, you can create a pull request to merge your changes into the `master` branch.
 

wiki/DocFX.md

@@ -15,7 +15,7 @@ We used to use **Jekyll** as our static site generator, but we decided to switch
   
 # Packages and Dependencies
 
-Eleventy is a **Node.js** application. Please follow our [Installation](Installation) guide to install Node.js and all the required dependencies.
+Eleventy is a **Node.js** application. Please follow our [Installation](installation.md) guide to install Node.js and all the required dependencies.
 
 Packages we currently use:
 

wiki/Home.md

@@ -25,7 +25,7 @@ Here are the technologies we use to build our website:
   - [A Simplified Overview](Understanding-the-Stride-Documentation-Generation-Pipeline#a-simplified-overview)
   - [Docs Build Workflow](Understanding-the-Stride-Documentation-Generation-Pipeline#docs-build-workflow)
   - [Workflow Diagram](Understanding-the-Stride-Documentation-Generation-Pipeline#workflow-diagram)
-- [Installation](Installation)
+- [Installation](installation.md)
   - [Prerequisites](Installation#prerequisites)
   - [Installation Steps](Installation#installation-steps)
   - [Running the Development Server](Installation#running-the-development-server)

wiki/_Sidebar.md

@@ -4,7 +4,7 @@
   - [A Simplified Overview](Understanding-the-Stride-Documentation-Generation-Pipeline#a-simplified-overview)
   - [Docs Build Workflow](Understanding-the-Stride-Documentation-Generation-Pipeline#docs-build-workflow)
   - [Workflow Diagram](Understanding-the-Stride-Documentation-Generation-Pipeline#workflow-diagram)
-- [Installation](Installation)
+- [Installation](installation.md)
   - [Prerequisites](Installation#prerequisites)
   - [Installation Steps](Installation#installation-steps)
   - [Running the Development Server](Installation#running-the-development-server)