The Data Editor uses a wide range of different inputs. Each input corresponds to a field in your front matter or data file, providing an editing interface for those values. Inputs have a type, label and a comment.
Use the _inputs configuration to change types, labels, comments, instance values, and specific type options. Some configuration (notably input type) is automatically set for you based on the input key.
Input configuration
copied
Input configuration
copied
Input configuration
copied
The above code shows the _inputs configuration set in the same file, but you can choose where to set this for inputs across your site in the configuration cascade.
Each key inside _inputs targets one or more inputs in the Data Editor. These keys can target inputs directly by key name, or the nested path to the input.
This configuration applies to title inputs:
Input configuration
copied
Input configuration
copied
Input configuration
copied
This configuration applies to title inputs at the root level of your data only:
Input configuration
copied
Input configuration
copied
Input configuration
copied
This configuration applies to title inputs directly inside seo objects:
Input configuration
copied
Input configuration
copied
Input configuration
copied
This configuration applies to image inputs inside card array items:
Input configuration
copied
Input configuration
copied
Input configuration
copied
This configuration applies to inline images array items:
Changes the editing interface for an input. Each input appears and behave differently, takes different options, and processes different values. See more details in the type section below.
For unknown types, or if the input contains an unsupported value (e.g. an array value in a text input), the disabled type is used instead.
Changes the subtext below the label. Has no default. Supports a limited set of Markdown: links, bold, italic, subscript, superscript and inline code elements are allowed.
Useful for adding reminders or additional context for your team members on a specific input.
Configuration settings passed on to the input when displayed. These are specific to each input. The available types and their options are listed below.
Controls if and how the value of this input is instantiated when created. This occurs when creating files, or adding array items containing the configured input. Has no default. Must be one of UUID or NOW.
Toggles the visibility of this input. Useful for when you need an input to exist, but don't want it edited or seen. Defaults to the naming convention, true for input keys starting with an underscore and false otherwise.
If set as a boolean, the input is hidden based if true.
If set as a string, the input is hidden based on the value of another input. This can start with a ! to reverse the value.
published hides an input when the sibling input published is truthy
!published hides an input when the sibling input published is falsy
Specifies whether or not this input configuration should be merged with any matching, less specific configuration. Defaults to true.
The configuration cascade works by finding the most specific _inputs entry. Usually, once an option is found in the cascade, there's no reason to keep looking.
When this is true, the cascade continues looking and each entry found is merged. This allows you to define a comment globally, then a different label for inputs in a collection without redefining the comment. You can stop the cascade at any given point by setting cascade to false.
The type defines how inputs appear and behave. The type used for each field is based on (in order):
type in _inputs for that key
Value (e.g. boolean values show as a checkbox)
Key name (e.g. color will give you a color picker)
This results in good defaults for unconfigured inputs, without hindering configured inputs. To change the type for an input you can use the _inputs configuration, or the naming conventions:
Input configuration
copied
Input configuration
copied
Input configuration
copied
Naming convention
copied
Naming convention
copied
Naming convention
copied
The naming conventions support snake_case, camelCase, PascalCase and kebab-case.
Here are all the available input types, each with their own available options: