> 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.md).

# Components

Browse the components available for building pages in Elements

Components are the building blocks used to create pages in Elements. Drag them onto the canvas, add content, and customise their appearance and behaviour in the Inspector.

The included collection is organised by purpose below. Store Components are installed separately, while Custom Components and the Elements API let developers create their own building blocks.

### Included Components

| Category                                                                                             | Includes                                                                                |
| ---------------------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------- |
| [Layout Components](/elements-docs/using-elements/components/layout-components.md)                   | Container, Divider, Flex, Grid, and Text Wrap                                           |
| [Content and Media](/elements-docs/using-elements/components/content-and-media.md)                   | Audio, Gallery, Image, Image Slider, Markdown, SVG, Text, Typography, and Video         |
| [Navigation and Interaction](/elements-docs/using-elements/components/navigation-and-interaction.md) | Accordion, Breadcrumbs, Button, Content Slider, Dropdown, Menu, Modal, Reveal, and Tabs |
| [Data and Organisation](/elements-docs/using-elements/components/data-and-organisation.md)           | CMS, Filter, Filter Tags, List, Table, Top Pages, and Tree                              |
| [Styling and Effects](/elements-docs/using-elements/components/styling-and-effects.md)               | 3D Transform, Background, Elements Badge, and Mask                                      |
| [Form](/elements-docs/using-elements/components/form.md)                                             | Form structure, fields, submission, success, error, and email delivery                  |

### Common Controls

Many components share controls for layout, sizing, spacing, typography, backgrounds, transitions, effects, filters, transforms, borders, and advanced settings.

[Browse the Common Controls reference](/elements-docs/using-elements/components/common-controls.md).

### Store Components

The Elements Store provides additional free and paid components that install into Elements.

[Browse Store Components](/elements-docs/using-elements/store-components.md).

### Custom Components

If you know some HTML, you can create project-specific components with editable content, dropzones, Inspector controls, styles, JavaScript, and build-time hooks.

[Learn about Custom Components](/elements-docs/developers/custom-components.md) or open the [Elements API overview](/elements-docs/developers/building-extensions.md).

{% hint style="info" %}
The components supplied with Elements use the same API available to third-party developers. Their source is a useful reference when you are ready to build complete Element Packs.
{% 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.realmacsoftware.com/elements-docs/using-elements/components.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.