Fieldsets are used to store and organize reusable fields.


Fieldsets are almost functionally equivalent to Blueprints, except that they exist for you to be able to create reusable fields.

While Blueprints attach directly to content like collections or forms, Fieldsets are not directly attached to anything.

Fieldsets contain fields, just like Blueprints, but the benefit of using a Fieldset is that you can import their fields (or the whole thing) into other Blueprints. You can even import fieldsets into certain fieldtypes, like Grid, Replicator, or Bard.

Fieldsets can only have fields. They don't have sections like Blueprints can.

Creating Fieldsets

There are 2 ways to create fieldsets:

  • In the Fieldsets area of the control panel.
  • Creating a YAML file in the appropriate place within resources/fieldsets/. More on that in a moment.

Once created, you can begin to define its fields.

Directory Structure

Whether you manually create your fieldsets's YAML file, or use the control panel, they will all end up as YAML files in the resources/fieldsets directory.


YAML Structure

At its most basic, a fieldset has an array of fields.

handle: content
type: markdown
handle: featured
type: toggle

Using Fields

As mentioned earlier, a Fieldset is not inherently attached to anything. In order to use a field (or fields) in a fieldset, you'll need to approach it from the Blueprint side.

See the Reusable Fields section of the Blueprint docs for more details.

HR: Section
Learn More!

There is more to learn more in these related articles:

HR: Section
Docs feedback

Submit improvements, related content, or suggestions through Github.

Betterify this page →