> For the complete documentation index, see [llms.txt](https://docs.umbraco.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.umbraco.com/umbraco-cms/extend-your-project/backoffice-extensions/examples-and-playground.md).

# Examples and Playground

Practical examples and hands-on experience are good ways to learn.

The Umbraco CMS codebase comes with a set of customization examples and a way to run them using a local front-end server. This setup enables you to change the code and review the effects instantly by refreshing your browser.

[Browse the available examples in the Umbraco CMS Repository](https://github.com/umbraco/Umbraco-CMS/tree/main/src/Umbraco.Web.UI.Client/examples).

## Get Started

1. Clone the source code from [Umbraco-CMS GitHub repository](https://github.com/umbraco/Umbraco-CMS/).
2. Make sure you have **npm** installed.
3. Open a terminal and navigate to `src/Umbraco.Web.UI.Client` .
4. Run the command: `npm install` .

### Run an Example

Start a local server and run one of the examples: `npm run example` .

### Create a playground

You can add a new example and use it as your playground. If it covers a specific topic that would be of interest to others, you can contribute it as a pull request.

To create a new example, follow these steps:

1. Create a new folder with a name of your choice in the `examples/` folder.
2. Add an `index.ts` file that exports an array of manifests as the default export (See the other examples if in doubt).
3. Run your example using the command listed above in [Run an example](#run-an-example).


---

# 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.umbraco.com/umbraco-cms/extend-your-project/backoffice-extensions/examples-and-playground.md?ask=<question>&goal=<user_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.