Extends and reuse for status

Hi,

Is it possible to use extends for other things than fields? I use below status at a couple of places.

status:
  draft:
    label: Draft
    text: The page is in draft mode and only visible for logged in editors.
  unlisted:
    label: Unlisted
    text: The page is public and accessible via URL.
  listed:
    label: Listed
    text: The page is public and added to the main menu.

Not possible for now, please upvote

1 Like

:+1: :+1: :+1:

I did a quick test, and this works:

/site/blueprints/options/status.yml

draft:
  label: Draft
  text: Bla bla
unlisted:
  label: Unlisted
  text: la le lu
listed:
  label: Listed
  text: blub blub blue

Blueprint:

status:
  extends: options/status
1 Like

Seems trivial, but would you accept an addition of this to your documentation, for the status section in the blueprints/Page Blueprint page? I noticed, that’s a question for which I didn’t have an answer, right from the beginning of using Kirby, and only now really took the time to look that up in the forum. After one created a couple of blueprints, this “problem of repetition” pops up frequently.

@renestalder Could you please create an issue on GitHub in the getkirby.com repo, here things get easily lost.

1 Like