📝 Add Mapping

src/SUMMARY.md

@@ -4,5 +4,6 @@
   - [What is Bolt](./introduction/what_is_bolt.md)
   - [Entity, Component and Systems (ECS)](./introduction/ecs.md)
   - [Ephemeral Rollups](./introduction/ephemeral-rollups.md)
+  - [Mapping and State listening](./introduction/mapping-and-state-listening.md)
 - [Prerequisites](./prerequisites/prerequisites.md)
   - [Useful Resources](./prerequisites/useful_resources.md)

src/introduction/mapping-and-state-listening.md

@@ -0,0 +1,9 @@
+# Mapping and State listening
+
+The standardized **ECS** pattern allows for easy integration of game components with a rendering engine to display the game interface. The presented framework can be viewed as an open and permissionless alternative to a backend intended as a multiplayer game server. 
+
+For visualization and rendering, existing engines such as [Unity](https://unity.com/), [Unreal Engine](https://www.unrealengine.com), [Phaser](https://phaser.io/), and others can be used. 
+
+The standardized structure of the components allows for automatic mapping of components and entity properties (abstracting serialization and deserialization. State updates can be easily performed and intercepted, providing a mechanism similar to the [Observer pattern](https://en.wikipedia.org/wiki/Observer_pattern) to listen to state changes and update the rendering.
+
+If you are building with Unity, the [Solana.Unity-SDK](https://github.com/magicblock-labs/Solana.Unity-SDK) gives you all the necessary tools to connect the gaming interface with Bolt.