Component/Schema Configuration

Section titled Field types Field types

One field type is the smallest part in Storyblok terminology. It can be a single input field or even a custom field type (plugin). You can see the list of all field types in the following table with links to the detailed documentation of the field type.

Here you can learn more about all options when configuring your content types and components in Storyblok.

Section titled Config Tab Config Tab

You can find the general settings in the Config tab of your component/content type.

Section titled Technical name Technical name

This is the technical name that will be included in the JSON content of your content entries under the attribute component. If you do not define a "Display name" the "Technical name" will be transformed to a human-readable name in the editor interface. For example: "feature_area" will be transformed to "Feature Area".

Be aware! Changing the technical name can take a few minutes to update all content items. Make sure your editors have saved their current work and exit the editor. If you use branches, only the "Preview" branch will have the new component name until you deploy the other branches.

Section titled Display name Display name

The value of this field will be shown for editors as a component/content-type name. If this field is empty, the "Technical name" will be shown.

<div id="topic-preview"></div>

Section titled Preview field Preview field

The preview field allows you to select one of the fields you set up in the schema so that the value entered in this field will be shown when you see this block in the overview (e.g., in the body with nestable blocks). For example, if you set up a headline text field, you could set this as the preview. Storyblok automatically sets one of the fields as a preview

Section titled Preview template Preview template

With this option, you can define a template that gets rendered in the blocks field. The template language you can use here is based on Squirrelly 8.

If you still have templates based on Squirrely 7, you can see our old documentation here. Please update your old templates.

To render the preview, you use the following template.

<div>{{it.text}}</div>
<!-- ".image" is the field name -->
{{@image(it.image.filename)/}} 

<!-- old image field -->
{{@image(it.image)/}} 

All fields you have defined in your schema can be used with the following syntax: {{it.YOUR_FIELD_NAME}}. When using helpers like @if() or @image() the attributes are accessible via the it object.

Allowed HTML tags

• Tags: div, span, strong, ul, li, p
• Attributes: class

Styling

Preview templates can be styled using the blok ink: classes for specific text styling:

<div class="text-red">{{it.error}}</div>

Linked Stories

If you linked another story inside your schema through a single or multi-select field, you could only use the story id in the preview template, not the fields inside that linked story.

# possible
<div>{{it.linkedAuthor}}</div>

# not possible
<div>{{it.linkedAuthor.name}}</div>

Available helpers

@image

{{@image(it.image.filename)/}}

if/else

{{@if(it.your_attribute === "1")}}
Display this
{{#else}}
Display that
{{/if}}

@each

{{@each(it.somearray) => val, index}}
Display this
The current array element is {{val}}
The current index is {{index}}
{{/each}}

@foreach

{{@foreach(it.someobject) => key, val}}
This loops over each of an objects keys and values.
The value of the current child is {{val}}
The current key is {{key}}
{{/foreach}}

Section titled Preview Screenshot Preview Screenshot

This option lets you define a screenshot shown when the user inserts a new component in the blocks field. This helps the user to identify the component type better.

Section titled Block icon Block icon

Here you can set the icon that defines this block.

Section titled General configuration options General configuration options

All field types except the Blocks are translatable and all field types contain general configuration options - Required, Description, Display name.

Section titled Text Text

The text field should be used for short one-line long strings. The most common use case is the name of the product or author.

Sample JSON produced by Text Field:

        
      "content": {
  "field_name": "Value of the field"
}

    

Section titled Textarea Textarea

Textarea field should be used for one paragraph without the possibility of styling or creating multiple paragraphs. The most common sample is a short teaser text of a product or article.

Sample JSON produced by TextArea Field:

        
      "content": {
  "field_name": "Value of the field"
}
    

Section titled Image Image

The image field is used to insert or select images from the assets library. It can be used to crop your images to the preferred ratio.

Section titled How to crop the image? How to crop the image?

You can crop the image by clicking on the image thumbnail. This action will open the image overlay, where you can select the cropped area from the original image.

If you set Force Crop to true, you are able to predefine the ratio or fixed-sized of the crop area. In this case, the content editor will be forced to crop the image in the predefined size or ratio.

Sample JSON produced by Text Field:

        
      "content": {
  "field_name": "//a.storyblok.com/f/81002/200x200/df0881e1b2/unnamed.jpg"
}
    

Section titled Date/Time Date/Time

Sample JSON produced by Date/Time Field:

        
      “data”: “2023-11-21 23:56"
    

Section titled Boolean Boolean

Boolean is one of the Basic Field Types. It indicates a checkbox, which can hold two values, either True or False.

You can filter entries by boolean value. Imagine you want to allow your editors to have featured products with a boolean flag in your content schema. To filter all products to only receive the featured once you can utilize the filter_query operation to check for an exact value.

Sample JSON produced by Boolean Field:

        
      "content":false
    

Section titled Link Link

Links are another representation of your content entries, eg. Stories. With the Links format, you can resolve uuids of stories. The links object returned consists of multiple keys, where each key is the uuid of one Story. In the link object, you will have access to basic information to identify, load or already display a link to that resource.

Section titled The Link(s) Object The Link(s) Object

You can access a draft or published versionof your links by providing the version parameter and the correct token type (eg. preview for draft, public for published).

Section titled Retrieve Multiple Links Retrieve Multiple Links

Returns the links object containing all links of one space. Use the version parameter and the correct token types to receive either draft and published or only published links.

Section titled Anchor option for internal link Anchor option for internal link

It is also possible to set an anchor for internal links. The option can be enabled in the schema configuration as shown below.

Section titled Dynamic Links Dynamic Links

If you're looking for anchor links for lets say headlines it would be something to be implemented in your frontend which can take the current string of your headline and transforms it to a specific entry. One example would be Anchorjs.

Sample JSON produced by Link Field:

        
      "content":{
  "id":"","url":"","linktype":"story","fieldtype":"multilink","cached_url":""
}
    

Section titled File File

A single file upload input and access to the asset manager.

Section titled Asset Asset

Assets in Storyblok are all files that you upload either using an image, file or multi-assets field or in the asset manager itself. Assets uploaded to Storyblok will be hosted on our infrastructure and delivered through our CDN with the best possible performance for you. Additionally, you can use our built-in image service to optimize and resize your images. Below you can find the MIME types for each asset type.

Section titled The Asset Object The Asset Object

You can now choose “Default Asset Folder” for the field type file which was previously only available for the type image.

Sample JSON produced by File Field:

        
      "content":{
  "id":"","url":"","linktype":"story","fieldtype":"multilink","cached_url":""
}
    

Section titled Multi-Asset Multi-Asset

A multi-asset upload input, including a description for each and access to the asset manager.

Additionally, you can use our built-in image service to optimize and resize your images. Below you can find the MIME types for each asset type.

• Multi-Asset fields can be reordered via drag controls.
• You can allow multiple image uploads in one field using the multi-asset field type.

Sample JSON produced by Multi-Asset Field:

        
      "content":{
  "id":"","url":"","linktype":"story","fieldtype":"multilink","cached_url":""
}
    

Section titled Single-Option Single-Option

Single-Option is a dropdown of key/value pairs, Stories, Datasources, external JSONs, or Field Level Translation Languages.

Section titled SOURCE TYPE SOURCE TYPE

There are several source types in the Single-Option Field which are as below:

Section titled Self Self

Sample JSON produced by Single-Option Self Source Field:

        
      "content":{
  "id":"","url":"","linktype":"story","fieldtype":"multilink","cached_url":""
}
    

Section titled Stories Stories

Sample JSON produced by Single-Option Stories Source Field:

        
      "content":{
  "id":"","url":"","linktype":"story","fieldtype":"multilink","cached_url":""
}
    

Section titled Languages Languages

Sample JSON produced by Single-Option Languages Source Field:

        
      "content":{
  "id":"","url":"","linktype":"story","fieldtype":"multilink","cached_url":""
}
    

Section titled Datasources Datasources

Sample JSON produced by Single-Option Datasource Source Field:

        
      "content":{
  "id":"","url":"","linktype":"story","fieldtype":"multilink","cached_url":""
}
    

Section titled External JSON External JSON

Sample JSON produced by Single-Option External JSON Source Field:

        
      "content":{
  "id":"","url":"","linktype":"story","fieldtype":"multilink","cached_url":""
}
    

Section titled Multi-Option Multi-Option

A multi-select option of key/value pairs, Stories, Datasources, external JSONs, or Field Level Translation Languages. 

All the configuration options are similar to Single-Option. The only difference is that we get an additional configuration option in Multi-Option, which is as below:

Section titled The default value for multi-options The default value for multi-options

You can set a Default Value for multi-options with the following schema:

        
      [ "your_first_value", "your_second_value", "third", ... ]
    

Sample JSON produced by Multi-Option Field:

        
      "content":["value1","value2", ... ]
    

Section titled Number Number

A number text field without formatting. 

Sample JSON produced by Number Field:

        
      "content":"number_value"
    

Section titled Markdown Markdown

Write markdown with a text area and additional formatting options.

There is also an example of how to use it with our migration CLI to transform fields.

Sample JSON produced by _Markdown Field (for bold & italic):

        
      "content":"**Bold**\n\n*Italic*"
    

Section titled Richtext Richtext

A multi-line field with formatting options that results in a JSON format. Storyblok comes with a powerful Richtext editor that saves your content in a structured JSON format. You can customize the toolbar for each field individually and even let the user insert Storyblok blocks. If you have written your content in Markdown you can import it using the toolbar button "Paste from Markdown".

Section titled Features Features

• Customizable Toolbar: Bold, Italic, Strikethrough, Underline, Inline-code, Code-block, Paragraph, H1, H2, H3, H4, H5, H6, Unordered list, Ordered list, Quote, Horizontal rule, Link, Image, Components, Paste Markdown, Emoji, Text coloring, Undo/Redo, Subscript, Superscript, Anchor
• Clean JSON Output
• JSON to HTML converter included in SDKs
• Advanced link dialog with "New window" option and asset link function
• Advanced image dialog with alt-tag and title definition
• Component insertion with allowlist option
• Paste from Markdown import function
• Auto-height and sticky-toolbar
• Works with export and import app
• Code-language selector of code-block

Sample JSON produced by Richtext Field (for bold , italic and anchor):

        
      "content": {
  "type": "doc",
  "content": [
    {
      "type": "paragraph",
      "content": [
        {
          "text": "Hello, world.",
          "type": "text",
          "marks": [
            {
              "type": "anchor",
              "attrs": {
                "id": "test-anchor-id"
              }
            }
          ]
        },
        {
          "text": " this is some ",
          "type": "text"
        },
        {
          "text": "dummy",
          "type": "text",
          "marks": [
            {
              "type": "bold"
            }
          ]
        },
        {
          "text": "testing",
          "type": "text",
          "marks": [
            {
              "type": "italic"
            }
          ]
        }
      ]
    }
  ]
}
    

Section titled Table Table

It is easy to use field type to manage tables.

Section titled Features Features

• Add, move or delete rows and columns
• Outputs structured JSON
• Allows multi-line text
• Works with translation export and import

Section titled Developer documentation Developer documentation

The table field type stores its information as structured JSON and you need to take care of the rendering of the HTML.

Following an example:

        
      {
  "plugin": "translateable-table",
  "thead": [
    {
      "value": "Head1"
    },
    {
      "value": "Head2"
    }
  ],
  "tbody": [
    {
      "component": "_table_row",
      "body": [
        {
          "component": "_table_col",
          "value": "one"
        },
        {
          "component": "_table_col",
          "value": "two"
        }
      ]
    }
  ]
}
    

In a template language like Liquid you could write something like the following to render the table:

        
      <table>
  <thead>
    <tr>
      {% for th in content.thead %}
        <th>{{ th.value }}</th>
      {% endfor %}
    </tr>
  </thead>
  <tbody>
    {% for tr in content.tbody %}
      <tr>
        {% for td in tr.body %}
          <td>{{ td.value }}</td>
        {% endfor %}
      </tr>
    {% endfor %}
  </tbody>
</table>
    

Sample JSON produced by Table Field:

        
      "content":{
  "tbody":[
  {
    "_uid":"a3fc5b10-d309-41af-89a0-d5131d93ce4f",
    "body":[
    {
      "_uid":"ede4bb0f-a25c-4046-9d52-0e71f6a6bb14",
      "value":"",
      "component":"_table_col"
    },
    {
      "_uid":"05527061-fb62-4127-9219-0667f707470e",
      "value":"",
      "component":"_table_col"
    },
    {
      "_uid":"fbd202c7-ebd9-423c-95ab-4489478073d3",
      "value":"",
      "component":"_table_col"
    }],
    "component":"_table_row"
  }],
  "thead":[
  {
    "_uid":"e35c2247-d319-4f6e-8fff-b4c52b66cc92",
    "value":"Heading 1",
    "component":"_table_head"
  },
  {
    "_uid":"e3142f21-ea52-4ac3-bef6-616f327e71d6",
    "value":"Heading 2",
    "component":"_table_head"
  },
  {
    "_uid":"051e9c71-9839-4cdd-b4b6-43d663111b27",
    "value":"Heading 3",
    "component":"_table_head"
  }],
  "fieldtype":"table"
}
    

Section titled Blocks Blocks

Blocks is a field to interleave other components in your current one, a field to allow nesting of Bloks.

This type of component lives only within a Story and other Bloks, like Hero, Grid, and Full-Width Image. You can’t create new Stories from this as it is only a part of one Story. To use them in one content type you will need to create a field of the type blocks that

allows the nesting of components.

        
      {
    "story": {
    "uuid": "ac0d2ed0-e323-43ca-ae59-5cd7d38683cb",
    "name": "My third post",
    "slug": "my-third-post",
    "full_slug": "posts/my-third-post",
    "content": {
-      "component": "your_content_type",
+      "component": "page",
        // fields you define for your content type
+      "body": [ // also a field you defined (type blocks)
+         {
+            "component": "teaser",
+            "headline": "My headline Content",
+            // fields you define for your blok
+         }
        ]
    },
    ...
}
    

Section titled Nestable blocks Nestable blocks

Every block in Storyblok can have child blocks. If you define a block as nestable, then the editor of the content can position that block in a nestable area.

Usually, root blocks like pages, articles and products aren’t defined as nestable, as they are designed to build the root of your content structure. Read more on “What is a root block?”.

Sample JSON produced by Block Field (added Button block):

        
      "content":[
{
  "_uid":"f96a9549-9687-4351-849b-89ac8c55a3c2",
  "link":"",
  "text":"",
  "style":[],
  "component":"button",
  "is_inline":false,
  "paragraph_style":[]
}]
    

Section titled Group Group

Group field allows you to group fields in a section (no input possibility).

Section titled Component Groups Component Groups

A component group can be used to group components together. Each component can have only one component group.

Section titled The Component Object The Component Object

Section titled The Component Group Object The Component Group Object

Section titled Retrieve one Component Group Retrieve one Component Group

Returns a single, fully loaded component group object by providing a specific numeric id.

Section titled Retrieve multiple Component Groups  Retrieve multiple Component Groups 

Returns an array of component group objects. The response of this endpoint is not paginated and you will retrieve all component groups.

Section titled Create a Component Group Create a Component Group

Section titled Delete a Component Group Delete a Component Group

Delete any component group using its numeric id.

Section titled Conditional Fields Conditional Fields

Section titled Plugins aka Custom Field Type Plugins aka Custom Field Type

A custom field type is a field type (plugin) that can be created by you or your developer to fulfil special requirements, that can't be fulfilled by the default set of the field types. The common sample is the integration with 3rd party services as e-shops or image services as Cloudinary.

Section titled Presets Presets

A preset defines the sample data of the component and each component may have defined a list of multiple presets. This feature should be used to guide your content creator in the process of creating new stories as they don't have to start always with empty components. They may choose one of the presets and tweak the data of it. Only a user with developer rights may create/edit preset.

Section titled Example use case Example use case

Let's say we have a teaser component with three different design variants. 

1. Teaser with background image
2. Teaser with background colour and text
3. Teaser with a call to action button

We could define three different components in Storyblok or we can define a component called Teaser with different options. The single-component approach can be difficult to understand for a content creator without enough experience. To make the process easier, we can define three presets for those three variants and let the content creator choose the preset in the creation process. This will add a component with pre-filled values into the Story.

Section titled How to define Preset? How to define Preset?

Only developers can create and edit the Presets. If the developer opens the Story in the Content Editor, he/she can see the Define schema button and next to it a dropdown arrow. The Define Preset button is hidden in this dropdown. By using the Define preset button a preset overlay is open, where you can define the Name of the preset and see the existing presets plus which one is selected as the default one for the component. After filling in the name of the preset and clicking the Add preset button, the preset is created in the component.

You may always edit the preset by clicking on the name of the preset in the list of existing presets. This will open for you the following options.

• Presets can be also managed using the Management API. Read more about it in the MAPI Docs.