Support for tabs

[jasonvarga]

In Statamic 4, blueprints were updated a little. PHPStorm users (and probably other editors using this schema) are now seeing validation errors.

Blueprints can have a top level tabs key. The tabs are keyed by handle.

Each tab has multiple sections, which do not have named keys.

title: My Blueprint
tabs:
  tab_one:
    display: Tab One
    sections:
      -
        display: My Section # optional
        instructions: Some instructions #optional
        fields: [] # Same as existing fields.
      -
        fields: []

The top level sections as used on Statamic 3.x is still valid.

If I can help, let me know. But I'm sure you can update this more easily than me.

[Konafets]

@jasonvarga Thanks for bringing this up. One question: Does the top level section must still be present?

[jasonvarga]

Does the top level section must still be present?

Nope.

In v4, only tabs will be at the top level, if you are using the Control Panel to save your blueprint.
But we still support sections at the top level in order for v3 blueprints to be backwards compatible.

Does that make sense?

[Konafets]

After an upgrade from v3 to v4 a v3 blueprint with the old structure can still be used but will updated to the new form only if the user saves it via CP? In essence the schema must allow both versions at once. Is that correct?

[jasonvarga]

Correct!