> For the complete documentation index, see [llms.txt](https://docs.eximee.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.eximee.com/documentation/documentation-en/budowanie-aplikacji/interfejs-uzytkownika/formularze/style-formularza-i-style-komponentu.md).

# Form styles and component styles

## Adding CSS styles to the application <a href="#title-text" id="title-text"></a>

After clicking the button in the left sidebar menu **Application style** ![](https://wiki.consdata.pl/download/thumbnails/221080918/image2021-7-23_9-47-27.png?version=1\&modificationDate=1627026448030\&api=v2) a side panel with the CSS stylesheet editor embedded in the application will slide out. The button **Application style** is visible only in the editor **Request**.

<figure><img src="https://2112972046-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2CssJT0zIo4SJQLbSZ6l%2Fuploads%2FSMcm57wtXSxf13uD8Scg%2Fimage.png?alt=media&amp;token=e61a6696-0c97-492e-bd6a-289397fbf132" alt="" width="563"><figcaption><p><em><strong>Figure 1.</strong> Application style editing panel</em></p></figcaption></figure>

The CSS editor offers:

* CSS syntax highlighting and autocomplete,
* text search,
* basic CSS validation,
* automatic refresh of the application after every change to the CSS definition.

The created style is applied by entering its name in the field **Style names** available in the section **Styling** panel **Properties**.

## Component styling and platform styles

Base components can be assigned styles defined in the platform or styles created in the application. Their names should be added in the panel **Properties** → section **Styling** → **Style names** (add subsequent styles by pressing the Enter key).

<figure><img src="https://2112972046-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2CssJT0zIo4SJQLbSZ6l%2Fuploads%2FInzGqtM0R05vRCPMCpgu%2Fimage.png?alt=media&amp;token=47174030-8536-47c2-b998-056761fd07fb" alt=""><figcaption><p><em><strong>Figure 2.</strong> Example style <strong>ex-textfield-without-left-padding</strong> added to the component</em></p></figcaption></figure>

\
\
When adding a platform style, we get a list of style suggestions available for a given component.

<figure><img src="https://2112972046-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2CssJT0zIo4SJQLbSZ6l%2Fuploads%2F8jLl3zt3yiYRECXwzdx9%2Fimage.png?alt=media&amp;token=45c3b53f-1aa1-4eae-8bc0-81cd3bba2ede" alt=""><figcaption><p><em><strong>Figure 3.</strong> Example list of suggestions for the Label component</em></p></figcaption></figure>

{% hint style="warning" %}
Available platform styles may vary depending on the deployment
{% endhint %}


---

# 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.eximee.com/documentation/documentation-en/budowanie-aplikacji/interfejs-uzytkownika/formularze/style-formularza-i-style-komponentu.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.
