> For the complete documentation index, see [llms.txt](https://academy.any2info.com/any2info-academy/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://academy.any2info.com/any2info-academy/no-code-platform/app-studio/designertools.md).

# Designer tools

The user interface and functionality of any application can be built  on the designer screens where all tools are available.

Any2info distinguishes between 3 types of layout that can be put together in the app studio in a dedicated "Designer screen" available for this purpose. 

In all cases, the composition of the work takes place visually on a central work surface, called [**canvas**](/any2info-academy/no-code-platform/app-studio/designertools/canvas.md)**,** with functions on the [**toolbar**](/any2info-academy/no-code-platform/app-studio/designertools/toolbar.md), the [**left sidebar**](/any2info-academy/no-code-platform/app-studio/designertools/left-sidebar.md), the [**right sidebar**](/any2info-academy/no-code-platform/app-studio/designertools/right-sidebar.md) and in the [**footer**](/any2info-academy/no-code-platform/app-studio/designertools/footer-functions.md) of the designer screen.

In the footer bar there are functions to **add default** [**styling**](/any2info-academy/no-code-platform/app-studio/designertools/stylesheets.md) (text, colors, [**icons**](/any2info-academy/no-code-platform/app-studio/designertools/icons.md), etc.) to the application components. 

<figure><img src="https://870194474-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-M_kE41Rl4pOtwKfvvQq%2Fuploads%2FuXFILhqVCIKAxuxKqDMU%2FImage%20designer%20tools.png?alt=media&amp;token=1e2b1d25-f41e-4e50-a526-74499a90aab2" 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://academy.any2info.com/any2info-academy/no-code-platform/app-studio/designertools.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.