Better notes

Author: GameOverture

mkdocs/docs/editor/asset-manager.md

@@ -4,6 +4,8 @@ title: "Asset Manager"
 
 ## Overview
 
+The below example is for all asset types besides **Code**, which is covered below in the [Code & Build Management](#code-build-management) section.   
+
 <figure>
   <img src="../img/editor/asset-manager.png" alt="Asset Manager Dock Window">
   <figcaption>Your source code is also considered assets! Along with textures and audio. </figcaption>
@@ -39,4 +41,37 @@ title: "Asset Manager"
 
 Right-clicking an asset and selecting **Properties...** will open the **Asset Properties** dialog.
 
+## Code & Build Management
+
+When you select the **Code** tab in the **Asset Manager**, you'll see a list of your game's C++ source code files. These files are organized into **Builds**, which are configurations that determine how your code is compiled and linked.
+
+### Build Settings
+
+With the desired **Project** active, you can open the **Build Settings** in the menu `Project > Build Settings`
+
+![Build Settings Dialog](../img/editor/dlg_build_settings.png)
+
+**Output Name** is the name of the final executable file created when building your game.
+
+Below that you can choose which 3rd party vendors Harmony will use if you have a preference. The **Extras** require you to manually install them in the respective `HarmonyEngine/Engine/extras/` directory. Follow the instructions in the `README.txt` file included in each extra's folder.
+
+### Adding Additional Library Dependencies
+
+If you need certain code libraries/dependencies to be included in your build click the ![Add Button](../img/editor/generic-add.png) **Add library dependency** button.
+
+![Library dependency widgets](../img/editor/dlg_build_settings_dependency.png)
+
+The library dependency must be a CMake compatible package. You must specify the following two fields:
+
+- **CMakeLists.txt Project Name**: The library target name used within the `add_library()` command.
+- **Library relative location**: Use the "Browse..." button to select the folder where the library's root `CMakeLists.txt` is located
+
+**Options** can be left blank, but is useful if you want to override default options or inject CMake scripting code. The options are parsed (and cached) before the library is included.
+
+> If you already have an existing compatible build, CMake may try to update the environment automatically when you try to compile. On occasion you may need to recreate your build after adding dependencies.
+
+## Creating New Builds
+
+With your **Build Settings** determined, you can create a new build of your game by selecting `Project > New Build` from the menu, or by pressing `Ctrl+Shift+B`.
 
+Any existing source code is independent of your builds, so removing the **Project**'s `/build/` folder can be done freely. 

mkdocs/docs/editor/projects.md

@@ -20,7 +20,9 @@ To create a new Project in the Project Explorer you can:
 **Code Name** will be used to create the main C++ class, and must be compliant with standard naming conventions.
 
 The final **Project Location** (where all the project files will be dumped) is assembled by what's specified in the text field PLUS whether **Create game directory at location** is checked.
-> If you want to specify a common location for multiple game projects, specify that root location the text field and keep **Create game directory at location** checked.
+
+!!! note "Example Setup"
+    If you want to specify a common location for multiple game projects, specify that root location the text field and keep **Create game directory at location** checked.
 
 Within **Advanced** you can customize how the project folders (like the assets or source code) reside and what they're named. You can even specify locations outside the **Project Location**. For each entry, specify the relative path from the **Project Location**, and the name of the directory itself.
 
@@ -39,33 +41,3 @@ Within **Advanced** you can customize how the project folders (like the assets o
 
 Under Development - Dialog tool meant to edit the game's .hyproj file
 
-## Build Settings
-
-With the desired **Project** active, you can open the **Build Settings** in the menu `Project > Build Settings`
-
-![Build Settings Dialog](../img/editor/dlg_build_settings.png)
-
-**Output Name** is the name of the final executable file created when building your game.
-
-Below that you can choose which 3rd party vendors Harmony will use if you have a preference. The **Extras** require you to manually install them in the respective `HarmonyEngine/Engine/extras/` directory. Follow the instructions in the `README.txt` file included in each extra's folder.
-
-### Adding Additional Library Dependencies
-
-If you need certain code libraries/dependencies to be included in your build click the ![Add Button](../img/editor/generic-add.png) **Add library dependency** button.
-
-![Library dependency widgets](../img/editor/dlg_build_settings_dependency.png)
-
-The library dependency must be a CMake compatible package. You must specify the following two fields:
-
-- **CMakeLists.txt Project Name**: The library target name used within the `add_library()` command.
-- **Library relative location**: Use the "Browse..." button to select the folder where the library's root `CMakeLists.txt` is located
-
-**Options** can be left blank, but is useful if you want to override default options or inject CMake scripting code. The options are parsed (and cached) before the library is included.
-
-> If you already have an existing compatible build, CMake may try to update the environment automatically when you try to compile. On occasion you may need to recreate your build after adding dependencies.
-
-## Creating New Builds
-
-With your **Build Settings** determined, you can create a new build of your game by selecting `Project > New Build` from the menu, or by pressing `Ctrl+Shift+B`.
-
-Any existing source code is independent of your builds, so removing the **Project**'s `/build/` folder can be done freely. 

mkdocs/docs/getting-started/index.md

@@ -10,7 +10,8 @@ hide: toc
 - Want a code-first workflow without the overhead of large general-purpose engines. 
 - Need builds that are performant, lightweight, and cross-platform (including the web browser with optional WebAssembly deployment)
 
-> Itermediate C++ knowledge is recommended, but Harmony is also a great way to learn C/C++ for those with the aptitude.
+!!! note
+    Basic C++ knowledge including pointers and lambdas is recommended, but Harmony is also a great way to learn C/C++ for those wanting to learn.
 
 The Harmony Engine consists of two main projects.
 The editor tool (**HyEditor**) that manages projects, assets, and scenes. And the engine itself (**HyEngine**) which is a static library that links into your game application.

mkdocs/mkdocs.yml

@@ -51,6 +51,8 @@ markdown_extensions:
       pygments_lang_class: true
   - pymdownx.inlinehilite
   - pymdownx.snippets
+  - admonition
+  - pymdownx.details
   - pymdownx.superfences
 
 extra_css: