Basics are a concept like partials or mixins. They are used to have a pre-defined set of fields that can be reused and have to be defined only once.
There are two different ways of using it.
The first way is to use Basics like layouts for your UI. The Basics are added after the fields of your content block. This is useful if you want to have a set of fields that are always available for a content block.
List of the standard Basics shipped with Content Blocks:
This is an example on how to add the classic Fluid Styled Content “Appearance” Tab.
name: example/basics basics: - TYPO3/Appearance - TYPO3/Links fields: # - ...
You can add as many Basics as you need. Note, that all Basics are simply concatenated onto each other. Be careful, not to create an invalid state by gluing incompatible Basics together.
The second way is to use Basics directly between your custom fields. This can
be done by using the identifier and the type
name: example/basics basics: - TYPO3/Appearance fields: - identifier: header useExistingField: true - identifier: TYPO3/Links type: Basic
You can define your own Basics by placing one or more YAML files into
ContentBlocks/Basics. The name of the YAML file can be chosen freely.
Example on how to create a single Basic:
identifier: Vendor/YourBasic fields: - identifier: a_basic_field type: Text
fields part is exactly the same as in Content Blocks. Here
you can define a Tab, a Palette or simply a set of fields.
Unlike Content Block names, it is not mandatory to provide a vendor name for your Basic identifier. However, it is recommended to avoid using too generic names to avoid conflicts.