Difference between extending blueprints (simple and extended)

Kirby 3 Solved ✅
1

Hi there,

can anybody explain me the difference between the simple extended blueprint and the extended extended blueprint :slight_smile:

This works:

sidebar: pages/fields/sidebar

And also this:

sidebar:
    extends: pages/fields/sidebar

What’s the exact difference? Inside of the yaml file there are multiple fields like this:

type: group
fields:

  content_sidebar_top:
    label: Sidebar Top
    type: textarea
    
  content_sidebar_bottom:
    label: Sidebar Bottom
    type: textarea
2

The first version is usually used when you want to use the field group “as defined” in the field blueprint (the external file, e.g. pages/fields/sidebar).

The second version is usually used if you want to use the field group as a “skeleton”, but want to “alter” things that are defined in the field blueprint (e.g. field names).

3

Thanks for the answer. So it makes more sense to use the “extended” one cause of flexibility? But how can field names be changed? Or did you mean the Label or such things as default values or similar?

4

AFAIK every property can be overridden. You can have a look at the guide on how to implement this in field groups: https://getkirby.com/docs/guide/blueprints/extending-blueprints#reusing-and-extending-field-groups

5

Thanks :slight_smile: