[Draft] 2D Onboarding Tutorial

articles/getting_started/5_adding_basic_code.md

@@ -319,6 +319,6 @@ We recommend browsing through the [Getting to know MonoGame](../getting_to_know/
 
 ## Further Reading
 
-Check out the [Tutorials section](../tutorials.md) for many more helpful guides and tutorials on building games with MonoGame.  We have an expansive library of helpful content, all provided by other MonoGame developers in the community.
+Check out the [Tutorials section](../tutorials/index.md) for many more helpful guides and tutorials on building games with MonoGame.  We have an expansive library of helpful content, all provided by other MonoGame developers in the community.
 
 Additionally, be sure to check out the official [MonoGame Samples](../samples.md) page for fully built sample projects built with MonoGame and targeting our most common platforms.

articles/help_and_support.md

@@ -5,7 +5,7 @@ description: Where to get help and support when using MonoGame.
 
 # Help and Support
 
-There is a wealth of [community created content, blogs and tutorials](tutorials.md) available.
+There is a wealth of [community created content, blogs and tutorials](tutorials/index.md) available.
 
 If you want to find an answer to a more specific problem, you can ask it on our [GitHub Discussions](https://github.com/MonoGame/MonoGame/discussions) page.
 

articles/toc.yml

@@ -1,113 +1,151 @@
 - name: Introduction
-  href: 
+  href:
 - name: Roadmap
   href: /roadmap/
 - name: What's New
   href: whats_new.md
 - name: Getting Started
   href: getting_started/index.md
   items:
-  - name: Introduction
-    href: getting_started/
-  - name: Supported platforms
-    href: getting_started/platforms.md
-  - name: 1. Setting up your OS for development
-    items:
-    - name: Windows
-      href: getting_started/1_setting_up_your_os_for_development_windows.md
-    - name: macOS
-      href: getting_started/1_setting_up_your_os_for_development_macos.md
-    - name: Ubuntu 20.04
-      href: getting_started/1_setting_up_your_os_for_development_ubuntu.md
-  - name: 2. Choosing your IDE
-    items:
-    - name: Visual Studio for Windows
-      href: getting_started/2_choosing_your_ide_visual_studio.md
-    - name: Visual Studio Code
-      href: getting_started/2_choosing_your_ide_vscode.md
-    - name: Rider
-      href: getting_started/2_choosing_your_ide_rider.md
-  - name: 3. Understanding the Code
-    href: getting_started/3_understanding_the_code.md
-  - name: 4. Adding Content
-    href: getting_started/4_adding_content.md
-  - name: 5. Adding Basic Code
-    href: getting_started/5_adding_basic_code.md
-  - name: Packaging
-    href: getting_started/packaging_games.md
-  - name: Preparing for consoles
-    href: getting_started/preparing_for_consoles.md
-  - name: Using Development Nuget Packages
-    href: getting_started/using_development_nuget_packages.md
-  - name: Tools
-    items:
     - name: Introduction
-      href: getting_started/tools/
-    - name: MGCB
-      href: getting_started/tools/mgcb.md
-    - name: MGCB Editor
-      href: getting_started/tools/mgcb_editor.md
-    - name: MGFXC
-      href: getting_started/tools/mgfxc.md
-  - name: Content Pipeline
-    items:
-    - name: Introduction
-      href: getting_started/content_pipeline/index.md
-    - name: Why use the Content Pipeline
-      href: getting_started/content_pipeline/why_content_pipeline.md
-    - name: Using MGCB Editor
-      href: getting_started/content_pipeline/using_mgcb_editor.md
-    - name: Custom Effects
-      href: getting_started/content_pipeline/custom_effects.md
-    - name: TrueType fonts
-      href: getting_started/content_pipeline/adding_ttf_fonts.md
-    - name: Localization
-      href: getting_started/content_pipeline/localization.md
+      href: getting_started/
+    - name: Supported platforms
+      href: getting_started/platforms.md
+    - name: 1. Setting up your OS for development
+      items:
+        - name: Windows
+          href: getting_started/1_setting_up_your_os_for_development_windows.md
+        - name: macOS
+          href: getting_started/1_setting_up_your_os_for_development_macos.md
+        - name: Ubuntu 20.04
+          href: getting_started/1_setting_up_your_os_for_development_ubuntu.md
+    - name: 2. Choosing your IDE
+      items:
+        - name: Visual Studio for Windows
+          href: getting_started/2_choosing_your_ide_visual_studio.md
+        - name: Visual Studio Code
+          href: getting_started/2_choosing_your_ide_vscode.md
+        - name: Rider
+          href: getting_started/2_choosing_your_ide_rider.md
+    - name: 3. Understanding the Code
+      href: getting_started/3_understanding_the_code.md
+    - name: 4. Adding Content
+      href: getting_started/4_adding_content.md
+    - name: 5. Adding Basic Code
+      href: getting_started/5_adding_basic_code.md
+    - name: Packaging
+      href: getting_started/packaging_games.md
+    - name: Preparing for consoles
+      href: getting_started/preparing_for_consoles.md
+    - name: Using Development Nuget Packages
+      href: getting_started/using_development_nuget_packages.md
+    - name: Tools
+      items:
+        - name: Introduction
+          href: getting_started/tools/
+        - name: MGCB
+          href: getting_started/tools/mgcb.md
+        - name: MGCB Editor
+          href: getting_started/tools/mgcb_editor.md
+        - name: MGFXC
+          href: getting_started/tools/mgfxc.md
+    - name: Content Pipeline
+      items:
+        - name: Introduction
+          href: getting_started/content_pipeline/index.md
+        - name: Why use the Content Pipeline
+          href: getting_started/content_pipeline/why_content_pipeline.md
+        - name: Using MGCB Editor
+          href: getting_started/content_pipeline/using_mgcb_editor.md
+        - name: Custom Effects
+          href: getting_started/content_pipeline/custom_effects.md
+        - name: TrueType fonts
+          href: getting_started/content_pipeline/adding_ttf_fonts.md
+        - name: Localization
+          href: getting_started/content_pipeline/localization.md
 - name: Getting to know MonoGame
   href: getting_to_know/
   items:
-  - name: What is
-    href: getting_to_know/whatis/
-    items:
-    - name: Audio
-      href: getting_to_know/whatis/audio/
-    - name: Content Pipeline
-      href: getting_to_know/whatis/content_pipeline/
-    - name: Graphics
-      href: getting_to_know/whatis/graphics/
-    - name: Input
-      href: getting_to_know/whatis/input/
-    - name: The Game Loop
-      href: getting_to_know/whatis/game_loop/
-    - name: Vector / Matrix / Quaternions
-      href: getting_to_know/whatis/vector_matrix_quat/
-    - name: MonoGame Class Library
-      href: getting_to_know/whatis/monogame_class_library/
-  - name: How to
-    href: getting_to_know/howto/
-    items:
-    - name: Audio
-      href: getting_to_know/howto/audio/
-    - name: Content Pipeline
-      href: getting_to_know/howto/content_pipeline/
-    - name: Graphics
-      href: getting_to_know/howto/graphics/
-    - name: Input
-      href: getting_to_know/howto/input/
+    - name: What is
+      href: getting_to_know/whatis/
+      items:
+        - name: Audio
+          href: getting_to_know/whatis/audio/
+        - name: Content Pipeline
+          href: getting_to_know/whatis/content_pipeline/
+        - name: Graphics
+          href: getting_to_know/whatis/graphics/
+        - name: Input
+          href: getting_to_know/whatis/input/
+        - name: The Game Loop
+          href: getting_to_know/whatis/game_loop/
+        - name: Vector / Matrix / Quaternions
+          href: getting_to_know/whatis/vector_matrix_quat/
+        - name: MonoGame Class Library
+          href: getting_to_know/whatis/monogame_class_library/
+    - name: How to
+      href: getting_to_know/howto/
+      items:
+        - name: Audio
+          href: getting_to_know/howto/audio/
+        - name: Content Pipeline
+          href: getting_to_know/howto/content_pipeline/
+        - name: Graphics
+          href: getting_to_know/howto/graphics/
+        - name: Input
+          href: getting_to_know/howto/input/
 - name: Migration
   items:
-  - name: Migrating from XNA
-    href: migration/migrate_xna.md
-  - name: Migrating from 3.7
-    href: migration/migrate_37.md
-  - name: Migrating from 3.8.0
-    href: migration/migrate_38.md
-  - name: Updating Versions
-    href: migration/updating_versions.md
+    - name: Migrating from XNA
+      href: migration/migrate_xna.md
+    - name: Migrating from 3.7
+      href: migration/migrate_37.md
+    - name: Migrating from 3.8.0
+      href: migration/migrate_38.md
+    - name: Updating Versions
+      href: migration/updating_versions.md
 - name: Samples and Demos
   href: samples.md
-- name: Community Tutorials
-  href: tutorials.md
+- name: Tutorials
+  href: tutorials/
+  items:
+    - name: Building 2D Games
+      href: tutorials/building_2d_games/
+      items:
+        - name: "01: What Is MonoGame?"
+          href: tutorials/building_2d_games/01_what_is_monogame/
+        - name: "02: Getting Started"
+          href: tutorials/building_2d_games/02_getting_started/
+        - name: "03: The Game1 File"
+          href: tutorials/building_2d_games/03_the_game1_file/
+        - name: "04: Creating a Class Library"
+          href: tutorials/building_2d_games/04_creating_a_class_library/
+        - name: "05: Content Pipeline"
+          href: tutorials/building_2d_games/05_content_pipeline/
+        - name: "06: Working with Textures"
+          href: tutorials/building_2d_games/06_working_with_textures/
+        - name: "07: Optimizing Texture Rendering"
+          href: tutorials/building_2d_games/07_optimizing_texture_rendering/
+        - name: "08: The Sprite Class"
+          href: tutorials/building_2d_games/08_the_sprite_class/
+        - name: "09: The AnimatedSprite Class"
+          href: tutorials/building_2d_games/09_the_animatedsprite_class/
+        - name: "10: Handling Input"
+          href: tutorials/building_2d_games/10_handling_input/
+        - name: "11: Input Management"
+          href: tutorials/building_2d_games/11_input_management/
+        - name: "12: Collision Detection"
+          href: tutorials/building_2d_games/12_collision_detection/
+        - name: "13: Working With Tilemaps"
+          href: tutorials/building_2d_games/13_working_with_tilemaps/          
+        - name: "14: Sound Effects and Music"
+          href: tutorials/building_2d_games/14_soundeffects_and_music/
+        - name: "15: Audio Controller"
+          href: tutorials/building_2d_games/15_audio_controller/
+        - name: "16: Working with SpriteFonts"
+          href: tutorials/building_2d_games/16_working_with_spritefonts/
+        - name: "17: Scenes"
+          href: tutorials/building_2d_games/17_scenes/
 - name: Console Access
   href: console_access.md
 - name: Help and Support

articles/tutorials/building_2d_games/01_what_is_monogame/index.md

@@ -0,0 +1,83 @@
+---
+title: "Chapter 01: What is MonoGame"
+description: Learn about the history of MonoGame and explore the features it provides to developers when creating games.
+---
+
+## A Brief History
+
+In 2006, Microsoft released a game development framework named *XNA Game Studio* to facilitate game development for Windows PC and the Xbox 360 console. It revolutionized game development for indie creators by bringing a simplified approach to building games and offering a set of tools that lowered the entry barrier for aspiring game developers. Out of XNA Game Studio came critically acclaimed titles such as [Bastion](https://www.supergiantgames.com/games/bastion/) and [Terraria](https://terraria.org/). In 2008, XNA was expanded to support development for both the Zune and Windows Phone.
+
+> [!NOTE]
+>
+> Fun fact, provided by community member stromkos, The release of XNA 3.0 in 2008, which added the support for Windows Phone, is also the release that specified the default window resolution of 800x480 for new projects as this was the preferred resolution on Windows Phone. [It is still the default resolution used in MonoGame projects today](https://github.com/MonoGame/MonoGame/blob/8b35cf50783777507cd6b21828ed0109b3b07b50/MonoGame.Framework/GraphicsDeviceManager.cs#L44).
+
+As XNA became more popular, the need for cross-platform development started to grow. In 2009, [José Antonio Leal de Farias](https://github.com/jalf) introduced *XNA Touch*, an open-source project that aimed to make games with XNA playable on iOS devices. This marked the beginning of what would later become MonoGame. [Dominique Louis](https://github.com/CartBlanche) came on board in 2009 and soon took over as full-time project lead, driving its initial development and expansion. The project attracted other developers, such as [Tom Spilman](https://github.com/tomspilman), who were interested in expanding the scope of the project as well as its reach.
+
+The official first release of MonoGame occurred in 2011, as an open-source version of XNA. While it still had the same familiar API as XNA, the cross-platform support was expanded to include Windows, macOS, Linux, iOS, Android, Xbox, and PlayStation. Despite Microsoft discontinuing XNA in 2013, MonoGame continued to grow and develop. Maintenance of the project was given to [Steve Williams](https://github.com/KonajuGames) and [Tom Spilman](https://github.com/tomspilman) in 2014. In order to direct its future development and undertaking, the [MonoGame Foundation](https://monogame.net/about/) was formed on September 29th, 2023.
+
+Today, MonoGame is a mature cross-platform framework, that is built with the spirit of preserving XNA while adopting modern game development practices. Some popular titles created using MonoGame includes [Celeste](https://store.steampowered.com/app/504230/Celeste/), [Stardew Valley](https://store.steampowered.com/app/413150/Stardew\_Valley/), and [Streets of Rage 4](https://store.steampowered.com/app/985890/Streets\_of\_Rage\_4/).
+
+| ![Figure 1-1: Celeste](./images/celeste.png) | ![Figure 1-2: Stardew Valley](./images/stardew-valley.png) |
+| :---: | :---: |
+| **Figure 1-1 Celeste.** | **Figure 1-2: Stardew Valley** |
+| ![Figure 1-3: Streets of Rage 4](./images/sor4.jpg) | |
+| **Figure 1-3: Streets of Rage 4** | |
+
+## Features
+
+MonoGame, following in the footsteps of XNA, is a "bring your own tools" framework. It provides developers the basic blocks to design the game, engines, and/or tools. As a code-first approach to game development, MonoGame does not include any pre-built editors or interfaces; instead, it gives developers the freedom to create their own working environment.
+
+### API
+
+At its core, MonoGame offers a set of libraries and APIs to handle common game development tasks. These include:
+
+1. **Graphics Rendering**: 2D and 3D rendering are supported through the graphics API offered by MonoGame. This API provides sprite batching for 2D graphics, a flexible 3D pipeline, and shaders for custom visuals and effects.
+2. **Input Handling**: Input from keyboard, mouse, gamepads, and touchscreens are supported, allowing for development of games for any platform and different styles of play.
+3. **Audio**: A comprehensive audio system that can be used to create sound effects as well as play music with included support for many audio formats.
+4. **Content Pipeline**: An out-of-the-box workflow for importing and processing game assets such as textures, models, and audio, and compiling them to a format that is optimal for the game's target platform.
+5. **Math Library**: A math library specifically optimized for game development, providing essential mathematical functions and operations.
+
+### Cross Platform
+
+One of the main advantages of MonoGame is its cross-platform support. Games built with MonoGame are compatible with a variety of platforms, including:
+
+* **Desktop**: Windows, macOS, and Linux.
+* **Mobile**: iOS and Android.
+* **Consoles** [(with appropriate license)](https://docs.monogame.net/articles/console\_access.html): Xbox, PlayStation, and Nintendo Switch.
+
+By providing cross-platform support, developers can target multiple platforms from a single code base, significantly reducing development time and resources needed for porting.
+
+### Programming Language Support
+
+MonoGame is designed and built in C#. It is the official programming language supported in documentation, samples, and community discussion. However, MonoGame is not exclusively tied to C#. As a .NET library, MonoGame can be used with any .NET-compatible language, including Visual Basic and F#.
+
+> [!CAUTION]
+> While the alternative .NET languages can be used, community support may be limited outside the scope of C#.
+
+Regardless of which .NET language is used, developers should have a foundational understanding of the language and programming concepts such as:
+
+* Object-oriented programming.
+* Data types and structures.
+* Control flow and loops.
+* Error handling and debugging.
+
+## See Also
+
+* [About MonoGame | MonoGame](https://monogame.net/about)
+
+## Test Your Knowledge
+
+1. Name one of the advantages of using the MonoGame framework to develop games.
+
+    :::question-answer
+    Any of the following are advantages of using the MonoGame framework.
+    1. It provides cross-platform support, allowing developers to target multiple platforms from a single code base.
+    2. It offers a set of libraries and APIs common for game development tasks, such as graphics rendering, input handling, audio, and content management.
+    3. It is a "bring your own tools" framework, giving developers flexibility in their working environment.
+    :::
+
+2. What programming languages can be used when creating a game with MonoGame?
+
+    :::question-answer
+    The primary language used is C#, which is the same language that the MonoGame framework is developed in.  However, any .NET language can be used, such as F# or Visual Basic.
+    :::