Merge pull request #187 from Aggror/contributor-section+wiki

Updates to Contributor section+wiki

README.md

@@ -11,7 +11,7 @@ Welcome to the Stride Docs repository. This repository contains all the source f
 
 ## 🚀 Getting Started
 
-All the information you need to get started with Stride Docs development can be found in the 📚 [Stride Docs Wiki](https://github.com/stride3d/stride-docs/wiki).
+All the information you need to get started with Stride Docs development can be found in the 📚 [Stride Docs](https://doc.stride3d.net/latest/en/contributors/documentation/index.html).
 
 ## 🤝 Contributing
 

en/contributors/documentation/content.md

@@ -1,9 +1,7 @@
-# Documentation Contents
-
+# Documentation content
 - [Content Updates](#content-updates)
   - [Small Updates](#small-updates)
   - [Major Updates](#major-updates)
-  - [Updating Wiki](#updating-wiki)
 - [Manual](#manual)
   - [Creating New Page](#creating-new-manual-page)
 - [Tutorial](#tutorial)
@@ -21,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.
 
@@ -62,20 +60,10 @@ 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.
 
-## Updating Wiki
-
-While wiki pages can be updated directly in the GitHub web interface, this feature is restricted only to contributors who can edit the wiki directly. We have decided to move our wiki pages to a regular folder in this repository called `wiki`, allowing us to use the same process as we do for the website content. If any changes are made directly on the wiki pages, they will be overwritten by the next wiki deployment.
-
-Wiki pages are deployed through a separate GitHub action, `stride-docs-wiki.yml`, which is triggered by updates in the `wiki` folder or can be triggered manually. The `wiki` folder is ignored by the docfx build process, ensuring that the wiki pages are not deployed to the website. Additionally, any pushes to the `wiki` folder will not trigger the website deployment.
-
-You can update the wiki pages as any other content pages, by following the steps in the [Small Updates](#small-updates) section.
-
-⚠️**Important:** If you are updating any headers in the wiki pages, please make sure to update the *Table of Contents* at the top of the page, [Home](Home) page and `_Sidebar.md`. Also, you might need to search for all the links to the updated header and update them as well.
-
 # Manual
 
 These pages contain information about how to use Stride, an open-source C# game engine.

en/contributors/documentation/deployment-azure.md

@@ -1,5 +1,4 @@
-# Table of Contents
-
+# Deployment in Azure
 - [Step-by-Step Guide to Deploying Azure Web Apps (Windows) with IIS](#step-by-step-guide-to-deploying-azure-web-apps-windows-with-iis)
   - [Setting up a new Azure Web App (Windows) with IIS](#setting-up-a-new-azure-web-app-windows-with-iis)
   - [Adjusting the Web App Configuration](#adjusting-the-web-app-configuration)

en/contributors/documentation/deployment.md

@@ -1,11 +1,9 @@
-# Table of Contents
-
+# Deployment
 We tested five different deployment methods and chose Azure Web Apps IIS ASP.NET 4.8.
 
 - [GitHub Pages](#github-pages)
 - [Azure Web Apps](#azure-web-apps)
   - [Deploying with .NET Framework](#deploying-with-net-framework)
-- [Deployment To Wiki](#deployment-to-wiki)
 
 # GitHub Pages
 
@@ -48,28 +46,9 @@ 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).
-
-# Deployment To Wiki
-
-While the GitHub wiki offers a convenient way to document a project, it has some drawbacks, such as not being part of the repository by default and restricting edits to collaborators. To address these issues and allow community editing, we have implemented an alternative approach.
-
-We created a `wiki` folder within the repository, which contains all wiki pages. The GitHub action `stride-web-wiki.yml` deploys the `wiki` folder to the GitHub wiki.
-
-The GitHub action `stride-web-wiki.yml` is triggered when:
-
-1. A push is made to the `master` branch of the `stride-website` repository
-1. The action is manually triggered
-
-You can manually trigger the action by navigating to the **Actions** tab and clicking the **Run workflow** button.
-
-This GitHub action only monitors changes to the `wiki` folder. Any modifications made to the `wiki` folder will be deployed to the GitHub wiki. Note that changes to the `wiki` folder will not trigger other GitHub actions.
-
-We use the [Wiki Page Creator GitHub Action](https://github.com/marketplace/actions/wiki-page-creator-action) to deploy the `wiki` folder to the GitHub wiki.
-
-**Note**: ⚠️ A GitHub personal access token (GH_PAT) is required for authentication. This token is stored as a secret in the repository settings.⚠️
+[Step-by-Step Deployment Guide for Azure Web Apps (Windows) with IIS and Stride Website](deployment-azure.md).
 
 **Recommendation**
 
 1. **ASP.NET 4.8 with IIS** for Staging
-1. **ASP.NET 4.8 with IIS** for Release
+2. **ASP.NET 4.8 with IIS** for Release

en/contributors/documentation/docfx.md

@@ -1,4 +1,5 @@
-[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
+[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.
 
@@ -13,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:
 
@@ -39,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.
 
@@ -80,7 +81,6 @@ The folder structure is crucial for Eleventy, as it determines the output of the
 - `/posts` - Blog posts
 - `/posts/2014-2021` - Old blog posts which are merged to the same output folder as `/posts`
   - this folder is only for convenience to easily access new posts
-- `/wiki` - Excluded from build process, used only for wiki deployment
 
 **Files**
 
@@ -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/documentation-generation-pipeline.md

@@ -1,5 +1,4 @@
-# Table of Contents
-
+# Documentation generation pipeline
 - [Introduction](#introduction)
 - [A Simplified Overview](#a-simplified-overview)
 - [Docs Build Workflow](#docs-build-workflow)

en/contributors/documentation/index.md

@@ -1,6 +1,7 @@
-This documentation serves as a comprehensive guide to help you navigate and contribute to the **Stride Docs** website.
+# 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!
 
@@ -11,7 +12,6 @@ Here are the technologies we use to build our website:
 - [Mustache](https://mustache.github.io/) template engine (docfx dropped Liquid template engine support)
 - Bootstrap
 - Emojis (because why not? 😎)
-- GitHub Wiki
 - HTML, JavaScript, CSS, JSON
 - PowerShell scripts
 - GitHub Actions (CI/CD) - Don't worry, this is already set up, you don't need to worry about it.
@@ -30,7 +30,6 @@ Here are the 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)
     - [Manual](content.md#manual)
       - [Creating New Page](content.md#creating-new-manual-page)
     - [Tutorial](content.md#tutorial)
@@ -47,18 +46,17 @@ 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)
-    - [Deployment To Wiki](deployment.md#deployment-to-wiki)
 - [Troubleshooting and FAQ](troubleshooting-and-faq.md)
     - [Known Issues](troubleshooting-and-faq.md#known-issues)
     - [Common Issues and Solutions](troubleshooting-and-faq.md#common-issues-and-solutions)

en/contributors/documentation/installation.md

@@ -1,6 +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.
 
@@ -89,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/new-language.md

@@ -1,3 +1,6 @@
+# New language
+WIP
+
 This guide will walk you through the steps on contributing a different language for the documentation
 
 # Adding a new language

en/contributors/documentation/roadmap.md

@@ -1,3 +1,4 @@
+# Documentation roadmap
 This is a proposal for our website roadmap and ongoing website development plan.
 
 - Tackle existing issues listed in the [Issues](https://github.com/stride3d/stride-website/issues)

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

@@ -1,5 +1,4 @@
-# Table of Contents
-
+# Troubleshooting and FAQ
 - [Known Issues](#known-issues)
 - [Common Issues and Solutions](#common-issues-and-solutions)
 - [Frequently Asked Questions](#frequently-asked-questions)
@@ -17,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

@@ -1,5 +1,4 @@
 # Build details
-
 This is a technical description what happens in our build and how it is organized. This covers mostly the build architecture of Stride itself.
 
 * [Targets](../Targets) contains the MSBuild target files used by Games
@@ -20,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.
 
@@ -39,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`.
@@ -67,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/architecture/build-pipeline.md

@@ -1,5 +1,4 @@
 # Build pipeline
-
 This document describes the Build pipeline in Stride, its current implementation (and legacy), and the work that should be done to improve it.
 
 ## Terminology

en/contributors/engine/architecture/dependency-graph.md

@@ -1,6 +1,5 @@
 # Dependency graph
 
-
 ### Assemblies
 <img src="../../media/assemblies_stride.svg" class="card-img-top" alt="Assemblies of Stride">
 <br><br>

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/building-source-windows-other-ide.md

@@ -1,6 +1,4 @@
-
-## Build Stride without Visual Studio
-
+## Build Stride without Visual Studio
 1. Install [Visual Studio Build Tools](https://aka.ms/vs/17/release/vs_BuildTools.exe) with the same prerequisites listed [here](building-source-windows.md)
 2. Add MSBuild's directory to your system's *PATH* (ex: `C:\Program Files (x86)\Microsoft Visual Studio\2022\BuildTools\MSBuild\Current\Bin`)
 3. Open a command prompt, point it to a directory and clone Stride to it: `git lfs clone https://github.com/stride3d/stride.git`

en/contributors/engine/building-source-windows.md

@@ -34,7 +34,7 @@ Here are the steps to build Stride with Visual Studio. If you do not have or wan
 Do note that test solutions might fail but it should not prevent you from building `Stride.GameStudio`.
 
 ## Other IDEs
-You are not  required to use Visual Studio to build the Stride engine with Visual Studio. You can also build entirely from command line or other IDE's such as [Rideror Visual Studio Code](building-source-windows-other-ide.md) 
+You are not required to use Visual Studio to build the Stride engine with Visual Studio. You can also build entirely from command line or other IDE's such as [Rider or Visual Studio Code](building-source-windows-other-ide.md) 
 
 
 

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/engine/localization.md

@@ -1,5 +1,4 @@
 # Localization
-
 You can help us translate Stride, by updating existing translations and/or adding new language at https://hosted.weblate.org/projects/stride/
 
 Translation are manually merged back from `weblate` branch to `master` branch.

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
@@ -23,7 +21,7 @@
     href: engine/source-debugging.md
   - name: Visual Studio plugin
     href: engine/visual-studio-plugin.md
-  - name: 🧬️ Architecture
+  - name: 🏗️️ Architecture
     expanded: false
     href: engine/architecture/index.md
     items:
@@ -37,7 +35,7 @@
       href: engine/architecture/dependency-graph.md
     - name: Asset introspection
       href: engine/architecture/build-pipeline.md
-- name: ℹ Contribute to the documentation
+- name: 🎓 Contribute to the documentation
   expanded: false
   href: documentation/index.md
   items:
@@ -47,8 +45,8 @@
     href: Documentation/installation.md
   - name: Content
     href: Documentation/content.md
-  - name: New language
-    href: Documentation/new-language.md
+#  - name: New language
+#    href: Documentation/new-language.md
   - name: Roadmap
     href: Documentation/roadmap.md
   - name: DocFX

en/contributors/ways-to-contribute.md

@@ -1,14 +1,15 @@
 # Ways to contribute
-Stride 3d is a non-profit, community-driven free and open source project.
+
+Stride 3d is a non-profit, community-driven, free and open source project.
 There are no full-time developers dedicated solely to Stride's advancement; instead, the engine progresses through the voluntary contributions of both the core team and the broader community.
 
 In order to thrive, Stride requires the help from other community members. There are various ways you can help:
 
-### Community activity 🤝
+### [Community activity](https://discord.gg/f6aerfE)🤝
 To make Stride3d better, just use it and tell others about it in your blogs, videos, and events. Get involved in discussions on [Discord](https://discord.gg/f6aerfE) and [Github Discussion](https://github.com/stride3d/stride/discussions). Being a user and spreading the word is vital for our engine, as we don't have a big marketing budget and rely on the community to grow.
 
 
-### Make games 🕹️
+### [Make games](https://github.com/stride3d/stride/wiki/Community-Projects) 🕹️
 The best way to promote Stride is by creating a cool demo or, even better, a full game. Having people see and play an actual game made with Stride is the most effective form of advertisement.
 
 
@@ -24,12 +25,12 @@ Making Stride more stable greatly improves usability and user satisfaction. So i
 Contributing to Pull Requests (PRs) is excellent as it enables active participation without local builds. Reviewing and offering feedback in this collaborative process enhances code quality and maintains project standards, fostering a sense of community and knowledge sharing.
 
 
-### [Contribute code](engine/index.md) 
+### [Contribute code](engine/index.md) 🤖
 If you're passionate about C# and want to contribute by building features or fixing bugs in Stride, dive into the source code and get involved!
 Have a look at the Github issues label [Good first issue](https://github.com/stride3d/stride/labels/good%20first%20issue) or funded [Open Collective projects](https://opencollective.com/stride3d/projects)
 
 ### [Contribute to Documentation](documentation/index.md) 🪶
 Enhance the official documentation and tutorials by expanding the manual or creating textual/video guides. Your contributions will greatly improve accessibility and understanding for users.
 
-### [Contribute to Website](website/index.md) 🪶
+### [Contribute to Website](website/index.md) 🌐
 Enhance the official Stride website. Is design more your thing, or do you have an interesting blog post? It will all help us spread the word of Stride.

en/contributors/website/content.md

@@ -1,9 +1,7 @@
 # Website Content
-
 - [Content Updates](#content-updates)
   - [Small Updates](#small-updates)
   - [Major Updates](#major-updates)
-  - [Updating Wiki](#updating-wiki)
 - [Creating New Post](#creating-new-post)
   - [Post Naming Convention](#post-naming-convention)
   - [Post Front Matter](#post-front-matter)
@@ -26,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.
 
@@ -71,20 +69,10 @@ 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.
 
-## Updating Wiki
-
-While wiki pages can be updated directly in the GitHub web interface, this feature is restricted only to contributors who can edit the wiki directly. We have decided to move our wiki pages to a regular folder in this repository called [wiki](https://github.com/stride3d/stride-website/tree/master/wiki), allowing us to use the same process as we do for the website content. If any changes are made directly on the wiki pages, they will be overwritten by the next wiki deployment.
-
-Wiki pages are deployed through a separate GitHub action, `stride-web-wiki.yml`, which is triggered by updates in the `wiki` folder or can be triggered manually. The `wiki` folder is ignored by the Eleventy build process, ensuring that the wiki pages are not deployed to the website. Additionally, any pushes to the `wiki` folder will not trigger the website deployment.
-
-You can update the wiki pages as any other content pages, by following the steps in the [Small Updates](#small-updates) section.
-
-⚠️**Important:** If you are updating any headers in the wiki pages, please make sure to update the *Table of Contents* at the top of the page, [Home](https://github.com/stride3d/stride-website/blob/master/wiki/Home.md) page and [_Sidebar.md](https://github.com/stride3d/stride-website/blob/master/wiki/_Sidebar.md). Also, you might need to search for all the links to the updated header and update them as well.
-
 # Creating New Post
 
 To create a new blog post, you can follow one of these methods:

en/contributors/website/deployment-azure.md

@@ -1,5 +1,4 @@
 # Deployment Azure
-
 - [Step-by-Step Guide to Deploying Azure Web Apps (Windows) with IIS](#step-by-step-guide-to-deploying-azure-web-apps-windows-with-iis)
   - [Setting up a new Azure Web App (Windows) with IIS](#setting-up-a-new-azure-web-app-windows-with-iis)
   - [Adjusting the Web App Configuration](#adjusting-the-web-app-configuration)

en/contributors/website/deployment.md

@@ -1,5 +1,4 @@
-# Table of Contents
-
+# Website deployment
 We tested five different deployment methods (GitHub Pages, Azure Web App Windows/Linux IIS/Kestrel, Azure Static Web Apps) and chose to continue with the existing Azure Web Apps IIS ASP.NET 4.8 infrastructure.
 
 - [Azure Web Apps](#azure-web-apps)
@@ -25,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,8 +1,7 @@
-# Welcome to the Stride Website Wiki.
+# Contributing to the Stride website
+This documentation serves as a comprehensive guide to help you navigate and contribute to the **Stride website**.
 
-This wiki 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!
 
@@ -13,7 +12,6 @@ Technologies we use to build our website:
 - Mainly [Liquid](https://shopify.github.io/liquid/) and a bit Nunjucks (template engines)
 - Bootstrap
 - Font Awesome
-- GitHub Wiki
 - HTML, JavaScript, CSS, SCSS, and JSON
 - GitHub Actions (CI/CD) - Don't worry, this is already set up, you don't need to worry about it.
 
@@ -35,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 @@
-# Installation
+# 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)