![\"Markdown](\"/img/widgets-markdown.png\")
All configuration options for Netlify CMS are specified in a config.yml file, in the folder where you access the editor UI (usually in the /admin folder).
Alternatively, you can specify a custom config file using a link tag:
\n<!-- Note the \"type\" and \"rel\" attribute values, which are required. -->\n<link href=\"path/to/config.yml\" type=\"text/yaml\" rel=\"cms-config-url\">To see working configuration examples, you can start from a template or check out the CMS demo site. (No login required: click the login button and the CMS will open.) You can refer to the demo configuration code to see how each option was configured.
\nYou can find details about all configuration options below. Note that YAML syntax allows lists and objects to be written in block or inline style, and the code samples below include a mix of both.
\nThis setting is required.
\nThe backend option specifies how to access the content for your site, including authentication. Full details and code samples can be found in Backends.
Note: no matter where you access Netlify CMS — whether running locally, in a staging environment, or in your published site — it will always fetch and commit files in your hosted repository (for example, on GitHub), on the branch you configured in your Netlify CMS config.yml file. This means that content fetched in the admin UI will match the content in the repository, which may be different from your locally running site. It also means that content saved using the admin UI will save directly to the hosted repository, even if you're running the UI locally or in staging.
\nBy default, all entries created or edited in the Netlify CMS are committed directly into the main repository branch.
\nThe publish_mode option allows you to enable \"Editorial Workflow\" mode for more control over the content publishing phases. All unpublished entries will be arranged in a board according to their status, and they can be further reviewed and edited before going live.
Note: Editorial workflow works with GitHub repositories, and support for GitLab and Bitbucket is in beta.
\nYou can enable the Editorial Workflow with the following line in your Netlify CMS config.yml file:
publish_mode: editorial_workflowFrom a technical perspective, the workflow translates editor UI actions into common Git commands:
\n| Actions in Netlify UI ... | \nPerform these Git actions | \n
|---|---|
| Save draft | \nCommits to a new branch (named according to the pattern cms/collectionName/entrySlug), and opens a pull request | \n
| Edit draft | \nPushes another commit to the draft branch/pull request | \n
| Approve and publish draft | \nMerges pull request and deletes branch | \n
Netlify CMS users can upload files to your repository using the Media Gallery. The following settings specify where these files are saved, and where they can be accessed on your built site.
\nThis setting is required.
\nThe media_folder option specifies the folder path where uploaded files should be saved, relative to the base of the repo.
media_folder: \"static/images/uploads\"The public_folder option specifies the folder path where the files uploaded by the media library will be accessed, relative to the base of the built site. For fields controlled by [file] or [image] widgets, the value of the field is generated by prepending this path to the filename of the selected file. Defaults to the value of media_folder, with an opening / if one is not already included.
public_folder: \"/images/uploads\"Based on the settings above, if a user used an image widget field called avatar to upload and select an image called philosoraptor.png, the image would be saved to the repository at /static/images/uploads/philosoraptor.png, and the avatar field for the file would be set to /images/uploads/philosoraptor.png.
Media library integrations are configured via the media_library property, and its value should be an object with at least a name property. A config property can also be used for options that should be passed to the library in use.
Example:
\nmedia_library:\n name: uploadcare\n config:\n publicKey: demopublickeyThe site_url setting should provide a URL to your published site. May be used by the CMS for various functionality. Used together with a collection's preview_path to create links to live content.
Example:
\nsite_url: https://your-site.comWhen the display_url setting is specified, the CMS UI will include a link in the fixed area at the top of the page, allowing content authors to easily return to your main site. The text of the link consists of the URL without the protocol portion (e.g., your-site.com).
Defaults to site_url.
Example:
\ndisplay_url: https://your-site.comWhen the logo_url setting is specified, the CMS UI will change the logo displayed at the top of the login page, allowing you to brand the CMS with your own logo. logo_url is assumed to be a URL to an image file.
Example:
\nlogo_url: https://your-site.com/images/logo.svgThe CMS locale.
\nDefaults to en.
Other languages than English must be registered manually.
\nExample
\nIn your config.yml:
locale: 'de'And in your custom JavaScript code:
\nimport CMS from 'netlify-cms-app';\nimport { de } from 'netlify-cms-locales';\n\nCMS.registerLocale('de', de);When a translation for the selected locale is missing the English one will be used.
\n\n\nWhen importing
\nnetlify-cmsall locales are registered by default (so you only need to update yourconfig.yml).
Deploy preview links can be disabled by setting show_preview_links to false.
Example:
\nshow_preview_links: falseThe slug option allows you to change how filenames for entries are created and sanitized.\nIt also applies to filenames of media inserted via the default media library.
\nFor modifying the actual data in a slug, see the per-collection option below.
slug accepts multiple options:
encoding
unicode (default): Sanitize filenames (slugs) according to RFC3987 and the WHATWG URL spec. This spec allows non-ASCII (or non-Latin) characters to exist in URLs.ascii: Sanitize filenames (slugs) according to RFC3986. The only allowed characters are (0-9, a-z, A-Z, _, -, ~).clean_accents: Set to true to remove diacritics from slug characters before sanitizing. This is often helpful when using ascii encoding.sanitize_replacement: The replacement string used to substitute unsafe characters, defaults to -.Example
\nslug:\n encoding: \"ascii\"\n clean_accents: true\n sanitize_replacement: \"_\"This setting is required.
\nThe collections setting is the heart of your Netlify CMS configuration, as it determines how content types and editor fields in the UI generate files and content in your repository. Each collection you configure displays in the left sidebar of the Content page of the editor UI, in the order they are entered into your Netlify CMS config.yml file.
collections accepts a list of collection objects, each with the following options:
name (required): unique identifier for the collection, used as the key when referenced in other contexts (like the relation widget)identifier_field: see detailed description belowlabel: label for the collection in the editor UI; defaults to the value of namelabel_singular: singular label for certain elements in the editor; defaults to the value of labeldescription: optional text, displayed below the label when viewing a collectionfiles or folder (requires one of these): specifies the collection type and location; details in Collection Typesfilter: optional filter for folder collections; details in Collection Typescreate: for folder collections only; true allows users to create new items in the collection; defaults to falsepublish: for publish_mode: editorial_workflow only; false hides UI publishing controls for a collection; defaults to truedelete: false prevents users from deleting items in a collection; defaults to trueextension: see detailed description belowformat: see detailed description belowfrontmatter_delimiter: see detailed description under formatslug: see detailed description belowpreview_path: see detailed description belowpreview_path_date_field: see detailed description belowfields (required): see detailed description beloweditor: see detailed description belowsummary: see detailed description belowsortableFields: see detailed description belowThe last few options require more detailed information.
\nidentifier_fieldNetlify 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 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.
Example
\ncollections:\n - name: posts\n identifier_field: nameextension and formatThese settings determine how collection files are parsed and saved. Both are optional—Netlify 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.
\nextension 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, toml, 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 defaulttoml: parses and saves files as TOML-formatted data files; saves with toml extension by defaultjson: parses and saves files as JSON-formatted data files; saves with json extension by defaultfrontmatter: 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, TOML, 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 ---.toml-frontmatter: same as the frontmatter format above, except frontmatter will be both parsed and saved only as TOML, 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_delimiterIf 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 [\"(\", \")\"].
slugFor 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).
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:
\n{{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 dateExample:
\nslug: \"{{year}}-{{month}}-{{day}}_{{slug}}\"Example using field names:
\nslug: \"{{year}}-{{month}}-{{day}}_{{title}}_{{some_other_field}}\"Example using field name that conflicts with a template tag:
\nslug: \"{{year}}-{{month}}-{{day}}_{{fields.slug}}\"preview_pathA string representing the path where content in this collection can be found on the live site. This allows deploy preview links to direct to lead to a specific piece of content rather than the site root of a deploy preview.
\nAvailable template tags:
\nTemplate tags are the same as those for slug, with the following exceptions:
\n{{slug}} is the entire slug for the current entry (not just the url-safe identifier, as is the case with slug configuration){{year}} and {{month}}, are pulled from a date field in your entry, and may require additional configuration - see preview_path_date_field for details. If a date template tag is used and no date can be found, preview_path will be ignored.{{filename}} The file name without the extension part.{{extension}} The file extension.Examples:
\ncollections:\n - name: posts\n preview_path: \"blog/{{year}}/{{month}}/{{slug}}\"collections:\n - name: posts\n preview_path: \"blog/{{year}}/{{month}}/{{filename}}.{{extension}}\"preview_path_date_fieldThe name of a date field for parsing date-based template tags from preview_path. If this field is not provided and preview_path contains date-based template tags (eg. {{year}}), Netlify CMS will attempt to infer a usable date field by checking for common date field names, such as date. If you find that you need to specify a date field, you can use preview_path_date_field to tell Netlify CMS which field to use for preview path template tags.
Example:
\ncollections:\n - name: posts\n preview_path_date_field: \"updated_on\"fieldsThe fields option maps editor UI widgets to field-value pairs in the saved file. The order of the fields in your Netlify CMS config.yml file determines their order in the editor UI and in the saved file.
fields accepts a list of collection objects, each with the following options:
name (required): unique identifier for the field, used as the key when referenced in other contexts (like the relation widget)label: label for the field in the editor UI; defaults to the value of namewidget: defines editor UI and inputs and file field data types; details in Widgetsdefault: specify a default value for a field; available for most widget types (see Widgets for details on each widget type). Please note that field default value only works for folder collection type.required: specify as false to make a field optional; defaults to truepattern: add field validation by specifying a list with a regex pattern and an error message; more extensive validation can be achieved with custom widgetscomment: optional comment to add before the field (only supported for yaml)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.
Example:
\nfields:\n - label: \"Title\"\n name: \"title\"\n widget: \"string\"\n pattern: ['.{20,}', \"Must have at least 20 characters\"]\n - {label: \"Layout\", name: \"layout\", widget: \"hidden\", default: \"blog\"}\n - {label: \"Featured Image\", name: \"thumbnail\", widget: \"image\", required: false}\n - {label: \"Body\", name: \"body\", widget: \"markdown\"}\n comment: 'This is a multiline\\ncomment'editorThis setting changes options for the editor view of the collection. It has one option so far:
\npreview: set to false to disable the preview pane for this collection; defaults to trueExample:
\n editor:\n preview: falsesummaryThis 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:
\nTemplate tags are the same as those for slug, with the following additions:
\n{{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).Example
\n summary: \"Version: {{version}} - {{title}}\"sortableFieldsAn optional list of sort fields to show in the UI.
\nDefaults 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.
Example
\n # use dot notation for nested fields\n sortableFields: ['commit_date', 'title', 'commit_author', 'language.en']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\"}