feat: Game launcher and docs improvements (#292)

* feat: ClickHandlerComponent.cs - Enhance cube creation logic

- Added a new using directive for `Stride.CommunityToolkit.Mathematics` to access additional mathematical functions.
- Modified the `CreateCube()` method call to utilize `_random.NextPoint()` for generating a random point within a specified bounding box, improving randomness.
- Adjusted the y-coordinate to position the cube at a height of 10 units above the ground.

* refactor: ScreenPositionToWorldPositionRaycast removed

* feat: Profile added

* feat!: ShapeUpdater.cs - Improve debug text positioning

- Added two new constant integer variables: `TextIncrement` set to 16 and `StartTextPositionY` set to 32 for better text positioning in debug output.
- Modified the text position for debug print statements to utilize `StartTextPositionY`, enhancing maintainability and readability.
- Introduced additional debug print statements to provide more context about the application's state, including a message for faster count adjustment with the shift key.
- Updated the wording of the fill mode debug print statement for consistency and clarity.
- Adjusted the vertical positioning of debug print statements to use the new `TextIncrement` variable, facilitating easier layout adjustments.
- Removed an unused closing brace at the end of the file to correct a formatting error.

* refactor: Empty lines removed

* refactor: Code readability improvements

* refactor: Code clean up

* refactor: Update DebugRenderStage organization

- Changed `DebugRenderStage` from an internal enum within `ImmediateDebugRenderFeature` to a standalone internal enum for better organization.
- Removed the `partial` keyword from the `ImmediateDebugRenderFeature` class, indicating it is now fully defined in one file.
- Replaced references to `ImmediateDebugRenderFeature.DebugRenderStage` with `DebugRenderStage` in `ImmediateDebugRenderSystem` for improved readability.
- Removed the `using static` directive for `ImmediateDebugRenderFeature` in `ImmediateDebugRenderStageSelector.cs` to clarify code dependencies.

* docs: XML comments added

* refactor: Empty line removed

* feat: New example project added

* refactor: Code improvements

* refactor: Code clean up

* refactor: Examples experience improvements

* docs: XML comments added

* docs: XML comments added

* docs: XML comments addee

* feat: Benchmark project updated

* feat: FastList benchmark added

* feat: New test added

* feat: Another test added

* feat: Benchmark input updated

* refactor: ShapeUpdater.cs - Optimize shape management

- Replaced `FastList<T>` with `List<T>` for better performance.
- Introduced `EnsureSize<T>()` method to manage list capacity efficiently.
- Modified initialization of primitive properties to use spans for faster access.
- Streamlined logic for updating and rendering shapes to enhance performance and readability.
- Simplified `Clamp()` method to a more concise expression-bodied format.

* feat: Target framework updated

* refactor: Performance updates

* refactor: Readability updates

* refactor: Code readability updates

* fix: ImmediateDebugRenderSystem.cs - Correct vertex pairing

- Modify the `ImmediateDebugRenderSystem` class to fix the processing of vertex pairs in the rendering loop.
- Change the reference for the second vertex (`v2`) from the same vertex as `v1` to the next vertex in the array.
- Ensure that pairs of vertices are correctly formed for drawing lines, allowing for proper rendering of line segments between distinct vertex pairs.

* refactor : CurrentRenderMode.cs - Rename enum for clarity

- Renamed the enum `CurRenderMode` to `CurrentRenderMode`.

* refactor: Bullet replaced with Bepu

* refactor: Code readability improvements

* docs: XML comment added

* refactor: Performance updates

* refactor: ImmediateDebugRenderFeature - Improve null safety

- Updated `ImmediateDebugRenderFeature` to use nullable types for several buffer fields, enhancing handling of uninitialized states and preventing null reference exceptions.
- Added XML documentation comments to the constructor, clarifying its purpose and ensuring the feature is rendered last.
- Enhanced `UpdateBufferIfNecessary()` to check for empty data, allowing early returns and avoiding unnecessary updates.
- Updated references in `CheckBuffers()` to use the null-forgiving operator (`!`), indicating expected non-null buffers.
- Modified `SetPrimitiveRenderingPipelineState()` and `SetLineRenderingPipelineState()` to use the null-forgiving operator for `pipelineState`, `primitiveEffect`, and `lineEffect`.
- Cleared `lineVertices` and `instances` lists at the start of the `Prepare()` method to prevent data retention from previous frames.
- Safely disposed of buffers in `Unload()` using the null-conditional operator (`?.`) to avoid exceptions if buffers are null.
- Overall, these changes improve the robustness and clarity of the `ImmediateDebugRenderFeature` class, making it safer and easier to maintain.

* feat: ListExtensions.cs - Add list extension methods

- Introduced a new static class `ListExtensions` in the namespace `Stride.CommunityToolkit.Collections`.
- Added the `EnsureSize(List<T> list, int size)` method to ensure a list has at least a specified number of items by adding default values if necessary.
- Implemented the `SetCount(List<T> list, int size)` method to adjust the list's count to a specified size, either by adding default values or removing excess items.
- Included null and range checks in both methods to ensure safe operations on the list.

* refactor: Code improvements

* refactor: Simplify collection handling in ShapeUpdater and ImmediateDebugRenderFeature

- Added `Stride.CommunityToolkit.Collections` namespace to both `ShapeUpdater.cs` and `ImmediateDebugRenderFeature.cs` for enhanced collection functionalities.
- Removed the custom `EnsureSize()` method in `ShapeUpdater.cs` and replaced it with direct calls to `EnsureSize()` on the collections: `_primitivePositions`, `_primitiveRotations`, `_primitiveVelocities`, `_primitiveRotVelocities`, and `_primitiveColors`.
- Streamlined `ImmediateDebugRenderFeature.cs` by removing the custom `EnsureSize()` method and using `EnsureSize()` directly on `instances` and `lineVertices`.
- Eliminated the `SetCount()` method in `ImmediateDebugRenderFeature.cs`, replacing it with direct calls to `SetCount()` on `transforms` and `colors` lists.
- These changes enhance code clarity and maintainability by leveraging the capabilities of the `Stride.CommunityToolkit.Collections` library.

* refactor: Folder structure improvements

* refactor: Text renderes moved to Renderers folder

* docs: XML comments updates

* refactor: File and folder structure updates to remove circular dependencies

* refactor: Empty lines removed

* refactor: Typo fixes

* docs: XML comments added

* refactor: DebugPrimitveType added

* docs: XML comments added

* refactor: ImmediateDebugRenderSystem.cs - Simplify debug message storage

- Replaced `FastList<DebugRenderable>` with `List<DebugRenderable>` for `renderMessages` and `renderMessagesWithLifetime` to simplify data structure.
- Updated list handling to use `CollectionsMarshal.AsSpan` for improved performance during iteration.
- Adjusted comments and logic related to the lifetime management of render messages to align with the new list implementation.

* refactor: Common functionality merged

* refactor: DebugRenderable.cs moved to a separate file

* refactor: Renderable.cs added

* docs: XML example updates

* refactor: Code readability improvements and old code removed

* docs: Examples docs updated

* refactor: Provider folder renamed to Core

* docs: Improvements

* fix: Grammar corrected

* docs: Title corrected

* refactor: Code readability updates

* docs: Docs improvements

* docs: Project names updated

* docs: References correction

* docs: Windows package included in the note

* docs: Addititional docs added

* fix: ImGuiSystem.cs - Clean up using directives and fields

- Deleted the private field `DebugTextSystem? debug;` to simplify the class.
- Changed `vertexBinding` from a nullable type (`VertexBufferBinding?`) to a non-nullable type (`VertexBufferBinding`) to ensure it is always initialized.

* docs: Comment removed

* docs: Docs improvements

* docs: Grammar and content improvements

* docs: Update documentation for clarity and new examples

- Updated documentation across multiple files: `advance-examples.md`, `basic-examples.md`, `other-examples.md`, `create-project.md`, and `index.md`.
- Added new examples in `advance-examples.md`, including "ImGui UI," "Box2D.NET Physics," and "Mesh Outline," with some entries reorganized for clarity.
- Enhanced `other-examples.md` with the addition of "Debug Shapes Usage" and "Stride + SignalR."
- Restructured `create-project.md` for improved readability, including renumbering steps and adding clarifying details.
- Simplified language in `index.md` to better communicate the benefits of the code-only approach over Stride Game Studio.
- Overall, these changes aim to enhance the clarity, organization, and accessibility of the documentation for users of the Stride Game Engine.

* chore: Release notes added

* docs: Docs grammar and wording improvements

* fix: Release notes correction

* fix: List corrected

Author: VaclavElias

Stride.CommunityToolkit.sln

@@ -124,6 +124,8 @@ Project("{FAE04EC0-301F-11D3-BF4B-00C04F79EFBC}") = "Stride.CommunityToolkit.Tes
 EndProject
 Project("{2150E333-8FDC-42A3-9474-1A3956D46DE8}") = "tests", "tests", "{0AB3BF05-4346-4AA6-1389-037BE0695223}"
 EndProject
+Project("{FAE04EC0-301F-11D3-BF4B-00C04F79EFBC}") = "Example08_DebugShapes_Usage", "examples\code-only\Example08_DebugShapes_Usage\Example08_DebugShapes_Usage.csproj", "{777B81CA-7C38-40DB-AD02-66FB1E5B5738}"
+EndProject
 Global
 	GlobalSection(SolutionConfigurationPlatforms) = preSolution
 		Debug|Any CPU = Debug|Any CPU
@@ -337,6 +339,10 @@ Global
 		{5C1A3E6A-7E65-4F3F-9E6C-5C0A7D9E1234}.Debug|Any CPU.Build.0 = Debug|Any CPU
 		{5C1A3E6A-7E65-4F3F-9E6C-5C0A7D9E1234}.Release|Any CPU.ActiveCfg = Release|Any CPU
 		{5C1A3E6A-7E65-4F3F-9E6C-5C0A7D9E1234}.Release|Any CPU.Build.0 = Release|Any CPU
+		{777B81CA-7C38-40DB-AD02-66FB1E5B5738}.Debug|Any CPU.ActiveCfg = Debug|Any CPU
+		{777B81CA-7C38-40DB-AD02-66FB1E5B5738}.Debug|Any CPU.Build.0 = Debug|Any CPU
+		{777B81CA-7C38-40DB-AD02-66FB1E5B5738}.Release|Any CPU.ActiveCfg = Release|Any CPU
+		{777B81CA-7C38-40DB-AD02-66FB1E5B5738}.Release|Any CPU.Build.0 = Release|Any CPU
 	EndGlobalSection
 	GlobalSection(SolutionProperties) = preSolution
 		HideSolutionNode = FALSE
@@ -384,6 +390,7 @@ Global
 		{17E5E99D-DE7E-438E-BC6B-3A4C06A64387} = {30457B66-9E10-4290-9744-D0079DE0448B}
 		{170666D3-8F9F-151F-C88A-54261B1783C1} = {30457B66-9E10-4290-9744-D0079DE0448B}
 		{5C1A3E6A-7E65-4F3F-9E6C-5C0A7D9E1234} = {0AB3BF05-4346-4AA6-1389-037BE0695223}
+		{777B81CA-7C38-40DB-AD02-66FB1E5B5738} = {30457B66-9E10-4290-9744-D0079DE0448B}
 	EndGlobalSection
 	GlobalSection(ExtensibilityGlobals) = postSolution
 		SolutionGuid = {C7A8C18E-C1F5-492F-8173-51EC9495B78C}

docs/contributing/documentation/index.md

@@ -1,36 +1,36 @@
 # Documentation
 
-We use [DocFX](https://github.com/dotnet/docfx) to generate our documentation. Contributing to the documentation is straightforward: explore the existing docs, duplicate relevant pages, and update the content as needed. For more information on DocFX and Markdown syntax, refer to the [official guide](https://dotnet.github.io/docfx/docs/markdown.html). If you're new to the process, we're happy to assist you in getting started.
+We use [DocFX](https://github.com/dotnet/docfx) to generate our documentation. Contributing is straightforward: explore the existing docs, duplicate relevant pages, and update the content as needed. For DocFX and Markdown syntax, see the [official guide](https://dotnet.github.io/docfx/docs/markdown.html). If you're new, we're happy to help you get started.
 
 ## Installing DocFX
 
-To install the latest version of DocFX, use the following command:
+To install the latest DocFX as a global tool:
 
 ```bash
 dotnet tool install -g docfx
 ```
 
-## Building the Documentation
+## Building the documentation
 
-1. Navigate to the docs folder in the project directory:
+1. Navigate to the docs folder:
    ```
    stride-community-toolkit\docs\
    ```
-1. Run the `run.bat`` file to build the documentation:
+2. Run the `run.bat` file to build the docs:
    ```
    run.bat
    ```
-1. Once the process completes, you can access the documentation in your browser at:
+3. When complete, open the site in your browser:
    ```
    http://localhost:8080/
    ```
 
-## Editing the Documentation
+## Editing the documentation
 
-- All documentation files are located in the `docs` folder. You can edit these Markdown files to update or add content.
-- After making changes, re-run the `run.bat` command to rebuild the documentation and preview your updates in your browser.
+- All documentation files are under `docs`. Edit the Markdown files to update or add content.
+- After changes, re-run `run.bat` to rebuild and preview updates in your browser.
 
-## Submitting Changes
+## Submitting changes
 
-- Ensure you’re satisfied with the results.
+- Ensure you're satisfied with the result.
 - Submit a pull request to the `main` branch for review.

docs/contributing/examples/index.md

@@ -1,42 +1,20 @@
 # Contribute Examples
 
-You can see all examples in the [examples](https://github.com/stride3d/stride-community-toolkit/tree/main/examples/code-only) folder.
+All examples live in the [examples](https://github.com/stride3d/stride-community-toolkit/tree/main/examples/code-only) folder.
 
-If you would like your example be launchable from the console application, you can add it to the `Stride.CommunityToolkit.Examples` project which you can find here: [Stride.CommunityToolkit.Examples](https://github.com/stride3d/stride-community-toolkit/tree/main/src/Stride.CommunityToolkit.Examples).
+If you'd like your example to be launchable from the console application [Stride.CommunityToolkit.Examples](https://github.com/stride3d/stride-community-toolkit/tree/main/src/Stride.CommunityToolkit.Examples), follow these steps:
 
-1. Make sure you create an anchor class named `NamespaceAnchor.cs` if your example contains only `Programs.cs`, so the namespace can be accessible from `Stride.CommunityToolkit.Examples`.
-    ```csharp
-    namespace ExampleXY_YourExampleNamespace;
-    
-    /// <summary>
-    /// This empty class is here to make the namespace available in the nameof() operator in the main examples project.
-    /// </summary>
-    internal static class NamespaceAnchor;
+1. Create a project under `examples/code-only/` named `ExampleXY_YourExampleNamespace` (replace `XY` with the next available number).
+2. Add example metadata to the `*.csproj` (used in the console app menu):
+    ```xml
+    <ExampleTitle>Basic Example - Capsule with rigid body</ExampleTitle>
+    <ExampleOrder>100</ExampleOrder>
+    <ExampleEnabled>true</ExampleEnabled>
+    <ExampleCategory>1 - Basic Example</ExampleCategory>
     ```
-1. Add your example project to `Stride.CommunityToolkit.Examples` project.
-1. Update `Providers/ExampleProvider.cs`
-1. Run `Stride.CommunityToolkit.Examples`
-1. You should see your example listed in the console application.
-   ```
-   Stride Community Toolkit Examples
-
-   [1] Basic Example - Capsule with rigid body
-   [2] Basic Example - Capsule with rigid body in F#
-   [3] Basic Example - Capsule with rigid body in Visual Basic
-   [4] Basic Example - Give me a cube
-   [5] Basic Example - Stride UI - Canvas - Capsule with rigid body and Window
-   [6] Basic Example - Stride UI - Grid - Save and load game state
-   [7] Basic Example - Procedural Geometry
-   [8] Basic Example - Particles
-   [9] Advance Example - Myra UI - Draggable Window, GetService()
-   [10] Advance Example - Image Processing
-   [11] Advance Example - Root Renderer Shader
-   [12] Other - CubeClicker
-   [13] Other - Debug Shapes
-   [14] Other - Renderer
-   [Q] Quit
-
-   Enter choice and press ENTER to continue
-   ```
-1. Update the `Stride.CommunityToolkit.Docs/includes/manual/examples/basic-examples-outro.md` file with the new example.
-1. Update the `Stride.CommunityToolkit.Docs/includes/manual/basic-examples.md` or `advance-examples.md` or `other-examples.md` file with the new example.
+3. If `<ExampleEnabled>true</ExampleEnabled>`, it will automatically appear in the console menu.
+4. Run `Stride.CommunityToolkit.Examples`.
+5. You should see your example listed in the console application menu.
+   [!INCLUDE [examples-console-app](../../includes/manual/examples/examples-console-app.md)]
+6. Update `Stride.CommunityToolkit.Docs/includes/manual/examples/basic-examples-outro.md` to include the new example.
+7. Update `Stride.CommunityToolkit.Docs/includes/manual/basic-examples.md`, `advance-examples.md`, or `other-examples.md` to include the new example.

docs/contributing/index.md

@@ -1,27 +1,25 @@
 # Contributing
 
-## Welcome Contributors
+## Welcome, contributors
 
-Thank you for your interest in contributing to the **Stride Community Toolkit**. This guide will help you get started by providing guidelines, best practices, and resources for making meaningful contributions to the project. Whether you're fixing bugs, adding new features, or enhancing the documentation, your efforts are greatly appreciated and help make this toolkit better for everyone.
+Thanks for your interest in contributing to the **Stride Community Toolkit**. This guide helps you get started with guidelines, best practices, and resources for meaningful contributions. Whether you're fixing bugs, adding features, or enhancing docs, your help makes the toolkit better for everyone.
 
 > [!TIP]
-> Interested in contributing to the **Stride Engine** itself? Check out the official [Stride Engine Contribution Guide](https://doc.stride3d.net/latest/en/contributors/index.html).
+> Interested in contributing to the **Stride Engine** itself? See the official [Stride Engine Contribution Guide](https://doc.stride3d.net/latest/en/contributors/index.html).
 
-## Ways to Contribute
+## Ways to contribute
 
-Since the toolkit is currently in preview, we don't have extensive contribution instructions. However, you can follow these general guidelines to get started:
+The toolkit is currently in preview, so instructions are intentionally lightweight. You can:
 
-- **Submit Pull Requests (PRs):** You're welcome to make PRs directly to the [GitHub repository](https://github.com/stride3d/stride-community-toolkit). This is the quickest way to contribute.
-- **Report or Solve Issues:** Create a new issue on our [GitHub Issues](https://github.com/stride3d/stride-community-toolkit/issues) page or work on an existing one.
-- **Start a Discussion:** Use the [GitHub Discussions](https://github.com/stride3d/stride/discussions) page to share ideas, ask questions, or collaborate on future toolkit features.
-- **Join the Community on Discord:** For real-time discussions, join our Discord server and participate in the `#toolkit` channel [here](https://discord.com/channels/500285081265635328/1179562410655363132).
+- Submit pull requests directly to the [GitHub repository](https://github.com/stride3d/stride-community-toolkit).
+- Report or fix issues on our [GitHub Issues](https://github.com/stride3d/stride-community-toolkit/issues) page.
+- Start a discussion on [GitHub Discussions](https://github.com/stride3d/stride/discussions) to share ideas or ask questions.
+- Join our Discord for real-time chat in `#toolkit`: <https://discord.com/channels/500285081265635328/1179562410655363132>.
 
-## Additional Resources
+## Additional resources
 
-Here are some helpful links to get you started:
+- [Stride Community Toolkit GitHub Repository](https://github.com/stride3d/stride-community-toolkit)
+- [Stride Game Engine GitHub Repository](https://github.com/stride3d/stride)
+- [Stride Documentation](https://doc.stride3d.net/)
 
-- [Stride Community Toolkit GitHub Repository](https://github.com/stride3d/stride-community-toolkit): Explore the code, issues, and pull requests.
-- [Stride Game Engine GitHub Repository](https://github.com/stride3d/stride): Learn more about the main Stride Engine project.
-- [Stride Documentation](https://doc.stride3d.net/): Find official guides, APIs, and tutorials.
-
-We appreciate your time and effort in helping improve the **Stride Community Toolkit**. Your contributions make a difference, whether you're fixing a small bug, suggesting a new feature, or enhancing the documentation 🙂.
+We appreciate your time and effort in improving the **Stride Community Toolkit**, whether you're fixing a small bug, suggesting a feature, or polishing the docs 🙂.

docs/contributing/toolkit/index.md

@@ -1,29 +1,28 @@
 # Contribute Code
 
-If you are a developer and you want to help building Stride Community Toolkit, than you can do so in various ways.
+If you are a developer and want to help build the Stride Community Toolkit, then you can do so in various ways.
 
-## Check Our Issue Tracker
+## Check our issue tracker
 
-If you are just getting started with toolkit, issues marked with ['good first issue'](https://github.com/stride3d/stride-community-toolkit/labels/good%20first%20issue) can be a good entry point.
-Please take a look at our [issue tracker](https://github.com/stride3d/stride-community-toolkit/issues) for other issues.
+If you're just getting started, issues marked as ['good first issue'](https://github.com/stride3d/stride-community-toolkit/labels/good%20first%20issue) are a great entry point. You can also browse our full [issue tracker](https://github.com/stride3d/stride-community-toolkit/issues).
 
+## Coordinate work
 
-## Notify Users
+Before you start working on an issue:
+- Comment on the relevant issue (or create one) to signal interest.
+- Check on GitHub or Discord if you need direction or context.
+- Ensure no one else is actively working on the same item.
+- Outline your approach and gather feedback to ensure the design fits the project.
 
-Once you start working on an issue, leave a message on the appropriate issue or create one if none exists to:
-* You can always check on Github or Discord if you need to get started somewhere or if you need a general sense of approaching an issue. 
-* Make sure that no one else is working on that same issue
-* Lay out your plans and discuss it with collaborators and users to make sure it is properly architectured and would fit well in the project
+## Coding style
 
-## Coding Style
+Use Stride's `.editorconfig` when making changes.
 
-Please use and follow Stride's `.editorconfig` when making changes to files.
+## Submitting changes
 
-## Submitting Changes
-
-* Push your changes to a specific branch in your fork.
-* Use that branch to create and fill out a pull request to the official repository.
+- Push changes to a topic branch in your fork.
+- Open a pull request from that branch to the official repository.
 
 ## Contributing to Stride Engine
 
-If you are interested in contributing to the Stride Engine, please visit the [Stride Engine Contribution](https://doc.stride3d.net/latest/en/contributors/index.html) page.
+Interested in contributing to the Stride Engine? See the [Stride Engine Contribution](https://doc.stride3d.net/latest/en/contributors/index.html) page.

docs/contributing/toolkit/library-project.md

@@ -1,29 +1,29 @@
 # Creating a New Library Project
 
-## Steps to Create a New NuGet Library
+## Steps to create a new NuGet library
 
-1. **Create the Project**:
-   - Add a new project in the `src` folder, following the naming convention: `Stride.CommunityToolkit.<LibraryName>`. 
-   - Refer to the [existing libraries](https://github.com/stride3d/stride-community-toolkit/tree/main/src) to ensure consistency with the folder/subfolder structure.
-2. **Configure the Project File**:
-   - Update the `.csproj` file with the correct package metadata.
-   - Review existing library project files to ensure all necessary properties (e.g., `Title`, `Description`, `Import`) are included.
-3. **Update Documentation**:
-   - Add the new library's name and description to `docs/includes/libraries.md`. This will display the library on:
-     - The home page.
-     - The Getting Started page.
-4. **Generate API Documentation**:
-   - Update `docs/docfx.json` to include the new `.csproj` location, ensuring that the [API documentation](../../api/index.md) is generated for the new library.
-5. **Update CI/CD Workflows**:
-   - Add the new project to:
-     - `.github\workflows\dotnet.yml` (`PROJECTS`).
-     - `.github\workflows\dotnet-nuget.yml` (`env` and `# Stride.CommunityToolkit.<LibraryName>` section).
-6. **Optional: Add Example Projects**:
-   - If adding example projects, follow the existing folder structure pattern in the `examples` directory.
-7. **Optional: Add Guidance Content**:
-   - If you plan to include guidance or tutorials for the new library:
-     - Add new pages to the `docs/manual` folder.
-     - Update the `toc.yml` file to include links to the new content.
+1. Create the project
+   - Add a new project under `src`, following the naming convention `Stride.CommunityToolkit.<LibraryName>`.
+   - Refer to the [existing libraries](https://github.com/stride3d/stride-community-toolkit/tree/main/src) for folder structure consistency.
+2. Configure the project file
+   - Update the `.csproj` with correct package metadata.
+   - Review existing library projects to ensure all necessary properties (e.g., `Title`, `Description`, `PackageTags`) are included.
+3. Update documentation
+   - Add the new library's name and description to `docs/includes/libraries.md`. This displays the library on:
+     - The home page
+     - The Getting Started page
+4. Generate API documentation
+   - Update `docs/docfx.json` to include the new `.csproj` so the [API documentation](../../api/index.md) is generated for the library.
+5. Update CI/CD workflows
+   - Add the project to:
+     - `.github/workflows/dotnet.yml` (`PROJECTS`)
+     - `.github/workflows/dotnet-nuget.yml` (`env` and the `# Stride.CommunityToolkit.<LibraryName>` section)
+6. Optional: add example projects
+   - If adding examples, follow the existing folder structure in `examples`.
+7. Optional: add guidance content
+   - If you plan to include guides or tutorials:
+     - Add new pages to `docs/manual`.
+     - Update the `toc.yml` to link the new content.
 
 > [!TIP]
-> Don't hesitate to reach out to the maintainers for assistance. Whether it's improving the process, code, clarifying steps, or helping with code, we're here to help!
+> Reach out to maintainers anytime, process improvements, clarifications, or code reviews, we're happy to help!

docs/includes/manual/advance-examples.md

@@ -1,6 +1,9 @@
-- [Simple Constraint](../../manual/code-only/examples/simple-constraint.md): Shows how to create a simple constraint between two entities.
-- [Various Constraints](../../manual/code-only/examples/constraints.md): Shows how to create various constraints between entities, including distance limit, distance servo, ball socket, and point-on-line servo.
-- [Myra UI - Draggable Window, GetService()](../../manual/code-only/examples/myra-ui-draggable-window-and-services.md): Illustrates using Myra UI to create a draggable window, display a health bar, and access registered services.
-- [Stride UI - Draggable Window](../../manual/code-only/examples/stride-ui-draggable-window.md): Illustrates using Stride UI to create a draggable window.
-- [Image Processing](../../manual/code-only/examples/image-processing.md): Shows how to apply image processing effects to a texture.
-- [Root Renderer Shader](../../manual/code-only/examples/root-renderer-shader.md): Shows how to create a custom shader for the root renderer.
+- [Simple Constraint](../../manual/code-only/examples/simple-constraint.md): Demonstrates creating a simple constraint between two entities.
+- [Various Constraints](../../manual/code-only/examples/constraints.md): Demonstrates distance limit, distance servo, ball socket, and point-on-line servo constraints between entities.
+- [Myra UI - Draggable Window, GetService()](../../manual/code-only/examples/myra-ui-draggable-window-and-services.md): Demonstrates using Myra UI to create a draggable window, display a health bar, and access registered services.
+- [Stride UI - Draggable Window](../../manual/code-only/examples/stride-ui-draggable-window.md): Demonstrates using Stride UI to create a draggable window.
+- [ImGui UI](../../manual/code-only/examples/imgui-ui.md): Demonstrates using ImGui to create a simple UI.
+- [Image Processing](../../manual/code-only/examples/image-processing.md): Demonstrates applying image-processing effects to a texture.
+- [Root Renderer Shader](../../manual/code-only/examples/root-renderer-shader.md): Demonstrates creating a custom shader for the root renderer.
+- [Box2D.NET Physics](../../manual/code-only/examples/box2d-physics.md): Demonstrates integrating Box2D.NET physics into a Stride project.
+- [Mesh Outline](../../manual/code-only/examples/mesh-outline.md): Demonstrates creating a mesh-outline effect.