> For the complete documentation index, see [llms.txt](https://docs.jetadmin.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.jetadmin.io/component-designer/how-to-work-with-component-designer.md).

# How to work with component designer

**Component Designer** has six distinct areas: 

1. **Toolbar** – find tools to switch between selection and hand, and also to create [frames](/component-designer/frames-and-groups.md), shapes, text, images and [action components](/component-designer/action-components.md). These will be the building blocks of your designs.
2. **Parameters** – allow you to pass dynamic variables from your app to the component ang change states
3. **Actions** – trigger actions on the page, outside of your component
4. **Layers sidebar** – gives you access to layers.
5. **Canvas** – is your working area where you’ll arrange layers to create your designs. You’ll find lots of room to explore and iterate on your ideas.
6. [**Right sidebar**](/component-designer/right-sidebar.md) – access more information about your layers. With a layer selected, you can explore the properties of your current selection.

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


---

# 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.jetadmin.io/component-designer/how-to-work-with-component-designer.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.