Palette

The Palette field is used to group other fields. Grouped fields will be displayed next to each other rather than below each other.

Pre-defined palettes as for example the TYPO3/Header palette for Content Elements are available as Basics.

Warning

Palettes are defined on table definition level. This means if you define a Palette with identifier "my_palette" in Content Block A and Content Block B of the same type (e.g. ContentElement), then they will override each other. So make sure to have unique identifiers. An exception to this rule is using Palettes inside Basics. Then you can share them, while the configuration always stays the same, as they are centrally defined.

Labels

XLF translation keys for Palettes have the following convention:

<body>
    <trans-unit id="palettes.PALETTE_IDENTIFIER.label">
        <source>Label for Palette</source>
    </trans-unit>
    <trans-unit id="palettes.PALETTE_IDENTIFIER.description">
        <source>Description for Palette</source>
    </trans-unit>
    <trans-unit id="COLLECTION_IDENTIFIER.palettes.PALETTE_IDENTIFIER.label">
        <source>Label for Palette in Collection</source>
    </trans-unit>
    <trans-unit id="COLLECTION_IDENTIFIER1.COLLECTION_IDENTIFIER2.palettes.PALETTE_IDENTIFIER.label">
        <source>Label for Palette in nested Collection</source>
    </trans-unit>
</body>

Examples

Minimal

name: example/palette
fields:
  - identifier: palette_1
    type: Palette
    label: Palette 1
    description: My palette description
    fields:
      - identifier: number
        type: Number
      - identifier: text
        type: Text

For in-depth information about palettes refer to the TCA documentation.