> ## Documentation Index
> Fetch the complete documentation index at: https://docs.dc.ag/llms.txt
> Use this file to discover all available pages before exploring further.

# Elements

> Define element types as reusable blueprints with header and row fields.

Under **Templates → Elements** you define the **element types**: which fields an element has and how it is structured. This is the blueprint. You place the fully populated elements later via the page editor.

<Note>
  Here you create the **types**. You manage the individual **instances** (populated elements) under [Content → Elements](/docs/en/dynamic-content/user-guide/elemente); they are inserted in the editor of a page or shopping world via the **Element** tab.
</Note>

## The Standard Elements

Seven element types are delivered by default. The list shows description, code, and modification data.

<Note>
  These seven elements are only the delivered standard. You are not restricted to them: this is exactly where element types can be adjusted, added, or removed, so the available elements in your installation may differ.
</Note>

| Element         | Code             |
| --------------- | ---------------- |
| Bannergrid      | `bannergrid`     |
| Content boxes   | `contentBoxes`   |
| Image / Text    | `boxLeftRight`   |
| Benefits        | `benefits`       |
| Highlight boxes | `highlightboxes` |
| Video banner    | `videobanner`    |
| Link boxes      | `linkboxes`      |

<Info>
  You manage the fully populated elements under [Content → Elements](/docs/en/dynamic-content/user-guide/elemente).
</Info>

## Creating an Element Type

Open **Templates → Elements** and click **+ New**. In the **"Create new element"** dialog you define the basics:

* **Preview image**: Icon for recognition in the CMS
* **Code**: Unique technical identifier
* **Description**: Display name
* **Show in all languages**: Makes the type available across languages

Save first. You define the field structure afterwards in the editing view.

## Defining Fields

Select an element type and click **Edit**. The fields are divided into two areas:

<AccordionGroup>
  <Accordion title="Header Fields">
    Fields that apply once to the entire element, e.g. an overarching heading. If the area remains empty, the element has no shared header.
  </Accordion>

  <Accordion title="Row Fields">
    Fields that repeat per entry. They determine what each individual **element entry** contains (e.g. each banner of a bannergrid).
  </Accordion>
</AccordionGroup>

Each field has a **type** and a **description**. With **+ New**, **Edit**, **Delete**, and **Up** / **Down** you maintain the fields and their order.

The same types as for collection fields are available:

* **Input field**: Text, rich text field, link, option field, date, image
* **Sitepart**: full-fledged content types such as image or video

<Note>
  Bannergrid example (row fields): Sitepart Image, Sitepart Video, input field Text "Heading", input field rich text field "Subline", input field Link, input field Text "CTA Text", input field option field "Text position horizontal", input field option field "Text position vertical".
</Note>

Below, as when creating, you will find the **Preview image**, the **General** area (code, description, show in all languages), and an **Info** area with the modification data.

## Related Topics

<CardGroup cols={2}>
  <Card title="Manage Elements" icon="puzzle-piece" href="/docs/en/dynamic-content/user-guide/elemente">
    Maintain populated element instances on pages.
  </Card>

  <Card title="Content Types" icon="shapes" href="/docs/en/dynamic-content/user-guide/inhaltsarten">
    Application of the individual element types.
  </Card>

  <Card title="Collections" icon="folder-tree" href="/docs/en/dynamic-content/user-guide/kollektionen-anlegen">
    Define the structure for collections.
  </Card>

  <Card title="Page Templates" icon="clone" href="/docs/en/dynamic-content/user-guide/seitenvorlagen">
    Blueprints for entire pages.
  </Card>
</CardGroup>