@cloudcannon/configuration-types 0.0.53 → 0.0.54

package/dist/cloudcannon-structure-value.schema.json

@@ -1,7 +1,5 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "title": "Structure Value",
-  "description": "A single value option within a structure, defining the data format and appearance for content editors.",
   "$id": "https://github.com/cloudcannon/configuration-types/releases/latest/download/cloudcannon-structure-value.schema.json",
   "allOf": [
     {
@@ -9,274 +7,7 @@
     }
   ],
   "definitions": {
-    "type.structure.values.[*]": {
-      "title": "Structure Value",
-      "description": "This key represents a single value option within a structure, defining the data format and appearance for content editors.",
-      "type": "object",
-      "properties": {
-        "reorder_inputs": {
-          "description": "This key toggles whether CloudCannon will reorder inputs in a file to match the order defined in a given value from a Structure.\n\nSetting this key to `false` will preserve the existing order of inputs in a file, regardless of the order defined in the Structure value.\n\nBy default, this key is `true` (i.e., inputs are reordered to match the Structure value).\n\nYou can also configure this behavior for all values of a Structure using `reorder_inputs` inside `_structures.*`.",
-          "default": true,
-          "type": "boolean",
-          "documented": true,
-          "title": "reorder_inputs",
-          "markdownDescription": "This key toggles whether CloudCannon will reorder inputs in a file to match the order defined in a given value from a Structure.\n\nSetting this key to `false` will preserve the existing order of inputs in a file, regardless of the order defined in the Structure value.\n\nBy default, this key is `true` (i.e., inputs are reordered to match the Structure value).\n\nYou can also configure this behavior for all values of a Structure using `reorder_inputs` inside `_structures.*`."
-        },
-        "hide_extra_inputs": {
-          "description": "This key toggles whether CloudCannon will hide inputs that are not present in a given value from a Structure from the [Data\nEditor](https://cloudcannon.com/documentation/articles/what-is-the-data-editor/).\n\nSetting this key to `true` will hide inputs that are not present in a given value from a Structure from the Data Editor. Hiding these inputs does not delete the data. You can see non-structure data keys by opening a file in the [Source Editor](https://cloudcannon.com/documentation/articles/what-is-the-source-editor/). This key has no effect if `remove_extra_inputs` is `true`.\n\nYou can also configure this behavior for all values of a Structure using `hide_extra_inputs` inside `_structures.*`.",
-          "default": false,
-          "type": "boolean",
-          "documented": true,
-          "title": "hide_extra_inputs",
-          "markdownDescription": "This key toggles whether CloudCannon will hide inputs that are not present in a given value from a Structure from the [Data\nEditor](https://cloudcannon.com/documentation/articles/what-is-the-data-editor/).\n\nSetting this key to `true` will hide inputs that are not present in a given value from a Structure from the Data Editor. Hiding these inputs does not delete the data. You can see non-structure data keys by opening a file in the [Source Editor](https://cloudcannon.com/documentation/articles/what-is-the-source-editor/). This key has no effect if `remove_extra_inputs` is `true`.\n\nYou can also configure this behavior for all values of a Structure using `hide_extra_inputs` inside `_structures.*`."
-        },
-        "remove_empty_inputs": {
-          "description": "This key toggles whether CloudCannon will remove empty nested inputs from an Object Input or Array Input using a given value from a Structure before\npersisting them to your file.\n\nSetting this key to `true` will remove empty nested inputs from an Object Input or Array Input using a given value from a Structure before\npersisting them to your file. CloudCannon considers an input to be empty when its value is `null`, `' '`, or undefined. If this key is true, empty inputs will be visible in the [Data Editor](https://cloudcannon.com/documentation/articles/what-is-the-data-editor/) but not the [Source\nEditor](https://cloudcannon.com/documentation/articles/what-is-the-source-editor/). For this key to function, you must also configure `id_key` for the Structure, as removing inputs prevents CloudCannon from comparing Structure values.\n\nYou can also configure this behavior for all values of a Structure using `remove_empty_inputs` inside `_structures.*`.",
-          "default": false,
-          "type": "boolean",
-          "documented": true,
-          "title": "remove_empty_inputs",
-          "markdownDescription": "This key toggles whether CloudCannon will remove empty nested inputs from an Object Input or Array Input using a given value from a Structure before\npersisting them to your file.\n\nSetting this key to `true` will remove empty nested inputs from an Object Input or Array Input using a given value from a Structure before\npersisting them to your file. CloudCannon considers an input to be empty when its value is `null`, `' '`, or undefined. If this key is true, empty inputs will be visible in the [Data Editor](https://cloudcannon.com/documentation/articles/what-is-the-data-editor/) but not the [Source\nEditor](https://cloudcannon.com/documentation/articles/what-is-the-source-editor/). For this key to function, you must also configure `id_key` for the Structure, as removing inputs prevents CloudCannon from comparing Structure values.\n\nYou can also configure this behavior for all values of a Structure using `remove_empty_inputs` inside `_structures.*`."
-        },
-        "remove_extra_inputs": {
-          "description": "This key toggles whether CloudCannon will remove inputs that are not present in a given value from a Structure from a file before loading it in an\nEditing Interface.\n\nSetting this key to `true` will remove inputs that are not present in a given value from a Structure from a file before loading it in an Editing Interface. Non-Structure inputs will not be visible in the [Visual Editor](https://cloudcannon.com/documentation/articles/what-is-the-visual-editor/), [Content\nEditor](https://cloudcannon.com/documentation/articles/what-is-the-content-editor/), or [Data Editor](https://cloudcannon.com/documentation/articles/what-is-the-data-editor/), and saving the file\nwill remove them from the file before persisting the changes to your Git repository.\n\nYou can also configure this behavior for all values of a Structure using `remove_extra_inputs` inside `_structures.*`.",
-          "default": true,
-          "type": "boolean",
-          "documented": true,
-          "title": "remove_extra_inputs",
-          "markdownDescription": "This key toggles whether CloudCannon will remove inputs that are not present in a given value from a Structure from a file before loading it in an\nEditing Interface.\n\nSetting this key to `true` will remove inputs that are not present in a given value from a Structure from a file before loading it in an Editing Interface. Non-Structure inputs will not be visible in the [Visual Editor](https://cloudcannon.com/documentation/articles/what-is-the-visual-editor/), [Content\nEditor](https://cloudcannon.com/documentation/articles/what-is-the-content-editor/), or [Data Editor](https://cloudcannon.com/documentation/articles/what-is-the-data-editor/), and saving the file\nwill remove them from the file before persisting the changes to your Git repository.\n\nYou can also configure this behavior for all values of a Structure using `remove_extra_inputs` inside `_structures.*`."
-        },
-        "preview": {
-          "allOf": [
-            {
-              "$ref": "#/definitions/type.preview"
-            }
-          ],
-          "documented": false,
-          "title": "preview"
-        },
-        "picker_preview": {
-          "allOf": [
-            {
-              "$ref": "#/definitions/type.picker_preview"
-            }
-          ],
-          "documented": false,
-          "title": "picker_preview"
-        },
-        "_inputs": {
-          "allOf": [
-            {
-              "$ref": "#/definitions/type._inputs"
-            }
-          ],
-          "documented": false,
-          "title": "_inputs"
-        },
-        "_inputs_from_glob": {
-          "allOf": [
-            {
-              "$ref": "#/definitions/type._inputs_from_glob"
-            }
-          ],
-          "documented": false,
-          "title": "_inputs_from_glob"
-        },
-        "_select_data": {
-          "allOf": [
-            {
-              "$ref": "#/definitions/type._select_data"
-            }
-          ],
-          "documented": false,
-          "title": "_select_data"
-        },
-        "_structures": {
-          "allOf": [
-            {
-              "$ref": "#/definitions/type._structures"
-            }
-          ],
-          "documented": false,
-          "title": "_structures"
-        },
-        "_structures_from_glob": {
-          "allOf": [
-            {
-              "$ref": "#/definitions/type._structures_from_glob"
-            }
-          ],
-          "documented": false,
-          "title": "_structures_from_glob"
-        },
-        "id": {
-          "description": "This key defines the string used to identify a given Structure value when refering to it from other input configuration.\n\n## Examples\n\nIn this example, we have configured the `blog_post` ID for the entry labeled `Blog` in the `article_information` Structure.\n\n```yaml\n_structures:\n  article_information:\n    values:\n      - label: Blog\n        id: blog_post\n```",
-          "type": "string",
-          "documented": true,
-          "title": "id",
-          "markdownDescription": "This key defines the string used to identify a given Structure value when refering to it from other input configuration.\n\n## Examples\n\nIn this example, we have configured the `blog_post` ID for the entry labeled `Blog` in the `article_information` Structure.\n\n```yaml\n_structures:\n  article_information:\n    values:\n      - label: Blog\n        id: blog_post\n```"
-        },
-        "default": {
-          "description": "This key toggles whether CloudCannon should treat an entry in the `values` array as the default option for your Object or Array input.\n\nSetting this key to `true` will mark this entry as the default option for your Object or Array input. If multiple entries in the `values` array are set to `true`, CloudCannon will use the first entry. If CloudCannon cannot determine the type of an entry within the `values` array based on the `id_key` or matching inputs across `values[*].value` objects,\nit will fall back to the default entry.\n\n## Examples\n\nIn this example, we want the entry labelled `Employee` to be our default option for populating inputs configured with the `staff` Structure.\n\n```yaml\n_structures:\n  staff:\n    style: modal\n    values:\n      - label: Employee\n        default: true\n        value:\n          name:\n          job_description:\n          profile_picture:\n      - label: Manager\n        value:\n          name:\n          job_description:\n          profile_picture:\n          url:\n```",
-          "default": false,
-          "type": "boolean",
-          "documented": true,
-          "title": "default",
-          "markdownDescription": "This key toggles whether CloudCannon should treat an entry in the `values` array as the default option for your Object or Array input.\n\nSetting this key to `true` will mark this entry as the default option for your Object or Array input. If multiple entries in the `values` array are set to `true`, CloudCannon will use the first entry. If CloudCannon cannot determine the type of an entry within the `values` array based on the `id_key` or matching inputs across `values[*].value` objects,\nit will fall back to the default entry.\n\n## Examples\n\nIn this example, we want the entry labelled `Employee` to be our default option for populating inputs configured with the `staff` Structure.\n\n```yaml\n_structures:\n  staff:\n    style: modal\n    values:\n      - label: Employee\n        default: true\n        value:\n          name:\n          job_description:\n          profile_picture:\n      - label: Manager\n        value:\n          name:\n          job_description:\n          profile_picture:\n          url:\n```"
-        },
-        "icon": {
-          "description": "This key defines an icon used when displaying the structure (defaults to either `format_list_bulleted` for items in arrays, or `notes` otherwise).\n\n## Examples\n\nIn this example, CloudCannon will display the `article` icon for the entry labeled `Blog` in the `article_information` Structure.\n\n```yaml\n_structures:\n  article_information:\n    values:\n      - label: Blog\n        icon: article\n```",
-          "allOf": [
-            {
-              "$ref": "#/definitions/icon"
-            }
-          ],
-          "documented": true,
-          "title": "icon",
-          "markdownDescription": "This key defines an icon used when displaying the structure (defaults to either `format_list_bulleted` for items in arrays, or `notes` otherwise).\n\n## Examples\n\nIn this example, CloudCannon will display the `article` icon for the entry labeled `Blog` in the `article_information` Structure.\n\n```yaml\n_structures:\n  article_information:\n    values:\n      - label: Blog\n        icon: article\n```"
-        },
-        "image": {
-          "description": "This key defines the path to an image in your source files used when displaying the structure value.\n\nCan be either a source (has priority) or output path.\n\n## Examples\n\nIn this example, we have configured the `/images/blog-icon.png` image for the entry labeled `Blog` in the `article_information` Structure.\n\n```yaml\n_structures:\n  article_information:\n    values:\n      - label: Blog\n        image: /images/blog-icon.png\n```",
-          "type": "string",
-          "documented": true,
-          "title": "image",
-          "markdownDescription": "This key defines the path to an image in your source files used when displaying the structure value.\n\nCan be either a source (has priority) or output path.\n\n## Examples\n\nIn this example, we have configured the `/images/blog-icon.png` image for the entry labeled `Blog` in the `article_information` Structure.\n\n```yaml\n_structures:\n  article_information:\n    values:\n      - label: Blog\n        image: /images/blog-icon.png\n```"
-        },
-        "label": {
-          "description": "This key defines the display name for a given value in a Structure.\n\nThe name will appear in the *+ Add* button dropdown below an Object or Array input or in the Structures modal (if configured).\n\nBy default, this key falls back to `unknown`.\n\n## Examples\n\nIn this example, we want two value options for our `staff` structure: one called `Manager` and one called `Employee`.\n\n```yaml\n_structures:\n  staff:\n    values:\n      - label: Employee\n        value:\n          name:\n          job_description:\n          profile_picture:\n      - label: Manager\n        value:\n          name:\n          job_description:\n          profile_picture:\n          url:\n```",
-          "type": "string",
-          "documented": true,
-          "title": "label",
-          "markdownDescription": "This key defines the display name for a given value in a Structure.\n\nThe name will appear in the *+ Add* button dropdown below an Object or Array input or in the Structures modal (if configured).\n\nBy default, this key falls back to `unknown`.\n\n## Examples\n\nIn this example, we want two value options for our `staff` structure: one called `Manager` and one called `Employee`.\n\n```yaml\n_structures:\n  staff:\n    values:\n      - label: Employee\n        value:\n          name:\n          job_description:\n          profile_picture:\n      - label: Manager\n        value:\n          name:\n          job_description:\n          profile_picture:\n          url:\n```"
-        },
-        "tags": {
-          "description": "This key defines which tags are associated with a given value in a Structure.\n\nYou can use tags to group and filter Structure options when selecting from a modal.\n\nThis key has no default.\n\n## Examples\n\nIn this example we have three options for the `page_components` Structure: `Hero Component`, `Feature Component`, and `Video Component`. We can search the Structure modal using the `image`, `text`, `button`, and `video` tags to filter Structure values.\n\n```yaml\n_structures:\n  page_components:\n    style: modal\n    values:\n      - label: Hero Component\n        tags:\n          - image\n          - text\n        value:\n          title:\n          description:\n          image_path:\n          link:\n            text:\n            url:\n      - label: Feature Component\n        tags:\n          - image\n          - text\n          - button\n        value:\n          image_path:\n          title:\n          description:\n          button:\n            link:\n            text:\n          reversed_layout: false\n      - label: Video Component\n        tags:\n          - image\n          - video\n        value:\n          image_path:\n          videoUrl:\n```",
-          "type": "array",
-          "items": {
-            "type": "string",
-            "documented": true,
-            "title": "tags[*]",
-            "description": "This key represents an individual tag string in the `values[*].tags` array.\n\nThe value is a string that specifies a tag associated with a structure value.\n\n## Examples\n\nIn this example, we have configured the `featured` and `news` tags for the entry labeled `Blog` in the `article_information` Structure.\n\n```yaml\n_structures:\n  article_information:\n    values:\n      - label: Blog\n        tags:\n          - featured\n          - news\n```",
-            "markdownDescription": "This key represents an individual tag string in the `values[*].tags` array.\n\nThe value is a string that specifies a tag associated with a structure value.\n\n## Examples\n\nIn this example, we have configured the `featured` and `news` tags for the entry labeled `Blog` in the `article_information` Structure.\n\n```yaml\n_structures:\n  article_information:\n    values:\n      - label: Blog\n        tags:\n          - featured\n          - news\n```"
-          },
-          "documented": true,
-          "title": "tags",
-          "markdownDescription": "This key defines which tags are associated with a given value in a Structure.\n\nYou can use tags to group and filter Structure options when selecting from a modal.\n\nThis key has no default.\n\n## Examples\n\nIn this example we have three options for the `page_components` Structure: `Hero Component`, `Feature Component`, and `Video Component`. We can search the Structure modal using the `image`, `text`, `button`, and `video` tags to filter Structure values.\n\n```yaml\n_structures:\n  page_components:\n    style: modal\n    values:\n      - label: Hero Component\n        tags:\n          - image\n          - text\n        value:\n          title:\n          description:\n          image_path:\n          link:\n            text:\n            url:\n      - label: Feature Component\n        tags:\n          - image\n          - text\n          - button\n        value:\n          image_path:\n          title:\n          description:\n          button:\n            link:\n            text:\n          reversed_layout: false\n      - label: Video Component\n        tags:\n          - image\n          - video\n        value:\n          image_path:\n          videoUrl:\n```"
-        },
-        "groups": {
-          "description": "This key defines the order and custom grouping for inputs within a Structure.\n\nThe value is an array of group objects. Each group object can contain a `heading`, `comment`, `collapsed`, and `inputs` array.\n\n## Examples\n\nIn this example, we want to separate the inputs into two groups with descriptive headings: `title` and `subtitle` under the `Titles` heading, and `author` under the `Details` heading.\n\n```yaml\n_structures:\n  article_information:\n    values:\n      - label: Blog\n        value:\n          title:\n          subtitle:\n          author:\n        groups:\n          - heading: Titles\n            inputs:\n              - title\n              - subtitle\n          - heading: Details\n            inputs:\n              - author\n```",
-          "type": "array",
-          "items": {
-            "type": "object",
-            "properties": {
-              "heading": {
-                "description": "This key defines the main text for the group shown when collapsed or expanded.\n\nThe value is a string that specifies the heading text displayed for the group.\n\n## Examples\n\nIn this example, we have configured a group heading to organize structure inputs under the \"Titles\" heading.\n\n```yaml\n_structures:\n  article_information:\n    values:\n      - label: Blog\n        value:\n          title:\n          subtitle:\n          author:\n        groups:\n          - heading: Titles\n            inputs:\n              - title\n              - subtitle\n          - heading: Details\n            inputs:\n              - author\n```",
-                "type": "string",
-                "documented": true,
-                "title": "heading",
-                "markdownDescription": "This key defines the main text for the group shown when collapsed or expanded.\n\nThe value is a string that specifies the heading text displayed for the group.\n\n## Examples\n\nIn this example, we have configured a group heading to organize structure inputs under the \"Titles\" heading.\n\n```yaml\n_structures:\n  article_information:\n    values:\n      - label: Blog\n        value:\n          title:\n          subtitle:\n          author:\n        groups:\n          - heading: Titles\n            inputs:\n              - title\n              - subtitle\n          - heading: Details\n            inputs:\n              - author\n```"
-              },
-              "comment": {
-                "description": "This key defines the subtext displayed below the `heading` for a group.\n\nThe value is a string that supports a limited set of Markdown: links, bold, italic, subscript, superscript, and inline code elements are allowed.\n\n## Examples\n\nIn this example, we have configured a group comment with Markdown formatting to provide additional context below the heading.\n\n```yaml\n_structures:\n  article_information:\n    values:\n      - label: Blog\n        value:\n          title:\n          subtitle:\n          author:\n        groups:\n          - heading: Titles\n            comment: Make these SEO-friendly\n            inputs:\n              - title\n              - subtitle\n          - heading: Details\n            inputs:\n              - author\n```",
-                "type": "string",
-                "documented": true,
-                "title": "comment",
-                "markdownDescription": "This key defines the subtext displayed below the `heading` for a group.\n\nThe value is a string that supports a limited set of Markdown: links, bold, italic, subscript, superscript, and inline code elements are allowed.\n\n## Examples\n\nIn this example, we have configured a group comment with Markdown formatting to provide additional context below the heading.\n\n```yaml\n_structures:\n  article_information:\n    values:\n      - label: Blog\n        value:\n          title:\n          subtitle:\n          author:\n        groups:\n          - heading: Titles\n            comment: Make these SEO-friendly\n            inputs:\n              - title\n              - subtitle\n          - heading: Details\n            inputs:\n              - author\n```"
-              },
-              "collapsed": {
-                "description": "This key defines whether a group is collapsed or expanded when first viewed.\n\nThe value is a boolean. When `true`, CloudCannon displays the group in a collapsed state. When `false`, CloudCannon displays the group in an expanded state.\n\nBy default, CloudCannon displays groups in an expanded state.\n\n## Examples\n\nIn this example, we have configured the \"Details\" group to be collapsed by default.\n\n```yaml\n_structures:\n  article_information:\n    values:\n      - label: Blog\n        value:\n          title:\n          subtitle:\n          author:\n        groups:\n          - heading: Titles\n            collapsed: true\n            inputs:\n              - title\n              - subtitle\n          - heading: Details\n            inputs:\n              - author\n```",
-                "default": false,
-                "type": "boolean",
-                "documented": true,
-                "title": "collapsed",
-                "markdownDescription": "This key defines whether a group is collapsed or expanded when first viewed.\n\nThe value is a boolean. When `true`, CloudCannon displays the group in a collapsed state. When `false`, CloudCannon displays the group in an expanded state.\n\nBy default, CloudCannon displays groups in an expanded state.\n\n## Examples\n\nIn this example, we have configured the \"Details\" group to be collapsed by default.\n\n```yaml\n_structures:\n  article_information:\n    values:\n      - label: Blog\n        value:\n          title:\n          subtitle:\n          author:\n        groups:\n          - heading: Titles\n            collapsed: true\n            inputs:\n              - title\n              - subtitle\n          - heading: Details\n            inputs:\n              - author\n```"
-              },
-              "inputs": {
-                "description": "This key defines which inputs are included in a group within a structure value.\n\nThe value is an array of input key name strings that specify which inputs belong to this group.\n\n## Examples\n\nIn this example, we have configured a group to include the `title` and `subtitle` inputs.\n\n```yaml\n_structures:\n  article_information:\n    values:\n      - label: Blog\n        value:\n          title:\n          subtitle:\n          author:\n        groups:\n          - heading: Titles\n            inputs:\n              - title\n              - subtitle\n          - heading: Details\n            inputs:\n              - author\n```",
-                "type": "array",
-                "items": {
-                  "type": "string",
-                  "documented": true,
-                  "title": "inputs[*]",
-                  "description": "This key represents an individual input key name string in the `values[*].groups[*].inputs` array.\n\nThe value is a string that specifies the key name of an input to include in a group within a structure value.\n\n## Examples\n\nIn this example, we have configured a group to include the `title` input.\n\n```yaml\n_structures:\n  article_information:\n    values:\n      - label: Blog\n        value:\n          title:\n          subtitle:\n          author:\n        groups:\n          - heading: Titles\n            inputs:\n              - title\n              - subtitle\n          - heading: Details\n            inputs:\n              - author\n```",
-                  "markdownDescription": "This key represents an individual input key name string in the `values[*].groups[*].inputs` array.\n\nThe value is a string that specifies the key name of an input to include in a group within a structure value.\n\n## Examples\n\nIn this example, we have configured a group to include the `title` input.\n\n```yaml\n_structures:\n  article_information:\n    values:\n      - label: Blog\n        value:\n          title:\n          subtitle:\n          author:\n        groups:\n          - heading: Titles\n            inputs:\n              - title\n              - subtitle\n          - heading: Details\n            inputs:\n              - author\n```"
-                },
-                "documented": true,
-                "title": "inputs",
-                "markdownDescription": "This key defines which inputs are included in a group within a structure value.\n\nThe value is an array of input key name strings that specify which inputs belong to this group.\n\n## Examples\n\nIn this example, we have configured a group to include the `title` and `subtitle` inputs.\n\n```yaml\n_structures:\n  article_information:\n    values:\n      - label: Blog\n        value:\n          title:\n          subtitle:\n          author:\n        groups:\n          - heading: Titles\n            inputs:\n              - title\n              - subtitle\n          - heading: Details\n            inputs:\n              - author\n```"
-              },
-              "documentation": {
-                "description": "Provides a custom link for documentation for editors shown above the collection file list.",
-                "allOf": [
-                  {
-                    "$ref": "#/definitions/type.documentation"
-                  }
-                ],
-                "documented": false,
-                "title": "documentation",
-                "markdownDescription": "Provides a custom link for documentation for editors shown above the collection file list."
-              }
-            },
-            "additionalProperties": false,
-            "documented": true,
-            "title": "groups[*]",
-            "description": "This key represents an individual group object in the `values[*].groups` array.\n\nThe value is an object that groups inputs together within a structure value without changing the data structure. Each group typically contains a `heading` and `inputs` array.\n\n## Examples\n\nIn this example, we have configured a group with a heading and inputs array to organize structure inputs.\n\n```yaml\n_structures:\n  article_information:\n    values:\n      - label: Blog\n        value:\n          title:\n          subtitle:\n          author:\n        groups:\n          - heading: Titles\n            inputs:\n              - title\n              - subtitle\n          - heading: Details\n            inputs:\n              - author\n```",
-            "markdownDescription": "This key represents an individual group object in the `values[*].groups` array.\n\nThe value is an object that groups inputs together within a structure value without changing the data structure. Each group typically contains a `heading` and `inputs` array.\n\n## Examples\n\nIn this example, we have configured a group with a heading and inputs array to organize structure inputs.\n\n```yaml\n_structures:\n  article_information:\n    values:\n      - label: Blog\n        value:\n          title:\n          subtitle:\n          author:\n        groups:\n          - heading: Titles\n            inputs:\n              - title\n              - subtitle\n          - heading: Details\n            inputs:\n              - author\n```"
-          },
-          "documented": true,
-          "title": "groups",
-          "markdownDescription": "This key defines the order and custom grouping for inputs within a Structure.\n\nThe value is an array of group objects. Each group object can contain a `heading`, `comment`, `collapsed`, and `inputs` array.\n\n## Examples\n\nIn this example, we want to separate the inputs into two groups with descriptive headings: `title` and `subtitle` under the `Titles` heading, and `author` under the `Details` heading.\n\n```yaml\n_structures:\n  article_information:\n    values:\n      - label: Blog\n        value:\n          title:\n          subtitle:\n          author:\n        groups:\n          - heading: Titles\n            inputs:\n              - title\n              - subtitle\n          - heading: Details\n            inputs:\n              - author\n```"
-        },
-        "place_groups_below": {
-          "description": "This key defines which order input groups and ungrouped inputs appear in.",
-          "default": false,
-          "type": "boolean",
-          "documented": true,
-          "title": "place_groups_below",
-          "markdownDescription": "This key defines which order input groups and ungrouped inputs appear in."
-        },
-        "tabbed": {
-          "description": "This key toggles whether CloudCannon should create tabs in the Data Editor if you have two layers of nested object within your Structure.\n\nSetting this key to `true` will create tabs in the Data Editor for two layers of nested objects within your Structure.\n\nBy default, this key is `false` (i.e., Object and Array inputs using this Structure option are not tabbed).\n\n## Examples\n\nIn this example, we want the `content` and `style` keys in our Structure to be tabs at the top of the Data Editor, with the `title` and `text`, and `color` and `font` keys nested within those tabs respectively.\n\n```yaml\n_structures:\n  components:\n    values:\n      - label: Component\n        tabbed: true\n        value:\n          content:\n            title:\n            text:\n          style:\n            color:\n            font:\n```",
-          "default": false,
-          "type": "boolean",
-          "documented": true,
-          "title": "tabbed",
-          "markdownDescription": "This key toggles whether CloudCannon should create tabs in the Data Editor if you have two layers of nested object within your Structure.\n\nSetting this key to `true` will create tabs in the Data Editor for two layers of nested objects within your Structure.\n\nBy default, this key is `false` (i.e., Object and Array inputs using this Structure option are not tabbed).\n\n## Examples\n\nIn this example, we want the `content` and `style` keys in our Structure to be tabs at the top of the Data Editor, with the `title` and `text`, and `color` and `font` keys nested within those tabs respectively.\n\n```yaml\n_structures:\n  components:\n    values:\n      - label: Component\n        tabbed: true\n        value:\n          content:\n            title:\n            text:\n          style:\n            color:\n            font:\n```"
-        },
-        "value": {
-          "description": "This key defines which nested inputs the Structure value should add to an Object or Array input.\n\nYou must define this key for the Structure value to function.\n\nNested keys can be any [input](https://cloudcannon.com/documentation/articles/what-are-inputs/) you require in your Object or Array.\n\nFor more information, please read our documentation on [configuring an Object input](https://cloudcannon.com/documentation/articles/configure-an-object-input/) and\n[configuring and Array input](https://cloudcannon.com/documentation/articles/configure-an-array-input/).\n\n## Examples\n\nIn this example we want to populate the `details` Object input with the nested keys `title`, `subtitle`, and `author` we have defined under the `values.value` key.\n\n```yaml\n_structures:\n  article_information:\n    values:\n      - label: Blog\n        value:\n          title:\n          subtitle:\n          author:\n_inputs:\n  details:\n    type: object\n    options:\n      structures: _structures.article_information\n```",
-          "documented": true,
-          "title": "value",
-          "markdownDescription": "This key defines which nested inputs the Structure value should add to an Object or Array input.\n\nYou must define this key for the Structure value to function.\n\nNested keys can be any [input](https://cloudcannon.com/documentation/articles/what-are-inputs/) you require in your Object or Array.\n\nFor more information, please read our documentation on [configuring an Object input](https://cloudcannon.com/documentation/articles/configure-an-object-input/) and\n[configuring and Array input](https://cloudcannon.com/documentation/articles/configure-an-array-input/).\n\n## Examples\n\nIn this example we want to populate the `details` Object input with the nested keys `title`, `subtitle`, and `author` we have defined under the `values.value` key.\n\n```yaml\n_structures:\n  article_information:\n    values:\n      - label: Blog\n        value:\n          title:\n          subtitle:\n          author:\n_inputs:\n  details:\n    type: object\n    options:\n      structures: _structures.article_information\n```"
-        },
-        "description": {
-          "description": "This key defines short descriptive text for editors shown in the Data Editor for expanded values matching this Structure value.\n\nHas no default.\n\nSupports a limited set of Markdown: links, bold, italic, subscript, superscript, and inline code elements are allowed.",
-          "type": "string",
-          "documented": true,
-          "title": "description",
-          "markdownDescription": "This key defines short descriptive text for editors shown in the Data Editor for expanded values matching this Structure value.\n\nHas no default.\n\nSupports a limited set of Markdown: links, bold, italic, subscript, superscript, and inline code elements are allowed."
-        },
-        "documentation": {
-          "description": "Provides a custom link for documentation for editors shown in the Data Editor for expanded values matching this Structure value. Has no default.",
-          "allOf": [
-            {
-              "$ref": "#/definitions/type.documentation"
-            }
-          ],
-          "documented": false,
-          "title": "documentation",
-          "markdownDescription": "Provides a custom link for documentation for editors shown in the Data Editor for expanded values matching this Structure value. Has no default."
-        }
-      },
-      "required": [
-        "value"
-      ],
-      "additionalProperties": false,
-      "documented": true,
-      "markdownDescription": "This key represents a single value option within a structure, defining the data format and appearance for content editors."
-    },
     "type.preview": {
-      "title": "Preview",
       "type": "object",
       "properties": {
         "text": {
@@ -308,6 +39,7 @@
         }
       },
       "additionalProperties": false,
+      "title": "Preview",
       "documented": true,
       "description": "This key defines the appearance of a Card.\n\nYou can configure Card preview for [Collections](https://cloudcannon.com/documentation/articles/what-is-a-collection/), [Schemas](https://cloudcannon.com/documentation/articles/what-is-a-schema/),\n[Object inputs](https://cloudcannon.com/documentation/articles/what-is-an-object-input/), [Array inputs](https://cloudcannon.com/documentation/articles/what-is-an-array-input/), [Select\ninputs](https://cloudcannon.com/documentation/articles/what-is-a-select-input/), [Structures](https://cloudcannon.com/documentation/articles/what-is-a-structure/), the Structure modal,\n[Snippets](https://cloudcannon.com/documentation/articles/what-is-a-snippet/), and the Snippet modal.\n\nFor more information about previews, please read our documentation on [configuring card previews](https://cloudcannon.com/documentation/articles/configure-your-card-previews/).\n\n## Examples\n\nIn this example, we have configured the appearance of file Cards in the *Collection browser*.\n\n```yaml\ncollections_config:\n  blog:\n    preview:\n      text:\n        - key: title\n      subtext:\n        - key: author\n      icon: edit_note\n      icon_color:\n        - key: color\n        - '#ff0000'\n      image:\n        - key: image\n      metadata:\n        - template: [url]\n        - icon: event\n          text:\n            - template: 'Published on {date|date_long}'\n      gallery:\n        - key: featured_image\n```\n\nIn this example, we have configured the appearance of Cards in inputs using the Structure `staff`.\n\n```yaml\n_structures:\n  staff:\n    values:\n      - value:\n          _type: Employee\n          name:\n          job_description:\n          profile_picture:\n        preview:\n          text:\n            - key: name\n            - Employee\n          subtext:\n            - key: job_description\n            - Description of position\n          image:\n            - key: profile_picture\n          icon: support_agent\n      - value:\n          _type: Manager\n          name:\n          job_description:\n          profile_picture:\n          url:\n        preview:\n          text:\n            - key: name\n            - Manager\n          subtext:\n            - key: job_description\n            - Description of position\n          image:\n            - key: profile_picture\n          icon: face\n```",
       "markdownDescription": "This key defines the appearance of a Card.\n\nYou can configure Card preview for [Collections](https://cloudcannon.com/documentation/articles/what-is-a-collection/), [Schemas](https://cloudcannon.com/documentation/articles/what-is-a-schema/),\n[Object inputs](https://cloudcannon.com/documentation/articles/what-is-an-object-input/), [Array inputs](https://cloudcannon.com/documentation/articles/what-is-an-array-input/), [Select\ninputs](https://cloudcannon.com/documentation/articles/what-is-a-select-input/), [Structures](https://cloudcannon.com/documentation/articles/what-is-a-structure/), the Structure modal,\n[Snippets](https://cloudcannon.com/documentation/articles/what-is-a-snippet/), and the Snippet modal.\n\nFor more information about previews, please read our documentation on [configuring card previews](https://cloudcannon.com/documentation/articles/configure-your-card-previews/).\n\n## Examples\n\nIn this example, we have configured the appearance of file Cards in the *Collection browser*.\n\n```yaml\ncollections_config:\n  blog:\n    preview:\n      text:\n        - key: title\n      subtext:\n        - key: author\n      icon: edit_note\n      icon_color:\n        - key: color\n        - '#ff0000'\n      image:\n        - key: image\n      metadata:\n        - template: [url]\n        - icon: event\n          text:\n            - template: 'Published on {date|date_long}'\n      gallery:\n        - key: featured_image\n```\n\nIn this example, we have configured the appearance of Cards in inputs using the Structure `staff`.\n\n```yaml\n_structures:\n  staff:\n    values:\n      - value:\n          _type: Employee\n          name:\n          job_description:\n          profile_picture:\n        preview:\n          text:\n            - key: name\n            - Employee\n          subtext:\n            - key: job_description\n            - Description of position\n          image:\n            - key: profile_picture\n          icon: support_agent\n      - value:\n          _type: Manager\n          name:\n          job_description:\n          profile_picture:\n          url:\n        preview:\n          text:\n            - key: name\n            - Manager\n          subtext:\n            - key: job_description\n            - Description of position\n          image:\n            - key: profile_picture\n          icon: face\n```"
@@ -339,17 +71,16 @@
       "title": "text(previewentries)"
     },
     "type.preview-entry.(array)": {
-      "title": "Array Preview Entry",
       "type": "array",
       "items": {
         "$ref": "#/definitions/type.preview-entry"
       },
+      "title": "Array Preview Entry",
       "documented": true,
       "description": "This key represents an array of preview entries for displaying data on *Cards* in the *Collection browser*, *Structures*, and *Snippets*.\n\nThe value is an array of preview entry objects, strings, or `false` values. Each preview entry object can contain a `key`, `template`, or `text` property. When multiple entries are provided, CloudCannon will use them in order as fallback options.\n\n## Examples\n\nIn this example, we have configured an array of preview entries with an array of values to provide fallback options. CloudCannon will use the value of `title` first, then the `{name}` template, and finally fall back to the static text value.\n\n```yaml\ncollections_config:\n  blog:\n    preview:\n      text:\n        - key: title\n        - template: '{name}'\n        - text: 'Untitled'\n```",
       "markdownDescription": "This key represents an array of preview entries for displaying data on *Cards* in the *Collection browser*, *Structures*, and *Snippets*.\n\nThe value is an array of preview entry objects, strings, or `false` values. Each preview entry object can contain a `key`, `template`, or `text` property. When multiple entries are provided, CloudCannon will use them in order as fallback options.\n\n## Examples\n\nIn this example, we have configured an array of preview entries with an array of values to provide fallback options. CloudCannon will use the value of `title` first, then the `{name}` template, and finally fall back to the static text value.\n\n```yaml\ncollections_config:\n  blog:\n    preview:\n      text:\n        - key: title\n        - template: '{name}'\n        - text: 'Untitled'\n```"
     },
     "type.preview-entry": {
-      "title": "Preview Entry",
       "anyOf": [
         {
           "$ref": "#/definitions/type.preview-entry.(key)"
@@ -367,17 +98,17 @@
           "$ref": "#/definitions/type.preview-entry.(false)"
         }
       ],
+      "title": "Preview Entry",
       "documented": true,
       "description": "This key defines a preview entry configuration for displaying data on *Cards* in the *Collection browser*, *Structures*, and *Snippets*.\n\nThe value can be an object with a `key`, `template`, or `text` property, a raw text string, `false`, or an array of these values. When multiple entries are provided, CloudCannon will use them in order as fallback options. Preview entries are used to configure how data is displayed in card previews.\n\n## Examples\n\nIn this example, we have configured a preview entry with an array of values to provide fallback options. CloudCannon will use the value of `title` first, then the `{name}` template, and finally fall back to the static text value.\n\n```yaml\ncollections_config:\n  blog:\n    preview:\n      text:\n        - key: title\n        - template: '{name}'\n        - text: 'Untitled'\n```\n\nIn this example, we have configured a preview entry to display the `title` key.\n\n```yaml\ncollections_config:\n  blog:\n    preview:\n      text:\n        - key: title\n```",
       "markdownDescription": "This key defines a preview entry configuration for displaying data on *Cards* in the *Collection browser*, *Structures*, and *Snippets*.\n\nThe value can be an object with a `key`, `template`, or `text` property, a raw text string, `false`, or an array of these values. When multiple entries are provided, CloudCannon will use them in order as fallback options. Preview entries are used to configure how data is displayed in card previews.\n\n## Examples\n\nIn this example, we have configured a preview entry with an array of values to provide fallback options. CloudCannon will use the value of `title` first, then the `{name}` template, and finally fall back to the static text value.\n\n```yaml\ncollections_config:\n  blog:\n    preview:\n      text:\n        - key: title\n        - template: '{name}'\n        - text: 'Untitled'\n```\n\nIn this example, we have configured a preview entry to display the `title` key.\n\n```yaml\ncollections_config:\n  blog:\n    preview:\n      text:\n        - key: title\n```"
     },
     "type.preview-entry.(key)": {
-      "title": "Key Preview Entry",
       "type": "object",
       "properties": {
         "key": {
-          "title": "Key Value",
           "type": "string",
+          "title": "Key Value",
           "documented": true,
           "description": "This key defines the data key name to display in a key preview entry.\n\nThe value is a string that specifies the name of a data key whose value will be displayed on *Cards* in the *Collection browser*, *Structures*, and *Snippets*.\n\n## Examples\n\nIn this example, we have configured the key value to display the `title` field.\n\n```yaml\ncollections_config:\n  blog:\n    preview:\n      text:\n        - key: title\n```",
           "markdownDescription": "This key defines the data key name to display in a key preview entry.\n\nThe value is a string that specifies the name of a data key whose value will be displayed on *Cards* in the *Collection browser*, *Structures*, and *Snippets*.\n\n## Examples\n\nIn this example, we have configured the key value to display the `title` field.\n\n```yaml\ncollections_config:\n  blog:\n    preview:\n      text:\n        - key: title\n```"
@@ -387,17 +118,17 @@
         "key"
       ],
       "additionalProperties": false,
+      "title": "Key Preview Entry",
       "documented": true,
       "description": "This key represents a key preview entry type for displaying data from a specific key on *Cards* in the *Collection browser*, *Structures*, and *Snippets*.\n\nThe value is an object that contains a `key` property with a string value. This displays the value of the specified data key in card previews.\n\n## Examples\n\nIn this example, we have configured a key preview entry to display the `title` key.\n\n```yaml\ncollections_config:\n  blog:\n    preview:\n      text:\n        - key: title\n```",
       "markdownDescription": "This key represents a key preview entry type for displaying data from a specific key on *Cards* in the *Collection browser*, *Structures*, and *Snippets*.\n\nThe value is an object that contains a `key` property with a string value. This displays the value of the specified data key in card previews.\n\n## Examples\n\nIn this example, we have configured a key preview entry to display the `title` key.\n\n```yaml\ncollections_config:\n  blog:\n    preview:\n      text:\n        - key: title\n```"
     },
     "type.preview-entry.(template)": {
-      "title": "Template Preview Entry",
       "type": "object",
       "properties": {
         "template": {
-          "title": "Template Value",
           "type": "string",
+          "title": "Template Value",
           "documented": true,
           "description": "This key defines the template string to use in a template preview entry.\n\nThe value is a string that specifies a template with placeholders (e.g., `{name}`, `{date}`) that will be replaced with data values when displayed on *Cards* in the *Collection browser*, *Structures*, and *Snippets*.\n\n## Examples\n\nIn this example, we have configured the template value to display author and date.\n\n```yaml\ncollections_config:\n  blog:\n    preview:\n      text:\n        - template: '{author} - {date}'\n```",
           "markdownDescription": "This key defines the template string to use in a template preview entry.\n\nThe value is a string that specifies a template with placeholders (e.g., `{name}`, `{date}`) that will be replaced with data values when displayed on *Cards* in the *Collection browser*, *Structures*, and *Snippets*.\n\n## Examples\n\nIn this example, we have configured the template value to display author and date.\n\n```yaml\ncollections_config:\n  blog:\n    preview:\n      text:\n        - template: '{author} - {date}'\n```"
@@ -407,17 +138,17 @@
         "template"
       ],
       "additionalProperties": false,
+      "title": "Template Preview Entry",
       "documented": true,
       "description": "This key represents a template preview entry type for displaying formatted text using a template on *Cards* in the *Collection browser*, *Structures*, and *Snippets*.\n\nThe value is an object that contains a `template` property with a string value. This displays formatted text using template syntax (e.g., `{name}`) in card previews.\n\n## Examples\n\nIn this example, we have configured a template preview entry to display formatted text.\n\n```yaml\ncollections_config:\n  blog:\n    preview:\n      text:\n        - template: '{author} - {date}'\n```",
       "markdownDescription": "This key represents a template preview entry type for displaying formatted text using a template on *Cards* in the *Collection browser*, *Structures*, and *Snippets*.\n\nThe value is an object that contains a `template` property with a string value. This displays formatted text using template syntax (e.g., `{name}`) in card previews.\n\n## Examples\n\nIn this example, we have configured a template preview entry to display formatted text.\n\n```yaml\ncollections_config:\n  blog:\n    preview:\n      text:\n        - template: '{author} - {date}'\n```"
     },
     "type.preview-entry.(text)": {
-      "title": "Text Preview Entry",
       "type": "object",
       "properties": {
         "text": {
-          "title": "Text Value",
           "type": "string",
+          "title": "Text Value",
           "documented": true,
           "description": "This key defines the static text string to display in a text preview entry.\n\nThe value is a string that specifies static text to display on *Cards* in the *Collection browser*, *Structures*, and *Snippets*.\n\n## Examples\n\nIn this example, we have configured the text value to display a static fallback message.\n\n```yaml\ncollections_config:\n  blog:\n    preview:\n      text:\n        - text: 'Untitled'\n```",
           "markdownDescription": "This key defines the static text string to display in a text preview entry.\n\nThe value is a string that specifies static text to display on *Cards* in the *Collection browser*, *Structures*, and *Snippets*.\n\n## Examples\n\nIn this example, we have configured the text value to display a static fallback message.\n\n```yaml\ncollections_config:\n  blog:\n    preview:\n      text:\n        - text: 'Untitled'\n```"
@@ -427,21 +158,22 @@
         "text"
       ],
       "additionalProperties": false,
+      "title": "Text Preview Entry",
       "documented": true,
       "description": "This key represents a text preview entry type for displaying static text on *Cards* in the *Collection browser*, *Structures*, and *Snippets*.\n\nThe value is an object that contains a `text` property with a string value. This displays static text in card previews.\n\n## Examples\n\nIn this example, we have configured a text preview entry to display static text.\n\n```yaml\ncollections_config:\n  blog:\n    preview:\n      text:\n        - text: 'Untitled'\n```",
       "markdownDescription": "This key represents a text preview entry type for displaying static text on *Cards* in the *Collection browser*, *Structures*, and *Snippets*.\n\nThe value is an object that contains a `text` property with a string value. This displays static text in card previews.\n\n## Examples\n\nIn this example, we have configured a text preview entry to display static text.\n\n```yaml\ncollections_config:\n  blog:\n    preview:\n      text:\n        - text: 'Untitled'\n```"
     },
     "type.preview-entry.(raw-text)": {
-      "title": "Raw Text Preview Entry",
       "type": "string",
+      "title": "Raw Text Preview Entry",
       "documented": true,
       "description": "This key represents a raw text preview entry type for displaying static text on *Cards* in the *Collection browser*, *Structures*, and *Snippets*.\n\nThe value is a string that specifies static text to display in card previews. This is equivalent to using `{ text: \"...\" }` but in a simpler format.\n\n## Examples\n\nIn this example, we have configured a raw text preview entry to display static text.\n\n```yaml\ncollections_config:\n  blog:\n    preview:\n      text: 'Untitled'\n```",
       "markdownDescription": "This key represents a raw text preview entry type for displaying static text on *Cards* in the *Collection browser*, *Structures*, and *Snippets*.\n\nThe value is a string that specifies static text to display in card previews. This is equivalent to using `{ text: \"...\" }` but in a simpler format.\n\n## Examples\n\nIn this example, we have configured a raw text preview entry to display static text.\n\n```yaml\ncollections_config:\n  blog:\n    preview:\n      text: 'Untitled'\n```"
     },
     "type.preview-entry.(false)": {
-      "title": "False Preview Entry",
       "type": "boolean",
       "const": false,
+      "title": "False Preview Entry",
       "documented": true,
       "description": "This key represents a preview entry that disables the preview display for a specific field on *Cards* in the *Collection browser*, *Structures*, and *Snippets*.\n\nThe value must be `false`. Setting a preview entry to `false` will hide that preview element.\n\n## Examples\n\nIn this example, we have configured the preview text to be disabled.\n\n```yaml\ncollections_config:\n  blog:\n    preview:\n      text: false\n```",
       "markdownDescription": "This key represents a preview entry that disables the preview display for a specific field on *Cards* in the *Collection browser*, *Structures*, and *Snippets*.\n\nThe value must be `false`. Setting a preview entry to `false` will hide that preview element.\n\n## Examples\n\nIn this example, we have configured the preview text to be disabled.\n\n```yaml\ncollections_config:\n  blog:\n    preview:\n      text: false\n```"
@@ -617,9 +349,16 @@
       "description": "This key defines the appearance of a Card when choosing an item to create. This uses `preview` as a base, and keys inside this object are overrides.\n\nYou can configure Card preview for [Collections](https://cloudcannon.com/documentation/articles/what-is-a-collection/), [Schemas](https://cloudcannon.com/documentation/articles/what-is-a-schema/),\n[Object inputs](https://cloudcannon.com/documentation/articles/what-is-an-object-input/), [Array inputs](https://cloudcannon.com/documentation/articles/what-is-an-array-input/), [Select\ninputs](https://cloudcannon.com/documentation/articles/what-is-a-select-input/), [Structures](https://cloudcannon.com/documentation/articles/what-is-a-structure/), the Structure modal,\n[Snippets](https://cloudcannon.com/documentation/articles/what-is-a-snippet/), and the Snippet modal.\n\nFor more information about previews, please read our documentation on [configuring card previews](https://cloudcannon.com/documentation/articles/configure-your-card-previews/).\n\n## Examples\n\nIn this example, we have configured the appearance of Cards in inputs using the Structure `staff` when adding items.\n\n```yaml\n_structures:\n  staff:\n    values:\n      - value:\n          _type: Employee\n          name:\n          job_description:\n          profile_picture:\n        picker_preview:\n          text:\n            - key: name\n            - Employee\n          subtext:\n            - key: job_description\n            - Description of position\n          image:\n            - key: profile_picture\n          icon: support_agent\n      - value:\n          _type: Manager\n          name:\n          job_description:\n          profile_picture:\n          url:\n        picker_preview:\n          text:\n            - key: name\n            - Manager\n          subtext:\n            - key: job_description\n            - Description of position\n          image:\n            - key: profile_picture\n          icon: face\n```",
       "markdownDescription": "This key defines the appearance of a Card when choosing an item to create. This uses `preview` as a base, and keys inside this object are overrides.\n\nYou can configure Card preview for [Collections](https://cloudcannon.com/documentation/articles/what-is-a-collection/), [Schemas](https://cloudcannon.com/documentation/articles/what-is-a-schema/),\n[Object inputs](https://cloudcannon.com/documentation/articles/what-is-an-object-input/), [Array inputs](https://cloudcannon.com/documentation/articles/what-is-an-array-input/), [Select\ninputs](https://cloudcannon.com/documentation/articles/what-is-a-select-input/), [Structures](https://cloudcannon.com/documentation/articles/what-is-a-structure/), the Structure modal,\n[Snippets](https://cloudcannon.com/documentation/articles/what-is-a-snippet/), and the Snippet modal.\n\nFor more information about previews, please read our documentation on [configuring card previews](https://cloudcannon.com/documentation/articles/configure-your-card-previews/).\n\n## Examples\n\nIn this example, we have configured the appearance of Cards in inputs using the Structure `staff` when adding items.\n\n```yaml\n_structures:\n  staff:\n    values:\n      - value:\n          _type: Employee\n          name:\n          job_description:\n          profile_picture:\n        picker_preview:\n          text:\n            - key: name\n            - Employee\n          subtext:\n            - key: job_description\n            - Description of position\n          image:\n            - key: profile_picture\n          icon: support_agent\n      - value:\n          _type: Manager\n          name:\n          job_description:\n          profile_picture:\n          url:\n        picker_preview:\n          text:\n            - key: name\n            - Manager\n          subtext:\n            - key: job_description\n            - Description of position\n          image:\n            - key: profile_picture\n          icon: face\n```"
     },
+    "__schema0": {
+      "allOf": [
+        {
+          "$ref": "#/definitions/type._inputs"
+        }
+      ],
+      "documented": false,
+      "title": "_inputs"
+    },
     "type._inputs": {
-      "title": "Inputs",
-      "description": "This key defines which inputs are available at a given level of the configuration cascade.\n\nThis key has no default.\n\nIf undefined at higher levels of the [configuration cascade](https://cloudcannon.com/documentation/articles/using-the-configuration-cascade/), `_inputs` will default to any\nvalues configured in the [CloudCannon configuration file](https://cloudcannon.com/documentation/articles/what-is-the-cloudcannon-configuration-file/).\n\n## Examples\n\nIn this example, we have configured the `date_created` key as a *Date and Time Input*, which will automatically populate when you create a file using this input. Editors cannot alter this input as the interface is disabled.\n\n```yaml\n_inputs:\n  date_created:\n    type: datetime\n    label: Date of article creation\n    comment: UTC +0 timezone\n    context:\n      open: false\n      title: Help\n      icon: help\n      content: This date field will automatically populate when you create an article.\n    hidden: false\n    disabled: true\n    instance_value: NOW\n    cascade: true\n    options:\n      timezone: Etc/UTC\n```\n\nIn this example, we have configured the `blog_tags` key as a *Multiselect Input* in the `blog` Collection.\n\n```yaml\ncollections_config:\n  blog:\n    _inputs:\n      blog_tags:\n        type: multiselect\n        label: Blog type\n        comment: Select a blog type\n        context:\n          open: false\n          title: Help\n          icon: help\n          content: |\n            Blog tags help our users filter articles by topic.\n        options:\n          values:\n            - Opinion\n            - Feature\n            - Resource\n```",
       "type": "object",
       "propertyNames": {
         "type": "string"
@@ -627,15 +366,14 @@
       "additionalProperties": {
         "$ref": "#/definitions/Input"
       },
+      "title": "Inputs",
+      "description": "This key defines which inputs are available at a given level of the configuration cascade.\n\nThis key has no default.\n\nIf undefined at higher levels of the [configuration cascade](https://cloudcannon.com/documentation/articles/using-the-configuration-cascade/), `_inputs` will default to any\nvalues configured in the [CloudCannon configuration file](https://cloudcannon.com/documentation/articles/what-is-the-cloudcannon-configuration-file/).\n\n## Examples\n\nIn this example, we have configured the `date_created` key as a *Date and Time Input*, which will automatically populate when you create a file using this input. Editors cannot alter this input as the interface is disabled.\n\n```yaml\n_inputs:\n  date_created:\n    type: datetime\n    label: Date of article creation\n    comment: UTC +0 timezone\n    context:\n      open: false\n      title: Help\n      icon: help\n      content: This date field will automatically populate when you create an article.\n    hidden: false\n    disabled: true\n    instance_value: NOW\n    cascade: true\n    options:\n      timezone: Etc/UTC\n```\n\nIn this example, we have configured the `blog_tags` key as a *Multiselect Input* in the `blog` Collection.\n\n```yaml\ncollections_config:\n  blog:\n    _inputs:\n      blog_tags:\n        type: multiselect\n        label: Blog type\n        comment: Select a blog type\n        context:\n          open: false\n          title: Help\n          icon: help\n          content: |\n            Blog tags help our users filter articles by topic.\n        options:\n          values:\n            - Opinion\n            - Feature\n            - Resource\n```",
       "documented": true,
       "markdownDescription": "This key defines which inputs are available at a given level of the configuration cascade.\n\nThis key has no default.\n\nIf undefined at higher levels of the [configuration cascade](https://cloudcannon.com/documentation/articles/using-the-configuration-cascade/), `_inputs` will default to any\nvalues configured in the [CloudCannon configuration file](https://cloudcannon.com/documentation/articles/what-is-the-cloudcannon-configuration-file/).\n\n## Examples\n\nIn this example, we have configured the `date_created` key as a *Date and Time Input*, which will automatically populate when you create a file using this input. Editors cannot alter this input as the interface is disabled.\n\n```yaml\n_inputs:\n  date_created:\n    type: datetime\n    label: Date of article creation\n    comment: UTC +0 timezone\n    context:\n      open: false\n      title: Help\n      icon: help\n      content: This date field will automatically populate when you create an article.\n    hidden: false\n    disabled: true\n    instance_value: NOW\n    cascade: true\n    options:\n      timezone: Etc/UTC\n```\n\nIn this example, we have configured the `blog_tags` key as a *Multiselect Input* in the `blog` Collection.\n\n```yaml\ncollections_config:\n  blog:\n    _inputs:\n      blog_tags:\n        type: multiselect\n        label: Blog type\n        comment: Select a blog type\n        context:\n          open: false\n          title: Help\n          icon: help\n          content: |\n            Blog tags help our users filter articles by topic.\n        options:\n          values:\n            - Opinion\n            - Feature\n            - Resource\n```"
     },
     "Input": {
-      "title": "Input",
       "anyOf": [
         {
-          "title": "Known Input",
-          "description": "This key defines an input configuration at a given level of the configuration cascade.\n\nThe value is an object that can contain `type`, `label`, `options`, `disabled`, `hidden`, and other input-specific properties. Each input configuration defines how team members interact with data in the *Data Editor*.\n\nFor more information, please read our documentation on [inputs](https://cloudcannon.com/documentation/articles/what-are-inputs/).\n\n## Examples\n\nIn this example, we have configured the `title` key as a *Text Input* in the `blog` Collection.\n\n```yaml\ncollections_config:\n  blog:\n    _inputs:\n      title:\n        type: text\n        label: Title\n```",
           "oneOf": [
             {
               "$ref": "#/definitions/TextInput"
@@ -695,6 +433,8 @@
               "$ref": "#/definitions/AutoInput"
             }
           ],
+          "title": "Known Input",
+          "description": "This key defines an input configuration at a given level of the configuration cascade.\n\nThe value is an object that can contain `type`, `label`, `options`, `disabled`, `hidden`, and other input-specific properties. Each input configuration defines how team members interact with data in the *Data Editor*.\n\nFor more information, please read our documentation on [inputs](https://cloudcannon.com/documentation/articles/what-are-inputs/).\n\n## Examples\n\nIn this example, we have configured the `title` key as a *Text Input* in the `blog` Collection.\n\n```yaml\ncollections_config:\n  blog:\n    _inputs:\n      title:\n        type: text\n        label: Title\n```",
           "documented": true,
           "markdownDescription": "This key defines an input configuration at a given level of the configuration cascade.\n\nThe value is an object that can contain `type`, `label`, `options`, `disabled`, `hidden`, and other input-specific properties. Each input configuration defines how team members interact with data in the *Data Editor*.\n\nFor more information, please read our documentation on [inputs](https://cloudcannon.com/documentation/articles/what-are-inputs/).\n\n## Examples\n\nIn this example, we have configured the `title` key as a *Text Input* in the `blog` Collection.\n\n```yaml\ncollections_config:\n  blog:\n    _inputs:\n      title:\n        type: text\n        label: Title\n```"
         },
@@ -702,13 +442,12 @@
           "$ref": "#/definitions/UnknownInput"
         }
       ],
+      "title": "Input",
       "documented": true,
       "description": "This key defines an input configuration at a given level of the configuration cascade.\n\nThe value is an object that can contain `type`, `label`, `options`, `disabled`, `hidden`, and other input-specific properties. Each input configuration defines how team members interact with data in the *Data Editor*.\n\nFor more information, please read our documentation on [inputs](https://cloudcannon.com/documentation/articles/what-are-inputs/).\n\n## Examples\n\nIn this example, we have configured the `title` key as a *Text Input* in the `blog` Collection.\n\n```yaml\ncollections_config:\n  blog:\n    _inputs:\n      title:\n        type: text\n        label: Title\n```",
       "markdownDescription": "This key defines an input configuration at a given level of the configuration cascade.\n\nThe value is an object that can contain `type`, `label`, `options`, `disabled`, `hidden`, and other input-specific properties. Each input configuration defines how team members interact with data in the *Data Editor*.\n\nFor more information, please read our documentation on [inputs](https://cloudcannon.com/documentation/articles/what-are-inputs/).\n\n## Examples\n\nIn this example, we have configured the `title` key as a *Text Input* in the `blog` Collection.\n\n```yaml\ncollections_config:\n  blog:\n    _inputs:\n      title:\n        type: text\n        label: Title\n```"
     },
     "TextInput": {
-      "title": "Text Input",
-      "description": "This key defines a simple editing interface for plain text.\n\n## Examples\n\nIn this example, we have configured the `title` key as a *Text Input*.\n\n```yaml\n_inputs:\n  title:\n    type: text\n    label: Blog Title\n```",
       "type": "object",
       "properties": {
         "comment": {
@@ -753,8 +492,6 @@
           "$ref": "#/definitions/type._inputs.*.cascade"
         },
         "type": {
-          "title": "Type",
-          "description": "This key defines the input type, which controls how this input appears and behaves.\n\n## Examples\n\nIn this example, we have configured the `title` key as a *Text Input* type.\n\n```yaml\n_inputs:\n  title:\n    type: text\n```",
           "type": "string",
           "enum": [
             "text",
@@ -766,11 +503,12 @@
             "github",
             "instagram"
           ],
+          "title": "Type",
+          "description": "This key defines the input type, which controls how this input appears and behaves.\n\n## Examples\n\nIn this example, we have configured the `title` key as a *Text Input* type.\n\n```yaml\n_inputs:\n  title:\n    type: text\n```",
           "documented": true,
           "markdownDescription": "This key defines the input type, which controls how this input appears and behaves.\n\n## Examples\n\nIn this example, we have configured the `title` key as a *Text Input* type.\n\n```yaml\n_inputs:\n  title:\n    type: text\n```"
         },
         "options": {
-          "description": "This key defines options that are specific to Text Inputs.\n\n## Examples\n\nIn this example, we have configured *Text Input* options including comment and icon.\n\n```yaml\n_inputs:\n  title:\n    type: text\n    options:\n      comment: Enter a title\n      icon: title\n```",
           "type": "object",
           "properties": {
             "max_length": {
@@ -878,6 +616,7 @@
             }
           },
           "additionalProperties": false,
+          "description": "This key defines options that are specific to Text Inputs.\n\n## Examples\n\nIn this example, we have configured *Text Input* options including comment and icon.\n\n```yaml\n_inputs:\n  title:\n    type: text\n    options:\n      comment: Enter a title\n      icon: title\n```",
           "documented": true,
           "title": "options",
           "markdownDescription": "This key defines options that are specific to Text Inputs.\n\n## Examples\n\nIn this example, we have configured *Text Input* options including comment and icon.\n\n```yaml\n_inputs:\n  title:\n    type: text\n    options:\n      comment: Enter a title\n      icon: title\n```"
@@ -887,6 +626,8 @@
         "type"
       ],
       "additionalProperties": false,
+      "title": "Text Input",
+      "description": "This key defines a simple editing interface for plain text.\n\n## Examples\n\nIn this example, we have configured the `title` key as a *Text Input*.\n\n```yaml\n_inputs:\n  title:\n    type: text\n    label: Blog Title\n```",
       "documented": true,
       "markdownDescription": "This key defines a simple editing interface for plain text.\n\n## Examples\n\nIn this example, we have configured the `title` key as a *Text Input*.\n\n```yaml\n_inputs:\n  title:\n    type: text\n    label: Blog Title\n```"
     },
@@ -898,7 +639,6 @@
       "markdownDescription": "This key defines the subtitle text above an Input.\n\nCloudCannon supports a limited selection of Markdown formatting for the value of this key: links, bold, italic, subscript, superscript, and inline\ncode.\n\nThis key has no default.\n\n## Examples\n\nIn this example, we want to add helpful guidance for our `page_description` Input.\n\n```yaml\n_inputs:\n  page_description:\n    type: text\n    label: Page Description\n    comment: Enter a brief description of this page for search engines\n```"
     },
     "type._inputs.*.context": {
-      "description": "This key defines a context box for extra information about an Input.\n\nThis key has no default.\n\n## Examples\n\nIn this example, we want to add a context box to our `date_created` Input to explain its purpose.\n\n```yaml\n_inputs:\n  date_created:\n    type: datetime\n    label: Date of article creation\n    instance_value: NOW\n    context:\n      open: false\n      title: Help\n      icon: help\n      content: This date field will automatically populate when you create an article.\n```",
       "type": "object",
       "properties": {
         "content": {
@@ -936,13 +676,12 @@
         }
       },
       "additionalProperties": false,
+      "description": "This key defines a context box for extra information about an Input.\n\nThis key has no default.\n\n## Examples\n\nIn this example, we want to add a context box to our `date_created` Input to explain its purpose.\n\n```yaml\n_inputs:\n  date_created:\n    type: datetime\n    label: Date of article creation\n    instance_value: NOW\n    context:\n      open: false\n      title: Help\n      icon: help\n      content: This date field will automatically populate when you create an article.\n```",
       "documented": true,
       "title": "context",
       "markdownDescription": "This key defines a context box for extra information about an Input.\n\nThis key has no default.\n\n## Examples\n\nIn this example, we want to add a context box to our `date_created` Input to explain its purpose.\n\n```yaml\n_inputs:\n  date_created:\n    type: datetime\n    label: Date of article creation\n    instance_value: NOW\n    context:\n      open: false\n      title: Help\n      icon: help\n      content: This date field will automatically populate when you create an article.\n```"
     },
     "icon": {
-      "title": "Icon",
-      "description": "Material Symbol icon names available in CloudCannon for UI elements and content previews.",
       "type": "string",
       "enum": [
         "123",
@@ -4530,17 +4269,17 @@
         "zoom_out",
         "zoom_out_map"
       ],
+      "title": "Icon",
+      "description": "Material Symbol icon names available in CloudCannon for UI elements and content previews.",
       "documented": false,
       "markdownDescription": "Material Symbol icon names available in CloudCannon for UI elements and content previews."
     },
     "type.documentation": {
-      "title": "Documentation",
-      "description": "This key defines the documentation link at the top of a *Collection browser*.\n\nCollection documentation is useful for assisting your team members.\n\n## Examples\n\nIn this example, the documentation link for the `data` Collection goes to [CloudCannon Documentation](https://cloudcannon.com/documentation/).\n\n```yaml\ncollections_config:\n  data:\n    documentation:\n      url: https://cloudcannon.com/documentation/\n      text: CloudCannon Documentation\n      icon: star\n```",
       "type": "object",
       "properties": {
         "url": {
-          "description": "This key defines the URL for the documentation link at the top of a *Collection browser*.\n\nYou must define this key for the\n`documentation` object to function.\n\nThis key has no default.\n\n## Examples\n\nIn this example, we have configured the `blog` Collection documentation link to go to `example.com`.\n\n```yaml\ncollections_config:\n  blog:\n    documentation:\n      url: https://example.com\n```",
           "type": "string",
+          "description": "This key defines the URL for the documentation link at the top of a *Collection browser*.\n\nYou must define this key for the\n`documentation` object to function.\n\nThis key has no default.\n\n## Examples\n\nIn this example, we have configured the `blog` Collection documentation link to go to `example.com`.\n\n```yaml\ncollections_config:\n  blog:\n    documentation:\n      url: https://example.com\n```",
           "documented": true,
           "title": "url",
           "markdownDescription": "This key defines the URL for the documentation link at the top of a *Collection browser*.\n\nYou must define this key for the\n`documentation` object to function.\n\nThis key has no default.\n\n## Examples\n\nIn this example, we have configured the `blog` Collection documentation link to go to `example.com`.\n\n```yaml\ncollections_config:\n  blog:\n    documentation:\n      url: https://example.com\n```"
@@ -4569,6 +4308,8 @@
         "url"
       ],
       "additionalProperties": false,
+      "title": "Documentation",
+      "description": "This key defines the documentation link at the top of a *Collection browser*.\n\nCollection documentation is useful for assisting your team members.\n\n## Examples\n\nIn this example, the documentation link for the `data` Collection goes to [CloudCannon Documentation](https://cloudcannon.com/documentation/).\n\n```yaml\ncollections_config:\n  data:\n    documentation:\n      url: https://cloudcannon.com/documentation/\n      text: CloudCannon Documentation\n      icon: star\n```",
       "documented": true,
       "markdownDescription": "This key defines the documentation link at the top of a *Collection browser*.\n\nCollection documentation is useful for assisting your team members.\n\n## Examples\n\nIn this example, the documentation link for the `data` Collection goes to [CloudCannon Documentation](https://cloudcannon.com/documentation/).\n\n```yaml\ncollections_config:\n  data:\n    documentation:\n      url: https://cloudcannon.com/documentation/\n      text: CloudCannon Documentation\n      icon: star\n```"
     },
@@ -4584,15 +4325,15 @@
       "default": false,
       "anyOf": [
         {
-          "title": "Boolean Hidden",
           "type": "boolean",
+          "title": "Boolean Hidden",
           "documented": true,
           "description": "This key represents a boolean value for the `hidden` key that toggles whether CloudCannon hides an input from view.\n\nWhen set to `true`, CloudCannon hides the input from the *Data Editor* and the sidebar of the *Visual Editor* or *Content Editor*. The input still exists in the file and can be edited in the *Source Editor*.\n\nWhen set to `false`, CloudCannon displays the input normally.\n\nBy default, this key follows the input naming convention where key names beginning with an underscore are hidden (`true`). Otherwise, this key defaults to `false` (i.e., the input is visible).\n\n## Examples\n\nIn this example, we have configured an input to be hidden using a boolean value, making it only editable in the *Source Editor*.\n\n```yaml\n_inputs:\n  internal_id:\n    type: text\n    label: Internal ID\n    hidden: true\n```",
           "markdownDescription": "This key represents a boolean value for the `hidden` key that toggles whether CloudCannon hides an input from view.\n\nWhen set to `true`, CloudCannon hides the input from the *Data Editor* and the sidebar of the *Visual Editor* or *Content Editor*. The input still exists in the file and can be edited in the *Source Editor*.\n\nWhen set to `false`, CloudCannon displays the input normally.\n\nBy default, this key follows the input naming convention where key names beginning with an underscore are hidden (`true`). Otherwise, this key defaults to `false` (i.e., the input is visible).\n\n## Examples\n\nIn this example, we have configured an input to be hidden using a boolean value, making it only editable in the *Source Editor*.\n\n```yaml\n_inputs:\n  internal_id:\n    type: text\n    label: Internal ID\n    hidden: true\n```"
         },
         {
-          "title": "Query String Hidden",
           "type": "string",
+          "title": "Query String Hidden",
           "documented": true,
           "description": "This key represents a query string value for the `hidden` key that conditionally hides an input based on another input's value.\n\nThe value is a string that references a sibling input key name. CloudCannon evaluates the referenced input's value to determine whether to hide this input.\n\nWhen the referenced input is truthy, CloudCannon hides this input. You can reverse this behavior by prefixing the string with `!`.\n\nFor reverse values in YAML files, the string should be wrapped in single or double quotation marks.\n\n## Examples\n\nIn this example, we have configured an input to be hidden when the `published` input is truthy.\n\n```yaml\n_inputs:\n  published:\n    type: checkbox\n    label: Published\n  draft_notes:\n    type: textarea\n    label: Draft notes\n    hidden: published\n```\n\nIn this example, we have configured an input to be hidden when the `published` input is falsy using the `!` prefix.\n\n```yaml\n_inputs:\n  published:\n    type: checkbox\n    label: Published\n  publish_date:\n    type: datetime\n    label: Publish date\n    hidden: '!published'\n```",
           "markdownDescription": "This key represents a query string value for the `hidden` key that conditionally hides an input based on another input's value.\n\nThe value is a string that references a sibling input key name. CloudCannon evaluates the referenced input's value to determine whether to hide this input.\n\nWhen the referenced input is truthy, CloudCannon hides this input. You can reverse this behavior by prefixing the string with `!`.\n\nFor reverse values in YAML files, the string should be wrapped in single or double quotation marks.\n\n## Examples\n\nIn this example, we have configured an input to be hidden when the `published` input is truthy.\n\n```yaml\n_inputs:\n  published:\n    type: checkbox\n    label: Published\n  draft_notes:\n    type: textarea\n    label: Draft notes\n    hidden: published\n```\n\nIn this example, we have configured an input to be hidden when the `published` input is falsy using the `!` prefix.\n\n```yaml\n_inputs:\n  published:\n    type: checkbox\n    label: Published\n  publish_date:\n    type: datetime\n    label: Publish date\n    hidden: '!published'\n```"
@@ -4607,15 +4348,15 @@
       "default": false,
       "anyOf": [
         {
-          "title": "Boolean",
           "type": "boolean",
+          "title": "Boolean",
           "documented": true,
           "description": "This key represents a boolean value for the `disabled` key that toggles whether CloudCannon prevents editing of an input value.\n\nWhen set to `true`, CloudCannon prevents team members from editing the input value in the *Data Editor* or the sidebar of the *Visual Editor* or *Content Editor*. The input value is still displayed but cannot be modified outside of the *Source Editor*.\n\nWhen set to `false`, team members can edit the input value normally.\n\nBy default, this key is `false` (i.e., team members can edit input values).\n\n## Examples\n\nIn this example, we have configured a datetime input to be disabled using a boolean value, preventing editors from modifying the automatically generated date.\n\n```yaml\n_inputs:\n  date_created:\n    type: datetime\n    label: Date of article creation\n    disabled: true\n    instance_value: NOW\n```",
           "markdownDescription": "This key represents a boolean value for the `disabled` key that toggles whether CloudCannon prevents editing of an input value.\n\nWhen set to `true`, CloudCannon prevents team members from editing the input value in the *Data Editor* or the sidebar of the *Visual Editor* or *Content Editor*. The input value is still displayed but cannot be modified outside of the *Source Editor*.\n\nWhen set to `false`, team members can edit the input value normally.\n\nBy default, this key is `false` (i.e., team members can edit input values).\n\n## Examples\n\nIn this example, we have configured a datetime input to be disabled using a boolean value, preventing editors from modifying the automatically generated date.\n\n```yaml\n_inputs:\n  date_created:\n    type: datetime\n    label: Date of article creation\n    disabled: true\n    instance_value: NOW\n```"
         },
         {
-          "title": "Query String",
           "type": "string",
+          "title": "Query String",
           "documented": true,
           "description": "This key represents a query string value for the `disabled` key that conditionally prevents editing of an input value based on another input's value.\n\nThe value is a string that references a sibling input key name. CloudCannon evaluates the referenced input's value to determine whether to disable this input.\n\nWhen the referenced input is truthy, CloudCannon disables this input. You can reverse this behavior by prefixing the string with `!`.\n\nFor reverse values in YAML files, the string should be wrapped in single or double quotation marks.\n\n## Examples\n\nIn this example, we have configured an input to be disabled when the `published` input is truthy.\n\n```yaml\n_inputs:\n  published:\n    type: checkbox\n    label: Published\n  edit_date:\n    type: datetime\n    label: Last edited\n    disabled: published\n```\n\nIn this example, we have configured an input to be disabled when the `published` input is falsy using the `!` prefix.\n\n```yaml\n_inputs:\n  published:\n    type: checkbox\n    label: Published\n  draft_notes:\n    type: textarea\n    label: Draft notes\n    disabled: '!published'\n```",
           "markdownDescription": "This key represents a query string value for the `disabled` key that conditionally prevents editing of an input value based on another input's value.\n\nThe value is a string that references a sibling input key name. CloudCannon evaluates the referenced input's value to determine whether to disable this input.\n\nWhen the referenced input is truthy, CloudCannon disables this input. You can reverse this behavior by prefixing the string with `!`.\n\nFor reverse values in YAML files, the string should be wrapped in single or double quotation marks.\n\n## Examples\n\nIn this example, we have configured an input to be disabled when the `published` input is truthy.\n\n```yaml\n_inputs:\n  published:\n    type: checkbox\n    label: Published\n  edit_date:\n    type: datetime\n    label: Last edited\n    disabled: published\n```\n\nIn this example, we have configured an input to be disabled when the `published` input is falsy using the `!` prefix.\n\n```yaml\n_inputs:\n  published:\n    type: checkbox\n    label: Published\n  draft_notes:\n    type: textarea\n    label: Draft notes\n    disabled: '!published'\n```"
@@ -4831,8 +4572,8 @@
       "markdownDescription": "This key defines a custom error message that explains why a value has failed the validation criteria from `options.required`.\n\nThis key requires you to define `options.required`.\n\nThis key has no default.\n\nThis key is available for Array, Code, Color, Date and Time, File, Number, Object, Select and Multiselect, Text, Rich Text, and URL Inputs.\n\n## Examples\n\nIn this example, we prompt our team to use enter an Input value using a required message.\n\n```yaml\n_inputs:\n  author:\n    type: text\n    comment: Enter the name of the author for this blog post.\n    options:\n      required: true\n      required_message: You are not allowed to leave this blank.\n```"
     },
     "type._inputs.*.options.empty_type(text)": {
-      "description": "This key defines how an 'empty' value will be saved. Does not apply to existing empty values.",
       "default": "null",
+      "description": "This key defines how an 'empty' value will be saved. Does not apply to existing empty values.",
       "type": "string",
       "enum": [
         "null",
@@ -4843,8 +4584,6 @@
       "markdownDescription": "This key defines how an 'empty' value will be saved. Does not apply to existing empty values."
     },
     "TextareaInput": {
-      "title": "Textarea Input",
-      "description": "This key defines an editing interface for plain text.\n\n## Examples\n\nIn this example, we have configured the `description` key as a *Textarea Input*.\n\n```yaml\n_inputs:\n  description:\n    type: textarea\n    label: Description\n```",
       "type": "object",
       "properties": {
         "comment": {
@@ -4889,15 +4628,14 @@
           "$ref": "#/definitions/type._inputs.*.cascade"
         },
         "type": {
-          "title": "Type",
-          "description": "This key defines the input type, which controls how this input appears and behaves.\n\n## Examples\n\nIn this example, we have configured the `description` key as a *Textarea Input* type.\n\n```yaml\n_inputs:\n  description:\n    type: textarea\n```",
           "type": "string",
           "const": "textarea",
+          "title": "Type",
+          "description": "This key defines the input type, which controls how this input appears and behaves.\n\n## Examples\n\nIn this example, we have configured the `description` key as a *Textarea Input* type.\n\n```yaml\n_inputs:\n  description:\n    type: textarea\n```",
           "documented": true,
           "markdownDescription": "This key defines the input type, which controls how this input appears and behaves.\n\n## Examples\n\nIn this example, we have configured the `description` key as a *Textarea Input* type.\n\n```yaml\n_inputs:\n  description:\n    type: textarea\n```"
         },
         "options": {
-          "description": "This key defines options that are specific to Textarea Inputs.\n\n## Examples\n\nIn this example, we have configured *Textarea Input* options including comment and character count.\n\n```yaml\n_inputs:\n  description:\n    type: textarea\n    options:\n      comment: Enter a description\n      show_count: true\n```",
           "type": "object",
           "properties": {
             "max_length": {
@@ -4980,6 +4718,7 @@
             }
           },
           "additionalProperties": false,
+          "description": "This key defines options that are specific to Textarea Inputs.\n\n## Examples\n\nIn this example, we have configured *Textarea Input* options including comment and character count.\n\n```yaml\n_inputs:\n  description:\n    type: textarea\n    options:\n      comment: Enter a description\n      show_count: true\n```",
           "documented": true,
           "title": "options",
           "markdownDescription": "This key defines options that are specific to Textarea Inputs.\n\n## Examples\n\nIn this example, we have configured *Textarea Input* options including comment and character count.\n\n```yaml\n_inputs:\n  description:\n    type: textarea\n    options:\n      comment: Enter a description\n      show_count: true\n```"
@@ -4989,12 +4728,12 @@
         "type"
       ],
       "additionalProperties": false,
+      "title": "Textarea Input",
+      "description": "This key defines an editing interface for plain text.\n\n## Examples\n\nIn this example, we have configured the `description` key as a *Textarea Input*.\n\n```yaml\n_inputs:\n  description:\n    type: textarea\n    label: Description\n```",
       "documented": true,
       "markdownDescription": "This key defines an editing interface for plain text.\n\n## Examples\n\nIn this example, we have configured the `description` key as a *Textarea Input*.\n\n```yaml\n_inputs:\n  description:\n    type: textarea\n    label: Description\n```"
     },
     "CodeInput": {
-      "title": "Code Input",
-      "description": "This key defines an editing interface for code or mono-spaced plain text content.",
       "type": "object",
       "properties": {
         "comment": {
@@ -5039,15 +4778,14 @@
           "$ref": "#/definitions/type._inputs.*.cascade"
         },
         "type": {
-          "title": "Type",
-          "description": "This key defines the input type, which controls how this input appears and behaves.",
           "type": "string",
           "const": "code",
+          "title": "Type",
+          "description": "This key defines the input type, which controls how this input appears and behaves.",
           "documented": true,
           "markdownDescription": "This key defines the input type, which controls how this input appears and behaves."
         },
         "options": {
-          "description": "This key defines options that are specific to Code Inputs.",
           "type": "object",
           "properties": {
             "tab_size": {
@@ -5176,6 +4914,7 @@
             }
           },
           "additionalProperties": false,
+          "description": "This key defines options that are specific to Code Inputs.",
           "documented": true,
           "title": "options",
           "markdownDescription": "This key defines options that are specific to Code Inputs."
@@ -5185,6 +4924,8 @@
         "type"
       ],
       "additionalProperties": false,
+      "title": "Code Input",
+      "description": "This key defines an editing interface for code or mono-spaced plain text content.",
       "documented": true,
       "markdownDescription": "This key defines an editing interface for code or mono-spaced plain text content."
     },
@@ -5221,8 +4962,6 @@
       "title": "theme(theme)"
     },
     "Syntax": {
-      "title": "Syntax",
-      "description": "Available syntax highlighting languages for code editors in CloudCannon.",
       "type": "string",
       "enum": [
         "c_cpp",
@@ -5294,12 +5033,12 @@
         "xquery",
         "yaml"
       ],
+      "title": "Syntax",
+      "description": "Available syntax highlighting languages for code editors in CloudCannon.",
       "documented": false,
       "markdownDescription": "Available syntax highlighting languages for code editors in CloudCannon."
     },
     "ColorInput": {
-      "title": "Color Input",
-      "description": "This key defines an editing interface for color values.",
       "type": "object",
       "properties": {
         "comment": {
@@ -5344,15 +5083,14 @@
           "$ref": "#/definitions/type._inputs.*.cascade"
         },
         "type": {
-          "title": "Type",
-          "description": "This key defines the input type, which controls how this input appears and behaves.",
           "type": "string",
           "const": "color",
+          "title": "Type",
+          "description": "This key defines the input type, which controls how this input appears and behaves.",
           "documented": true,
           "markdownDescription": "This key defines the input type, which controls how this input appears and behaves."
         },
         "options": {
-          "description": "This key defines options that are specific to Color Inputs.",
           "type": "object",
           "properties": {
             "max_length": {
@@ -5462,6 +5200,7 @@
             }
           },
           "additionalProperties": false,
+          "description": "This key defines options that are specific to Color Inputs.",
           "documented": true,
           "title": "options",
           "markdownDescription": "This key defines options that are specific to Color Inputs."
@@ -5471,12 +5210,12 @@
         "type"
       ],
       "additionalProperties": false,
+      "title": "Color Input",
+      "description": "This key defines an editing interface for color values.",
       "documented": true,
       "markdownDescription": "This key defines an editing interface for color values."
     },
     "BooleanInput": {
-      "title": "Boolean Input",
-      "description": "This key defines an editing interface for true or false values.\n\n## Examples\n\nIn this example, we have configured the `featured` key as a *Boolean Input*.\n\n```yaml\n_inputs:\n  featured:\n    type: switch\n    label: Featured\n```",
       "type": "object",
       "properties": {
         "comment": {
@@ -5521,13 +5260,13 @@
           "$ref": "#/definitions/type._inputs.*.cascade"
         },
         "type": {
-          "title": "Type",
-          "description": "This key defines the input type, which controls how this input appears and behaves.\n\n## Examples\n\nIn this example, we have configured the `featured` key as a *Boolean Input* type.\n\n```yaml\n_inputs:\n  featured:\n    type: switch\n```",
           "type": "string",
           "enum": [
             "checkbox",
             "switch"
           ],
+          "title": "Type",
+          "description": "This key defines the input type, which controls how this input appears and behaves.\n\n## Examples\n\nIn this example, we have configured the `featured` key as a *Boolean Input* type.\n\n```yaml\n_inputs:\n  featured:\n    type: switch\n```",
           "documented": true,
           "markdownDescription": "This key defines the input type, which controls how this input appears and behaves.\n\n## Examples\n\nIn this example, we have configured the `featured` key as a *Boolean Input* type.\n\n```yaml\n_inputs:\n  featured:\n    type: switch\n```"
         }
@@ -5536,12 +5275,12 @@
         "type"
       ],
       "additionalProperties": false,
+      "title": "Boolean Input",
+      "description": "This key defines an editing interface for true or false values.\n\n## Examples\n\nIn this example, we have configured the `featured` key as a *Boolean Input*.\n\n```yaml\n_inputs:\n  featured:\n    type: switch\n    label: Featured\n```",
       "documented": true,
       "markdownDescription": "This key defines an editing interface for true or false values.\n\n## Examples\n\nIn this example, we have configured the `featured` key as a *Boolean Input*.\n\n```yaml\n_inputs:\n  featured:\n    type: switch\n    label: Featured\n```"
     },
     "NumberInput": {
-      "title": "Number Input",
-      "description": "This key defines an editing interface for numeric values.\n\n## Examples\n\nIn this example, we have configured the `quantity` key as a *Number Input*.\n\n```yaml\n_inputs:\n  quantity:\n    type: number\n    label: Quantity\n```",
       "type": "object",
       "properties": {
         "comment": {
@@ -5586,15 +5325,14 @@
           "$ref": "#/definitions/type._inputs.*.cascade"
         },
         "type": {
-          "title": "Type",
-          "description": "This key defines the input type, which controls how this input appears and behaves.\n\n## Examples\n\nIn this example, we have configured the `quantity` key as a *Number Input* type.\n\n```yaml\n_inputs:\n  quantity:\n    type: number\n```",
           "type": "string",
           "const": "number",
+          "title": "Type",
+          "description": "This key defines the input type, which controls how this input appears and behaves.\n\n## Examples\n\nIn this example, we have configured the `quantity` key as a *Number Input* type.\n\n```yaml\n_inputs:\n  quantity:\n    type: number\n```",
           "documented": true,
           "markdownDescription": "This key defines the input type, which controls how this input appears and behaves.\n\n## Examples\n\nIn this example, we have configured the `quantity` key as a *Number Input* type.\n\n```yaml\n_inputs:\n  quantity:\n    type: number\n```"
         },
         "options": {
-          "description": "This key defines options that are specific to Number Inputs.\n\n## Examples\n\nIn this example, we have configured *Number Input* options including min and max values.\n\n```yaml\n_inputs:\n  quantity:\n    type: number\n    options:\n      min: 1\n      max: 100\n```",
           "type": "object",
           "properties": {
             "required": {
@@ -5641,6 +5379,7 @@
             }
           },
           "additionalProperties": false,
+          "description": "This key defines options that are specific to Number Inputs.\n\n## Examples\n\nIn this example, we have configured *Number Input* options including min and max values.\n\n```yaml\n_inputs:\n  quantity:\n    type: number\n    options:\n      min: 1\n      max: 100\n```",
           "documented": true,
           "title": "options",
           "markdownDescription": "This key defines options that are specific to Number Inputs.\n\n## Examples\n\nIn this example, we have configured *Number Input* options including min and max values.\n\n```yaml\n_inputs:\n  quantity:\n    type: number\n    options:\n      min: 1\n      max: 100\n```"
@@ -5650,12 +5389,14 @@
         "type"
       ],
       "additionalProperties": false,
+      "title": "Number Input",
+      "description": "This key defines an editing interface for numeric values.\n\n## Examples\n\nIn this example, we have configured the `quantity` key as a *Number Input*.\n\n```yaml\n_inputs:\n  quantity:\n    type: number\n    label: Quantity\n```",
       "documented": true,
       "markdownDescription": "This key defines an editing interface for numeric values.\n\n## Examples\n\nIn this example, we have configured the `quantity` key as a *Number Input*.\n\n```yaml\n_inputs:\n  quantity:\n    type: number\n    label: Quantity\n```"
     },
     "type._inputs.*.options.empty_type(number)": {
-      "description": "This key defines how an 'empty' value will be saved. Does not apply to existing empty values.\n\n## Examples\n\nIn this example, we have configured how empty number values will be saved.\n\n```yaml\n_inputs:\n  quantity:\n    type: number\n    options:\n      empty_type: number\n```",
       "default": "null",
+      "description": "This key defines how an 'empty' value will be saved. Does not apply to existing empty values.\n\n## Examples\n\nIn this example, we have configured how empty number values will be saved.\n\n```yaml\n_inputs:\n  quantity:\n    type: number\n    options:\n      empty_type: number\n```",
       "type": "string",
       "enum": [
         "null",
@@ -5666,15 +5407,15 @@
       "markdownDescription": "This key defines how an 'empty' value will be saved. Does not apply to existing empty values.\n\n## Examples\n\nIn this example, we have configured how empty number values will be saved.\n\n```yaml\n_inputs:\n  quantity:\n    type: number\n    options:\n      empty_type: number\n```"
     },
     "type._inputs.*.options.min": {
-      "description": "This key defines the minimum numerical value CloudCannon will allow in an Input.\n\nWhen configured, CloudCannon will prevent you from entering a lesser numerical value.\n\nIf the Input already contains a lesser numerical value, CloudCannon will require you to enter a valid value to save your changes, or discard your\nunsaved changes.\n\nThis key is required for `range` inputs.\n\nValue can be any number.\n\nIf `options.max` is also configured, this key cannot be a greater number.\n\nThis key has no default.\n\nThis key is available for Number Inputs.\n\n## Examples\n\nIn this example, we want to add a rating out of five for each article in our travel blog using the `rating` Input. This Input limits you to a minimum rating of one.\n\n```yaml\n_inputs:\n  rating:\n    type: number\n    comment: How highly did you rate this experience?\n    options:\n      max: 5\n      min: 1\n```",
       "type": "number",
+      "description": "This key defines the minimum numerical value CloudCannon will allow in an Input.\n\nWhen configured, CloudCannon will prevent you from entering a lesser numerical value.\n\nIf the Input already contains a lesser numerical value, CloudCannon will require you to enter a valid value to save your changes, or discard your\nunsaved changes.\n\nThis key is required for `range` inputs.\n\nValue can be any number.\n\nIf `options.max` is also configured, this key cannot be a greater number.\n\nThis key has no default.\n\nThis key is available for Number Inputs.\n\n## Examples\n\nIn this example, we want to add a rating out of five for each article in our travel blog using the `rating` Input. This Input limits you to a minimum rating of one.\n\n```yaml\n_inputs:\n  rating:\n    type: number\n    comment: How highly did you rate this experience?\n    options:\n      max: 5\n      min: 1\n```",
       "documented": true,
       "title": "min",
       "markdownDescription": "This key defines the minimum numerical value CloudCannon will allow in an Input.\n\nWhen configured, CloudCannon will prevent you from entering a lesser numerical value.\n\nIf the Input already contains a lesser numerical value, CloudCannon will require you to enter a valid value to save your changes, or discard your\nunsaved changes.\n\nThis key is required for `range` inputs.\n\nValue can be any number.\n\nIf `options.max` is also configured, this key cannot be a greater number.\n\nThis key has no default.\n\nThis key is available for Number Inputs.\n\n## Examples\n\nIn this example, we want to add a rating out of five for each article in our travel blog using the `rating` Input. This Input limits you to a minimum rating of one.\n\n```yaml\n_inputs:\n  rating:\n    type: number\n    comment: How highly did you rate this experience?\n    options:\n      max: 5\n      min: 1\n```"
     },
     "type._inputs.*.options.max": {
-      "description": "This key defines the maximum numerical value CloudCannon will allow in an Input.\n\nWhen configured, CloudCannon will prevent you from entering a greater numerical value.\n\nIf the Input already contains a greater numerical value, CloudCannon will require you to enter a valid value to save your changes, or discard your\nunsaved changes.\n\nThis key is required for `range` inputs.\n\nValue can be any integer.\n\nIf `options.min` is also configured, this key cannot be a lesser number.\n\nThis key has no default.\n\nThis key is available for Number Inputs.\n\n## Examples\n\nIn this example, we want to add a rating out of five for each article in our travel blog using the `rating` Input. This Input limits you to a maximum rating of five.\n\n```yaml\n_inputs:\n  rating:\n    type: number\n    comment: How highly did you rate this experience?\n    options:\n      max: 5\n      min: 1\n```",
       "type": "number",
+      "description": "This key defines the maximum numerical value CloudCannon will allow in an Input.\n\nWhen configured, CloudCannon will prevent you from entering a greater numerical value.\n\nIf the Input already contains a greater numerical value, CloudCannon will require you to enter a valid value to save your changes, or discard your\nunsaved changes.\n\nThis key is required for `range` inputs.\n\nValue can be any integer.\n\nIf `options.min` is also configured, this key cannot be a lesser number.\n\nThis key has no default.\n\nThis key is available for Number Inputs.\n\n## Examples\n\nIn this example, we want to add a rating out of five for each article in our travel blog using the `rating` Input. This Input limits you to a maximum rating of five.\n\n```yaml\n_inputs:\n  rating:\n    type: number\n    comment: How highly did you rate this experience?\n    options:\n      max: 5\n      min: 1\n```",
       "documented": true,
       "title": "max",
       "markdownDescription": "This key defines the maximum numerical value CloudCannon will allow in an Input.\n\nWhen configured, CloudCannon will prevent you from entering a greater numerical value.\n\nIf the Input already contains a greater numerical value, CloudCannon will require you to enter a valid value to save your changes, or discard your\nunsaved changes.\n\nThis key is required for `range` inputs.\n\nValue can be any integer.\n\nIf `options.min` is also configured, this key cannot be a lesser number.\n\nThis key has no default.\n\nThis key is available for Number Inputs.\n\n## Examples\n\nIn this example, we want to add a rating out of five for each article in our travel blog using the `rating` Input. This Input limits you to a maximum rating of five.\n\n```yaml\n_inputs:\n  rating:\n    type: number\n    comment: How highly did you rate this experience?\n    options:\n      max: 5\n      min: 1\n```"
@@ -5701,8 +5442,6 @@
       "markdownDescription": "This key defines a custom error message that explains why a value has failed the validation criteria from `options.max`.\nThis key requires you to define `options.max`.\n\nThis key has no default.\n\nThis key is available for Number Inputs.\n\n## Examples\n\nIn this example, we prompt our team to enter a valid number using a custom message.\n\n```yaml\n_inputs:\n  rating:\n    type: number\n    comment: How highly did you rate this experience?\n    options:\n      max: 5\n      max_message: Cannot be more than 5\n      min: 1\n      min_message: Cannot be less than 1\n```"
     },
     "RangeInput": {
-      "title": "Range Input",
-      "description": "This key defines a slider interface for selecting a numeric value.",
       "type": "object",
       "properties": {
         "comment": {
@@ -5747,15 +5486,14 @@
           "$ref": "#/definitions/type._inputs.*.cascade"
         },
         "type": {
-          "title": "Type",
-          "description": "This key defines the input type, which controls how this input appears and behaves.",
           "type": "string",
           "const": "range",
+          "title": "Type",
+          "description": "This key defines the input type, which controls how this input appears and behaves.",
           "documented": true,
           "markdownDescription": "This key defines the input type, which controls how this input appears and behaves."
         },
         "options": {
-          "description": "This key defines options that are specific to Range Inputs.",
           "type": "object",
           "properties": {
             "required": {
@@ -5794,6 +5532,7 @@
             "max"
           ],
           "additionalProperties": false,
+          "description": "This key defines options that are specific to Range Inputs.",
           "documented": true,
           "title": "options",
           "markdownDescription": "This key defines options that are specific to Range Inputs."
@@ -5803,12 +5542,12 @@
         "type"
       ],
       "additionalProperties": false,
+      "title": "Range Input",
+      "description": "This key defines a slider interface for selecting a numeric value.",
       "documented": true,
       "markdownDescription": "This key defines a slider interface for selecting a numeric value."
     },
     "RichTextInput": {
-      "title": "Rich Text Input",
-      "description": "This key defines an editing interface for HTML markup content.",
       "type": "object",
       "properties": {
         "comment": {
@@ -5853,18 +5592,17 @@
           "$ref": "#/definitions/type._inputs.*.cascade"
         },
         "type": {
-          "title": "Type",
-          "description": "This key defines the input type, which controls how this input appears and behaves.",
           "type": "string",
           "enum": [
             "html",
             "markdown"
           ],
+          "title": "Type",
+          "description": "This key defines the input type, which controls how this input appears and behaves.",
           "documented": true,
           "markdownDescription": "This key defines the input type, which controls how this input appears and behaves."
         },
         "options": {
-          "description": "This key defines options that are specific to Rich Text Inputs.",
           "type": "object",
           "properties": {
             "mime_type": {
@@ -6070,11 +5808,11 @@
             },
             "allow_resize": {
               "deprecated": true,
-              "description": "**⚠️ DEPRECATED:** This key is deprecated. Use `preview_resize` instead.\nThis key toggles whether CloudCannon will show the resize handler to vertically resize the input.\n\nSetting this key to `false` will hide the resize handler.\n\nBy default, this key is `true` (i.e., the resize handler is shown).",
               "type": "boolean",
               "documented": true,
               "title": "allow_resize",
-              "markdownDescription": "**⚠️ DEPRECATED:** This key is deprecated. Use `preview_resize` instead.\nThis key toggles whether CloudCannon will show the resize handler to vertically resize the input.\n\nSetting this key to `false` will hide the resize handler.\n\nBy default, this key is `true` (i.e., the resize handler is shown)."
+              "description": "This key is deprecated. Use `preview_resize` instead.\n\nThis key toggles whether CloudCannon will show the resize handler to vertically resize the input.\n\nSetting this key to `false` will hide the resize handler.\n\nBy default, this key is `true` (i.e., the resize handler is shown).",
+              "markdownDescription": "This key is deprecated. Use `preview_resize` instead.\n\nThis key toggles whether CloudCannon will show the resize handler to vertically resize the input.\n\nSetting this key to `false` will hide the resize handler.\n\nBy default, this key is `true` (i.e., the resize handler is shown)."
             },
             "prevent_resize": {
               "description": "Shows or hides the resize handler to vertically resize the input.",
@@ -6093,6 +5831,7 @@
             }
           },
           "additionalProperties": false,
+          "description": "This key defines options that are specific to Rich Text Inputs.",
           "documented": true,
           "title": "options",
           "markdownDescription": "This key defines options that are specific to Rich Text Inputs."
@@ -6102,6 +5841,8 @@
         "type"
       ],
       "additionalProperties": false,
+      "title": "Rich Text Input",
+      "description": "This key defines an editing interface for HTML markup content.",
       "documented": true,
       "markdownDescription": "This key defines an editing interface for HTML markup content."
     },
@@ -6191,8 +5932,8 @@
         "type": "object",
         "properties": {
           "size": {
-            "description": "This key defines a number suffixed with \"x\" (relative size) or \"w\" (fixed width) for setting the dimensions of the image (e.g. 2x, 3x, 100w, 360w).\n\n## Examples\n\nIn this example, we have configured a size definition for an *Image Input* to create a 2x relative size image.\n\n```yaml\n_inputs:\n  hero_image:\n    type: image\n    options:\n      sizes:\n        - size: 2x\n```",
             "type": "string",
+            "description": "This key defines a number suffixed with \"x\" (relative size) or \"w\" (fixed width) for setting the dimensions of the image (e.g. 2x, 3x, 100w, 360w).\n\n## Examples\n\nIn this example, we have configured a size definition for an *Image Input* to create a 2x relative size image.\n\n```yaml\n_inputs:\n  hero_image:\n    type: image\n    options:\n      sizes:\n        - size: 2x\n```",
             "documented": true,
             "title": "size",
             "markdownDescription": "This key defines a number suffixed with \"x\" (relative size) or \"w\" (fixed width) for setting the dimensions of the image (e.g. 2x, 3x, 100w, 360w).\n\n## Examples\n\nIn this example, we have configured a size definition for an *Image Input* to create a 2x relative size image.\n\n```yaml\n_inputs:\n  hero_image:\n    type: image\n    options:\n      sizes:\n        - size: 2x\n```"
@@ -6218,7 +5959,6 @@
       "markdownDescription": "This key defines definitions for creating additional images of different sizes when uploading or selecting existing files.\n\n## Examples\n\nIn this example, we have configured an *Image Input* to create additional images of different sizes when uploading or selecting files.\n\n```yaml\n_inputs:\n  hero_image:\n    type: image\n    options:\n      sizes:\n        - size: 2x\n        - size: 3x\n```"
     },
     "type.paths": {
-      "title": "Paths",
       "type": "object",
       "properties": {
         "static": {
@@ -6244,6 +5984,7 @@
         }
       },
       "additionalProperties": false,
+      "title": "Paths",
       "documented": true,
       "description": "This key defines paths for your Rich Text editors or File inputs.\n\nIf undefined at higher levels of the [configuration cascade](https://cloudcannon.com/documentation/articles/using-the-configuration-cascade/), `paths` will default to any\nvalues configured in the [CloudCannon configuration file](https://cloudcannon.com/documentation/articles/what-is-the-cloudcannon-configuration-file/).\n\n## Examples\n\nIn this example, we have configured paths for the `blog` Collection to set custom upload and static paths.\n\n```yaml\ncollections_config:\n  blog:\n    paths:\n      uploads: /uploads/blog/\n      static: /assets/\n```",
       "markdownDescription": "This key defines paths for your Rich Text editors or File inputs.\n\nIf undefined at higher levels of the [configuration cascade](https://cloudcannon.com/documentation/articles/using-the-configuration-cascade/), `paths` will default to any\nvalues configured in the [CloudCannon configuration file](https://cloudcannon.com/documentation/articles/what-is-the-cloudcannon-configuration-file/).\n\n## Examples\n\nIn this example, we have configured paths for the `blog` Collection to set custom upload and static paths.\n\n```yaml\ncollections_config:\n  blog:\n    paths:\n      uploads: /uploads/blog/\n      static: /assets/\n```"
@@ -6565,8 +6306,6 @@
       "markdownDescription": "This key toggles whether CloudCannon will display a tool in your WYSIWYG toolbar to merge a list item with the item below it in an ordered or unordered list.\n\nSetting this key to `true` will enable a tool in your WYSIWYG toolbar to merge a list item with the item below it."
     },
     "DateInput": {
-      "title": "Date/Datetime Input",
-      "description": "This key defines an editing interface for date and/or time values.",
       "type": "object",
       "properties": {
         "comment": {
@@ -6611,18 +6350,17 @@
           "$ref": "#/definitions/type._inputs.*.cascade"
         },
         "type": {
-          "title": "Type",
-          "description": "This key defines the input type, which controls how this input appears and behaves.",
           "type": "string",
           "enum": [
             "date",
             "datetime"
           ],
+          "title": "Type",
+          "description": "This key defines the input type, which controls how this input appears and behaves.",
           "documented": true,
           "markdownDescription": "This key defines the input type, which controls how this input appears and behaves."
         },
         "options": {
-          "description": "This key defines options that are specific to Date Inputs.",
           "type": "object",
           "properties": {
             "required": {
@@ -6655,10 +6393,10 @@
               "description": "This key defines the earliest date and time, inclusive, that CloudCannon will allow in an Input.\n\nWhen configured, CloudCannon will prevent you from selecting an earlier date and time.\n\nIf the Input already contains an earlier date and time, CloudCannon will require you to change it to a valid value to save your changes, or discard\nyour unsaved changes.\n\nValue must be in [ISO8601](https://www.iso.org/iso-8601-date-and-time-format.html) format.\n\nThe value can have quotation marks or no quotation marks.\n\nIf `options.end_before` is also configured, this key cannot be a later date and time.\n\nThis key has no default.\n\nThis key is available for Date and Time Inputs.\n\n## Examples\n\nIn this example, we want our team to enter the date and time of an event in the `2022_event` Input. This Input will only allow dates on or after January 1st, 2022.\n\n```yaml\n_inputs:\n  2022_event:\n    type: datetime\n    options:\n      start_from: 2022-01-01T00:00:00Z\n      end_before: 2023-01-01T00:00:00Z\n```",
               "anyOf": [
                 {
-                  "title": "String Start From",
                   "type": "string",
                   "format": "date-time",
                   "pattern": "^(?:(?:\\d\\d[2468][048]|\\d\\d[13579][26]|\\d\\d0[48]|[02468][048]00|[13579][26]00)-02-29|\\d{4}-(?:(?:0[13578]|1[02])-(?:0[1-9]|[12]\\d|3[01])|(?:0[469]|11)-(?:0[1-9]|[12]\\d|30)|(?:02)-(?:0[1-9]|1\\d|2[0-8])))T(?:(?:[01]\\d|2[0-3]):[0-5]\\d(?::[0-5]\\d(?:\\.\\d+)?)?(?:Z||([+-](?:[01]\\d|2[0-3]):[0-5]\\d)))$",
+                  "title": "String Start From",
                   "documented": true,
                   "description": "This key defines the earliest date and time, inclusive, that CloudCannon will allow in an Input.\n\nWhen configured, CloudCannon will prevent you from selecting an earlier date and time.\n\nIf the Input already contains an earlier date and time, CloudCannon will require you to change it to a valid value to save your changes, or discard\nyour unsaved changes.\n\nValue must be in [ISO8601](https://www.iso.org/iso-8601-date-and-time-format.html) format and should be in quotes.\n\nIf `options.end_before` is also configured, this key cannot be a later date and time.\n\nThis key has no default.\n\nThis key is available for Date and Time Inputs.",
                   "markdownDescription": "This key defines the earliest date and time, inclusive, that CloudCannon will allow in an Input.\n\nWhen configured, CloudCannon will prevent you from selecting an earlier date and time.\n\nIf the Input already contains an earlier date and time, CloudCannon will require you to change it to a valid value to save your changes, or discard\nyour unsaved changes.\n\nValue must be in [ISO8601](https://www.iso.org/iso-8601-date-and-time-format.html) format and should be in quotes.\n\nIf `options.end_before` is also configured, this key cannot be a later date and time.\n\nThis key has no default.\n\nThis key is available for Date and Time Inputs."
@@ -6685,10 +6423,10 @@
               "description": "This key defines the date and time, exclusive, that CloudCannon will allow in an Input.\n\nWhen configured, CloudCannon will prevent you from selecting a later date and time.\n\nIf the Input already contains a later date and time, CloudCannon will require you to change it to a valid value to save your changes, or discard your\nunsaved changes.\n\nValue must be in [ISO8601](https://www.iso.org/iso-8601-date-and-time-format.html) format.\n\nThe value can have quotation marks or no quotation marks.\n\nIf `options.start_from` is also configured, this key cannot be an earlier date and time.\n\nThis key has no default.\n\nThis key is available for Date and Time Inputs.\n\n## Examples\n\nIn this example, we want our team to enter the date and time of an event in the `2022_event` Input. This Input will only allow dates before January 1st, 2023.\n\n```yaml\n_inputs:\n  2022_event:\n    type: datetime\n    options:\n      start_from: 2022-01-01T00:00:00Z\n      end_before: 2023-01-01T00:00:00Z\n```",
               "anyOf": [
                 {
-                  "title": "String End Before",
                   "type": "string",
                   "format": "date-time",
                   "pattern": "^(?:(?:\\d\\d[2468][048]|\\d\\d[13579][26]|\\d\\d0[48]|[02468][048]00|[13579][26]00)-02-29|\\d{4}-(?:(?:0[13578]|1[02])-(?:0[1-9]|[12]\\d|3[01])|(?:0[469]|11)-(?:0[1-9]|[12]\\d|30)|(?:02)-(?:0[1-9]|1\\d|2[0-8])))T(?:(?:[01]\\d|2[0-3]):[0-5]\\d(?::[0-5]\\d(?:\\.\\d+)?)?(?:Z||([+-](?:[01]\\d|2[0-3]):[0-5]\\d)))$",
+                  "title": "String End Before",
                   "documented": true,
                   "description": "This key defines the date and time, exclusive, that CloudCannon will allow in an Input.\n\nWhen configured, CloudCannon will prevent you from selecting a later date and time.\n\nIf the Input already contains a later date and time, CloudCannon will require you to change it to a valid value to save your changes, or discard your\nunsaved changes.\n\nValue must be in [ISO8601](https://www.iso.org/iso-8601-date-and-time-format.html) format.\n\nIf `options.start_from` is also configured, this key cannot be an earlier date and time.\n\nThis key has no default.\n\nThis key is available for Date and Time Inputs.",
                   "markdownDescription": "This key defines the date and time, exclusive, that CloudCannon will allow in an Input.\n\nWhen configured, CloudCannon will prevent you from selecting a later date and time.\n\nIf the Input already contains a later date and time, CloudCannon will require you to change it to a valid value to save your changes, or discard your\nunsaved changes.\n\nValue must be in [ISO8601](https://www.iso.org/iso-8601-date-and-time-format.html) format.\n\nIf `options.start_from` is also configured, this key cannot be an earlier date and time.\n\nThis key has no default.\n\nThis key is available for Date and Time Inputs."
@@ -6713,6 +6451,7 @@
             }
           },
           "additionalProperties": false,
+          "description": "This key defines options that are specific to Date Inputs.",
           "documented": true,
           "title": "options",
           "markdownDescription": "This key defines options that are specific to Date Inputs."
@@ -6722,11 +6461,12 @@
         "type"
       ],
       "additionalProperties": false,
+      "title": "Date/Datetime Input",
+      "description": "This key defines an editing interface for date and/or time values.",
       "documented": true,
       "markdownDescription": "This key defines an editing interface for date and/or time values."
     },
     "type.timezone": {
-      "title": "Timezone",
       "type": "string",
       "enum": [
         "Africa/Abidjan",
@@ -7325,13 +7065,12 @@
         "WET",
         "Zulu"
       ],
+      "title": "Timezone",
       "documented": true,
       "description": "This key defines the timezone for your Site.\n\nValue must be in IANA timezone format.\n\nFor more information, please read our documentation on [Date and Time inputs](https://cloudcannon.com/documentation/articles/what-are-date-and-time-inputs/).",
       "markdownDescription": "This key defines the timezone for your Site.\n\nValue must be in IANA timezone format.\n\nFor more information, please read our documentation on [Date and Time inputs](https://cloudcannon.com/documentation/articles/what-are-date-and-time-inputs/)."
     },
     "TimeInput": {
-      "title": "Time Input",
-      "description": "This key defines an editing interface for time values only.",
       "type": "object",
       "properties": {
         "comment": {
@@ -7376,15 +7115,14 @@
           "$ref": "#/definitions/type._inputs.*.cascade"
         },
         "type": {
-          "title": "Type",
-          "description": "This key defines the input type, which controls how this input appears and behaves.",
           "type": "string",
           "const": "time",
+          "title": "Type",
+          "description": "This key defines the input type, which controls how this input appears and behaves.",
           "documented": true,
           "markdownDescription": "This key defines the input type, which controls how this input appears and behaves."
         },
         "options": {
-          "description": "This key defines options that are specific to Time Inputs.",
           "type": "object",
           "properties": {
             "required": {
@@ -7404,6 +7142,7 @@
             }
           },
           "additionalProperties": false,
+          "description": "This key defines options that are specific to Time Inputs.",
           "documented": true,
           "title": "options",
           "markdownDescription": "This key defines options that are specific to Time Inputs."
@@ -7413,12 +7152,12 @@
         "type"
       ],
       "additionalProperties": false,
+      "title": "Time Input",
+      "description": "This key defines an editing interface for time values only.",
       "documented": true,
       "markdownDescription": "This key defines an editing interface for time values only."
     },
     "FileInput": {
-      "title": "File Input",
-      "description": "This key defines an editing interface for uploading files to your repository or DAM and browsing existing assets.",
       "type": "object",
       "properties": {
         "comment": {
@@ -7463,19 +7202,18 @@
           "$ref": "#/definitions/type._inputs.*.cascade"
         },
         "type": {
-          "title": "Type",
-          "description": "This key defines the input type, which controls how this input appears and behaves.",
           "type": "string",
           "enum": [
             "file",
             "document",
             "image"
           ],
+          "title": "Type",
+          "description": "This key defines the input type, which controls how this input appears and behaves.",
           "documented": true,
           "markdownDescription": "This key defines the input type, which controls how this input appears and behaves."
         },
         "options": {
-          "description": "This key defines options that are specific to File Inputs.",
           "type": "object",
           "properties": {
             "mime_type": {
@@ -7597,6 +7335,7 @@
             }
           },
           "additionalProperties": false,
+          "description": "This key defines options that are specific to File Inputs.",
           "documented": true,
           "title": "options",
           "markdownDescription": "This key defines options that are specific to File Inputs."
@@ -7606,6 +7345,8 @@
         "type"
       ],
       "additionalProperties": false,
+      "title": "File Input",
+      "description": "This key defines an editing interface for uploading files to your repository or DAM and browsing existing assets.",
       "documented": true,
       "markdownDescription": "This key defines an editing interface for uploading files to your repository or DAM and browsing existing assets."
     },
@@ -7613,18 +7354,18 @@
       "description": "This key defines which file types are available to select or upload to this input.\n\nAccepted format is an array or comma-separated string of MIME types.\n\nThe special value \"*\" means any type is accepted.\n\n## Examples\n\nIn this example, we have configured a *Image Input* to accept only JPEG or PNG files.\n\n```yaml\n_inputs:\n  featured_image:\n    type: image\n    options:\n      accepts_mime_types:\n        - image/jpeg\n        - image/png\n```",
       "anyOf": [
         {
-          "title": "Comma Separated Accepts Mime Types",
           "type": "string",
+          "title": "Comma Separated Accepts Mime Types",
           "documented": true,
           "description": "This key represents a comma-separated string format for the `accepts_mime_types` key that restricts which file types are available to select or upload in *File Inputs*.\n\nThe value is a string containing MIME types separated by commas. Each MIME type specifies a file type that CloudCannon will allow for this input.\n\nAvailable MIME types include image formats (`image/x-icon`, `image/gif`, `image/jpeg`, `image/png`, `image/webp`, `image/bmp`, `image/svg+xml`) and document formats (`application/pdf`, `application/msword`, `application/vnd.openxmlformats-officedocument.wordprocessingml.document`, `application/vnd.ms-excel`, `application/vnd.openxmlformats-officedocument.spreadsheetml.sheet`, `application/vnd.ms-powerpoint`, `application/vnd.openxmlformats-officedocument.presentationml.presentation`).\n\nUse the comma-separated format when you prefer a more compact configuration or when working with a small number of MIME types.\n\nThe special value `\"*\"` means any file type is accepted.\n\n## Examples\n\nIn this example, we have configured a *File Input* to accept only image files using a comma-separated string of image MIME types.\n\n```yaml\n_inputs:\n  hero_image:\n    type: file\n    label: Hero Image\n    options:\n      accepts_mime_types: 'image/jpeg,image/png,image/webp'\n```\n\nIn this example, we have configured a *File Input* to accept only document files using a comma-separated string of document MIME types.\n\n```yaml\n_inputs:\n  document:\n    type: file\n    label: Document\n    options:\n      accepts_mime_types: 'application/pdf,application/msword'\n```\n\nIn this example, we have configured a *File Input* to accept any file type using the special `\"*\"` value.\n\n```yaml\n_inputs:\n  any_file:\n    type: file\n    label: Any File\n    options:\n      accepts_mime_types: '*'\n```",
           "markdownDescription": "This key represents a comma-separated string format for the `accepts_mime_types` key that restricts which file types are available to select or upload in *File Inputs*.\n\nThe value is a string containing MIME types separated by commas. Each MIME type specifies a file type that CloudCannon will allow for this input.\n\nAvailable MIME types include image formats (`image/x-icon`, `image/gif`, `image/jpeg`, `image/png`, `image/webp`, `image/bmp`, `image/svg+xml`) and document formats (`application/pdf`, `application/msword`, `application/vnd.openxmlformats-officedocument.wordprocessingml.document`, `application/vnd.ms-excel`, `application/vnd.openxmlformats-officedocument.spreadsheetml.sheet`, `application/vnd.ms-powerpoint`, `application/vnd.openxmlformats-officedocument.presentationml.presentation`).\n\nUse the comma-separated format when you prefer a more compact configuration or when working with a small number of MIME types.\n\nThe special value `\"*\"` means any file type is accepted.\n\n## Examples\n\nIn this example, we have configured a *File Input* to accept only image files using a comma-separated string of image MIME types.\n\n```yaml\n_inputs:\n  hero_image:\n    type: file\n    label: Hero Image\n    options:\n      accepts_mime_types: 'image/jpeg,image/png,image/webp'\n```\n\nIn this example, we have configured a *File Input* to accept only document files using a comma-separated string of document MIME types.\n\n```yaml\n_inputs:\n  document:\n    type: file\n    label: Document\n    options:\n      accepts_mime_types: 'application/pdf,application/msword'\n```\n\nIn this example, we have configured a *File Input* to accept any file type using the special `\"*\"` value.\n\n```yaml\n_inputs:\n  any_file:\n    type: file\n    label: Any File\n    options:\n      accepts_mime_types: '*'\n```"
         },
         {
-          "title": "Array Accepts Mime Types",
           "type": "array",
           "items": {
             "$ref": "#/definitions/MimeType"
           },
+          "title": "Array Accepts Mime Types",
           "documented": true,
           "description": "This key represents an array format for the `accepts_mime_types` key that restricts which file types are available to select or upload in *File Inputs*.\n\nThe value is an array of MIME type strings. Each string specifies a file type that CloudCannon will allow for this input.\n\nAvailable MIME types include image formats (`image/x-icon`, `image/gif`, `image/jpeg`, `image/png`, `image/webp`, `image/bmp`, `image/svg+xml`) and document formats (`application/pdf`, `application/msword`, `application/vnd.openxmlformats-officedocument.wordprocessingml.document`, `application/vnd.ms-excel`, `application/vnd.openxmlformats-officedocument.spreadsheetml.sheet`, `application/vnd.ms-powerpoint`, `application/vnd.openxmlformats-officedocument.presentationml.presentation`).\n\nUse the array format when you want to explicitly list multiple MIME types, making it easier to read and maintain in your configuration.\n\n## Examples\n\nIn this example, we have configured a *File Input* to accept only image files using an array of image MIME types.\n\n```yaml\n_inputs:\n  hero_image:\n    type: file\n    label: Hero Image\n    options:\n      accepts_mime_types:\n        - image/jpeg\n        - image/png\n        - image/webp\n```\n\nIn this example, we have configured a *File Input* to accept only document files using an array of document MIME types.\n\n```yaml\n_inputs:\n  document:\n    type: file\n    label: Document\n    options:\n      accepts_mime_types:\n        - application/pdf\n        - application/msword\n        - application/vnd.openxmlformats-officedocument.wordprocessingml.document\n```",
           "markdownDescription": "This key represents an array format for the `accepts_mime_types` key that restricts which file types are available to select or upload in *File Inputs*.\n\nThe value is an array of MIME type strings. Each string specifies a file type that CloudCannon will allow for this input.\n\nAvailable MIME types include image formats (`image/x-icon`, `image/gif`, `image/jpeg`, `image/png`, `image/webp`, `image/bmp`, `image/svg+xml`) and document formats (`application/pdf`, `application/msword`, `application/vnd.openxmlformats-officedocument.wordprocessingml.document`, `application/vnd.ms-excel`, `application/vnd.openxmlformats-officedocument.spreadsheetml.sheet`, `application/vnd.ms-powerpoint`, `application/vnd.openxmlformats-officedocument.presentationml.presentation`).\n\nUse the array format when you want to explicitly list multiple MIME types, making it easier to read and maintain in your configuration.\n\n## Examples\n\nIn this example, we have configured a *File Input* to accept only image files using an array of image MIME types.\n\n```yaml\n_inputs:\n  hero_image:\n    type: file\n    label: Hero Image\n    options:\n      accepts_mime_types:\n        - image/jpeg\n        - image/png\n        - image/webp\n```\n\nIn this example, we have configured a *File Input* to accept only document files using an array of document MIME types.\n\n```yaml\n_inputs:\n  document:\n    type: file\n    label: Document\n    options:\n      accepts_mime_types:\n        - application/pdf\n        - application/msword\n        - application/vnd.openxmlformats-officedocument.wordprocessingml.document\n```"
@@ -7635,8 +7376,6 @@
       "markdownDescription": "This key defines which file types are available to select or upload to this input.\n\nAccepted format is an array or comma-separated string of MIME types.\n\nThe special value \"*\" means any type is accepted.\n\n## Examples\n\nIn this example, we have configured a *Image Input* to accept only JPEG or PNG files.\n\n```yaml\n_inputs:\n  featured_image:\n    type: image\n    options:\n      accepts_mime_types:\n        - image/jpeg\n        - image/png\n```"
     },
     "MimeType": {
-      "title": "Mime Type",
-      "description": "This key represents an array format for the `accepts_mime_types` key that restricts which file types are available to select or upload in *File Inputs*.\n\nThe value is an array of MIME type strings. Each string specifies a file type that CloudCannon will allow for this input.\n\nAvailable MIME types include image formats (`image/x-icon`, `image/gif`, `image/jpeg`, `image/png`, `image/webp`, `image/bmp`, `image/svg+xml`) and document formats (`application/pdf`, `application/msword`, `application/vnd.openxmlformats-officedocument.wordprocessingml.document`, `application/vnd.ms-excel`, `application/vnd.openxmlformats-officedocument.spreadsheetml.sheet`, `application/vnd.ms-powerpoint`, `application/vnd.openxmlformats-officedocument.presentationml.presentation`).\n\nUse the array format when you want to explicitly list multiple MIME types, making it easier to read and maintain in your configuration.\n\n## Examples\n\nIn this example, we have configured a *File Input* to accept only image files using an array of image MIME types.\n\n```yaml\n_inputs:\n  hero_image:\n    type: file\n    label: Hero Image\n    options:\n      accepts_mime_types:\n        - image/jpeg\n        - image/png\n        - image/webp\n```\n\nIn this example, we have configured a *File Input* to accept only document files using an array of document MIME types.\n\n```yaml\n_inputs:\n  document:\n    type: file\n    label: Document\n    options:\n      accepts_mime_types:\n        - application/pdf\n        - application/msword\n        - application/vnd.openxmlformats-officedocument.wordprocessingml.document\n```",
       "type": "string",
       "enum": [
         "x-world/x-3dmf",
@@ -8073,6 +7812,8 @@
         "multipart/x-zip",
         "text/x-script.zsh"
       ],
+      "title": "Mime Type",
+      "description": "This key represents an array format for the `accepts_mime_types` key that restricts which file types are available to select or upload in *File Inputs*.\n\nThe value is an array of MIME type strings. Each string specifies a file type that CloudCannon will allow for this input.\n\nAvailable MIME types include image formats (`image/x-icon`, `image/gif`, `image/jpeg`, `image/png`, `image/webp`, `image/bmp`, `image/svg+xml`) and document formats (`application/pdf`, `application/msword`, `application/vnd.openxmlformats-officedocument.wordprocessingml.document`, `application/vnd.ms-excel`, `application/vnd.openxmlformats-officedocument.spreadsheetml.sheet`, `application/vnd.ms-powerpoint`, `application/vnd.openxmlformats-officedocument.presentationml.presentation`).\n\nUse the array format when you want to explicitly list multiple MIME types, making it easier to read and maintain in your configuration.\n\n## Examples\n\nIn this example, we have configured a *File Input* to accept only image files using an array of image MIME types.\n\n```yaml\n_inputs:\n  hero_image:\n    type: file\n    label: Hero Image\n    options:\n      accepts_mime_types:\n        - image/jpeg\n        - image/png\n        - image/webp\n```\n\nIn this example, we have configured a *File Input* to accept only document files using an array of document MIME types.\n\n```yaml\n_inputs:\n  document:\n    type: file\n    label: Document\n    options:\n      accepts_mime_types:\n        - application/pdf\n        - application/msword\n        - application/vnd.openxmlformats-officedocument.wordprocessingml.document\n```",
       "documented": true,
       "markdownDescription": "This key represents an array format for the `accepts_mime_types` key that restricts which file types are available to select or upload in *File Inputs*.\n\nThe value is an array of MIME type strings. Each string specifies a file type that CloudCannon will allow for this input.\n\nAvailable MIME types include image formats (`image/x-icon`, `image/gif`, `image/jpeg`, `image/png`, `image/webp`, `image/bmp`, `image/svg+xml`) and document formats (`application/pdf`, `application/msword`, `application/vnd.openxmlformats-officedocument.wordprocessingml.document`, `application/vnd.ms-excel`, `application/vnd.openxmlformats-officedocument.spreadsheetml.sheet`, `application/vnd.ms-powerpoint`, `application/vnd.openxmlformats-officedocument.presentationml.presentation`).\n\nUse the array format when you want to explicitly list multiple MIME types, making it easier to read and maintain in your configuration.\n\n## Examples\n\nIn this example, we have configured a *File Input* to accept only image files using an array of image MIME types.\n\n```yaml\n_inputs:\n  hero_image:\n    type: file\n    label: Hero Image\n    options:\n      accepts_mime_types:\n        - image/jpeg\n        - image/png\n        - image/webp\n```\n\nIn this example, we have configured a *File Input* to accept only document files using an array of document MIME types.\n\n```yaml\n_inputs:\n  document:\n    type: file\n    label: Document\n    options:\n      accepts_mime_types:\n        - application/pdf\n        - application/msword\n        - application/vnd.openxmlformats-officedocument.wordprocessingml.document\n```"
     },
@@ -8115,8 +7856,6 @@
       "markdownDescription": "This key toggles whether CloudCannon will prevent file uploads inside the \"Select existing file/image\" file browser modal window.\n\nSetting this key to `true` will prevent file uploads inside the file browser modal window.\n\n## Examples\n\nIn this example, CloudCannon will disable the option to upload files inside the file browser modal window.\n\n```yaml\n_inputs:\n  image:\n    type: file\n    options:\n      disable_upload_file_in_file_browser: true\n```"
     },
     "UrlInput": {
-      "title": "URL Input",
-      "description": "This key defines an editing interface for relative, absolute, and fully qualified URLs.",
       "type": "object",
       "properties": {
         "comment": {
@@ -8161,15 +7900,14 @@
           "$ref": "#/definitions/type._inputs.*.cascade"
         },
         "type": {
-          "title": "Type",
-          "description": "This key defines the input type, which controls how this input appears and behaves.",
           "type": "string",
           "const": "url",
+          "title": "Type",
+          "description": "This key defines the input type, which controls how this input appears and behaves.",
           "documented": true,
           "markdownDescription": "This key defines the input type, which controls how this input appears and behaves."
         },
         "options": {
-          "description": "This key defines options that are specific to URL Inputs.",
           "type": "object",
           "properties": {
             "mime_type": {
@@ -8323,6 +8061,7 @@
             }
           },
           "additionalProperties": false,
+          "description": "This key defines options that are specific to URL Inputs.",
           "documented": true,
           "title": "options",
           "markdownDescription": "This key defines options that are specific to URL Inputs."
@@ -8332,12 +8071,12 @@
         "type"
       ],
       "additionalProperties": false,
+      "title": "URL Input",
+      "description": "This key defines an editing interface for relative, absolute, and fully qualified URLs.",
       "documented": true,
       "markdownDescription": "This key defines an editing interface for relative, absolute, and fully qualified URLs."
     },
     "SelectInput": {
-      "title": "Select Input",
-      "description": "This key defines an editing interface for data with multiple predefined options.\n\nSelect inputs only allow one value.\n\n## Examples\n\nIn this example, we have configured the `category` key as a *Select Input*.\n\n```yaml\n_inputs:\n  category:\n    type: select\n    label: Category\n    options:\n      values:\n        - Blog\n        - News\n        - Events\n```",
       "type": "object",
       "properties": {
         "comment": {
@@ -8382,15 +8121,14 @@
           "$ref": "#/definitions/type._inputs.*.cascade"
         },
         "type": {
-          "title": "Type",
-          "description": "This key defines the input type, which controls how this input appears and behaves.\n\n## Examples\n\nIn this example, we have configured the `category` key as a *Select Input* type.\n\n```yaml\n_inputs:\n  category:\n    type: select\n    options:\n      values:\n        - Blog\n        - News\n        - Events\n```",
           "type": "string",
           "const": "select",
+          "title": "Type",
+          "description": "This key defines the input type, which controls how this input appears and behaves.\n\n## Examples\n\nIn this example, we have configured the `category` key as a *Select Input* type.\n\n```yaml\n_inputs:\n  category:\n    type: select\n    options:\n      values:\n        - Blog\n        - News\n        - Events\n```",
           "documented": true,
           "markdownDescription": "This key defines the input type, which controls how this input appears and behaves.\n\n## Examples\n\nIn this example, we have configured the `category` key as a *Select Input* type.\n\n```yaml\n_inputs:\n  category:\n    type: select\n    options:\n      values:\n        - Blog\n        - News\n        - Events\n```"
         },
         "options": {
-          "description": "This key defines options that are specific to Select Inputs.\n\n## Examples\n\nIn this example, we have configured *Select Input* options including values.\n\n```yaml\n_inputs:\n  category:\n    type: select\n    options:\n      values:\n        - Blog\n        - News\n        - Events\n```",
           "type": "object",
           "properties": {
             "required": {
@@ -8494,6 +8232,7 @@
             }
           },
           "additionalProperties": false,
+          "description": "This key defines options that are specific to Select Inputs.\n\n## Examples\n\nIn this example, we have configured *Select Input* options including values.\n\n```yaml\n_inputs:\n  category:\n    type: select\n    options:\n      values:\n        - Blog\n        - News\n        - Events\n```",
           "documented": true,
           "title": "options",
           "markdownDescription": "This key defines options that are specific to Select Inputs.\n\n## Examples\n\nIn this example, we have configured *Select Input* options including values.\n\n```yaml\n_inputs:\n  category:\n    type: select\n    options:\n      values:\n        - Blog\n        - News\n        - Events\n```"
@@ -8503,6 +8242,8 @@
         "type"
       ],
       "additionalProperties": false,
+      "title": "Select Input",
+      "description": "This key defines an editing interface for data with multiple predefined options.\n\nSelect inputs only allow one value.\n\n## Examples\n\nIn this example, we have configured the `category` key as a *Select Input*.\n\n```yaml\n_inputs:\n  category:\n    type: select\n    label: Category\n    options:\n      values:\n        - Blog\n        - News\n        - Events\n```",
       "documented": true,
       "markdownDescription": "This key defines an editing interface for data with multiple predefined options.\n\nSelect inputs only allow one value.\n\n## Examples\n\nIn this example, we have configured the `category` key as a *Select Input*.\n\n```yaml\n_inputs:\n  category:\n    type: select\n    label: Category\n    options:\n      values:\n        - Blog\n        - News\n        - Events\n```"
     },
@@ -8516,37 +8257,35 @@
     },
     "type._inputs.*.options.allow_empty": {
       "deprecated": true,
-      "description": "**⚠️ DEPRECATED:** This key is deprecated. If you want to prevent empty values, we recommend setting `_inputs.*.options.required` to `true` instead.\n\nThis key toggles whether CloudCannon will accept empty values, and pre-select the first option if opened with an empty value.\n\nSetting this key to `true` will allow CloudCannon to accept empty values.\n\n## Examples\n\nIn this example, CloudCannon will accept empty values for a *Select Input*.\n\n```yaml\n_inputs:\n  category:\n    type: select\n    options:\n      values:\n        - Blog\n        - News\n        - Events\n      allow_empty: true\n```",
+      "description": "This key is deprecated. If you want to prevent empty values, we recommend setting `_inputs.*.options.required` to `true` instead.\n\nThis key toggles whether CloudCannon will accept empty values, and pre-select the first option if opened with an empty value.\n\nSetting this key to `true` will allow CloudCannon to accept empty values.\n\n## Examples\n\nIn this example, CloudCannon will accept empty values for a *Select Input*.\n\n```yaml\n_inputs:\n  category:\n    type: select\n    options:\n      values:\n        - Blog\n        - News\n        - Events\n      allow_empty: true\n```",
       "type": "boolean",
       "documented": true,
       "title": "allow_empty",
-      "markdownDescription": "**⚠️ DEPRECATED:** This key is deprecated. If you want to prevent empty values, we recommend setting `_inputs.*.options.required` to `true` instead.\n\nThis key toggles whether CloudCannon will accept empty values, and pre-select the first option if opened with an empty value.\n\nSetting this key to `true` will allow CloudCannon to accept empty values.\n\n## Examples\n\nIn this example, CloudCannon will accept empty values for a *Select Input*.\n\n```yaml\n_inputs:\n  category:\n    type: select\n    options:\n      values:\n        - Blog\n        - News\n        - Events\n      allow_empty: true\n```"
+      "markdownDescription": "This key is deprecated. If you want to prevent empty values, we recommend setting `_inputs.*.options.required` to `true` instead.\n\nThis key toggles whether CloudCannon will accept empty values, and pre-select the first option if opened with an empty value.\n\nSetting this key to `true` will allow CloudCannon to accept empty values.\n\n## Examples\n\nIn this example, CloudCannon will accept empty values for a *Select Input*.\n\n```yaml\n_inputs:\n  category:\n    type: select\n    options:\n      values:\n        - Blog\n        - News\n        - Events\n      allow_empty: true\n```"
     },
     "type._inputs.*.options.values": {
       "description": "This key defines the values available to choose from.\n\nOptional, defaults to fetching values from the naming convention (e.g. `colors` or `my_colors` for data set `colors`).\n\n## Examples\n\nIn this example, we have configured a *Select Input* with custom values to choose from.\n\n```yaml\n_inputs:\n  category:\n    type: select\n    options:\n      values:\n        - Blog\n        - News\n        - Events\n```",
       "anyOf": [
         {
+          "type": "string",
           "title": "Dataset Reference Values",
           "description": "This key defines a reference to a dataset.",
-          "type": "string",
           "documented": true,
           "markdownDescription": "This key defines a reference to a dataset."
         },
         {
-          "description": "Data formats for populating select and multiselect input options, supporting arrays and objects.",
           "anyOf": [
             {
-              "title": "Text Array",
               "type": "array",
               "items": {
                 "type": "string",
                 "documented": false,
                 "title": "values(any-of-1)(text-array)[*]"
               },
+              "title": "Text Array",
               "documented": false
             },
             {
-              "title": "Text Object",
               "type": "object",
               "propertyNames": {
                 "type": "string"
@@ -8556,10 +8295,10 @@
                 "documented": false,
                 "title": "values(any-of-1)(text-object).*"
               },
+              "title": "Text Object",
               "documented": false
             },
             {
-              "title": "Object Array",
               "type": "array",
               "items": {
                 "type": "object",
@@ -8570,18 +8309,20 @@
                 "documented": false,
                 "title": "values(any-of-1)(object-array)[*]"
               },
+              "title": "Object Array",
               "documented": false
             },
             {
-              "title": "Object",
               "type": "object",
               "propertyNames": {
                 "type": "string"
               },
               "additionalProperties": {},
+              "title": "Object",
               "documented": false
             }
           ],
+          "description": "Data formats for populating select and multiselect input options, supporting arrays and objects.",
           "documented": false,
           "title": "values(any-of-1)",
           "markdownDescription": "Data formats for populating select and multiselect input options, supporting arrays and objects."
@@ -8625,8 +8366,6 @@
       "markdownDescription": "This key defines how CloudCannon should render selectable options in the dropdown of a *Select Input*.\n\n## Examples\n\nIn this example, we have configured a *Select Input* to display options using the card view.\n\n```yaml\n_inputs:\n  category:\n    type: select\n    options:\n      values:\n        - Blog\n        - News\n        - Events\n      picker_view: card\n```"
     },
     "MultiselectInput": {
-      "title": "Multiselect Input",
-      "description": "This key defines an editing interface for data with multiple predefined options.\n\nMultiselect inputs allow several values.\n\n## Examples\n\nIn this example, we have configured the `tags` key as a *Multiselect Input*.\n\n```yaml\n_inputs:\n  tags:\n    type: multiselect\n    label: Tags\n    options:\n      values:\n        - featured\n        - news\n        - events\n```",
       "type": "object",
       "properties": {
         "comment": {
@@ -8671,15 +8410,14 @@
           "$ref": "#/definitions/type._inputs.*.cascade"
         },
         "type": {
-          "title": "Type",
-          "description": "This key defines the input type, which controls how this input appears and behaves.\n\n## Examples\n\nIn this example, we have configured the `tags` key as a *Multiselect Input* type.\n\n```yaml\n_inputs:\n  tags:\n    type: multiselect\n```",
           "type": "string",
           "const": "multiselect",
+          "title": "Type",
+          "description": "This key defines the input type, which controls how this input appears and behaves.\n\n## Examples\n\nIn this example, we have configured the `tags` key as a *Multiselect Input* type.\n\n```yaml\n_inputs:\n  tags:\n    type: multiselect\n```",
           "documented": true,
           "markdownDescription": "This key defines the input type, which controls how this input appears and behaves.\n\n## Examples\n\nIn this example, we have configured the `tags` key as a *Multiselect Input* type.\n\n```yaml\n_inputs:\n  tags:\n    type: multiselect\n```"
         },
         "options": {
-          "description": "This key defines options that are specific to Multiselect Inputs.\n\n## Examples\n\nIn this example, we have configured *Multiselect Input* options including values.\n\n```yaml\n_inputs:\n  tags:\n    type: multiselect\n    options:\n      values:\n        - featured\n        - news\n        - events\n```",
           "type": "object",
           "properties": {
             "required": {
@@ -8753,6 +8491,7 @@
             }
           },
           "additionalProperties": false,
+          "description": "This key defines options that are specific to Multiselect Inputs.\n\n## Examples\n\nIn this example, we have configured *Multiselect Input* options including values.\n\n```yaml\n_inputs:\n  tags:\n    type: multiselect\n    options:\n      values:\n        - featured\n        - news\n        - events\n```",
           "documented": true,
           "title": "options",
           "markdownDescription": "This key defines options that are specific to Multiselect Inputs.\n\n## Examples\n\nIn this example, we have configured *Multiselect Input* options including values.\n\n```yaml\n_inputs:\n  tags:\n    type: multiselect\n    options:\n      values:\n        - featured\n        - news\n        - events\n```"
@@ -8762,6 +8501,8 @@
         "type"
       ],
       "additionalProperties": false,
+      "title": "Multiselect Input",
+      "description": "This key defines an editing interface for data with multiple predefined options.\n\nMultiselect inputs allow several values.\n\n## Examples\n\nIn this example, we have configured the `tags` key as a *Multiselect Input*.\n\n```yaml\n_inputs:\n  tags:\n    type: multiselect\n    label: Tags\n    options:\n      values:\n        - featured\n        - news\n        - events\n```",
       "documented": true,
       "markdownDescription": "This key defines an editing interface for data with multiple predefined options.\n\nMultiselect inputs allow several values.\n\n## Examples\n\nIn this example, we have configured the `tags` key as a *Multiselect Input*.\n\n```yaml\n_inputs:\n  tags:\n    type: multiselect\n    label: Tags\n    options:\n      values:\n        - featured\n        - news\n        - events\n```"
     },
@@ -8808,8 +8549,8 @@
       "markdownDescription": "This key defines a custom error message that explains why a value has failed the validation criteria from `options.unique_on`.\nThis key requires you to define `options.unique_on`.\n\nThis key has no default.\n\nThis key is available for Array inputs.\n\n## Examples\n\nIn this example, we want our team to add article filepaths to the `related_articles` Input. This Input requires all the filepaths to be unique.\n\n```yaml\n_inputs:\n  related_articles:\n    type: array\n    options:\n      unique_on: '$.path'\n      unique_on_message: The value for path must be different for all items.\n```\n\n```yaml\nrelated_articles:\n  - path: /articles/first-article.md\n    featured: true\n  - path: /articles/first-article.md\n    featured: false\n```"
     },
     "type._inputs.*.options.empty_type(array)": {
-      "description": "This key defines how an 'empty' value will be saved. Does not apply to existing empty values.\n\n## Examples\n\nIn this example, we have configured how empty array values will be saved.\n\n```yaml\n_inputs:\n  tags:\n    type: array\n    options:\n      empty_type: array\n```",
       "default": "null",
+      "description": "This key defines how an 'empty' value will be saved. Does not apply to existing empty values.\n\n## Examples\n\nIn this example, we have configured how empty array values will be saved.\n\n```yaml\n_inputs:\n  tags:\n    type: array\n    options:\n      empty_type: array\n```",
       "type": "string",
       "enum": [
         "null",
@@ -8820,8 +8561,6 @@
       "markdownDescription": "This key defines how an 'empty' value will be saved. Does not apply to existing empty values.\n\n## Examples\n\nIn this example, we have configured how empty array values will be saved.\n\n```yaml\n_inputs:\n  tags:\n    type: array\n    options:\n      empty_type: array\n```"
     },
     "ChoiceInput": {
-      "title": "Choice Input",
-      "description": "This key defines an editing interface for data with multiple predefined options.\n\nChoice inputs only allow one value.\n\n## Examples\n\nIn this example, we have configured the `status` key as a *Choice Input*.\n\n```yaml\n_inputs:\n  status:\n    type: choice\n    label: Status\n    options:\n      values:\n        - draft\n        - published\n        - archived\n```",
       "type": "object",
       "properties": {
         "comment": {
@@ -8866,15 +8605,14 @@
           "$ref": "#/definitions/type._inputs.*.cascade"
         },
         "type": {
-          "title": "Type",
-          "description": "This key defines the input type, which controls how this input appears and behaves.\n\n## Examples\n\nIn this example, we have configured the `status` key as a *Choice Input* type.\n\n```yaml\n_inputs:\n  status:\n    type: choice\n```",
           "type": "string",
           "const": "choice",
+          "title": "Type",
+          "description": "This key defines the input type, which controls how this input appears and behaves.\n\n## Examples\n\nIn this example, we have configured the `status` key as a *Choice Input* type.\n\n```yaml\n_inputs:\n  status:\n    type: choice\n```",
           "documented": true,
           "markdownDescription": "This key defines the input type, which controls how this input appears and behaves.\n\n## Examples\n\nIn this example, we have configured the `status` key as a *Choice Input* type.\n\n```yaml\n_inputs:\n  status:\n    type: choice\n```"
         },
         "options": {
-          "description": "This key defines options that are specific to Choice Inputs.\n\n## Examples\n\nIn this example, we have configured *Choice Input* options including values.\n\n```yaml\n_inputs:\n  status:\n    type: choice\n    options:\n      values:\n        - draft\n        - published\n        - archived\n```",
           "type": "object",
           "properties": {
             "required": {
@@ -8975,6 +8713,7 @@
             }
           },
           "additionalProperties": false,
+          "description": "This key defines options that are specific to Choice Inputs.\n\n## Examples\n\nIn this example, we have configured *Choice Input* options including values.\n\n```yaml\n_inputs:\n  status:\n    type: choice\n    options:\n      values:\n        - draft\n        - published\n        - archived\n```",
           "documented": true,
           "title": "options",
           "markdownDescription": "This key defines options that are specific to Choice Inputs.\n\n## Examples\n\nIn this example, we have configured *Choice Input* options including values.\n\n```yaml\n_inputs:\n  status:\n    type: choice\n    options:\n      values:\n        - draft\n        - published\n        - archived\n```"
@@ -8984,12 +8723,12 @@
         "type"
       ],
       "additionalProperties": false,
+      "title": "Choice Input",
+      "description": "This key defines an editing interface for data with multiple predefined options.\n\nChoice inputs only allow one value.\n\n## Examples\n\nIn this example, we have configured the `status` key as a *Choice Input*.\n\n```yaml\n_inputs:\n  status:\n    type: choice\n    label: Status\n    options:\n      values:\n        - draft\n        - published\n        - archived\n```",
       "documented": true,
       "markdownDescription": "This key defines an editing interface for data with multiple predefined options.\n\nChoice inputs only allow one value.\n\n## Examples\n\nIn this example, we have configured the `status` key as a *Choice Input*.\n\n```yaml\n_inputs:\n  status:\n    type: choice\n    label: Status\n    options:\n      values:\n        - draft\n        - published\n        - archived\n```"
     },
     "MultichoiceInput": {
-      "title": "Multichoice Input",
-      "description": "This key defines an editing interface for data with multiple predefined options.\n\nMultichoice inputs allow several values.\n\n## Examples\n\nIn this example, we have configured the `categories` key as a *Multichoice Input*.\n\n```yaml\n_inputs:\n  categories:\n    type: multichoice\n    label: Categories\n    options:\n      values:\n        - technology\n        - design\n        - business\n```",
       "type": "object",
       "properties": {
         "comment": {
@@ -9034,15 +8773,14 @@
           "$ref": "#/definitions/type._inputs.*.cascade"
         },
         "type": {
-          "title": "Type",
-          "description": "This key defines the type of editing interface used for an Input.\n\nEach Input type has a different appearance and functionality, processes and accepts different types of values, and has different configuration\noptions.\n\nValue can be one of the following: `auto`, `checkbox`, `switch`, `code`, `color`, `datetime`, `date`, `time`, `file`, `document`, `image`, `number`,\n`range`, `object`, `array`, `select`, `multiselect`, `choice`, `multichoice`, `text`, `textarea`, `email`, `html`, `markdown`, or `url`.\n\nIf the type or value of an Input is misconfigured, CloudCannon will display an orange warning instead of an Input.\n\nIf type is not configured for an Input, CloudCannon will attempt to determine Input type based on value or key name conventions.\n\n## Examples\n\nIn this example, we have configured the `categories` key as a *Multichoice Input* type.\n\n```yaml\n_inputs:\n  categories:\n    type: multichoice\n```",
           "type": "string",
           "const": "multichoice",
+          "title": "Type",
+          "description": "This key defines the type of editing interface used for an Input.\n\nEach Input type has a different appearance and functionality, processes and accepts different types of values, and has different configuration\noptions.\n\nValue can be one of the following: `auto`, `checkbox`, `switch`, `code`, `color`, `datetime`, `date`, `time`, `file`, `document`, `image`, `number`,\n`range`, `object`, `array`, `select`, `multiselect`, `choice`, `multichoice`, `text`, `textarea`, `email`, `html`, `markdown`, or `url`.\n\nIf the type or value of an Input is misconfigured, CloudCannon will display an orange warning instead of an Input.\n\nIf type is not configured for an Input, CloudCannon will attempt to determine Input type based on value or key name conventions.\n\n## Examples\n\nIn this example, we have configured the `categories` key as a *Multichoice Input* type.\n\n```yaml\n_inputs:\n  categories:\n    type: multichoice\n```",
           "documented": true,
           "markdownDescription": "This key defines the type of editing interface used for an Input.\n\nEach Input type has a different appearance and functionality, processes and accepts different types of values, and has different configuration\noptions.\n\nValue can be one of the following: `auto`, `checkbox`, `switch`, `code`, `color`, `datetime`, `date`, `time`, `file`, `document`, `image`, `number`,\n`range`, `object`, `array`, `select`, `multiselect`, `choice`, `multichoice`, `text`, `textarea`, `email`, `html`, `markdown`, or `url`.\n\nIf the type or value of an Input is misconfigured, CloudCannon will display an orange warning instead of an Input.\n\nIf type is not configured for an Input, CloudCannon will attempt to determine Input type based on value or key name conventions.\n\n## Examples\n\nIn this example, we have configured the `categories` key as a *Multichoice Input* type.\n\n```yaml\n_inputs:\n  categories:\n    type: multichoice\n```"
         },
         "options": {
-          "description": "This key defines options that are specific to Multichoice Inputs.\n\n## Examples\n\nIn this example, we have configured *Multichoice Input* options including values.\n\n```yaml\n_inputs:\n  categories:\n    type: multichoice\n    options:\n      values:\n        - technology\n        - design\n        - business\n```",
           "type": "object",
           "properties": {
             "required": {
@@ -9113,6 +8851,7 @@
             }
           },
           "additionalProperties": false,
+          "description": "This key defines options that are specific to Multichoice Inputs.\n\n## Examples\n\nIn this example, we have configured *Multichoice Input* options including values.\n\n```yaml\n_inputs:\n  categories:\n    type: multichoice\n    options:\n      values:\n        - technology\n        - design\n        - business\n```",
           "documented": true,
           "title": "options",
           "markdownDescription": "This key defines options that are specific to Multichoice Inputs.\n\n## Examples\n\nIn this example, we have configured *Multichoice Input* options including values.\n\n```yaml\n_inputs:\n  categories:\n    type: multichoice\n    options:\n      values:\n        - technology\n        - design\n        - business\n```"
@@ -9122,12 +8861,12 @@
         "type"
       ],
       "additionalProperties": false,
+      "title": "Multichoice Input",
+      "description": "This key defines an editing interface for data with multiple predefined options.\n\nMultichoice inputs allow several values.\n\n## Examples\n\nIn this example, we have configured the `categories` key as a *Multichoice Input*.\n\n```yaml\n_inputs:\n  categories:\n    type: multichoice\n    label: Categories\n    options:\n      values:\n        - technology\n        - design\n        - business\n```",
       "documented": true,
       "markdownDescription": "This key defines an editing interface for data with multiple predefined options.\n\nMultichoice inputs allow several values.\n\n## Examples\n\nIn this example, we have configured the `categories` key as a *Multichoice Input*.\n\n```yaml\n_inputs:\n  categories:\n    type: multichoice\n    label: Categories\n    options:\n      values:\n        - technology\n        - design\n        - business\n```"
     },
     "ObjectInput": {
-      "title": "Object Input",
-      "description": "This key defines a user interface for a group of inputs.",
       "type": "object",
       "properties": {
         "comment": {
@@ -9172,15 +8911,14 @@
           "$ref": "#/definitions/type._inputs.*.cascade"
         },
         "type": {
-          "title": "Type",
-          "description": "This key defines the input type, which controls how this input appears and behaves.",
           "type": "string",
           "const": "object",
+          "title": "Type",
+          "description": "This key defines the input type, which controls how this input appears and behaves.",
           "documented": true,
           "markdownDescription": "This key defines the input type, which controls how this input appears and behaves."
         },
         "options": {
-          "description": "This key defines options that are specific to Object Inputs.",
           "type": "object",
           "properties": {
             "required": {
@@ -9403,6 +9141,7 @@
             }
           },
           "additionalProperties": false,
+          "description": "This key defines options that are specific to Object Inputs.",
           "documented": true,
           "title": "options",
           "markdownDescription": "This key defines options that are specific to Object Inputs."
@@ -9412,12 +9151,14 @@
         "type"
       ],
       "additionalProperties": false,
+      "title": "Object Input",
+      "description": "This key defines a user interface for a group of inputs.",
       "documented": true,
       "markdownDescription": "This key defines a user interface for a group of inputs."
     },
     "type._inputs.*.options.empty_type(object)": {
-      "description": "This key defines how an 'empty' value will be saved. Does not apply to existing empty values.\n\n## Examples\n\nIn this example, we have configured how empty object values will be saved.\n\n```yaml\n_inputs:\n  metadata:\n    type: object\n    options:\n      empty_type: object\n```",
       "default": "null",
+      "description": "This key defines how an 'empty' value will be saved. Does not apply to existing empty values.\n\n## Examples\n\nIn this example, we have configured how empty object values will be saved.\n\n```yaml\n_inputs:\n  metadata:\n    type: object\n    options:\n      empty_type: object\n```",
       "type": "string",
       "enum": [
         "null",
@@ -9428,15 +9169,13 @@
       "markdownDescription": "This key defines how an 'empty' value will be saved. Does not apply to existing empty values.\n\n## Examples\n\nIn this example, we have configured how empty object values will be saved.\n\n```yaml\n_inputs:\n  metadata:\n    type: object\n    options:\n      empty_type: object\n```"
     },
     "type.structure-reference": {
+      "type": "string",
       "title": "Structure Reference",
       "description": "A reference to an existing structure.",
-      "type": "string",
       "documented": true,
       "markdownDescription": "A reference to an existing structure."
     },
     "type.structure": {
-      "title": "Structure",
-      "description": "This key defines data formats when adding new items to arrays and objects, with options for how editors choose from available values.",
       "type": "object",
       "properties": {
         "reorder_inputs": {
@@ -9472,11 +9211,11 @@
           "markdownDescription": "This key toggles whether CloudCannon will remove inputs that are not present in a Structure from a file before loading it in an Editing Interface.\n\nSetting this key to `true` will remove inputs that are not present in a Structure from a file before loading it in an Editing Interface. Non-Structure inputs will not be visible in the [Visual Editor](https://cloudcannon.com/documentation/articles/what-is-the-visual-editor/), [Content\nEditor](https://cloudcannon.com/documentation/articles/what-is-the-content-editor/), or [Data Editor](https://cloudcannon.com/documentation/articles/what-is-the-data-editor/), and saving the file\nwill remove them from the file before persisting the changes to your Git repository.\n\nYou can also configure this behavior for specific values of a Structure using `values[*].remove_extra_inputs`.\n\n## Examples\n\nIn this example, we want to delete old inputs that are not in the Structure from the associated file.\n\n```yaml\n_structures:\n  related_articles:\n    remove_extra_inputs: true\n    values:\n      - value:\n        name:\n        description:\n        url:\n```"
         },
         "values": {
-          "description": "This key defines the options available for a Structure.\n\nYou must define this key for the Structure to function.\n\nThis key has no default.\n\n## Examples\n\nIn this example, we want to add the `title`, `subtitle`, `author`, `featured_image`, and `url` fields to Object or Array inputs that reference this Structure.\n\n```yaml\n_structures:\n  related_articles:\n    values:\n      - label: Blog\n        id:\n        default: true\n        tabbed: false\n        tags:\n          - blog\n        value:\n          title:\n          subtitle:\n          author:\n          featured_image:\n          url:\n        _inputs:\n          featured_image:\n            type: image\n            options:\n              width: 50\n              height: 50\n        groups:\n          - heading: Titles\n            inputs:\n              - title\n              - subtitle\n          - heading: Details\n            inputs:\n              - author\n              - image\n              - url\n        preview:\n          text:\n            - template: \"{title}\"\n          subtext:\n            - template: \"By {author}\"\n          image:\n            - key: image\n        picker_preview:\n          text: Blog\n          subtext: Add a related blog\n          icon: post_add\n```",
           "type": "array",
           "items": {
             "$ref": "#/definitions/type.structure.values.[*]"
           },
+          "description": "This key defines the options available for a Structure.\n\nYou must define this key for the Structure to function.\n\nThis key has no default.\n\n## Examples\n\nIn this example, we want to add the `title`, `subtitle`, `author`, `featured_image`, and `url` fields to Object or Array inputs that reference this Structure.\n\n```yaml\n_structures:\n  related_articles:\n    values:\n      - label: Blog\n        id:\n        default: true\n        tabbed: false\n        tags:\n          - blog\n        value:\n          title:\n          subtitle:\n          author:\n          featured_image:\n          url:\n        _inputs:\n          featured_image:\n            type: image\n            options:\n              width: 50\n              height: 50\n        groups:\n          - heading: Titles\n            inputs:\n              - title\n              - subtitle\n          - heading: Details\n            inputs:\n              - author\n              - image\n              - url\n        preview:\n          text:\n            - template: \"{title}\"\n          subtext:\n            - template: \"By {author}\"\n          image:\n            - key: image\n        picker_preview:\n          text: Blog\n          subtext: Add a related blog\n          icon: post_add\n```",
           "documented": true,
           "title": "values",
           "markdownDescription": "This key defines the options available for a Structure.\n\nYou must define this key for the Structure to function.\n\nThis key has no default.\n\n## Examples\n\nIn this example, we want to add the `title`, `subtitle`, `author`, `featured_image`, and `url` fields to Object or Array inputs that reference this Structure.\n\n```yaml\n_structures:\n  related_articles:\n    values:\n      - label: Blog\n        id:\n        default: true\n        tabbed: false\n        tags:\n          - blog\n        value:\n          title:\n          subtitle:\n          author:\n          featured_image:\n          url:\n        _inputs:\n          featured_image:\n            type: image\n            options:\n              width: 50\n              height: 50\n        groups:\n          - heading: Titles\n            inputs:\n              - title\n              - subtitle\n          - heading: Details\n            inputs:\n              - author\n              - image\n              - url\n        preview:\n          text:\n            - template: \"{title}\"\n          subtext:\n            - template: \"By {author}\"\n          image:\n            - key: image\n        picker_preview:\n          text: Blog\n          subtext: Add a related blog\n          icon: post_add\n```"
@@ -9511,17 +9250,384 @@
             "select",
             "modal"
           ],
-          "documented": true,
-          "title": "style",
-          "markdownDescription": "This key defines how CloudCannon shows Structure options to populate an Object or Array input.\n\nThis can be using a select-style search bar or a pop-up modal.\n\nModals are useful when you have several value options for your Structure.\n\nValues can be one of the following: `select`, or `modal`.\n\n## Examples\n\nIn this example, the `related_articles` Structure only has one option so a `select` searchbar is appropriate.\n\n```yaml\n_structures:\n  related_articles:\n    style: select\n    values:\n      - value:\n        name:\n        description:\n        url:\n```"
+          "documented": true,
+          "title": "style",
+          "markdownDescription": "This key defines how CloudCannon shows Structure options to populate an Object or Array input.\n\nThis can be using a select-style search bar or a pop-up modal.\n\nModals are useful when you have several value options for your Structure.\n\nValues can be one of the following: `select`, or `modal`.\n\n## Examples\n\nIn this example, the `related_articles` Structure only has one option so a `select` searchbar is appropriate.\n\n```yaml\n_structures:\n  related_articles:\n    style: select\n    values:\n      - value:\n        name:\n        description:\n        url:\n```"
+        }
+      },
+      "required": [
+        "values"
+      ],
+      "additionalProperties": false,
+      "title": "Structure",
+      "description": "This key defines data formats when adding new items to arrays and objects, with options for how editors choose from available values.",
+      "documented": true,
+      "markdownDescription": "This key defines data formats when adding new items to arrays and objects, with options for how editors choose from available values."
+    },
+    "type.structure.values.[*]": {
+      "type": "object",
+      "properties": {
+        "reorder_inputs": {
+          "description": "This key toggles whether CloudCannon will reorder inputs in a file to match the order defined in a given value from a Structure.\n\nSetting this key to `false` will preserve the existing order of inputs in a file, regardless of the order defined in the Structure value.\n\nBy default, this key is `true` (i.e., inputs are reordered to match the Structure value).\n\nYou can also configure this behavior for all values of a Structure using `reorder_inputs` inside `_structures.*`.",
+          "default": true,
+          "type": "boolean",
+          "documented": true,
+          "title": "reorder_inputs",
+          "markdownDescription": "This key toggles whether CloudCannon will reorder inputs in a file to match the order defined in a given value from a Structure.\n\nSetting this key to `false` will preserve the existing order of inputs in a file, regardless of the order defined in the Structure value.\n\nBy default, this key is `true` (i.e., inputs are reordered to match the Structure value).\n\nYou can also configure this behavior for all values of a Structure using `reorder_inputs` inside `_structures.*`."
+        },
+        "hide_extra_inputs": {
+          "description": "This key toggles whether CloudCannon will hide inputs that are not present in a given value from a Structure from the [Data\nEditor](https://cloudcannon.com/documentation/articles/what-is-the-data-editor/).\n\nSetting this key to `true` will hide inputs that are not present in a given value from a Structure from the Data Editor. Hiding these inputs does not delete the data. You can see non-structure data keys by opening a file in the [Source Editor](https://cloudcannon.com/documentation/articles/what-is-the-source-editor/). This key has no effect if `remove_extra_inputs` is `true`.\n\nYou can also configure this behavior for all values of a Structure using `hide_extra_inputs` inside `_structures.*`.",
+          "default": false,
+          "type": "boolean",
+          "documented": true,
+          "title": "hide_extra_inputs",
+          "markdownDescription": "This key toggles whether CloudCannon will hide inputs that are not present in a given value from a Structure from the [Data\nEditor](https://cloudcannon.com/documentation/articles/what-is-the-data-editor/).\n\nSetting this key to `true` will hide inputs that are not present in a given value from a Structure from the Data Editor. Hiding these inputs does not delete the data. You can see non-structure data keys by opening a file in the [Source Editor](https://cloudcannon.com/documentation/articles/what-is-the-source-editor/). This key has no effect if `remove_extra_inputs` is `true`.\n\nYou can also configure this behavior for all values of a Structure using `hide_extra_inputs` inside `_structures.*`."
+        },
+        "remove_empty_inputs": {
+          "description": "This key toggles whether CloudCannon will remove empty nested inputs from an Object Input or Array Input using a given value from a Structure before\npersisting them to your file.\n\nSetting this key to `true` will remove empty nested inputs from an Object Input or Array Input using a given value from a Structure before\npersisting them to your file. CloudCannon considers an input to be empty when its value is `null`, `' '`, or undefined. If this key is true, empty inputs will be visible in the [Data Editor](https://cloudcannon.com/documentation/articles/what-is-the-data-editor/) but not the [Source\nEditor](https://cloudcannon.com/documentation/articles/what-is-the-source-editor/). For this key to function, you must also configure `id_key` for the Structure, as removing inputs prevents CloudCannon from comparing Structure values.\n\nYou can also configure this behavior for all values of a Structure using `remove_empty_inputs` inside `_structures.*`.",
+          "default": false,
+          "type": "boolean",
+          "documented": true,
+          "title": "remove_empty_inputs",
+          "markdownDescription": "This key toggles whether CloudCannon will remove empty nested inputs from an Object Input or Array Input using a given value from a Structure before\npersisting them to your file.\n\nSetting this key to `true` will remove empty nested inputs from an Object Input or Array Input using a given value from a Structure before\npersisting them to your file. CloudCannon considers an input to be empty when its value is `null`, `' '`, or undefined. If this key is true, empty inputs will be visible in the [Data Editor](https://cloudcannon.com/documentation/articles/what-is-the-data-editor/) but not the [Source\nEditor](https://cloudcannon.com/documentation/articles/what-is-the-source-editor/). For this key to function, you must also configure `id_key` for the Structure, as removing inputs prevents CloudCannon from comparing Structure values.\n\nYou can also configure this behavior for all values of a Structure using `remove_empty_inputs` inside `_structures.*`."
+        },
+        "remove_extra_inputs": {
+          "description": "This key toggles whether CloudCannon will remove inputs that are not present in a given value from a Structure from a file before loading it in an\nEditing Interface.\n\nSetting this key to `true` will remove inputs that are not present in a given value from a Structure from a file before loading it in an Editing Interface. Non-Structure inputs will not be visible in the [Visual Editor](https://cloudcannon.com/documentation/articles/what-is-the-visual-editor/), [Content\nEditor](https://cloudcannon.com/documentation/articles/what-is-the-content-editor/), or [Data Editor](https://cloudcannon.com/documentation/articles/what-is-the-data-editor/), and saving the file\nwill remove them from the file before persisting the changes to your Git repository.\n\nYou can also configure this behavior for all values of a Structure using `remove_extra_inputs` inside `_structures.*`.",
+          "default": true,
+          "type": "boolean",
+          "documented": true,
+          "title": "remove_extra_inputs",
+          "markdownDescription": "This key toggles whether CloudCannon will remove inputs that are not present in a given value from a Structure from a file before loading it in an\nEditing Interface.\n\nSetting this key to `true` will remove inputs that are not present in a given value from a Structure from a file before loading it in an Editing Interface. Non-Structure inputs will not be visible in the [Visual Editor](https://cloudcannon.com/documentation/articles/what-is-the-visual-editor/), [Content\nEditor](https://cloudcannon.com/documentation/articles/what-is-the-content-editor/), or [Data Editor](https://cloudcannon.com/documentation/articles/what-is-the-data-editor/), and saving the file\nwill remove them from the file before persisting the changes to your Git repository.\n\nYou can also configure this behavior for all values of a Structure using `remove_extra_inputs` inside `_structures.*`."
+        },
+        "preview": {
+          "allOf": [
+            {
+              "$ref": "#/definitions/type.preview"
+            }
+          ],
+          "documented": false,
+          "title": "preview"
+        },
+        "picker_preview": {
+          "allOf": [
+            {
+              "$ref": "#/definitions/type.picker_preview"
+            }
+          ],
+          "documented": false,
+          "title": "picker_preview"
+        },
+        "_inputs": {
+          "$ref": "#/definitions/__schema0"
+        },
+        "_inputs_from_glob": {
+          "allOf": [
+            {
+              "$ref": "#/definitions/type._inputs_from_glob"
+            }
+          ],
+          "documented": false,
+          "title": "_inputs_from_glob"
+        },
+        "_select_data": {
+          "allOf": [
+            {
+              "$ref": "#/definitions/type._select_data"
+            }
+          ],
+          "documented": false,
+          "title": "_select_data"
+        },
+        "_structures": {
+          "allOf": [
+            {
+              "$ref": "#/definitions/type._structures"
+            }
+          ],
+          "documented": false,
+          "title": "_structures"
+        },
+        "_structures_from_glob": {
+          "allOf": [
+            {
+              "$ref": "#/definitions/type._structures_from_glob"
+            }
+          ],
+          "documented": false,
+          "title": "_structures_from_glob"
+        },
+        "id": {
+          "description": "This key defines the string used to identify a given Structure value when refering to it from other input configuration.\n\n## Examples\n\nIn this example, we have configured the `blog_post` ID for the entry labeled `Blog` in the `article_information` Structure.\n\n```yaml\n_structures:\n  article_information:\n    values:\n      - label: Blog\n        id: blog_post\n```",
+          "type": "string",
+          "documented": true,
+          "title": "id",
+          "markdownDescription": "This key defines the string used to identify a given Structure value when refering to it from other input configuration.\n\n## Examples\n\nIn this example, we have configured the `blog_post` ID for the entry labeled `Blog` in the `article_information` Structure.\n\n```yaml\n_structures:\n  article_information:\n    values:\n      - label: Blog\n        id: blog_post\n```"
+        },
+        "default": {
+          "description": "This key toggles whether CloudCannon should treat an entry in the `values` array as the default option for your Object or Array input.\n\nSetting this key to `true` will mark this entry as the default option for your Object or Array input. If multiple entries in the `values` array are set to `true`, CloudCannon will use the first entry. If CloudCannon cannot determine the type of an entry within the `values` array based on the `id_key` or matching inputs across `values[*].value` objects,\nit will fall back to the default entry.\n\n## Examples\n\nIn this example, we want the entry labelled `Employee` to be our default option for populating inputs configured with the `staff` Structure.\n\n```yaml\n_structures:\n  staff:\n    style: modal\n    values:\n      - label: Employee\n        default: true\n        value:\n          name:\n          job_description:\n          profile_picture:\n      - label: Manager\n        value:\n          name:\n          job_description:\n          profile_picture:\n          url:\n```",
+          "default": false,
+          "type": "boolean",
+          "documented": true,
+          "title": "default",
+          "markdownDescription": "This key toggles whether CloudCannon should treat an entry in the `values` array as the default option for your Object or Array input.\n\nSetting this key to `true` will mark this entry as the default option for your Object or Array input. If multiple entries in the `values` array are set to `true`, CloudCannon will use the first entry. If CloudCannon cannot determine the type of an entry within the `values` array based on the `id_key` or matching inputs across `values[*].value` objects,\nit will fall back to the default entry.\n\n## Examples\n\nIn this example, we want the entry labelled `Employee` to be our default option for populating inputs configured with the `staff` Structure.\n\n```yaml\n_structures:\n  staff:\n    style: modal\n    values:\n      - label: Employee\n        default: true\n        value:\n          name:\n          job_description:\n          profile_picture:\n      - label: Manager\n        value:\n          name:\n          job_description:\n          profile_picture:\n          url:\n```"
+        },
+        "icon": {
+          "description": "This key defines an icon used when displaying the structure (defaults to either `format_list_bulleted` for items in arrays, or `notes` otherwise).\n\n## Examples\n\nIn this example, CloudCannon will display the `article` icon for the entry labeled `Blog` in the `article_information` Structure.\n\n```yaml\n_structures:\n  article_information:\n    values:\n      - label: Blog\n        icon: article\n```",
+          "allOf": [
+            {
+              "$ref": "#/definitions/icon"
+            }
+          ],
+          "documented": true,
+          "title": "icon",
+          "markdownDescription": "This key defines an icon used when displaying the structure (defaults to either `format_list_bulleted` for items in arrays, or `notes` otherwise).\n\n## Examples\n\nIn this example, CloudCannon will display the `article` icon for the entry labeled `Blog` in the `article_information` Structure.\n\n```yaml\n_structures:\n  article_information:\n    values:\n      - label: Blog\n        icon: article\n```"
+        },
+        "image": {
+          "description": "This key defines the path to an image in your source files used when displaying the structure value.\n\nCan be either a source (has priority) or output path.\n\n## Examples\n\nIn this example, we have configured the `/images/blog-icon.png` image for the entry labeled `Blog` in the `article_information` Structure.\n\n```yaml\n_structures:\n  article_information:\n    values:\n      - label: Blog\n        image: /images/blog-icon.png\n```",
+          "type": "string",
+          "documented": true,
+          "title": "image",
+          "markdownDescription": "This key defines the path to an image in your source files used when displaying the structure value.\n\nCan be either a source (has priority) or output path.\n\n## Examples\n\nIn this example, we have configured the `/images/blog-icon.png` image for the entry labeled `Blog` in the `article_information` Structure.\n\n```yaml\n_structures:\n  article_information:\n    values:\n      - label: Blog\n        image: /images/blog-icon.png\n```"
+        },
+        "label": {
+          "description": "This key defines the display name for a given value in a Structure.\n\nThe name will appear in the *+ Add* button dropdown below an Object or Array input or in the Structures modal (if configured).\n\nBy default, this key falls back to `unknown`.\n\n## Examples\n\nIn this example, we want two value options for our `staff` structure: one called `Manager` and one called `Employee`.\n\n```yaml\n_structures:\n  staff:\n    values:\n      - label: Employee\n        value:\n          name:\n          job_description:\n          profile_picture:\n      - label: Manager\n        value:\n          name:\n          job_description:\n          profile_picture:\n          url:\n```",
+          "type": "string",
+          "documented": true,
+          "title": "label",
+          "markdownDescription": "This key defines the display name for a given value in a Structure.\n\nThe name will appear in the *+ Add* button dropdown below an Object or Array input or in the Structures modal (if configured).\n\nBy default, this key falls back to `unknown`.\n\n## Examples\n\nIn this example, we want two value options for our `staff` structure: one called `Manager` and one called `Employee`.\n\n```yaml\n_structures:\n  staff:\n    values:\n      - label: Employee\n        value:\n          name:\n          job_description:\n          profile_picture:\n      - label: Manager\n        value:\n          name:\n          job_description:\n          profile_picture:\n          url:\n```"
+        },
+        "tags": {
+          "description": "This key defines which tags are associated with a given value in a Structure.\n\nYou can use tags to group and filter Structure options when selecting from a modal.\n\nThis key has no default.\n\n## Examples\n\nIn this example we have three options for the `page_components` Structure: `Hero Component`, `Feature Component`, and `Video Component`. We can search the Structure modal using the `image`, `text`, `button`, and `video` tags to filter Structure values.\n\n```yaml\n_structures:\n  page_components:\n    style: modal\n    values:\n      - label: Hero Component\n        tags:\n          - image\n          - text\n        value:\n          title:\n          description:\n          image_path:\n          link:\n            text:\n            url:\n      - label: Feature Component\n        tags:\n          - image\n          - text\n          - button\n        value:\n          image_path:\n          title:\n          description:\n          button:\n            link:\n            text:\n          reversed_layout: false\n      - label: Video Component\n        tags:\n          - image\n          - video\n        value:\n          image_path:\n          videoUrl:\n```",
+          "type": "array",
+          "items": {
+            "type": "string",
+            "documented": true,
+            "title": "tags[*]",
+            "description": "This key represents an individual tag string in the `values[*].tags` array.\n\nThe value is a string that specifies a tag associated with a structure value.\n\n## Examples\n\nIn this example, we have configured the `featured` and `news` tags for the entry labeled `Blog` in the `article_information` Structure.\n\n```yaml\n_structures:\n  article_information:\n    values:\n      - label: Blog\n        tags:\n          - featured\n          - news\n```",
+            "markdownDescription": "This key represents an individual tag string in the `values[*].tags` array.\n\nThe value is a string that specifies a tag associated with a structure value.\n\n## Examples\n\nIn this example, we have configured the `featured` and `news` tags for the entry labeled `Blog` in the `article_information` Structure.\n\n```yaml\n_structures:\n  article_information:\n    values:\n      - label: Blog\n        tags:\n          - featured\n          - news\n```"
+          },
+          "documented": true,
+          "title": "tags",
+          "markdownDescription": "This key defines which tags are associated with a given value in a Structure.\n\nYou can use tags to group and filter Structure options when selecting from a modal.\n\nThis key has no default.\n\n## Examples\n\nIn this example we have three options for the `page_components` Structure: `Hero Component`, `Feature Component`, and `Video Component`. We can search the Structure modal using the `image`, `text`, `button`, and `video` tags to filter Structure values.\n\n```yaml\n_structures:\n  page_components:\n    style: modal\n    values:\n      - label: Hero Component\n        tags:\n          - image\n          - text\n        value:\n          title:\n          description:\n          image_path:\n          link:\n            text:\n            url:\n      - label: Feature Component\n        tags:\n          - image\n          - text\n          - button\n        value:\n          image_path:\n          title:\n          description:\n          button:\n            link:\n            text:\n          reversed_layout: false\n      - label: Video Component\n        tags:\n          - image\n          - video\n        value:\n          image_path:\n          videoUrl:\n```"
+        },
+        "groups": {
+          "description": "This key defines the order and custom grouping for inputs within a Structure.\n\nThe value is an array of group objects. Each group object can contain a `heading`, `comment`, `collapsed`, and `inputs` array.\n\n## Examples\n\nIn this example, we want to separate the inputs into two groups with descriptive headings: `title` and `subtitle` under the `Titles` heading, and `author` under the `Details` heading.\n\n```yaml\n_structures:\n  article_information:\n    values:\n      - label: Blog\n        value:\n          title:\n          subtitle:\n          author:\n        groups:\n          - heading: Titles\n            inputs:\n              - title\n              - subtitle\n          - heading: Details\n            inputs:\n              - author\n```",
+          "type": "array",
+          "items": {
+            "type": "object",
+            "properties": {
+              "heading": {
+                "description": "This key defines the main text for the group shown when collapsed or expanded.\n\nThe value is a string that specifies the heading text displayed for the group.\n\n## Examples\n\nIn this example, we have configured a group heading to organize structure inputs under the \"Titles\" heading.\n\n```yaml\n_structures:\n  article_information:\n    values:\n      - label: Blog\n        value:\n          title:\n          subtitle:\n          author:\n        groups:\n          - heading: Titles\n            inputs:\n              - title\n              - subtitle\n          - heading: Details\n            inputs:\n              - author\n```",
+                "type": "string",
+                "documented": true,
+                "title": "heading",
+                "markdownDescription": "This key defines the main text for the group shown when collapsed or expanded.\n\nThe value is a string that specifies the heading text displayed for the group.\n\n## Examples\n\nIn this example, we have configured a group heading to organize structure inputs under the \"Titles\" heading.\n\n```yaml\n_structures:\n  article_information:\n    values:\n      - label: Blog\n        value:\n          title:\n          subtitle:\n          author:\n        groups:\n          - heading: Titles\n            inputs:\n              - title\n              - subtitle\n          - heading: Details\n            inputs:\n              - author\n```"
+              },
+              "comment": {
+                "description": "This key defines the subtext displayed below the `heading` for a group.\n\nThe value is a string that supports a limited set of Markdown: links, bold, italic, subscript, superscript, and inline code elements are allowed.\n\n## Examples\n\nIn this example, we have configured a group comment with Markdown formatting to provide additional context below the heading.\n\n```yaml\n_structures:\n  article_information:\n    values:\n      - label: Blog\n        value:\n          title:\n          subtitle:\n          author:\n        groups:\n          - heading: Titles\n            comment: Make these SEO-friendly\n            inputs:\n              - title\n              - subtitle\n          - heading: Details\n            inputs:\n              - author\n```",
+                "type": "string",
+                "documented": true,
+                "title": "comment",
+                "markdownDescription": "This key defines the subtext displayed below the `heading` for a group.\n\nThe value is a string that supports a limited set of Markdown: links, bold, italic, subscript, superscript, and inline code elements are allowed.\n\n## Examples\n\nIn this example, we have configured a group comment with Markdown formatting to provide additional context below the heading.\n\n```yaml\n_structures:\n  article_information:\n    values:\n      - label: Blog\n        value:\n          title:\n          subtitle:\n          author:\n        groups:\n          - heading: Titles\n            comment: Make these SEO-friendly\n            inputs:\n              - title\n              - subtitle\n          - heading: Details\n            inputs:\n              - author\n```"
+              },
+              "collapsed": {
+                "description": "This key defines whether a group is collapsed or expanded when first viewed.\n\nThe value is a boolean. When `true`, CloudCannon displays the group in a collapsed state. When `false`, CloudCannon displays the group in an expanded state.\n\nBy default, CloudCannon displays groups in an expanded state.\n\n## Examples\n\nIn this example, we have configured the \"Details\" group to be collapsed by default.\n\n```yaml\n_structures:\n  article_information:\n    values:\n      - label: Blog\n        value:\n          title:\n          subtitle:\n          author:\n        groups:\n          - heading: Titles\n            collapsed: true\n            inputs:\n              - title\n              - subtitle\n          - heading: Details\n            inputs:\n              - author\n```",
+                "default": false,
+                "type": "boolean",
+                "documented": true,
+                "title": "collapsed",
+                "markdownDescription": "This key defines whether a group is collapsed or expanded when first viewed.\n\nThe value is a boolean. When `true`, CloudCannon displays the group in a collapsed state. When `false`, CloudCannon displays the group in an expanded state.\n\nBy default, CloudCannon displays groups in an expanded state.\n\n## Examples\n\nIn this example, we have configured the \"Details\" group to be collapsed by default.\n\n```yaml\n_structures:\n  article_information:\n    values:\n      - label: Blog\n        value:\n          title:\n          subtitle:\n          author:\n        groups:\n          - heading: Titles\n            collapsed: true\n            inputs:\n              - title\n              - subtitle\n          - heading: Details\n            inputs:\n              - author\n```"
+              },
+              "inputs": {
+                "description": "This key defines which inputs are included in a group within a structure value.\n\nThe value is an array of input key name strings that specify which inputs belong to this group.\n\n## Examples\n\nIn this example, we have configured a group to include the `title` and `subtitle` inputs.\n\n```yaml\n_structures:\n  article_information:\n    values:\n      - label: Blog\n        value:\n          title:\n          subtitle:\n          author:\n        groups:\n          - heading: Titles\n            inputs:\n              - title\n              - subtitle\n          - heading: Details\n            inputs:\n              - author\n```",
+                "type": "array",
+                "items": {
+                  "type": "string",
+                  "documented": true,
+                  "title": "inputs[*]",
+                  "description": "This key represents an individual input key name string in the `values[*].groups[*].inputs` array.\n\nThe value is a string that specifies the key name of an input to include in a group within a structure value.\n\n## Examples\n\nIn this example, we have configured a group to include the `title` input.\n\n```yaml\n_structures:\n  article_information:\n    values:\n      - label: Blog\n        value:\n          title:\n          subtitle:\n          author:\n        groups:\n          - heading: Titles\n            inputs:\n              - title\n              - subtitle\n          - heading: Details\n            inputs:\n              - author\n```",
+                  "markdownDescription": "This key represents an individual input key name string in the `values[*].groups[*].inputs` array.\n\nThe value is a string that specifies the key name of an input to include in a group within a structure value.\n\n## Examples\n\nIn this example, we have configured a group to include the `title` input.\n\n```yaml\n_structures:\n  article_information:\n    values:\n      - label: Blog\n        value:\n          title:\n          subtitle:\n          author:\n        groups:\n          - heading: Titles\n            inputs:\n              - title\n              - subtitle\n          - heading: Details\n            inputs:\n              - author\n```"
+                },
+                "documented": true,
+                "title": "inputs",
+                "markdownDescription": "This key defines which inputs are included in a group within a structure value.\n\nThe value is an array of input key name strings that specify which inputs belong to this group.\n\n## Examples\n\nIn this example, we have configured a group to include the `title` and `subtitle` inputs.\n\n```yaml\n_structures:\n  article_information:\n    values:\n      - label: Blog\n        value:\n          title:\n          subtitle:\n          author:\n        groups:\n          - heading: Titles\n            inputs:\n              - title\n              - subtitle\n          - heading: Details\n            inputs:\n              - author\n```"
+              },
+              "documentation": {
+                "description": "Provides a custom link for documentation for editors shown above the collection file list.",
+                "allOf": [
+                  {
+                    "$ref": "#/definitions/type.documentation"
+                  }
+                ],
+                "documented": false,
+                "title": "documentation",
+                "markdownDescription": "Provides a custom link for documentation for editors shown above the collection file list."
+              }
+            },
+            "additionalProperties": false,
+            "documented": true,
+            "title": "groups[*]",
+            "description": "This key represents an individual group object in the `values[*].groups` array.\n\nThe value is an object that groups inputs together within a structure value without changing the data structure. Each group typically contains a `heading` and `inputs` array.\n\n## Examples\n\nIn this example, we have configured a group with a heading and inputs array to organize structure inputs.\n\n```yaml\n_structures:\n  article_information:\n    values:\n      - label: Blog\n        value:\n          title:\n          subtitle:\n          author:\n        groups:\n          - heading: Titles\n            inputs:\n              - title\n              - subtitle\n          - heading: Details\n            inputs:\n              - author\n```",
+            "markdownDescription": "This key represents an individual group object in the `values[*].groups` array.\n\nThe value is an object that groups inputs together within a structure value without changing the data structure. Each group typically contains a `heading` and `inputs` array.\n\n## Examples\n\nIn this example, we have configured a group with a heading and inputs array to organize structure inputs.\n\n```yaml\n_structures:\n  article_information:\n    values:\n      - label: Blog\n        value:\n          title:\n          subtitle:\n          author:\n        groups:\n          - heading: Titles\n            inputs:\n              - title\n              - subtitle\n          - heading: Details\n            inputs:\n              - author\n```"
+          },
+          "documented": true,
+          "title": "groups",
+          "markdownDescription": "This key defines the order and custom grouping for inputs within a Structure.\n\nThe value is an array of group objects. Each group object can contain a `heading`, `comment`, `collapsed`, and `inputs` array.\n\n## Examples\n\nIn this example, we want to separate the inputs into two groups with descriptive headings: `title` and `subtitle` under the `Titles` heading, and `author` under the `Details` heading.\n\n```yaml\n_structures:\n  article_information:\n    values:\n      - label: Blog\n        value:\n          title:\n          subtitle:\n          author:\n        groups:\n          - heading: Titles\n            inputs:\n              - title\n              - subtitle\n          - heading: Details\n            inputs:\n              - author\n```"
+        },
+        "place_groups_below": {
+          "description": "This key defines which order input groups and ungrouped inputs appear in.",
+          "default": false,
+          "type": "boolean",
+          "documented": true,
+          "title": "place_groups_below",
+          "markdownDescription": "This key defines which order input groups and ungrouped inputs appear in."
+        },
+        "tabbed": {
+          "description": "This key toggles whether CloudCannon should create tabs in the Data Editor if you have two layers of nested object within your Structure.\n\nSetting this key to `true` will create tabs in the Data Editor for two layers of nested objects within your Structure.\n\nBy default, this key is `false` (i.e., Object and Array inputs using this Structure option are not tabbed).\n\n## Examples\n\nIn this example, we want the `content` and `style` keys in our Structure to be tabs at the top of the Data Editor, with the `title` and `text`, and `color` and `font` keys nested within those tabs respectively.\n\n```yaml\n_structures:\n  components:\n    values:\n      - label: Component\n        tabbed: true\n        value:\n          content:\n            title:\n            text:\n          style:\n            color:\n            font:\n```",
+          "default": false,
+          "type": "boolean",
+          "documented": true,
+          "title": "tabbed",
+          "markdownDescription": "This key toggles whether CloudCannon should create tabs in the Data Editor if you have two layers of nested object within your Structure.\n\nSetting this key to `true` will create tabs in the Data Editor for two layers of nested objects within your Structure.\n\nBy default, this key is `false` (i.e., Object and Array inputs using this Structure option are not tabbed).\n\n## Examples\n\nIn this example, we want the `content` and `style` keys in our Structure to be tabs at the top of the Data Editor, with the `title` and `text`, and `color` and `font` keys nested within those tabs respectively.\n\n```yaml\n_structures:\n  components:\n    values:\n      - label: Component\n        tabbed: true\n        value:\n          content:\n            title:\n            text:\n          style:\n            color:\n            font:\n```"
+        },
+        "value": {
+          "description": "This key defines which nested inputs the Structure value should add to an Object or Array input.\n\nYou must define this key for the Structure value to function.\n\nNested keys can be any [input](https://cloudcannon.com/documentation/articles/what-are-inputs/) you require in your Object or Array.\n\nFor more information, please read our documentation on [configuring an Object input](https://cloudcannon.com/documentation/articles/configure-an-object-input/) and\n[configuring and Array input](https://cloudcannon.com/documentation/articles/configure-an-array-input/).\n\n## Examples\n\nIn this example we want to populate the `details` Object input with the nested keys `title`, `subtitle`, and `author` we have defined under the `values.value` key.\n\n```yaml\n_structures:\n  article_information:\n    values:\n      - label: Blog\n        value:\n          title:\n          subtitle:\n          author:\n_inputs:\n  details:\n    type: object\n    options:\n      structures: _structures.article_information\n```",
+          "documented": true,
+          "title": "value",
+          "markdownDescription": "This key defines which nested inputs the Structure value should add to an Object or Array input.\n\nYou must define this key for the Structure value to function.\n\nNested keys can be any [input](https://cloudcannon.com/documentation/articles/what-are-inputs/) you require in your Object or Array.\n\nFor more information, please read our documentation on [configuring an Object input](https://cloudcannon.com/documentation/articles/configure-an-object-input/) and\n[configuring and Array input](https://cloudcannon.com/documentation/articles/configure-an-array-input/).\n\n## Examples\n\nIn this example we want to populate the `details` Object input with the nested keys `title`, `subtitle`, and `author` we have defined under the `values.value` key.\n\n```yaml\n_structures:\n  article_information:\n    values:\n      - label: Blog\n        value:\n          title:\n          subtitle:\n          author:\n_inputs:\n  details:\n    type: object\n    options:\n      structures: _structures.article_information\n```"
+        },
+        "description": {
+          "description": "This key defines short descriptive text for editors shown in the Data Editor for expanded values matching this Structure value.\n\nHas no default.\n\nSupports a limited set of Markdown: links, bold, italic, subscript, superscript, and inline code elements are allowed.",
+          "type": "string",
+          "documented": true,
+          "title": "description",
+          "markdownDescription": "This key defines short descriptive text for editors shown in the Data Editor for expanded values matching this Structure value.\n\nHas no default.\n\nSupports a limited set of Markdown: links, bold, italic, subscript, superscript, and inline code elements are allowed."
+        },
+        "documentation": {
+          "description": "Provides a custom link for documentation for editors shown in the Data Editor for expanded values matching this Structure value. Has no default.",
+          "allOf": [
+            {
+              "$ref": "#/definitions/type.documentation"
+            }
+          ],
+          "documented": false,
+          "title": "documentation",
+          "markdownDescription": "Provides a custom link for documentation for editors shown in the Data Editor for expanded values matching this Structure value. Has no default."
         }
       },
       "required": [
-        "values"
+        "value"
       ],
       "additionalProperties": false,
+      "title": "Structure Value",
+      "description": "This key represents a single value option within a structure, defining the data format and appearance for content editors.",
       "documented": true,
-      "markdownDescription": "This key defines data formats when adding new items to arrays and objects, with options for how editors choose from available values."
+      "markdownDescription": "This key represents a single value option within a structure, defining the data format and appearance for content editors."
+    },
+    "type._inputs_from_glob": {
+      "type": "array",
+      "items": {
+        "type": "string",
+        "documented": true,
+        "title": "_inputs_from_glob[*]",
+        "description": "This key represents an individual glob pattern string in the `_inputs_from_glob` array.\n\nThe value is a string that specifies a file path pattern relative to the root of your repository. The path must end in the file extension `.cloudcannon.inputs.yml`.\n\n## Examples\n\nIn this example, we have several *Input Configuration Files* in the `.cloudcannon/inputs/` folder, with each file containing multiple *Input* definitions. The value of the `_inputs_from_glob` key tells CloudCannon to only use the `seo.cloudcannon.inputs.yml` and `blog-details.cloudcannon.inputs.yml` files in that folder.\n\n```yaml\ncollections_config:\n  posts:\n    path: content/posts\n    icon: event\n    inputs_from_glob:\n      - '/.cloudcannon/inputs/seo.cloudcannon.inputs.yml'\n      - '/.cloudcannon/inputs/blog-details.cloudcannon.inputs.yml'\n```",
+        "markdownDescription": "This key represents an individual glob pattern string in the `_inputs_from_glob` array.\n\nThe value is a string that specifies a file path pattern relative to the root of your repository. The path must end in the file extension `.cloudcannon.inputs.yml`.\n\n## Examples\n\nIn this example, we have several *Input Configuration Files* in the `.cloudcannon/inputs/` folder, with each file containing multiple *Input* definitions. The value of the `_inputs_from_glob` key tells CloudCannon to only use the `seo.cloudcannon.inputs.yml` and `blog-details.cloudcannon.inputs.yml` files in that folder.\n\n```yaml\ncollections_config:\n  posts:\n    path: content/posts\n    icon: event\n    inputs_from_glob:\n      - '/.cloudcannon/inputs/seo.cloudcannon.inputs.yml'\n      - '/.cloudcannon/inputs/blog-details.cloudcannon.inputs.yml'\n```"
+      },
+      "documented": true,
+      "title": "_inputs_from_glob",
+      "description": "This key defines globs that filter which files CloudCannon should use for *Input* configuration.\n\nValues in this array are relative to the root of your repository (i.e., `/`, not the value of `source`) and must end in the file extension\n`.cloudcannon.inputs.yml`.\n\nYou can use this key anywhere you would use the `_inputs` key in the configuration cascade.\n\nThis key has no default.\n\n## Examples\n\nIn this example, we have several *Input Configuration Files* in the `.cloudcannon/inputs/` folder, with each file containing multiple *Input* definitions. The value of the `_inputs_from_glob` key tells CloudCannon to only use the `seo.cloudcannon.inputs.yml` and `blog-details.cloudcannon.inputs.yml` files in that folder.\n\n```yaml\ncollections_config:\n  posts:\n    path: content/posts\n    icon: event\n    inputs_from_glob:\n      - '/.cloudcannon/inputs/seo.cloudcannon.inputs.yml'\n      - '/.cloudcannon/inputs/blogDetails.cloudcannon.inputs.yml'\n```\n\n```yaml\nseo_title:\n  type: text\n  options:\n    required: true\n    max_length: 50\nseo_description:\n  type: textarea\n  options:\n    show_count: true\n    required: true\n    max_length: 125\nseo_image:\n  type: image\n  options:\n    path:\n      uploads: images\n    accepts_mime_types:\n      - image/png\n      - image/jpeg\n    required: true\n    pattern: (?i)\\.(jpe?g|png)$\n    pattern_message: Please select a JPG or PNG image file\n```",
+      "markdownDescription": "This key defines globs that filter which files CloudCannon should use for *Input* configuration.\n\nValues in this array are relative to the root of your repository (i.e., `/`, not the value of `source`) and must end in the file extension\n`.cloudcannon.inputs.yml`.\n\nYou can use this key anywhere you would use the `_inputs` key in the configuration cascade.\n\nThis key has no default.\n\n## Examples\n\nIn this example, we have several *Input Configuration Files* in the `.cloudcannon/inputs/` folder, with each file containing multiple *Input* definitions. The value of the `_inputs_from_glob` key tells CloudCannon to only use the `seo.cloudcannon.inputs.yml` and `blog-details.cloudcannon.inputs.yml` files in that folder.\n\n```yaml\ncollections_config:\n  posts:\n    path: content/posts\n    icon: event\n    inputs_from_glob:\n      - '/.cloudcannon/inputs/seo.cloudcannon.inputs.yml'\n      - '/.cloudcannon/inputs/blogDetails.cloudcannon.inputs.yml'\n```\n\n```yaml\nseo_title:\n  type: text\n  options:\n    required: true\n    max_length: 50\nseo_description:\n  type: textarea\n  options:\n    show_count: true\n    required: true\n    max_length: 125\nseo_image:\n  type: image\n  options:\n    path:\n      uploads: images\n    accepts_mime_types:\n      - image/png\n      - image/jpeg\n    required: true\n    pattern: (?i)\\.(jpe?g|png)$\n    pattern_message: Please select a JPG or PNG image file\n```"
+    },
+    "type._select_data": {
+      "type": "object",
+      "propertyNames": {
+        "type": "string"
+      },
+      "additionalProperties": {
+        "anyOf": [
+          {
+            "type": "array",
+            "items": {
+              "type": "string",
+              "documented": true,
+              "title": "*(text-array)[*]"
+            },
+            "title": "Text Array Select Data",
+            "documented": true
+          },
+          {
+            "type": "object",
+            "propertyNames": {
+              "type": "string"
+            },
+            "additionalProperties": {
+              "type": "string",
+              "documented": true,
+              "title": "*(text-object).*"
+            },
+            "title": "Text Object Select Data",
+            "documented": true
+          },
+          {
+            "type": "array",
+            "items": {
+              "type": "object",
+              "propertyNames": {
+                "type": "string"
+              },
+              "additionalProperties": {},
+              "documented": true,
+              "title": "*(object-array)[*]"
+            },
+            "title": "Object Array Select Data",
+            "documented": true
+          },
+          {
+            "type": "object",
+            "propertyNames": {
+              "type": "string"
+            },
+            "additionalProperties": {},
+            "title": "Object Select Data",
+            "documented": true
+          }
+        ],
+        "description": "This key defines data formats for populating select and multiselect input options, supporting arrays and objects.",
+        "documented": true,
+        "title": "_select_data.*",
+        "markdownDescription": "This key defines data formats for populating select and multiselect input options, supporting arrays and objects."
+      },
+      "title": "Select Data",
+      "description": "This key defines defines fixed data sets to populate Select and Multiselect inputs at a given level of the configuration cascade.\n\nThis key has no default.\n\nIf undefined at higher levels of the [configuration cascade](https://cloudcannon.com/documentation/articles/using-the-configuration-cascade/), `_select_data` will default to\nany values configured in the [CloudCannon configuration file](https://cloudcannon.com/documentation/articles/what-is-the-cloudcannon-configuration-file/).\n\nFor more information, please read our documentation on [Select and Multiselect inputs](https://cloudcannon.com/documentation/articles/what-is-a-select-input/#fixed-data-sets).\n\n## Examples\n\nIn this example, we have configured the `blog_tags` Multiselect input for the `blog` Collection.\n\n```yaml\ncollections_config:\n  blog:\n    _select_data:\n      blog_topics:\n        - Opinion\n        - Feature\n        - Resource\n```",
+      "documented": true,
+      "markdownDescription": "This key defines defines fixed data sets to populate Select and Multiselect inputs at a given level of the configuration cascade.\n\nThis key has no default.\n\nIf undefined at higher levels of the [configuration cascade](https://cloudcannon.com/documentation/articles/using-the-configuration-cascade/), `_select_data` will default to\nany values configured in the [CloudCannon configuration file](https://cloudcannon.com/documentation/articles/what-is-the-cloudcannon-configuration-file/).\n\nFor more information, please read our documentation on [Select and Multiselect inputs](https://cloudcannon.com/documentation/articles/what-is-a-select-input/#fixed-data-sets).\n\n## Examples\n\nIn this example, we have configured the `blog_tags` Multiselect input for the `blog` Collection.\n\n```yaml\ncollections_config:\n  blog:\n    _select_data:\n      blog_topics:\n        - Opinion\n        - Feature\n        - Resource\n```"
+    },
+    "type._structures": {
+      "type": "object",
+      "propertyNames": {
+        "type": "string"
+      },
+      "additionalProperties": {
+        "$ref": "#/definitions/type.structure"
+      },
+      "title": "Structures",
+      "description": "This key defines which structures are available for [Object inputs](https://cloudcannon.com/documentation/articles/what-is-an-object-input/) and [Array\ninputs](https://cloudcannon.com/documentation/articles/what-is-an-array-input/) at a given level of the configuration cascade.\n\nThis key has no default.\n\nIf undefined at higher levels of the [configuration cascade](https://cloudcannon.com/documentation/articles/using-the-configuration-cascade/), `_structures` will default to\nany values configured in the [CloudCannon configuration file](https://cloudcannon.com/documentation/articles/what-is-the-cloudcannon-configuration-file/).\n\nFor more information, please read our documentation on [structures](https://cloudcannon.com/documentation/articles/what-is-a-structure/).\n\n## Examples\n\nIn this example, we want to populate an Array input in the `blog` Collection with Related Articles, including the `name`, `description`, and `url` fields.\n\n```yaml\ncollections_config:\n  blog:\n    _structures:\n      related_articles:\n        style: select\n        values:\n          - preview:\n              text:\n                - key: name\n              subtext:\n                - key: url\n            value:\n              name:\n              description:\n              url:\n```\n\nIn this example, we want to populate an Array input with Staff members, including the `name`, `job_description`, and `profile_picture` fields for all staff types, and the `url` field for Managers only.\n\n```yaml\n_structures:\n  staff:\n    style: modal\n    hide_extra_inputs: false\n    values:\n      - value:\n          _type: Employee\n          name:\n          job_description:\n          profile_picture:\n        preview:\n          text:\n            - key: name\n            - Employee\n          subtext:\n            - key: job_description\n            - Description of position\n          image:\n            - key: profile_picture\n          icon: support_agent\n      - value:\n          _type: Manager\n          name:\n          job_description:\n          profile_picture:\n          url:\n        preview:\n          text:\n            - key: name\n            - Manager\n          subtext:\n            - key: job_description\n            - Description of position\n          image:\n            - key: profile_picture\n          icon: face\n```",
+      "documented": true,
+      "markdownDescription": "This key defines which structures are available for [Object inputs](https://cloudcannon.com/documentation/articles/what-is-an-object-input/) and [Array\ninputs](https://cloudcannon.com/documentation/articles/what-is-an-array-input/) at a given level of the configuration cascade.\n\nThis key has no default.\n\nIf undefined at higher levels of the [configuration cascade](https://cloudcannon.com/documentation/articles/using-the-configuration-cascade/), `_structures` will default to\nany values configured in the [CloudCannon configuration file](https://cloudcannon.com/documentation/articles/what-is-the-cloudcannon-configuration-file/).\n\nFor more information, please read our documentation on [structures](https://cloudcannon.com/documentation/articles/what-is-a-structure/).\n\n## Examples\n\nIn this example, we want to populate an Array input in the `blog` Collection with Related Articles, including the `name`, `description`, and `url` fields.\n\n```yaml\ncollections_config:\n  blog:\n    _structures:\n      related_articles:\n        style: select\n        values:\n          - preview:\n              text:\n                - key: name\n              subtext:\n                - key: url\n            value:\n              name:\n              description:\n              url:\n```\n\nIn this example, we want to populate an Array input with Staff members, including the `name`, `job_description`, and `profile_picture` fields for all staff types, and the `url` field for Managers only.\n\n```yaml\n_structures:\n  staff:\n    style: modal\n    hide_extra_inputs: false\n    values:\n      - value:\n          _type: Employee\n          name:\n          job_description:\n          profile_picture:\n        preview:\n          text:\n            - key: name\n            - Employee\n          subtext:\n            - key: job_description\n            - Description of position\n          image:\n            - key: profile_picture\n          icon: support_agent\n      - value:\n          _type: Manager\n          name:\n          job_description:\n          profile_picture:\n          url:\n        preview:\n          text:\n            - key: name\n            - Manager\n          subtext:\n            - key: job_description\n            - Description of position\n          image:\n            - key: profile_picture\n          icon: face\n```"
+    },
+    "type._structures_from_glob": {
+      "type": "array",
+      "items": {
+        "type": "string",
+        "documented": true,
+        "title": "_structures_from_glob[*]",
+        "description": "This key represents an individual glob pattern string in the `_structures_from_glob` array.\n\nThe value is a string that specifies a file path pattern relative to the root of your repository. The path must end in the file extension `.cloudcannon.structures.yml`.\n\n## Examples\n\nIn this example, we have several *Structure Configuration Files* in the `.cloudcannon/structures/` folder. The value of the `_structures_from_glob` key tells CloudCannon to use the `staffMembers.cloudcannon.structures.yml` file in that folder.\n\n```yaml\n_structures_from_glob:\n  - '/.cloudcannon/structures/staffMembers.cloudcannon.structures.yml'\n```",
+        "markdownDescription": "This key represents an individual glob pattern string in the `_structures_from_glob` array.\n\nThe value is a string that specifies a file path pattern relative to the root of your repository. The path must end in the file extension `.cloudcannon.structures.yml`.\n\n## Examples\n\nIn this example, we have several *Structure Configuration Files* in the `.cloudcannon/structures/` folder. The value of the `_structures_from_glob` key tells CloudCannon to use the `staffMembers.cloudcannon.structures.yml` file in that folder.\n\n```yaml\n_structures_from_glob:\n  - '/.cloudcannon/structures/staffMembers.cloudcannon.structures.yml'\n```"
+      },
+      "documented": true,
+      "title": "_structures_from_glob",
+      "description": "This key defines globs that filter which files CloudCannon should use for *Structure* configuration.\n\nValues in this array are relative to the root of your repository (i.e., `/`, not the value of `source`) and must end in the file extension\n`.cloudcannon.structures.yml`.\n\nYou can use this key anywhere you would use the `_structures` key in the configuration cascade.\n\nPlease see our documentation on [values_from_glob](https://cloudcannon.com/documentation/developer-reference/configuration-file/types/structure/values_from_glob/) for defining individual\n*Structure* values in a split *Configuration File*.\n\nThis key has no default.\n\n## Examples\n\nIn this example, we have several *Structure Configuration Files* in the `.cloudcannon/structures/` folder. The value of the `_structures_from_glob` key tells CloudCannon to use the `staffMembers.cloudcannon.structures.yml` file in that folder.\n\n```yaml\n_structures_from_glob:\n  - '/.cloudcannon/structures/staffMembers.cloudcannon.structures.yml'\n```\n\n```yaml\nstaff:\n  style: modal\n  values:\n    - label: Employee\n      value:\n        name:\n        job_description:\n        profile_picture:\n    - label: Manager\n      value:\n        name:\n        job_description:\n        profile_picture:\n        url:\n```",
+      "markdownDescription": "This key defines globs that filter which files CloudCannon should use for *Structure* configuration.\n\nValues in this array are relative to the root of your repository (i.e., `/`, not the value of `source`) and must end in the file extension\n`.cloudcannon.structures.yml`.\n\nYou can use this key anywhere you would use the `_structures` key in the configuration cascade.\n\nPlease see our documentation on [values_from_glob](https://cloudcannon.com/documentation/developer-reference/configuration-file/types/structure/values_from_glob/) for defining individual\n*Structure* values in a split *Configuration File*.\n\nThis key has no default.\n\n## Examples\n\nIn this example, we have several *Structure Configuration Files* in the `.cloudcannon/structures/` folder. The value of the `_structures_from_glob` key tells CloudCannon to use the `staffMembers.cloudcannon.structures.yml` file in that folder.\n\n```yaml\n_structures_from_glob:\n  - '/.cloudcannon/structures/staffMembers.cloudcannon.structures.yml'\n```\n\n```yaml\nstaff:\n  style: modal\n  values:\n    - label: Employee\n      value:\n        name:\n        job_description:\n        profile_picture:\n    - label: Manager\n      value:\n        name:\n        job_description:\n        profile_picture:\n        url:\n```"
     },
     "entries_comment": {
       "description": "This key defines the subtitle text above the key input when adding or renaming entries within a mutable *Object Input*.\n\nThe value is a string that supports a limited selection of Markdown formatting: links, bold, italic, subscript, superscript, and inline code elements are allowed.\n\nAvailable for Mutable Objects only.\n\n## Examples\n\nIn this example, we have configured a comment with Markdown formatting to provide help text above the key input.\n\n```yaml\n_inputs:\n  metadata:\n    type: object\n    options:\n      allow_create: true\n      entries:\n        comment: Key names should be **lowercase** and use underscores (e.g., `article_title`)\n```",
@@ -9531,8 +9637,6 @@
       "markdownDescription": "This key defines the subtitle text above the key input when adding or renaming entries within a mutable *Object Input*.\n\nThe value is a string that supports a limited selection of Markdown formatting: links, bold, italic, subscript, superscript, and inline code elements are allowed.\n\nAvailable for Mutable Objects only.\n\n## Examples\n\nIn this example, we have configured a comment with Markdown formatting to provide help text above the key input.\n\n```yaml\n_inputs:\n  metadata:\n    type: object\n    options:\n      allow_create: true\n      entries:\n        comment: Key names should be **lowercase** and use underscores (e.g., `article_title`)\n```"
     },
     "ArrayInput": {
-      "title": "Array Input",
-      "description": "This key defines a user interface for lists of inputs or input groups.",
       "type": "object",
       "properties": {
         "comment": {
@@ -9577,15 +9681,14 @@
           "$ref": "#/definitions/type._inputs.*.cascade"
         },
         "type": {
-          "title": "Type",
-          "description": "This key defines the input type, which controls how this input appears and behaves.",
           "type": "string",
           "const": "array",
+          "title": "Type",
+          "description": "This key defines the input type, which controls how this input appears and behaves.",
           "documented": true,
           "markdownDescription": "This key defines the input type, which controls how this input appears and behaves."
         },
         "options": {
-          "description": "This key defines options that are specific to Array Inputs.",
           "type": "object",
           "properties": {
             "required": {
@@ -9646,6 +9749,7 @@
             }
           },
           "additionalProperties": false,
+          "description": "This key defines options that are specific to Array Inputs.",
           "documented": true,
           "title": "options",
           "markdownDescription": "This key defines options that are specific to Array Inputs."
@@ -9655,6 +9759,8 @@
         "type"
       ],
       "additionalProperties": false,
+      "title": "Array Input",
+      "description": "This key defines a user interface for lists of inputs or input groups.",
       "documented": true,
       "markdownDescription": "This key defines a user interface for lists of inputs or input groups."
     },
@@ -9683,9 +9789,6 @@
       "markdownDescription": "This key toggles whether CloudCannon will hide the controls on each item for moving them.\n\nSetting this key to `true` will hide the controls for moving items.\n\nBy default, this key is `false` (i.e., the controls for moving items are displayed)."
     },
     "AutoInput": {
-      "title": "Automatic Input",
-      "description": "Provides a default user interface based on the data contained.",
-      "excludeFromDocumentation": true,
       "type": "object",
       "properties": {
         "comment": {
@@ -9730,10 +9833,10 @@
           "$ref": "#/definitions/type._inputs.*.cascade"
         },
         "type": {
-          "title": "Type",
-          "description": "Sets an input type, which controls how this input appears and behaves.",
           "type": "string",
           "const": "auto",
+          "title": "Type",
+          "description": "Sets an input type, which controls how this input appears and behaves.",
           "documented": false,
           "markdownDescription": "Sets an input type, which controls how this input appears and behaves."
         },
@@ -9748,13 +9851,13 @@
         "type"
       ],
       "additionalProperties": false,
+      "title": "Automatic Input",
+      "description": "Provides a default user interface based on the data contained.",
+      "excludeFromDocumentation": true,
       "documented": false,
       "markdownDescription": "Provides a default user interface based on the data contained."
     },
     "UnknownInput": {
-      "title": "Unknown Input",
-      "description": "Provides a default user interface based on the data contained.",
-      "excludeFromDocumentation": true,
       "type": "object",
       "properties": {
         "comment": {
@@ -9806,115 +9909,13 @@
         }
       },
       "additionalProperties": false,
+      "title": "Unknown Input",
+      "description": "Provides a default user interface based on the data contained.",
+      "excludeFromDocumentation": true,
       "documented": false,
       "markdownDescription": "Provides a default user interface based on the data contained."
-    },
-    "type._inputs_from_glob": {
-      "type": "array",
-      "items": {
-        "type": "string",
-        "documented": true,
-        "title": "_inputs_from_glob[*]",
-        "description": "This key represents an individual glob pattern string in the `_inputs_from_glob` array.\n\nThe value is a string that specifies a file path pattern relative to the root of your repository. The path must end in the file extension `.cloudcannon.inputs.yml`.\n\n## Examples\n\nIn this example, we have several *Input Configuration Files* in the `.cloudcannon/inputs/` folder, with each file containing multiple *Input* definitions. The value of the `_inputs_from_glob` key tells CloudCannon to only use the `seo.cloudcannon.inputs.yml` and `blog-details.cloudcannon.inputs.yml` files in that folder.\n\n```yaml\ncollections_config:\n  posts:\n    path: content/posts\n    icon: event\n    inputs_from_glob:\n      - '/.cloudcannon/inputs/seo.cloudcannon.inputs.yml'\n      - '/.cloudcannon/inputs/blog-details.cloudcannon.inputs.yml'\n```",
-        "markdownDescription": "This key represents an individual glob pattern string in the `_inputs_from_glob` array.\n\nThe value is a string that specifies a file path pattern relative to the root of your repository. The path must end in the file extension `.cloudcannon.inputs.yml`.\n\n## Examples\n\nIn this example, we have several *Input Configuration Files* in the `.cloudcannon/inputs/` folder, with each file containing multiple *Input* definitions. The value of the `_inputs_from_glob` key tells CloudCannon to only use the `seo.cloudcannon.inputs.yml` and `blog-details.cloudcannon.inputs.yml` files in that folder.\n\n```yaml\ncollections_config:\n  posts:\n    path: content/posts\n    icon: event\n    inputs_from_glob:\n      - '/.cloudcannon/inputs/seo.cloudcannon.inputs.yml'\n      - '/.cloudcannon/inputs/blog-details.cloudcannon.inputs.yml'\n```"
-      },
-      "documented": true,
-      "title": "_inputs_from_glob",
-      "description": "This key defines globs that filter which files CloudCannon should use for *Input* configuration.\n\nValues in this array are relative to the root of your repository (i.e., `/`, not the value of `source`) and must end in the file extension\n`.cloudcannon.inputs.yml`.\n\nYou can use this key anywhere you would use the `_inputs` key in the configuration cascade.\n\nThis key has no default.\n\n## Examples\n\nIn this example, we have several *Input Configuration Files* in the `.cloudcannon/inputs/` folder, with each file containing multiple *Input* definitions. The value of the `_inputs_from_glob` key tells CloudCannon to only use the `seo.cloudcannon.inputs.yml` and `blog-details.cloudcannon.inputs.yml` files in that folder.\n\n```yaml\ncollections_config:\n  posts:\n    path: content/posts\n    icon: event\n    inputs_from_glob:\n      - '/.cloudcannon/inputs/seo.cloudcannon.inputs.yml'\n      - '/.cloudcannon/inputs/blogDetails.cloudcannon.inputs.yml'\n```\n\n```yaml\nseo_title:\n  type: text\n  options:\n    required: true\n    max_length: 50\nseo_description:\n  type: textarea\n  options:\n    show_count: true\n    required: true\n    max_length: 125\nseo_image:\n  type: image\n  options:\n    path:\n      uploads: images\n    accepts_mime_types:\n      - image/png\n      - image/jpeg\n    required: true\n    pattern: (?i)\\.(jpe?g|png)$\n    pattern_message: Please select a JPG or PNG image file\n```",
-      "markdownDescription": "This key defines globs that filter which files CloudCannon should use for *Input* configuration.\n\nValues in this array are relative to the root of your repository (i.e., `/`, not the value of `source`) and must end in the file extension\n`.cloudcannon.inputs.yml`.\n\nYou can use this key anywhere you would use the `_inputs` key in the configuration cascade.\n\nThis key has no default.\n\n## Examples\n\nIn this example, we have several *Input Configuration Files* in the `.cloudcannon/inputs/` folder, with each file containing multiple *Input* definitions. The value of the `_inputs_from_glob` key tells CloudCannon to only use the `seo.cloudcannon.inputs.yml` and `blog-details.cloudcannon.inputs.yml` files in that folder.\n\n```yaml\ncollections_config:\n  posts:\n    path: content/posts\n    icon: event\n    inputs_from_glob:\n      - '/.cloudcannon/inputs/seo.cloudcannon.inputs.yml'\n      - '/.cloudcannon/inputs/blogDetails.cloudcannon.inputs.yml'\n```\n\n```yaml\nseo_title:\n  type: text\n  options:\n    required: true\n    max_length: 50\nseo_description:\n  type: textarea\n  options:\n    show_count: true\n    required: true\n    max_length: 125\nseo_image:\n  type: image\n  options:\n    path:\n      uploads: images\n    accepts_mime_types:\n      - image/png\n      - image/jpeg\n    required: true\n    pattern: (?i)\\.(jpe?g|png)$\n    pattern_message: Please select a JPG or PNG image file\n```"
-    },
-    "type._select_data": {
-      "title": "Select Data",
-      "description": "This key defines defines fixed data sets to populate Select and Multiselect inputs at a given level of the configuration cascade.\n\nThis key has no default.\n\nIf undefined at higher levels of the [configuration cascade](https://cloudcannon.com/documentation/articles/using-the-configuration-cascade/), `_select_data` will default to\nany values configured in the [CloudCannon configuration file](https://cloudcannon.com/documentation/articles/what-is-the-cloudcannon-configuration-file/).\n\nFor more information, please read our documentation on [Select and Multiselect inputs](https://cloudcannon.com/documentation/articles/what-is-a-select-input/#fixed-data-sets).\n\n## Examples\n\nIn this example, we have configured the `blog_tags` Multiselect input for the `blog` Collection.\n\n```yaml\ncollections_config:\n  blog:\n    _select_data:\n      blog_topics:\n        - Opinion\n        - Feature\n        - Resource\n```",
-      "type": "object",
-      "propertyNames": {
-        "type": "string"
-      },
-      "additionalProperties": {
-        "description": "This key defines data formats for populating select and multiselect input options, supporting arrays and objects.",
-        "anyOf": [
-          {
-            "title": "Text Array Select Data",
-            "type": "array",
-            "items": {
-              "type": "string",
-              "documented": true,
-              "title": "*(text-array)[*]"
-            },
-            "documented": true
-          },
-          {
-            "title": "Text Object Select Data",
-            "type": "object",
-            "propertyNames": {
-              "type": "string"
-            },
-            "additionalProperties": {
-              "type": "string",
-              "documented": true,
-              "title": "*(text-object).*"
-            },
-            "documented": true
-          },
-          {
-            "title": "Object Array Select Data",
-            "type": "array",
-            "items": {
-              "type": "object",
-              "propertyNames": {
-                "type": "string"
-              },
-              "additionalProperties": {},
-              "documented": true,
-              "title": "*(object-array)[*]"
-            },
-            "documented": true
-          },
-          {
-            "title": "Object Select Data",
-            "type": "object",
-            "propertyNames": {
-              "type": "string"
-            },
-            "additionalProperties": {},
-            "documented": true
-          }
-        ],
-        "documented": true,
-        "title": "_select_data.*",
-        "markdownDescription": "This key defines data formats for populating select and multiselect input options, supporting arrays and objects."
-      },
-      "documented": true,
-      "markdownDescription": "This key defines defines fixed data sets to populate Select and Multiselect inputs at a given level of the configuration cascade.\n\nThis key has no default.\n\nIf undefined at higher levels of the [configuration cascade](https://cloudcannon.com/documentation/articles/using-the-configuration-cascade/), `_select_data` will default to\nany values configured in the [CloudCannon configuration file](https://cloudcannon.com/documentation/articles/what-is-the-cloudcannon-configuration-file/).\n\nFor more information, please read our documentation on [Select and Multiselect inputs](https://cloudcannon.com/documentation/articles/what-is-a-select-input/#fixed-data-sets).\n\n## Examples\n\nIn this example, we have configured the `blog_tags` Multiselect input for the `blog` Collection.\n\n```yaml\ncollections_config:\n  blog:\n    _select_data:\n      blog_topics:\n        - Opinion\n        - Feature\n        - Resource\n```"
-    },
-    "type._structures": {
-      "title": "Structures",
-      "description": "This key defines which structures are available for [Object inputs](https://cloudcannon.com/documentation/articles/what-is-an-object-input/) and [Array\ninputs](https://cloudcannon.com/documentation/articles/what-is-an-array-input/) at a given level of the configuration cascade.\n\nThis key has no default.\n\nIf undefined at higher levels of the [configuration cascade](https://cloudcannon.com/documentation/articles/using-the-configuration-cascade/), `_structures` will default to\nany values configured in the [CloudCannon configuration file](https://cloudcannon.com/documentation/articles/what-is-the-cloudcannon-configuration-file/).\n\nFor more information, please read our documentation on [structures](https://cloudcannon.com/documentation/articles/what-is-a-structure/).\n\n## Examples\n\nIn this example, we want to populate an Array input in the `blog` Collection with Related Articles, including the `name`, `description`, and `url` fields.\n\n```yaml\ncollections_config:\n  blog:\n    _structures:\n      related_articles:\n        style: select\n        values:\n          - preview:\n              text:\n                - key: name\n              subtext:\n                - key: url\n            value:\n              name:\n              description:\n              url:\n```\n\nIn this example, we want to populate an Array input with Staff members, including the `name`, `job_description`, and `profile_picture` fields for all staff types, and the `url` field for Managers only.\n\n```yaml\n_structures:\n  staff:\n    style: modal\n    hide_extra_inputs: false\n    values:\n      - value:\n          _type: Employee\n          name:\n          job_description:\n          profile_picture:\n        preview:\n          text:\n            - key: name\n            - Employee\n          subtext:\n            - key: job_description\n            - Description of position\n          image:\n            - key: profile_picture\n          icon: support_agent\n      - value:\n          _type: Manager\n          name:\n          job_description:\n          profile_picture:\n          url:\n        preview:\n          text:\n            - key: name\n            - Manager\n          subtext:\n            - key: job_description\n            - Description of position\n          image:\n            - key: profile_picture\n          icon: face\n```",
-      "type": "object",
-      "propertyNames": {
-        "type": "string"
-      },
-      "additionalProperties": {
-        "$ref": "#/definitions/type.structure"
-      },
-      "documented": true,
-      "markdownDescription": "This key defines which structures are available for [Object inputs](https://cloudcannon.com/documentation/articles/what-is-an-object-input/) and [Array\ninputs](https://cloudcannon.com/documentation/articles/what-is-an-array-input/) at a given level of the configuration cascade.\n\nThis key has no default.\n\nIf undefined at higher levels of the [configuration cascade](https://cloudcannon.com/documentation/articles/using-the-configuration-cascade/), `_structures` will default to\nany values configured in the [CloudCannon configuration file](https://cloudcannon.com/documentation/articles/what-is-the-cloudcannon-configuration-file/).\n\nFor more information, please read our documentation on [structures](https://cloudcannon.com/documentation/articles/what-is-a-structure/).\n\n## Examples\n\nIn this example, we want to populate an Array input in the `blog` Collection with Related Articles, including the `name`, `description`, and `url` fields.\n\n```yaml\ncollections_config:\n  blog:\n    _structures:\n      related_articles:\n        style: select\n        values:\n          - preview:\n              text:\n                - key: name\n              subtext:\n                - key: url\n            value:\n              name:\n              description:\n              url:\n```\n\nIn this example, we want to populate an Array input with Staff members, including the `name`, `job_description`, and `profile_picture` fields for all staff types, and the `url` field for Managers only.\n\n```yaml\n_structures:\n  staff:\n    style: modal\n    hide_extra_inputs: false\n    values:\n      - value:\n          _type: Employee\n          name:\n          job_description:\n          profile_picture:\n        preview:\n          text:\n            - key: name\n            - Employee\n          subtext:\n            - key: job_description\n            - Description of position\n          image:\n            - key: profile_picture\n          icon: support_agent\n      - value:\n          _type: Manager\n          name:\n          job_description:\n          profile_picture:\n          url:\n        preview:\n          text:\n            - key: name\n            - Manager\n          subtext:\n            - key: job_description\n            - Description of position\n          image:\n            - key: profile_picture\n          icon: face\n```"
-    },
-    "type._structures_from_glob": {
-      "type": "array",
-      "items": {
-        "type": "string",
-        "documented": true,
-        "title": "_structures_from_glob[*]",
-        "description": "This key represents an individual glob pattern string in the `_structures_from_glob` array.\n\nThe value is a string that specifies a file path pattern relative to the root of your repository. The path must end in the file extension `.cloudcannon.structures.yml`.\n\n## Examples\n\nIn this example, we have several *Structure Configuration Files* in the `.cloudcannon/structures/` folder. The value of the `_structures_from_glob` key tells CloudCannon to use the `staffMembers.cloudcannon.structures.yml` file in that folder.\n\n```yaml\n_structures_from_glob:\n  - '/.cloudcannon/structures/staffMembers.cloudcannon.structures.yml'\n```",
-        "markdownDescription": "This key represents an individual glob pattern string in the `_structures_from_glob` array.\n\nThe value is a string that specifies a file path pattern relative to the root of your repository. The path must end in the file extension `.cloudcannon.structures.yml`.\n\n## Examples\n\nIn this example, we have several *Structure Configuration Files* in the `.cloudcannon/structures/` folder. The value of the `_structures_from_glob` key tells CloudCannon to use the `staffMembers.cloudcannon.structures.yml` file in that folder.\n\n```yaml\n_structures_from_glob:\n  - '/.cloudcannon/structures/staffMembers.cloudcannon.structures.yml'\n```"
-      },
-      "documented": true,
-      "title": "_structures_from_glob",
-      "description": "This key defines globs that filter which files CloudCannon should use for *Structure* configuration.\n\nValues in this array are relative to the root of your repository (i.e., `/`, not the value of `source`) and must end in the file extension\n`.cloudcannon.structures.yml`.\n\nYou can use this key anywhere you would use the `_structures` key in the configuration cascade.\n\nPlease see our documentation on [values_from_glob](https://cloudcannon.com/documentation/developer-reference/configuration-file/types/structure/values_from_glob/) for defining individual\n*Structure* values in a split *Configuration File*.\n\nThis key has no default.\n\n## Examples\n\nIn this example, we have several *Structure Configuration Files* in the `.cloudcannon/structures/` folder. The value of the `_structures_from_glob` key tells CloudCannon to use the `staffMembers.cloudcannon.structures.yml` file in that folder.\n\n```yaml\n_structures_from_glob:\n  - '/.cloudcannon/structures/staffMembers.cloudcannon.structures.yml'\n```\n\n```yaml\nstaff:\n  style: modal\n  values:\n    - label: Employee\n      value:\n        name:\n        job_description:\n        profile_picture:\n    - label: Manager\n      value:\n        name:\n        job_description:\n        profile_picture:\n        url:\n```",
-      "markdownDescription": "This key defines globs that filter which files CloudCannon should use for *Structure* configuration.\n\nValues in this array are relative to the root of your repository (i.e., `/`, not the value of `source`) and must end in the file extension\n`.cloudcannon.structures.yml`.\n\nYou can use this key anywhere you would use the `_structures` key in the configuration cascade.\n\nPlease see our documentation on [values_from_glob](https://cloudcannon.com/documentation/developer-reference/configuration-file/types/structure/values_from_glob/) for defining individual\n*Structure* values in a split *Configuration File*.\n\nThis key has no default.\n\n## Examples\n\nIn this example, we have several *Structure Configuration Files* in the `.cloudcannon/structures/` folder. The value of the `_structures_from_glob` key tells CloudCannon to use the `staffMembers.cloudcannon.structures.yml` file in that folder.\n\n```yaml\n_structures_from_glob:\n  - '/.cloudcannon/structures/staffMembers.cloudcannon.structures.yml'\n```\n\n```yaml\nstaff:\n  style: modal\n  values:\n    - label: Employee\n      value:\n        name:\n        job_description:\n        profile_picture:\n    - label: Manager\n      value:\n        name:\n        job_description:\n        profile_picture:\n        url:\n```"
     }
   },
   "documented": false,
-  "markdownDescription": "A single value option within a structure, defining the data format and appearance for content editors."
+  "title": ""
 }