--- group: Collections title: Collections Configuration weight: 9 --- `collections` accepts a list of collection objects, each with the following options | Name | Type | Default | Description | | --------------------- | ---------------------------------------------------------------------------------------------------------------------------------- | --------- | --------------------------------------------------------------------------------------------------------------------------------------------------------- | | name | string | | Unique identifier for the collection, used as the key when referenced in other contexts (like the [relation widget](/docs/widgets/#relation)) | | identifier_field | string | `'title'` | _Optional_. See [identifier_field](#identifier_field) below | | label | string | `name` | _Optional_. Label for the collection in the editor UI | | label_singular | string | `label` | _Optional_. Singular label for certain elements in the editor | | icon | string | | _Optional_. Unique name of icon to use in main menu. See [Custom Icons](/docs/custom-icons) | | description | string | | _Optional_. Text displayed below the label when viewing a collection | | files or folder | [Collection Files](/docs/collection-types#file-collections)
\| [Collection Folder](/docs/collection-types#folder-collections) | | **Requires one of these**: Specifies the collection type and location; details in [Collection Types](/docs/collection-types) | | filter | string | | _Optional_. Filter for [Folder Collections](/docs/collection-types#folder-collections) | | create | string | `false` | _Optional_. **For [Folder Collections](/docs/collection-types#folder-collections) only**
`true` - Allows users to create new items in the collection | | hide | string | `false` | _Optional_. `true` hides a collection in the CMS UI. Useful when using the relation widget to hide referenced collections | | delete | string | `true` | _Optional_. `false` prevents users from deleting items in a collection | | extension | string | | _Optional_. See [extension](#extension-and-format) below | | format | string | | _Optional_. See [format](#extension-and-format) below | | frontmatter_delimiter | string | | _Optional_. See [frontmatter_delimiter](#frontmatter_delimiter) below | | slug | string | | _Optional_. See [slug](#slug) below | | fields (required) | string | | _Optional_. See [fields](#fields) below. Ignored if [Files Collection](/docs/collection-types#file-collections) | | editor | string | | _Optional_. See [editor](#editor) below | | summary | string | | _Optional_. See [summary](#summary) below | | sortable_fields | string | | _Optional_. See [sortable_fields](#sortable_fields) below | | view_filters | string | | _Optional_. See [view_filters](#view_filters) below | | view_groups | string | | _Optional_. See [view_groups](#view_groups) below | ## `identifier_field` Static CMS expects every entry to provide a field named `"title"` that serves as an identifier for the entry. The identifier field serves as an entry's title when viewing a list of entries, and is used in [slug](#slug) creation. If you would like to use a field other than `"title"` as the identifier, you can set `identifier_field` to the name of the other field. ```yaml collections: - name: posts identifier_field: name ``` ```js collections: [ { name: 'posts', identifier_field: 'name', }, ], ``` ## `extension` and `format` These settings determine how collection files are parsed and saved. Both are optional—Static CMS will attempt to infer your settings based on existing items in the collection. If your collection is empty, or you'd like more control, you can set these fields explicitly. `extension` determines the file extension searched for when finding existing entries in a folder collection and it determines the file extension used to save new collection items. It accepts the following values: `yml`, `yaml`, `json`, `md`, `markdown`, `html`. You may also specify a custom `extension` not included in the list above, as long as the collection files can be parsed and saved in one of the supported formats below. `format` determines how collection files are parsed and saved. It will be inferred if the `extension` field or existing collection file extensions match one of the supported extensions above. It accepts the following values: - `yml` or `yaml`: parses and saves files as YAML-formatted data files; saves with `yml` extension by default - `json`: parses and saves files as JSON-formatted data files; saves with `json` extension by default - `frontmatter`: parses files and saves files with data frontmatter followed by an unparsed body text (edited using a `body` field); saves with `md` extension by default; default for collections that can't be inferred. Collections with `frontmatter` format (either inferred or explicitly set) can parse files with frontmatter in YAML or JSON format. However, they will be saved with YAML frontmatter. - `yaml-frontmatter`: same as the `frontmatter` format above, except frontmatter will be both parsed and saved only as YAML, followed by unparsed body text. The default delimiter for this option is `---`. - `json-frontmatter`: same as the `frontmatter` format above, except frontmatter will be both parsed and saved as JSON, followed by unparsed body text. The default delimiter for this option is `{` `}`. ## `frontmatter_delimiter` If you have an explicit frontmatter format declared, this option allows you to specify a custom delimiter like `~~~`. If you need different beginning and ending delimiters, you can use an array like `["(", ")"]`. ## `slug` For folder collections where users can create new items, the `slug` option specifies a template for generating new filenames based on a file's creation date and `title` field. (This means that all collections with `create: true` must have a `title` field (a different field can be used via [`identifier_field`](#identifier_field)). The slug template can also reference a field value by name, eg. `{{title}}`. If a field name conflicts with a built in template tag name - for example, if you have a field named `slug`, and would like to reference that field via `{{slug}}`, you can do so by adding the explicit `fields.` prefix, eg. `{{fields.slug}}`. **Available Template Tags** - Any field can be referenced by wrapping the field name in double curly braces, eg. `{{author}}` - `{{slug}}`: a url-safe version of the `title` field (or identifier field) for the file - `{{year}}`: 4-digit year of the file creation date - `{{month}}`: 2-digit month of the file creation date - `{{day}}`: 2-digit day of the month of the file creation date - `{{hour}}`: 2-digit hour of the file creation date - `{{minute}}`: 2-digit minute of the file creation date - `{{second}}`: 2-digit second of the file creation date ### Examples #### Basic Example ```yaml slug: '{{year}}-{{month}}-{{day}}_{{slug}}' ``` ```js slug: '{{year}}-{{month}}-{{day}}_{{slug}}', ``` #### Field Names ```yaml slug: '{{year}}-{{month}}-{{day}}_{{title}}_{{some_other_field}}' ``` ```js slug: '{{year}}-{{month}}-{{day}}_{{title}}_{{some_other_field}}', ``` #### Field Name That Conflicts With Template Tag ```yaml slug: '{{year}}-{{month}}-{{day}}_{{fields.slug}}' ``` ```js slug: '{{year}}-{{month}}-{{day}}_{{fields.slug}}', ``` ## `fields` _Ignored if [Files Collection](/docs/collection-types#file-collections)_ The `fields` option maps editor UI widgets to field-value pairs in the saved file. The order of the fields in your Static CMS `config` file determines their order in the editor UI and in the saved file. `fields` accepts a list of widgets. See [widgets](/docs/widgets) for more details. In files with frontmatter, one field should be named `body`. This special field represents the section of the document (usually markdown) that comes after the frontmatter. ```yaml fields: - label: "Title" name: "title" widget: "string" pattern: ['.{20,}', "Must have at least 20 characters"] - {label: "Layout", name: "layout", widget: "hidden", default: "blog"} - {label: "Featured Image", name: "thumbnail", widget: "image", required: false} - {label: "Body", name: "body", widget: "markdown", comment: 'This is a multiline\ncomment' } ``` ```js fields: [ { label: 'Title', name: 'title', widget: 'string', pattern: ['.{20,}', 'Must have at least 20 characters'] }, { label: 'Layout', name: 'layout', widget: 'hidden', default: 'blog' }, { label: 'Featured Image', name: 'thumbnail', widget: 'image', required: false }, { label: 'Body', name: 'body', widget: 'markdown', comment: 'This is a multiline\\ncomment' }, ], ``` ## `editor` This setting changes options for the editor view of a collection or a file inside a files collection. It has the following options: | Name | Type | Default | Description | | ------- | ------- | ------- | ------------------------------------------------------------------------------------------------------------ | | preview | boolean | `true` | Set to `false` to disable the preview pane for this collection or file | | frame | boolean | `true` | | ```yaml editor: preview: false frame: false ``` ```js editor: { preview: false, frame: false, }, ``` **Note**: Setting this as a top level configuration will set the default for all collections ## `summary` This setting allows the customization of the collection list view. Similar to the `slug` field, a string with templates can be used to include values of different fields, e.g. `{{title}}`. This option over-rides the default of `title` field and `identifier_field`. **Available Template Tags** Template tags are the same as those for [slug](#slug), with the following additions: - `{{dirname}}` The path to the file's parent directory, relative to the collection's `folder`. - `{{filename}}` The file name without the extension part. - `{{extension}}` The file extension. - `{{commit_date}}` The file commit date on supported backends (git based backends). - `{{commit_author}}` The file author date on supported backends (git based backends). ```yaml summary: 'Version: {{version}} - {{title}}' ``` ```js summary: 'Version: {{version}} - {{title}}', ``` ## `sortable_fields` An optional list of sort fields to show in the UI. Defaults to inferring `title`, `date`, `author` and `description` fields and will also show `Update On` sort field in git based backends. When `author` field can't be inferred commit author will be used. ```yaml # use dot notation for nested fields sortable_fields: ['commit_date', 'title', 'commit_author', 'language.en'] ``` ```js // use dot notation for nested fields sortable_fields: ['commit_date', 'title', 'commit_author', 'language.en'], ``` ## `view_filters` An optional list of predefined view filters to show in the UI. Defaults to an empty list. ```yaml view_filters: - label: "Alice's and Bob's Posts" field: author pattern: 'Alice|Bob' - label: 'Posts published in 2020' field: date pattern: '2020' - label: Drafts field: draft pattern: true ``` ```js view_filters: [ { label: "Alice's and Bob's Posts", field: 'author', pattern: 'Alice|Bob', }, { label: 'Posts published in 2020', field: 'date', pattern: '2020', }, { label: 'Drafts', field: 'draft', pattern: true, }, ], ``` ## `view_groups` An optional list of predefined view groups to show in the UI. Defaults to an empty list. ```yaml view_groups: - label: Year field: date # groups items based on the value matched by the pattern pattern: \d{4} - label: Drafts field: draft ``` ```js view_groups: [ { label: 'Year', field: 'date', pattern: '\\d{4}', }, { label: 'Drafts', field: 'draft', }, ], ```