Fixed, added titles, typo fixes

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)
@@ -66,16 +64,6 @@ You would start with the local development environment, which is described in th
 
 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
 
@@ -50,26 +48,7 @@ The GitHub action `stride-website-staging-azure` builds the website and deploys
 
 [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.⚠️
-
 **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,3 +1,4 @@
+# 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.
 
 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.
@@ -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**
 

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,4 +1,5 @@
-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.
 
@@ -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)
@@ -58,7 +57,6 @@ Here are the technologies we use to build our website:
 - [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,3 +1,4 @@
+# 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.

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)

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

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/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/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

@@ -47,8 +47,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)
@@ -75,16 +73,6 @@ You would start with the local development environment, which is described in th
 
 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)

en/contributors/website/index.md

@@ -1,6 +1,5 @@
-# Welcome to the Stride Website Wiki.
-
-This wiki serves as a comprehensive guide to help you navigate and contribute to the **Stride website**.
+# 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.
 
@@ -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.
 

en/contributors/website/installation.md

@@ -1,4 +1,4 @@
-# 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.