> 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-ui-builder/13.latest/getting-started/user-interface.md).

# User Interface

Before you get to know Umbraco UI Builder, you need to become familiar with the Umbraco UI and a few of its concepts. This is because Umbraco UI Builder reuses these same concepts for constructing its UI.

![Sections, Trees, and Dashboards](/files/f7TJUehXgMTNinUTOwLS)

**1. Section** A distinct area of the Umbraco backoffice.**2. Tree** A hierarchical structure to help organize a section.\
**3. Dashboard** An intro screen for a section, usually with useful links for that section.

![List View](/files/W8496xZ0WNNnrNTppKVa)

**4. List View** A list-based view of items in a tree node.

![Editor](/files/oGXZ8uhsRs2DMdqhkqrg)

**5. Editor** The main content editing area is made up of tabs, fieldsets, and fields.

![Context Apps and Tabs](/files/9cQdG7CtJlzM6j8guMkx)

**6. Context Apps** A contextual section of a given editor UI.**7. Tabs** A tabbed container of content.

![Menu Item](/files/pTmCmDLd44YZLpd2R9H4)

**8. Menu Item** A context menu item + action.

![Bulk Action](/files/bq3rzE5q6nFxxbKGX3bU)

**9. Bulk Action** An action to perform on multiple list view items at once.


---

# 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.umbraco.com/umbraco-ui-builder/13.latest/getting-started/user-interface.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.