☁️ Loving our new documentation website? Provide feedback in the CloudCannon Community! ✨

_enabled_editors

Table of contents

Description:

This key defines which editing interfaces are available by default for files at a given level of the configuration cascade.

Whether an editing interface is available for a specific file is determined by other factors.

Values can be one of the following: visual, content, or data.

Specifying one or more editing interfaces will disable all unspecified editing interfaces.

You cannot disable the Source Editor with this key.

By default, this key is set to visual, content, and data.

If undefined at higher levels of the configuration cascade, _enabled_editables will default to any values configured in the CloudCannon configuration file.

For more information, please read our documentation on the Visual Editor, Content Editor, Data Editor, and Source Editor.

Appears in:
├── collections_config
│   └── *
│       ├── schemas
│       │   └── *
│       │       └── _enabled_editors
│       └── _enabled_editors
└── file_config
    └── [*]
        └── _enabled_editors
Type:
Array<_enabled_editors[*]>
Items:
[*]string#

This key defines the available editors in CloudCannon: visual, content, and data editors.

Allowed values: visual content data

All items must be unique.

Examples:

In this example, we have enabled only the Content Editor in the blog Collection.

Copied to clipboard
collections_config:
  blog:
    _enabled_editors:
      - content
{
  "collections_config": {
    "blog": {
      "_enabled_editors": [
        "content"
      ]
    }
  }
}
Open in a new tab