> For the complete documentation index, see [llms.txt](https://docs.decentraland.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.decentraland.org/creator/scenes-sdk7/getting-started/dev-workflow.md).

# Development Workflow

This document outlines the steps recommended for developing a scene for Decentraland, from ideation to publishing and beyond.

## Install the Creator Hub

Make sure you have the Decentraland Creator Hub installed.

* [Installation Guide](/creator/scene-editor/get-started/editor-installation.md)

If you intend to work with code, also make sure you install [Visual Studio Code](https://code.visualstudio.com/) or [Cursor AI](https://www.cursor.com/).

{% hint style="info" %}
**💡 Tip**: You can also use AI assistants to generate scene code from plain language descriptions. See [Vibe Coding with AI](/creator/scenes-sdk7/getting-started/vibe-coding.md) for how to get started with AI-assisted development.
{% endhint %}

## Design your experience

Think about how much space you need to take up, what kind of distribution, what kinds of mechanics you want players to be able to carry out, etc. The following documents can serve as a guide:

* [UX & UI Guide](/creator/scenes-sdk7/designing-the-experience/ux-ui-guide.md)
* [Design constraints for games](/creator/scenes-sdk7/designing-the-experience/design-games.md)
* [Scene MVP guidelines](/creator/scenes-sdk7/designing-the-experience/mvp-guidelines.md)

## Where to publish

In Decentraland, content is published to adjacent plots of land in a finite amount of space. Players can freely walk from one to the other. Each scene is its own contained little world, items from one scene can't extend out into another scene, and the code for each scene is sandboxed from all others.

Permission to publish to each of these is controlled via tokens. You don't need land to develop a scene, but you will need access to land once you're ready to publish.

Alternatively, you have the option to publish to Decentraland [Worlds](/creator/scenes-sdk7/publishing/publishing-options.md#decentraland-worlds), which are self-contained and isolated scenes.

The following options are available:

* Rent LAND
* Purchase LAND
* Obtain permissions from a land owner
* Publish to a Decentraland World, see [worlds](/creator/scenes-sdk7/publishing/publishing-options.md#decentraland-worlds) to learn more.

See [Publishing options](/creator/scenes-sdk7/publishing/publishing-options.md) for more details.

## Templates and examples

When creating a new scene, choose amongst several base template scenes that include some basic code and 3d models. Use these to get started faster.

* [Example scenes](https://studios.decentraland.org/resources?sdk_version=SDK7): here you can find a large collection of example scenes, each showcasing different mechanics that you can borrow. You can also clone any of these scenes and use it as a starting point.
* [Helper libraries](https://studios.decentraland.org/resources?sdk_version=SDK7\&resource_type=Library): these can simplify many common tasks.

## Art assets

If you're an experienced artist or you have access to someone who is, you can create custom `.gltf` or `.glb` models for your scene. See [3D model essentials](/creator/3d-modeling-and-animations/3d-models.md) for tips on how to create 3D models for Decentraland.

You don't need to create your own assets, though. See [Useful Resources](/creator/scenes-sdk7/getting-started/useful-resources.md) for asset libraries and generative AI tools you can use to source 3D models, as well as other tools that can speed up your workflow.

## Run a local preview

To run a preview of your scene, open it in the Creator Hub and click the **Preview** button. Alternatively, if you're working from the command line, run `npm run start` on your project's root folder.

* [Preview your scene](/creator/scenes-sdk7/getting-started/preview-scene.md) for more details.
* Check the [Debug a scene](/creator/scenes-sdk7/getting-started/preview-scene.md#debug-a-scene) for tips on how to debug any issues.
* Enable **Optimize Assets** in the preview settings (or run `npm run start -- --local-ab` from the CLI) to load your 3D models as optimized asset bundles. The preview runs smoother and shows the models just as they'll look once published. See [Preview with optimized assets](/creator/scenes-sdk7/getting-started/preview-scene.md#preview-with-optimized-assets).

{% hint style="info" %}
**💡 Tip**: When using the Creator Hub, every time you make a change on your scene, the preview is automatically updated. Even while running.
{% endhint %}

## Publish to Decentraland

Once you're happy with your scene, it's time to publish to Decentraland. For this, you need to own LAND, a Decentraland NAME, or an ETH ENS name, or have permissions given by someone that does.

See [publishing](/creator/scenes-sdk7/publishing/publishing.md) for instructions on how to do that.

Alternatively, you can publish to [Worlds](/creator/scenes-sdk7/publishing/publishing-options.md#decentraland-worlds), a personal 3D space that doesn't require LAND.

## Promote

Now that your scene is out there, spread the voice! Here are a few ways to do that:

* Share it on social media (#DCL)
* Announce it on [Discord](https://dcl.gg/discord)
* Submit it to be featured on [events.decentraland.org](https://events.decentraland.org/)
* Organize an event in your scene
* Add a spawn point on a high-traffic area that links to your scene

## Iterate

Once your scene has been live for a while and you've gotten feedback from players, you're in a great position to iterate on it!

Update your content with improvements and new features, deploying new versions of your scene to the same coordinates.

## Giving back

If you create a scene, game, or application that you're proud of, consider making it open source! That way others can learn from your code and build on your work. You can also share the whole project in [Awesome Repository](https://github.com/decentraland-scenes/Awesome-Repository).

If you build a reusable piece of functionality, you may want to make it into a library that others can import into their projects.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.decentraland.org/creator/scenes-sdk7/getting-started/dev-workflow.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.
