Updated readme

Author: jeffreylanters

README.md

@@ -123,16 +123,43 @@ public class MainController : Controller {
 }
 ```
 
+**Assets:** The [Controller](#controllers) allows the use of the Asset attribute on properties to automatically assign the values of referenced Assets. Assets can be assigned on the [Controller](#controllers) instance in your Scene. When assigning using the empty contructor, the property's name will be used for searching the Asset, to find an Asset by it's name, use the string overload. All types of UnityEngine's Object can be used in these fields. These properties are assigned during the OnInitialize cycle and are available for use at the OnInitialized cycle. When an asset is not found, an error is thrown.
+
+```csharp
+public class MainController : Controller {
+  [Asset] private GameObject playerPrefab;
+  [Asset ("ShopDialog")] private NpcDialog npcDialog;
+}
+```
+
 **Notes:** While it is recommended to move as much logic into [Services](#services) and [Systems](#systems), it is possible to let your [Controller](#controllers) house any functionality. If you use the [Controller](#controllers) for this purpose, try to keep it down to only Application wide and core functionality.
 
 ### Components
 
-_This secection of the documentation will be updated very soon!_
+**Introduction:** [Components](#components) are responsible for housing the data of your entities and should consist of nothing more than that. All properties should be public and will be accessible to all systems and controllers. [Components](#components) should be added to your entities in the Scene, an entity is not limited to one [Components](#components) and can hold as many as needed.
+
+```csharp
+public class MovementComponent : System<MovementComponent, MovementSystem> { }
+```
+
+_This secection of the documentation is in process!_
 
 ### Systems
 
-_This secection of the documentation will be updated very soon!_
+**Introduction:** The [Systems](#systems) are responsible for controlling all of your Entity [Components](#components) and are the closest you'll get of what you're used to when working with MonoBehaviours. The entire life cycles of your entities are managed in here.
+
+```csharp
+public class MovementSystem : System<MovementSystem, MovementComponent> { }
+```
+
+_This secection of the documentation is in process!_
 
 ### Services
 
-_This secection of the documentation will be updated very soon!_
+**Introduction:**
+
+```csharp
+public class AudioService : Service<AudioService> { }
+```
+
+_This secection of the documentation is in process!_