Was this page helpful?

CLI tools and Studio

To get a general understanding of our CLI you can either read about it here or go through some guides like the one for scripting migrations.

Set up the CLI for use with Studio

To be able to use the CLI for scripting migrations for Studio page types, install the latest version of the Contentful CLI.

Create an initial migration for the content model of Studio

Imagine you want to start rolling out Studio in multiple spaces without the need to go through the page types setup individually in every space. In that case, you can generate yourself a migration file by running:

contentful space generate migration --space-id ...

This will create a JavaScript file for you in your current folder.

With this migration file as a starting point you can programmatically set up spaces or environments for Studio easily. See Scripting migrations with the Contentful CLI for more examples.

Add a new reference field to the Landing Page

Let's consider an example of how to expand a standard Landing page in Studio with a dedicated section for the bottom of the web page.

First, we create a file called add-bottom-section.js with this content:

module.exports = function (migration) {
  const landing = migration.editContentType('page_landing');
    .name('Bottom section')
      { linkContentType: ['component_text'] },

Then, we use that file and migrate a Studio space with:

contentful space migration --space-id ... add-bottom-section.js

We assigned the Aggregate Component annotation to the newly created reference field to make Studio expand its linked entries by default in the page editor. Our guiding principle in this case is that it inherently belongs to one particular page and won't be reused in other pages (see When to activate the Component setting for more information).

Add a new page type to Studio

As another example of tailoring Studio towards your specific needs, let's add an "About" page type with the CLI. The page type creation flow will be the same as described in Set up page types in Studio, but the CLI allows to do it programmatically rather than manually.

Again, we create our migration first. Let's call it add-about-page.js and add this content:

module.exports = function (migration) {
  // create the content type
  const about = migration
    .name('About page')
    .description('About pages')
    // assign the AggregateRoot annotation will make this content type
    // available as a page type in Studio

  // add mandatory 'name' field
  about.createField('name').name('Internal name').type('Symbol').required(true);

  // re-use the text content type
      { linkContentType: ['component_text'] },
    // assign the AggregateComponent annotation will expand the entry
    // by default in Studio

In this migration file we complete a couple of tasks to automate the creation of a new page type:

  • Create a new content type.
  • Create some fields to the new content type.
  • Assign the Aggregate Root annotation to the content type which marks it as a page type in Studio.

As a last step, apply the migration on a space that was already set up for Studio by running:

contentful space migration --space-id ... migrations/add-about-page.js

Go to Studio and you will see an "About page" as an option when creating a new page.

Add custom tabs to a page type

With field groups you will be able to organize related fields of a page type into tabs and inline groups, allowing you to build more usable forms for editors who use Studio.

In this example we have iterated on the “About page” page type by adding some more fields: a slug field (ID: slug), an SEO reference field (ID: seo) and an image field (ID: image).

Fields of the About page page type

By default, Studio page types don’t have any tabs defined. All fields appear in a generic single “Content” tab as shown below.

Default field layout of the About page page type

To give the editors a clear distinction between page content and page settings we want to organize these fields into two respective tabs and group the two SEO related fields into a field set:

Content Page settings
Text (text field)
Image (asset field)
Title (text field)
SEO settings (field set)
  Slug (text field)
  SEO (reference field)

Again, we create our migration file first. Let's call it add-groups-to-about-page.js and add this code:

module.exports = function (migration) {
  const about = migration.editContentType('page_about')
  const editorLayout = about.createEditorLayout()

  // all fields are moved to first tab implicitly

  const pageSettings = editorLayout.createFieldGroup('page_settings').name('Page Settings')

  pageSettings.createFieldGroup('seo_settings').name('SEO settings')


In this migration the following tasks are defined:

  1. Create an editorLayout for the “About page” content type.
  2. Create two tabs and move the fields into them.
  3. In the “Page Settings” tab create an “SEO settings” field set.
  4. Move the “Slug” and “SEO” fields into the “SEO settings” field set.

As a last step, apply the migration on a space that was already set up for Studio by running:

contentful space migration --space-id ... migrations/add-groups-to-about-page.js

Open up a page of the “About page” page type in Studio and you should see your changes reflected in the Studio page editor.

Studio editor with two tabs and a field set