Is there a help page for nesting structure in blueprints

Kirby 3 Solved ✅
1

Hi,

Is there a page somewhere in the guide where you show the appropriate structure for blueprints? My structure seems completely off and i’m getting errors such as all my fields buying named the same.

Here is my code for those interested:

# Each page blueprint must have a title, the title may be different from the file name
title: Assurance vie

icon:

options:
  pages: true
  url: true
  duplicate: false
  delete: false
  update:
      *: true

columns:
  column_headline:
    sections:
      content:
        type: fields
        fields:
          Headline:
            type: text
            width: 1/2
            label: Main Title
          gap:
            width: 1/2
          HeadlineText:
            type: textarea
            width: 1/2
          gap:
            width: 1/2
  column_subheadline:
    sections:
      content:
        type: fields
        fields:
          SubHeadline:
            type: text
            width: 1/2
            label: Main Title
  column_subheadline_1:
    sections:
      content:
        type: fields
        fields:
          SubHeadline_1:
            type: text
            width: 1/2
            label: Main Title
          SubHeadlineText_1:
            type: textarea
            width: 1/2

Any tips or resources I can be referred to?

Thanks!

2

All keys in your blueprint must be unique, so you cannot use the same name for sections, fields, tabs etc. more than once per blueprint.

But I see 3 sections called content in your example, two fields called gap.

And your options are also named wrongly; Page blueprint | Kirby CMS

3

I see but I feel like i’m not though? Which ones am I using more than once? Except for “gap” but I think this one doesn’t count?

Also, can we use the same keys for different blue prints? For example, can each separate blue print for my pages have all the same keys?

4

See my post above:

As I said: they must be unique per blueprint which means, yes you can use the same keys in different blueprints…

It does, keys must be unique-all keys.

5

Ahhh I see. Thank you so much. I’ll give it a try.

6

I can’t seem to find where my options are named wrong. I checked the link you gave me, but they seem to be ok. Could you guide me in the right direction?

Also, the reason why I called some keys “gap” is because I just want to basically create a new paragraph for the new key without it extending 1/1. It says “Invalid field type (“gap_1”)” - Solved

Thank you.

7

The options pages and url don’t exist, delete, duplicate and update are fine.

8

Got it. I’ll remove them.

One more question: My “textarea” type field doesn’t seem to register any of the formatting from my panel. For example, when I create a new paragraph in my text area, it doesn’t show it on the front end and just bunches everything up. is there something else I must add?

Here’s the code for thr particular field:

column_headline:
    width: 2/3
    sections:
      headline_content:
        type: fields
        fields:
          headline:
            type: text
            label: Headline
          headlineText:
            type: textarea
            label: Headline Text

You’ve been a lot of help. Thanks :slight_smile:

9

How do you output the textarea field on the frontend? To output markdown and kirbytext tags, you need to render the field value with the kirbytext() method, see docs: Textarea | Kirby CMS

10

Yup that was it. I was just outputting it as regular text. Thank you!