> For the complete documentation index, see [llms.txt](https://docs.viverse.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.viverse.com/publishing-from-templates/creating-from-templates.md).
# Creating From Templates
This document details the process of creating a world from a template.
***
Templates are starter projects that are pre-built in VIVERSE. They are available on the profile page of your VIVERSE account.
**Prerequisites**
* In order to create worlds you must first create a VIVERSE account.
{% stepper %}
{% step %}
### Navigate to [worlds.viverse.com/profile](https://worlds.viverse.com/profile)
{% endstep %}
{% step %}
### Scroll down to "Worlds" and select the "Create World" button
{% endstep %}
{% step %}
### Select from the list of premade templates
{% endstep %}
{% step %}
### Updating the World Settings
Step 1. Select the **Details** page (A).
Step 2. Give the world a name in the **Name** field (B).
Step 3. Give the world a description in the **Description** field (C).
Step 4. Upload a thumbnail of the world in the **Thumbnail** (D) section.
Step 5. Assign at least genre to the world in the **Genre** (E) section.
Step 6. Set the compatible devices types for the world in the **Devices** (F) section.
{% endstep %}
{% step %}
### Adding gameplay trailer and screenshots
Step 1. Click on the **Media** (A) tab.
Step 2. Add a trailer video to the Trailer (B) section.
Step 3. Add images to the **Images** (C) section.
{% endstep %}
{% step %}
### Adding a GitHub link
Step 1. Click on the **Code & Collab** (A) tab.
Step 2. Add a GitHub link to the **GitHub** (B) section.
{% endstep %}
{% step %}
### Managing World Settings after creating a world
Step 1. Select the **Worlds** tab (A).
Step 2. Select the 3 dots (B) on the world that needs to be updated.
Step 3. Click **World Settings** (C).
{% endstep %}
{% endstepper %}
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://docs.viverse.com/publishing-from-templates/creating-from-templates.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
