![\"Markdown](\"/img/widgets-markdown.png\")
All editable content types are defined in the collections field of your config.yml file, and display in the left sidebar of the Content page of the editor UI.
Collections come in two main types: folder and files.
Folder collections represent one or more files with the same format, fields, and configuration options, all stored within the same folder in the repository. You might use a folder collection for blog posts, product pages, author data files, etc.
\nUnlike file collections, folder collections have the option to allow editors to create new items in the collection. This is set by the boolean create field.
Note: Folder collections must have at least one field with the name title for creating new entry slugs. That field should use the default string widget. The label for the field can be any string value. If you wish to use a different field as your identifier, set identifier_field to the field name. See the Collections reference doc for details on how collections and fields are configured. If you forget to add this field, you will get an error that your collection \"must have a field that is a valid entry identifier\".
Example:
\ncollections:\n - label: \"Blog\"\n name: \"blog\"\n folder: \"_posts/blog\"\n create: true\n fields:\n - {label: \"Title\", name: \"title\", widget: \"string\"}\n - {label: \"Publish Date\", name: \"date\", widget: \"datetime\"}\n - {label: \"Featured Image\", name: \"thumbnail\", widget: \"image\"}\n - {label: \"Body\", name: \"body\", widget: \"markdown\"}With identifier_field:
- label: \"Blog\"\n name: \"blog\"\n folder: \"_posts/blog\"\n create: true\n identifier_field: name\n fields:\n - {label: \"Name\", name: \"name\", widget: \"string\"}\n - {label: \"Publish Date\", name: \"date\", widget: \"datetime\"}\n - {label: \"Featured Image\", name: \"thumbnail\", widget: \"image\"}\n - {label: \"Body\", name: \"body\", widget: \"markdown\"}The entries for any folder collection can be filtered based on the value of a single field. By filtering a folder into different collections, you can manage files with different fields, options, extensions, etc. in the same folder.
\nThe filter option requires two fields:
field: The name of the collection field to filter on.value: The desired field value.The example below creates two collections in the same folder, filtered by the language field. The first collection includes posts with language: en, and the second, with language: es.
collections:\n - label: \"Blog in English\"\n name: \"english_posts\"\n folder: \"_posts\"\n create: true\n filter: {field: \"language\", value: \"en\"}\n fields:\n - {label: \"Language\", name: \"language\", widget: \"select\", options: [\"en\", \"es\"]}\n - {label: \"Title\", name: \"title\", widget: \"string\"}\n - {label: \"Content\", name: \"body\", widget: \"markdown\"}\n - label: \"Blog en Español\"\n name: \"spanish_posts\"\n folder: \"_posts\"\n create: true\n filter: {field: \"language\", value: \"es\"}\n fields:\n - {label: \"Lenguaje\", name: \"language\", widget: \"select\", options: [\"en\", \"es\"]}\n - {label: \"Titulo\", name: \"title\", widget: \"string\"}\n - {label: \"Contenido\", name: \"body\", widget: \"markdown\"}A files collection contains one or more uniquely configured files. Unlike items in folder collections, which repeat the same configuration over all files in the folder, each item in a files collection has an explicitly set path, filename, and configuration. This can be useful for unique files with a custom set of fields, like a settings file or a custom landing page with a unique content structure.
When configuring a files collection, configure each file in the collection separately, and list them under the files field of the collection. Each file has its own list of fields and a unique filepath specified in the file field (relative to the base of the repo).
Note: Files listed in a file collection must already exist in the hosted repository branch set in your Netlify CMS backend configuration. Files must also have a valid value for the file type. For example, an empty file works as valid YAML, but a JSON file must have a non-empty value to be valid, such as an empty object.
\nExample:
\ncollections:\n - label: \"Pages\"\n name: \"pages\"\n files:\n - label: \"About Page\"\n name: \"about\"\n file: \"site/content/about.yml\"\n fields:\n - {label: Title, name: title, widget: string}\n - {label: Intro, name: intro, widget: markdown}\n - label: Team\n name: team\n widget: list\n fields:\n - {label: Name, name: name, widget: string}\n - {label: Position, name: position, widget: string}\n - {label: Photo, name: photo, widget: image}\n - label: \"Locations Page\"\n name: \"locations\"\n file: \"site/content/locations.yml\"\n fields:\n - {label: Title, name: title, widget: string}\n - {label: Intro, name: intro, widget: markdown}\n - label: Locations\n name: locations\n widget: list\n fields:\n - {label: Name, name: name, widget: string}\n - {label: Address, name: address, widget: string}Components structure and Workflows
\nEditorial Workflow implementation
\ncreate-nuxt-appregisterPreviewStyleThe boolean widget translates a toggle switch input to a true/false value.
\nbooleanOptions:
\ndefault: accepts true or false; defaults to false when required is set to falseExample:
\n- {label: \"Draft\", name: \"draft\", widget: \"boolean\", default: true}The code widget provides a code editor (powered by Codemirror) with optional syntax awareness. Can output the raw code value or an object with the selected language and the raw code value.
\ncodeOptions:
\ndefault_language: optional; default language to useallow_language_selection: optional; defaults to false: allows syntax to be changedkeys: optional; sets key names for code and lang if outputting an object; defaults to { code: 'code', lang: 'lang' }output_code_only: set to true to output the string value only, defaults to falseExample:
\n- label: 'Code'\nname: 'code'\nwidget: 'code'Deprecation notice: the date widget has been deprecated and will be removed in the next major release. Please use the datetime widget instead.
\nThe date widget translates a date picker input to a date string. For saving date and time together, use the datetime widget.
\ndateOptions:
\ndefault: accepts a date string, or an empty string to accept blank input; otherwise defaults to current dateformat: optional; accepts Moment.js tokens; defaults to raw Date object (if supported by output format)dateFormat: optional; boolean or Moment.js tokens. If true use default locale format.timeFormat: optional; boolean or Moment.js tokens. If true use default locale format, false hides time-picker. Defaults to false.Example:
\n- label: 'Birthdate'\nname: 'birthdate'\nwidget: 'date'\ndefault: ''\nformat: 'MMM Do YY'The datetime widget translates a datetime picker to a datetime string. For saving the date only, use the date widget.
\ndatetimeOptions:
\ndefault: accepts a datetime string, or an empty string to accept blank input; otherwise defaults to current datetimeformat: sets storage format; accepts Moment.js tokens; defaults to raw Date object (if supported by output format)dateFormat: sets date display format in UI; boolean or Moment.js tokens. If true use default locale format.timeFormat: sets time display format in UI; boolean or Moment.js tokens. If true use default locale format, false hides time-picker.Example:
\n- label: \"Start time\"\n name: \"start\"\n widget: \"datetime\"\n default: \"\"\n dateFormat: \"DD.MM.YYYY\" # e.g. 24.12.2021\n timeFormat: \"HH:mm\" # e.g. 21:07\n format: \"LLL\"The file widget allows editors to upload a file or select an existing one from the media library. The path to the file will be saved to the field as a string.
\nfileOptions:
\ndefault: accepts a file path string; defaults to nullmedia_library: media library settings to apply when a media library is opened by the\ncurrent widgetallow_multiple: (default: true) when set to false, prevents multiple selection for any media library extension, but must be supported by the extension in useconfig: a configuration object that will be passed directly to the media library being\nused - available options are determined by the libraryExample:
\n- label: \"Manual PDF\"\n name: \"manual_pdf\"\n widget: \"file\"\n default: \"/uploads/general-manual.pdf\"\n media_library:\n config:\n multiple: trueHidden widgets do not display in the UI. In folder collections that allow users to create new items, you will often want to set a default for hidden fields, so they will be set without requiring an input.
\nhiddenOptions:
\ndefault: accepts any valid data type; recommended for collections that allow adding new itemsExample:
\n- {label: \"Layout\", name: \"layout\", widget: \"hidden\", default: \"blog\"}The image widget allows editors to upload an image or select an existing one from the media library. The path to the image file will be saved to the field as a string.
\nimageOptions:
\ndefault: accepts a file path string; defaults to nullmedia_library: media library settings to apply when a media library is opened by the\ncurrent widgetallow_multiple: (default: true) when set to false, prevents multiple selection for any media library extension, but must be supported by the extension in useconfig: a configuration object that will be passed directly to the media library being\nused - available options are determined by the libraryExample:
\n- label: \"Featured Image\"\n name: \"thumbnail\"\n widget: \"image\"\n default: \"/uploads/chocolate-dogecoin.jpg\"\n media_library:\n config:\n multiple: trueThe list widget allows you to create a repeatable item in the UI which saves as a list of widget values. map a user-provided string with a comma delimiter into a list. You can choose any widget as a child of a list widget—even other lists.
\nlistfields is specified, field containing a repeatable child widget, with controls for adding, deleting, and re-ordering the repeated widgets; if unspecified, a text input for entering comma-separated valuesOptions:
\ndefault: if fields is specified, declare defaults on the child widgets; if not, you may specify a list of strings to populate the text fieldallow_add: if added and labeled false, button to add additional widgets disappearscollapsed: if added and labeled false, the list widget's content does not collapse by defaultfield: a single widget field to be repeatedfields: a nested list of multiple widget fields to be included in each repeatable iterationExample (field/fields not specified):
- label: \"Tags\"\n name: \"tags\"\n widget: \"list\"\n default: [\"news\"]Example (allow_add marked false):
- label: \"Tags\"\n name: \"tags\"\n widget: \"list\"\n allow_add: false\n default: [\"news\"]Example (with field):
- label: \"Gallery\"\n name: \"galleryImages\"\n widget: \"list\"\n field: {label: Image, name: image, widget: image}Example (with fields):
- label: \"Testimonials\"\n name: \"testimonials\"\n widget: \"list\"\n fields:\n - {label: Quote, name: quote, widget: string, default: \"Everything is awesome!\"}\n - label: Author\n name: author\n widget: object\n fields:\n - {label: Name, name: name, widget: string, default: \"Emmet\"}\n - {label: Avatar, name: avatar, widget: image, default: \"/img/emmet.jpg\"}Example (collapsed marked false):
- label: \"Testimonials\"\n name: \"testimonials\"\n collapsed: false\n widget: \"list\"\n fields:\n - {label: Quote, name: quote, widget: string, default: \"Everything is awesome!\"}\n - {label: Author, name: author, widget: string }The map widget allows you to edit spatial data using an interactive map. Spatial data is saved as a GeoJSON string in WGS84 projection and is limited to a single geometry.
\nmapOptions:
\ndecimals: accepts a number to specify precision of saved coordinates; defaults to 7 decimalsdefault: accepts a GeoJSON string containing a single geometry; defaults to an empty stringtype: accepts one string value of Point, LineString or Polygon; defaults to PointExample:
\n- {label: \"Location\", name: \"location\", widget: \"map\" }The markdown widget provides a full fledged text editor - which is based on slate - that allows users to format text with features such as headings and blockquotes. Users are also allowed to write in markdown by simply flipping a switch.
\nPlease note: If you want to use your markdown editor to fill a markdown file contents after its frontmatter, you'll have to name the field body so the CMS recognizes it and saves the file accordingly.
markdownOptions:
\ndefault: accepts markdown contentminimal: accepts a boolean value, false by default. Sets the widget height to minimum possible.buttons: an array of strings representing the formatting buttons to display (all shown by default). Buttons include: bold, italic, code, link, heading-one, heading-two, heading-three, heading-four, heading-five, heading-six, quote, bulleted-list, and numbered-list.editorComponents: an array of strings representing the names of editor components to display (all shown by default). The image and code-block editor components are included with Netlify CMS by default, but others may be created and registered.Example:
\n- { label: 'Blog post content', name: 'body', widget: 'markdown' }This would render as:
\n
Please note: The markdown widget outputs a raw markdown string. Your static site generator may or may not render the markdown to HTML automatically. Consult with your static site generator's documentation for more information about rendering markdown.
"}},{"node":{"frontmatter":{"title":"number","label":"Number"},"html":"The number widget uses an HTML number input, saving the value as a string, integer, or floating point number.
\nnumbervalueType optionOptions:
\ndefault: accepts string or number value; defaults to empty stringvalueType: accepts int or float; any other value results in saving as a stringmin: accepts a number for minimum value accepted; unset by defaultmax: accepts a number for maximum value accepted; unset by defaultstep: accepts a number for stepping up/down values in the input; 1 by defaultExample:
\n- label: \"Puppy Count\"\n name: \"puppies\"\n widget: \"number\"\n default: 2\n valueType: \"int\"\n min: 1\n max: 101\n step: 2The object widget allows you to group multiple widgets together, nested under a single field. You can choose any widget as a child of an object widget—even other objects.
\nobjectOptions:
\ndefault: you can set defaults within each sub-field's configurationfields: (required) a nested list of widget fields to include in your widgetExample:
\n- label: \"Profile\"\n name: \"profile\"\n widget: \"object\"\n fields:\n - {label: \"Public\", name: \"public\", widget: \"boolean\", default: true}\n - {label: \"Name\", name: \"name\", widget: \"string\"}\n - label: \"Birthdate\"\n name: \"birthdate\"\n widget: \"date\"\n default: \"\"\n format: \"MM/DD/YYYY\"\n - label: \"Address\"\n name: \"address\"\n widget: \"object\"\n fields: \n - {label: \"Street Address\", name: \"street\", widget: \"string\"}\n - {label: \"City\", name: \"city\", widget: \"string\"}\n - {label: \"Postal Code\", name: \"post-code\", widget: \"string\"}The relation widget allows you to reference items from another collection. It provides a search input with a list of entries from the collection you're referencing, and the list automatically updates with matched entries based on what you've typed.
\nrelationOptions:
\ndefault: accepts any widget data type; defaults to an empty stringcollection: (required) name of the collection being referenced (string)displayFields: list of one or more names of fields in the referenced collection that will render in the autocomplete menu of the control. Defaults to valueField. For nested fields, separate each subfield with a . (E.g. name.first).searchFields: (required) list of one or more names of fields in the referenced collection to search for the typed value. Syntax to reference nested fields is similar to that of displayFields.valueField: (required) name of the field from the referenced collection whose value will be stored for the relation. Syntax to reference nested fields is similar to that of displayFields and searchFields. As valueField only allows for a single field, this parameter only accepts a string.multiple : accepts a boolean, defaults to falseoptionsLength: accepts integer to override number of options presented to user. Defaults to 20.Example (assuming a separate \"authors\" collection with \"name\" and \"twitterHandle\" fields with subfields \"first\" and \"last\" for the \"name\" field):
\n- label: \"Post Author\"\n name: \"author\"\n widget: \"relation\"\n collection: \"authors\"\n searchFields: [\"name.first\", \"twitterHandle\"]\n valueField: \"name.first\"\n displayFields: [\"twitterHandle\", \"followerCount\"]The generated UI input will search the authors collection by name and twitterHandle, and display each author's handle and follower count. On selection, the author name will be saved for the field.
\nThe select widget allows you to pick a string value from a dropdown menu.
\nselectOptions:
\ndefault: default values must be contained in options and are ignored otherwise
multiple: true enabled.label and value fields: accepts an object with label and value field or an array of such objects when multiple: true is enable. Defaults to no valueoptions: (required) a list of options for the dropdown menu; can be listed in two ways:
label and value fields: the label displays in the dropdown; the value is saved in the filemultiple: accepts a boolean; defaults to falsemin: minimum number of items; ignored if multiple is not truemax: maximum number of items; ignored if multiple is not trueExample (options as strings):
\n- label: \"Align Content\"\n name: \"align\"\n widget: \"select\"\n options: [\"left\", \"center\", \"right\"]Example (options as objects):
\n- label: \"City\"\n name: \"airport-code\"\n widget: \"select\"\n options:\n - { label: \"Chicago\", value: \"ORD\" }\n - { label: \"Paris\", value: \"CDG\" }\n - { label: \"Tokyo\", value: \"HND\" }Example (multiple):
\n- label: \"Tags\"\n name: \"tags\"\n widget: \"select\"\n multiple: true\n options: [\"Design\", \"UX\", \"Dev\"]\n default: [\"Design\"]Example (min/max):
\n- label: \"Tags\"\n name: \"tags\"\n widget: \"select\"\n multiple: true\n min: 1\n max: 3\n options: [\"Design\", \"UX\", \"Dev\"]\n default: [\"Design\"]The string widget translates a basic text input to a string value. For larger textarea inputs, use the text widget.
\nstringOptions:
\ndefault: accepts a string; defaults to an empty stringExample:
\n- {label: \"Title\", name: \"title\", widget: \"string\"}The text widget takes a multiline text field and saves it as a string. For shorter text inputs, use the string widget.
\ntextOptions:
\ndefault: accepts a string; defaults to an empty stringExample:
\n- {label: \"Description\", name: \"description\", widget: \"text\"}