> For the complete documentation index, see [llms.txt](https://docs.robpod.cloud/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.robpod.cloud/hmi-designer/design-steps/add-hmi-components.md).

# Add HMI Components

Once you have created a [new HMI panel](/hmi-designer/design-steps/create-new-hmi-panel.md), you can start adding **HMI Components** to it.

**HMI Components** are the basic User Interface elements that will compose your HMI panel.

Use the **Palette Toolbar** to add new HMI components to the panel.

<figure><img src="/files/N0vVkexYqqAt8TYTxVfY" alt=""><figcaption></figcaption></figure>

Click on a HMI Components **to move it or change its size.**

<figure><img src="/files/6HZFUb9uPWgtGwu0AdUm" alt=""><figcaption></figcaption></figure>

You can view and [edit the properties](/hmi-designer/design-steps/edit-hmi-components.md) of the selected HMI Component on the **side tool window.**

<figure><img src="/files/ymTxeiivmtYExlHzUpHF" alt=""><figcaption></figcaption></figure>

Each HMI components has is own characteristic properties that determines how it looks and how it will interact with the robot program. Have a look a the [HMI components list](/hmi-designer/hmi-components.md) to check properties of each element.


---

# 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.robpod.cloud/hmi-designer/design-steps/add-hmi-components.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.