# Module Manifests

**Module Manifest** is a simple text file in `JSON` or `YAML` format that describes a particular Artifact, World, or set of those. Below is a very simple example of a Module Manifest which describes a module with two Artifacts:

```yaml
assetId: asset.morpheusxr.car
name: Car
meta:
  preview: https://storage.googleapis.com/xmorpheus-public-assets/artifacts/previews/v2/car.png
contents:
  - artifact:
      id: car.ford
      data: data.uZ_dpln_mTUK3IGmeb46H.JOmjpVD5l-eEYrzAkvAUQ
  - artifact:
      id: car.bmw
      data: data.onveouruohpfpp9gfwpwi.orvouqv90ar9e0pf97vgr
```

As a Platform Module can contain one or more assets, all of them should be described in the `content` section using different kinds of Manifests

* [Artifact Manifest](https://platform.morpheusxr.com/platform-modules/module-manifests/artifact-manifest) (supported starting Release 5)
* [World Manifest](https://platform.morpheusxr.com/platform-modules/module-manifests/world-manifest) (supported starting Release 6)
* [Avatar Manifest](https://platform.morpheusxr.com/platform-modules/module-manifests/avatar-manifest) (supported starting Release 7)

## Module Manifest Parameters

<table data-full-width="true"><thead><tr><th width="180.5">Parameter</th><th>Usage, format, examples</th></tr></thead><tbody><tr><td><h4 id="manageable-complexity"><code>assetId</code></h4><p><strong><code>address</code></strong></p></td><td><p>Used to map a Module Config on a particular module.</p><ul><li><code>assetId</code> uses Java notation <code>com.companyName.moduleName</code>.</li><li><code>address</code> uses notation <code>universeName.morpheus.place/module/moduleName</code></li></ul></td></tr><tr><td><h4 id="manageable-complexity"><code>name</code></h4></td><td>Human readable name of the module. Used in the upcoming Marketplace and as a fallback for the names of the module contents</td></tr><tr><td><h4 id="manageable-complexity"><code>meta</code></h4></td><td>Structure with different meta data that is used in Marketplace and as fallback.<br>Same structures are expected in the <code>contents</code> of the module.</td></tr><tr><td><h4 id="manageable-complexity"><code>meta.preview</code></h4></td><td>URL for the preview image for the Module; when Module is configured for a particular Place, this image also used in-app for spawning module contents.</td></tr><tr><td><h4 id="manageable-complexity"><code>contents</code></h4></td><td>List of one or more manifests: <a href="module-manifests/artifact-manifest">Artifact Manifest</a>, <a href="module-manifests/world-manifest">World Manifest</a>, <a href="module-manifests/avatar-manifest">Avatar Manifest</a>.</td></tr></tbody></table>

&#x20;