include metadata page

Author: CyberHoward

framework/docs/src/4_get_started/3_module_builder.md

@@ -63,7 +63,7 @@ The builder constructor takes three variables:
 
 1. `module_id`: The module ID is a string that we defined above.
 2. `contract_version`: The contract version.
-3. `metadata`: An optional URL that can be used to retrieve data off-chain. Can be used with the Abstract Metadata Standard to automatically generate interactive front-end components for the module. This is explained in more detail in the [metadata section](./9_metadata.md).
+3. `metadata`: An optional URL that can be used to retrieve data off-chain. Can be used with the Abstract Metadata Standard to automatically generate interactive front-end components for the module. This is explained in more detail in the [metadata section](9_metadata.md).
 
 Amazing! You now have a very basic Abstract module. You can now add your custom logic to your module by adding handlers to the module.
 

framework/docs/src/4_get_started/9_metadata.md

@@ -1 +1,3 @@
-# Module Metadata
+# Module Metadata
+
+Module metadata is a set of information that describes a module. This information is stored on-chain and can be accessed by anyone. The metadata includes the following fields:

framework/docs/src/SUMMARY.md

@@ -43,6 +43,7 @@
 - [Abstract Client](./4_get_started/5_abstract_client.md)
 - [Deployment](./4_get_started/7_module_deployment.md)
 - [Dependencies](./4_get_started/8_dependencies.md)
+- [Metadata](./4_get_started/9_metadata.md)
 - [Modules](./modules/index.md)
     - [CW Staking](./modules/cw-staking.md)
     - [Dex](./modules/dex.md)