-
- name |
- Post type identifier, used in routes. Must be unique. |
-
-
- label |
- What the admin UI calls the post type. |
-
-
- folder |
- Where files of this type are stored, relative to the repo root. |
-
-
- create |
- Set to true to allow users to create new files in this collection.
- |
-
-
- slug |
- Template for filenames. {{year}}, {{month}}, and {{day}} pulls from the post's date field or save date. {{slug}} is a url-safe version of the post's title. Default is simply {{slug}}.
- |
-
-
- fields |
- Fields listed here are shown as fields in the content editor, then saved as front matter at the beginning of the document (except for body, which follows the front matter). Each field contains the following properties:
-
- label: Field label in the editor UI.name: Field name in the document front matter.widget: Determines UI style and value data type (details below).default (optional): Sets a default value for the field.
- |
-
-
+| Field | Description |
+| ------ | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| name | Post type identifier, used in routes. Must be unique. |
+| label | What the admin UI calls the post type. |
+| folder | Where files of this type are stored, relative to the repo root. |
+| create | Set to `true` to allow users to create new files in this collection. |
+| slug | Template for filenames. `{{ year }}`, `{{ month }}`, and `{{ day }}` pulls from the post's `date` field or save date. `{{ slug }}` is a url-safe version of the post's `title`. Default is simply `{{ slug }}`. |
+| fields | Fields listed here are shown as fields in the content editor, then saved as front matter at the beginning of the document (except for `body`, which follows the front matter). |
-As described above, the `widget` property specifies a built-in or custom UI widget for a given field. When a content editor enters a value into a widget, that value is saved in the document front matter as the value for the `name` specified for that field. A full listing of available widgets can be found in the [Widgets doc](../widgets).
+As described above, the `widget` property specifies a built-in or custom UI widget for a given field. When a content editor enters a value into a widget, that value is saved in the document front matter as the value for the `name` specified for that field. A full listing of available widgets can be found in the [Widgets doc](/docs/widgets).
-Based on this example, you can go through the post types in your site and add the appropriate settings to your Static CMS `config.yml` file. Each post type should be listed as a separate node under the `collections` field. See the [Collections reference doc](../configuration-options/#collections) for more configuration options.
-
-### Filter
-
-The entries for any collection can be filtered based on the value of a single field. The example collection below only shows post entries with the value `en` in the `language` field.
-
-```yaml
-collections:
- - name: "posts"
- label: "Post"
- folder: "_posts"
- filter:
- field: language
- value: en
- fields:
- - {label: "Language", name: "language"}
-```
+Based on this example, you can go through the post types in your site and add the appropriate settings to your Static CMS `config.yml` file. Each post type should be listed as a separate node under the `collections` field. See the [Collections reference doc](/docs/configuration-options/#collections) for more configuration options.
## Authentication
@@ -244,10 +184,10 @@ When a user logs in with the Netlify Identity widget, an access token directs to
```html