> For the complete documentation index, see [llms.txt](https://docs.realmacsoftware.com/elements-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.realmacsoftware.com/elements-docs/using-elements/components/common-controls.md).

# Common Controls

Common Controls are reusable Inspector groups that behave consistently across built-in components. Learning them once makes it easier to size, position, style, animate, and link components throughout a project.

The available groups depend on the selected component. Some components use a specialised variant with different defaults—for example, Image starts at 100% width, while a general component starts at Auto.

{% hint style="info" %}
Many values are responsive. When a control supports breakpoints, set the Base value first and add overrides only where the design needs to change.
{% endhint %}

<table data-view="cards"><thead><tr><th></th><th data-hidden data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td>Link</td><td><a href="/pages/D4lxTb6vEFswWpqxxvr9">/pages/D4lxTb6vEFswWpqxxvr9</a></td></tr><tr><td>Layout</td><td><a href="/pages/SMWGDh3L6XluqRMa4hsb">/pages/SMWGDh3L6XluqRMa4hsb</a></td></tr><tr><td>Sizing</td><td><a href="/pages/WBaHHB2jO7Zr3ZpxXVBO">/pages/WBaHHB2jO7Zr3ZpxXVBO</a></td></tr><tr><td>Spacing</td><td><a href="/pages/2Ziv1KCK4YcA6v2MaqWY">/pages/2Ziv1KCK4YcA6v2MaqWY</a></td></tr><tr><td>Typography &#x26; Text Styles</td><td><a href="/pages/RjrGDVpM4u1ATaKBt5lP">/pages/RjrGDVpM4u1ATaKBt5lP</a></td></tr><tr><td>Backgrounds</td><td><a href="/pages/hti3RweqHkEG6z0KRerc">/pages/hti3RweqHkEG6z0KRerc</a></td></tr><tr><td>Transitions</td><td><a href="/pages/3NVE1GJDVqKxh1Qkzely">/pages/3NVE1GJDVqKxh1Qkzely</a></td></tr><tr><td>Effects</td><td><a href="/pages/3Nhy3ktStoFSz2p5pjuF">/pages/3Nhy3ktStoFSz2p5pjuF</a></td></tr><tr><td>Filters</td><td><a href="/pages/QtJazNu4mLHqTGzpGtpg">/pages/QtJazNu4mLHqTGzpGtpg</a></td></tr><tr><td>Transforms</td><td><a href="/pages/zcVKcbyNYgzjjNB25N2j">/pages/zcVKcbyNYgzjjNB25N2j</a></td></tr><tr><td>Borders</td><td><a href="/pages/kY3SDwZZjIWIZ4eCS9vQ">/pages/kY3SDwZZjIWIZ4eCS9vQ</a></td></tr><tr><td>Advanced</td><td><a href="/pages/tS9mMbKxZvJF5VipaG19">/pages/tS9mMbKxZvJF5VipaG19</a></td></tr></tbody></table>

### How Common Controls Work

* **Theme values** use colours, spacing, typography, shadows, and borders defined in Theme Studio.
* **Custom values** accept valid CSS values where the control provides a manual mode.
* **Responsive controls** can be overridden at different breakpoints.
* **State controls** let you edit Static, Start, End, Normal, Hover, or other states without changing the state visitors initially see.
* **Conditional controls** appear only after the related feature is enabled or a compatible Type or Style is selected.

Individual component pages document any specialised defaults or behaviour that differs from these shared guides.


---

# 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.realmacsoftware.com/elements-docs/using-elements/components/common-controls.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.