@cloudcannon/configuration-types 0.0.53 → 0.0.54

package/dist/cloudcannon-config.latest.schema.json

@@ -1,8 +1,5 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "title": "Configuration",
-  "description": "The main CloudCannon configuration.",
-  "$id": "https://github.com/cloudcannon/configuration-types/releases/latest/download/cloudcannon-config.latest.schema.json",
   "type": "object",
   "properties": {
     "paths": {
@@ -256,9 +253,11 @@
     }
   },
   "additionalProperties": false,
+  "title": "Configuration",
+  "description": "The main CloudCannon configuration.",
+  "$id": "https://github.com/cloudcannon/configuration-types/releases/latest/download/cloudcannon-config.latest.schema.json",
   "definitions": {
     "type.paths": {
-      "title": "Paths",
       "type": "object",
       "properties": {
         "static": {
@@ -284,6 +283,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```"
@@ -367,7 +367,6 @@
       "markdownDescription": "This key defines your Collections.\n\n## Examples\n\nIn this example, we have configured a `blog` Collection. Key settings include two Schemas to populate files with different content, a Blog Tags input populated by a fixed data set, and a custom Create Path to generate file names from structured data.\n\n```yaml\ncollections_config:\n  blog:\n    path: content/blog\n    glob:\n      - '!_index.md'\n    name: Blog\n    icon: post_add\n    url: /blog/[full_slug]/\n    documentation:\n      url: https://example.com/travel-blog-style-guide\n      text: Documentation\n      icon: auto_stories\n    description: |-\n      This Collection is for *Travel blogs* and *Customer stories*.\n\n      If your have any questions, please contact Heather.\n    _editables:\n    _enabled_editors:\n      - content\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: _select_data.blog_topics\n    _select_data:\n      blog_topics:\n        - Opinion\n        - Feature\n        - Resource\n    create:\n      extra_data:\n        filename: '{date|year}-{date|month}-{date|day}-{title}'\n      path: '[relative_base_path]/{filename|slugify}.[ext]'\n    disable_add: false\n    disable_add_folder: false\n    disable_file_actions: false\n    schemas:\n      blog:\n        path: schemas/travel_blog.md\n        name: Blog Post\n        icon: post_add\n      customer_story:\n        path: schemas/customer_story.md\n        name: Customer Story\n        icon: post_add\n    schema_key: _blog_template\n    include_developer_files: false\n```\n\nIn this example, we have configured a `team` Collection. Key settings include custom sorting options, add options, and Card previews.\n\n```yaml\ncollections_config:\n  team:\n    path: _data/team\n    name: Our Team\n    singular_name: Team Member\n    icon: groups\n    disable_url: true\n    description: |-\n      This Collection has a file for every member of our team!\n    preview:\n      text:\n        - key: name\n      subtext:\n        - key: job_title\n      icon:\n        - key: profile_picture\n    sort:\n      key: name\n      order: ascending\n    sort_options:\n      - key: name\n        order: ascending\n        label: Name (A-Z)\n      - key: name\n        order: descending\n        label: Name (Z-A)\n      - key: job_title\n        order: ascending\n        label: Job Title (A-Z)\n      - key: date\n        order: descending\n        label: Job Title (Z-A)\n    _enabled_editors:\n      - data\n    add_options:\n      - name: Office Locations\n        icon: map\n        href: /our-offices\n    schemas:\n      manager:\n        path: schemas/manager.yml\n        name: Manager\n        icon: face\n      employee:\n        path: schemas/employee.yml\n        name: Employee\n        icon: support_agent\n```"
     },
     "collections_config.*": {
-      "title": "Collection Config",
       "type": "object",
       "properties": {
         "path": {
@@ -440,8 +439,6 @@
           "description": "This key defines the options for the *Sort* dropdown in a *Collection browser*.\n\nConfiguring sort options for a Collection will remove CloudCannon's default sorting options from the *Sort* dropdown.\n\nBy default, CloudCannon provides sorting options for path, file size, file creation time, and last modified, in ascending and descending order.\n\nCloudCannon will also read data keys from your early Collection files and provide options to sort by those key values.\n\n## Examples\n\nIn this example, the *Sort* dropdown in the `blog` *Collection browser* only contains options for sorting by `author` and `date` in ascending and descending order.\n\n```yaml\ncollections_config:\n  blog:\n    sort_options:\n      - key: author\n        order: ascending\n        label: Author (A-Z)\n      - key: author\n        order: descending\n        label: Author (Z-A)\n      - key: date\n        order: ascending\n        label: Date (Newest First)\n      - key: date\n        order: descending\n        label: Date (Oldest First)\n```",
           "type": "array",
           "items": {
-            "title": "SortOption",
-            "description": "This key represents a sort option for a Collection.",
             "type": "object",
             "properties": {
               "label": {
@@ -452,8 +449,8 @@
                 "markdownDescription": "This key defines the label used for a file sorting option in the *Sort* dropdown.\n\n## Examples\n\nIn this example, the sorting method which uses the `author` key is called \"Author (A-Z)\" in the *Sort* dropdown.\n\n```yaml\ncollections_config:\n  blog:\n    sort_options:\n      - key: author\n        order: ascending\n        label: Author (A-Z)\n```"
               },
               "key": {
-                "description": "This key defines which key an option in the *Sort* dropdown should use to sort files in your *Collection browser*.\n\nYou must define this key for every entry in the `sort_options` array for the object to function.\n\nValue must be the name of a structured data key in your Collection files.\n\nIf some files in your Collection do not have this data key, CloudCannon will sort those in ascending alphabetical order, after the file sorted by your\ndata key in the *Collection browser*.\n\n## Examples\n\nIn this example, the \"Author (A-Z)\" option in the *Sort* dropdown will use the `author` key to sort files in the `blog` *Collection browser*.\n\n```yaml\ncollections_config:\n  blog:\n    sort_options:\n      - key: author\n        order: ascending\n        label: Author (A-Z)\n```",
                 "type": "string",
+                "description": "This key defines which key an option in the *Sort* dropdown should use to sort files in your *Collection browser*.\n\nYou must define this key for every entry in the `sort_options` array for the object to function.\n\nValue must be the name of a structured data key in your Collection files.\n\nIf some files in your Collection do not have this data key, CloudCannon will sort those in ascending alphabetical order, after the file sorted by your\ndata key in the *Collection browser*.\n\n## Examples\n\nIn this example, the \"Author (A-Z)\" option in the *Sort* dropdown will use the `author` key to sort files in the `blog` *Collection browser*.\n\n```yaml\ncollections_config:\n  blog:\n    sort_options:\n      - key: author\n        order: ascending\n        label: Author (A-Z)\n```",
                 "documented": true,
                 "title": "key",
                 "markdownDescription": "This key defines which key an option in the *Sort* dropdown should use to sort files in your *Collection browser*.\n\nYou must define this key for every entry in the `sort_options` array for the object to function.\n\nValue must be the name of a structured data key in your Collection files.\n\nIf some files in your Collection do not have this data key, CloudCannon will sort those in ascending alphabetical order, after the file sorted by your\ndata key in the *Collection browser*.\n\n## Examples\n\nIn this example, the \"Author (A-Z)\" option in the *Sort* dropdown will use the `author` key to sort files in the `blog` *Collection browser*.\n\n```yaml\ncollections_config:\n  blog:\n    sort_options:\n      - key: author\n        order: ascending\n        label: Author (A-Z)\n```"
@@ -477,6 +474,8 @@
               "key"
             ],
             "additionalProperties": false,
+            "title": "SortOption",
+            "description": "This key represents a sort option for a Collection.",
             "documented": true,
             "markdownDescription": "This key represents a sort option for a Collection."
           },
@@ -517,8 +516,6 @@
           "items": {
             "anyOf": [
               {
-                "title": "Add Option",
-                "description": "This key represents the standard add option entry in a `collections_config.*.add_options` array.\n\nThe value is an object that defines an option available in the *+ Add* button dropdown at the top right of the *Collection browser*. Standard add options can contain optional `name`, `icon`, `editor`, `base_path`, `collection`, `schema`, and `default_content_file` keys.\n\n## Examples\n\nIn this example, we have configured a standard add option for the `people` Collection that uses the `employee` Schema and opens files in the [Data Editor](https://cloudcannon.com/documentation/articles/what-is-the-data-editor/).\n\n```yaml\ncollections_config:\n  people:\n    add_options:\n      - name: Add Staff Member\n        schema: employee\n        icon: face\n        editor: data\n    schemas:\n      employee:\n        path: /.cloudcannon/schemas/employee.yml\n```",
                 "type": "object",
                 "properties": {
                   "name": {
@@ -580,12 +577,12 @@
                   }
                 },
                 "additionalProperties": false,
+                "title": "Add Option",
+                "description": "This key represents the standard add option entry in a `collections_config.*.add_options` array.\n\nThe value is an object that defines an option available in the *+ Add* button dropdown at the top right of the *Collection browser*. Standard add options can contain optional `name`, `icon`, `editor`, `base_path`, `collection`, `schema`, and `default_content_file` keys.\n\n## Examples\n\nIn this example, we have configured a standard add option for the `people` Collection that uses the `employee` Schema and opens files in the [Data Editor](https://cloudcannon.com/documentation/articles/what-is-the-data-editor/).\n\n```yaml\ncollections_config:\n  people:\n    add_options:\n      - name: Add Staff Member\n        schema: employee\n        icon: face\n        editor: data\n    schemas:\n      employee:\n        path: /.cloudcannon/schemas/employee.yml\n```",
                 "documented": true,
                 "markdownDescription": "This key represents the standard add option entry in a `collections_config.*.add_options` array.\n\nThe value is an object that defines an option available in the *+ Add* button dropdown at the top right of the *Collection browser*. Standard add options can contain optional `name`, `icon`, `editor`, `base_path`, `collection`, `schema`, and `default_content_file` keys.\n\n## Examples\n\nIn this example, we have configured a standard add option for the `people` Collection that uses the `employee` Schema and opens files in the [Data Editor](https://cloudcannon.com/documentation/articles/what-is-the-data-editor/).\n\n```yaml\ncollections_config:\n  people:\n    add_options:\n      - name: Add Staff Member\n        schema: employee\n        icon: face\n        editor: data\n    schemas:\n      employee:\n        path: /.cloudcannon/schemas/employee.yml\n```"
               },
               {
-                "title": "HREF Add Option",
-                "description": "This key represents the URL add option object in a `collections_config.*.add_options` array.\n\nThe value is an object that defines an option available in the *+ Add* button dropdown at the top right of the *Collection browser*. URL add options must contain a required `href` key and can contain optional `name` and `icon` keys.\n\n## Examples\n\nIn this example, the *\\+ Add* button dropdown in the `team` *Collection browser* has a link to the Office Locations page on our live website.\n\n```yaml\ncollections_config:\n  team:\n    add_options:\n      - name: Office Locations\n        icon: map\n        href: /our-offices\n```",
                 "type": "object",
                 "properties": {
                   "name": {
@@ -608,8 +605,8 @@
                     "markdownDescription": "This key defines the icon displayed next to the text for a URL option in the *\\+ Add* button dropdown.\n\nThe value is a string that specifies an icon name from [Google's Material Symbols](https://fonts.google.com/icons?icon.set=Material+Symbols&icon.style=Rounded).\n\n## Examples\n\nIn this example, the *\\+ Add* button dropdown in the `team` *Collection browser* uses a link option with the icon `map` to navigate to the Office Locations page on our live website.\n\n```yaml\ncollections_config:\n  team:\n    add_options:\n      - name: Office Locations\n        icon: map\n        href: /our-offices\n```"
                   },
                   "href": {
-                    "description": "This key defines the link for a URL option in the *\\+ Add* button dropdown.\n\nThe value is a string that specifies a URL. Values can be an external URL or an internal URL relative to the current Site.\n\nThis key is required for URL add options in the `collections_config.*.add_options` array.\n\n## Examples\n\nIn this example, the *\\+ Add* button dropdown in the `team` *Collection browser* uses a link option with the URL `https://forms.gle/xxxxxxx`.\n\n```yaml\ncollections_config:\n  team:\n    add_options:\n      - name: Submit Form\n        icon: assignment_add\n        href: https://forms.gle/xxxxxxx\n```",
                     "type": "string",
+                    "description": "This key defines the link for a URL option in the *\\+ Add* button dropdown.\n\nThe value is a string that specifies a URL. Values can be an external URL or an internal URL relative to the current Site.\n\nThis key is required for URL add options in the `collections_config.*.add_options` array.\n\n## Examples\n\nIn this example, the *\\+ Add* button dropdown in the `team` *Collection browser* uses a link option with the URL `https://forms.gle/xxxxxxx`.\n\n```yaml\ncollections_config:\n  team:\n    add_options:\n      - name: Submit Form\n        icon: assignment_add\n        href: https://forms.gle/xxxxxxx\n```",
                     "documented": true,
                     "title": "href",
                     "markdownDescription": "This key defines the link for a URL option in the *\\+ Add* button dropdown.\n\nThe value is a string that specifies a URL. Values can be an external URL or an internal URL relative to the current Site.\n\nThis key is required for URL add options in the `collections_config.*.add_options` array.\n\n## Examples\n\nIn this example, the *\\+ Add* button dropdown in the `team` *Collection browser* uses a link option with the URL `https://forms.gle/xxxxxxx`.\n\n```yaml\ncollections_config:\n  team:\n    add_options:\n      - name: Submit Form\n        icon: assignment_add\n        href: https://forms.gle/xxxxxxx\n```"
@@ -619,6 +616,8 @@
                   "href"
                 ],
                 "additionalProperties": false,
+                "title": "HREF Add Option",
+                "description": "This key represents the URL add option object in a `collections_config.*.add_options` array.\n\nThe value is an object that defines an option available in the *+ Add* button dropdown at the top right of the *Collection browser*. URL add options must contain a required `href` key and can contain optional `name` and `icon` keys.\n\n## Examples\n\nIn this example, the *\\+ Add* button dropdown in the `team` *Collection browser* has a link to the Office Locations page on our live website.\n\n```yaml\ncollections_config:\n  team:\n    add_options:\n      - name: Office Locations\n        icon: map\n        href: /our-offices\n```",
                 "documented": true,
                 "markdownDescription": "This key represents the URL add option object in a `collections_config.*.add_options` array.\n\nThe value is an object that defines an option available in the *+ Add* button dropdown at the top right of the *Collection browser*. URL add options must contain a required `href` key and can contain optional `name` and `icon` keys.\n\n## Examples\n\nIn this example, the *\\+ Add* button dropdown in the `team` *Collection browser* has a link to the Office Locations page on our live website.\n\n```yaml\ncollections_config:\n  team:\n    add_options:\n      - name: Office Locations\n        icon: map\n        href: /our-offices\n```"
               }
@@ -679,13 +678,11 @@
             "type": "string"
           },
           "additionalProperties": {
-            "title": "Schema",
-            "description": "This key defines your schemas, which are the structured data formats for your content files.",
             "type": "object",
             "properties": {
               "path": {
-                "description": "This key defines the path to the schema file relative to the root folder of the site.",
                 "type": "string",
+                "description": "This key defines the path to the schema file relative to the root folder of the site.",
                 "documented": true,
                 "title": "path",
                 "markdownDescription": "This key defines the path to the schema file relative to the root folder of the site."
@@ -831,6 +828,8 @@
               "path"
             ],
             "additionalProperties": false,
+            "title": "Schema",
+            "description": "This key defines your schemas, which are the structured data formats for your content files.",
             "documented": true,
             "markdownDescription": "This key defines your schemas, which are the structured data formats for your content files."
           },
@@ -933,13 +932,14 @@
         "path"
       ],
       "additionalProperties": false,
+      "title": "Collection Config",
       "documented": true,
       "description": "This key defines your Collections, which are the sets of content files for your site grouped by folder.",
       "markdownDescription": "This key defines your Collections, which are the sets of content files for your site grouped by folder."
     },
     "path": {
-      "description": "This key defines the folder path for the collection key in which it is nested.\n\nThe value for this key is relative to your [Site source](https://cloudcannon.com/documentation/developer-reference/configuration-file/source/).\n\nEach Collection must have a unique path.\n\n## Examples\n\nIn this example, the files for the `blog` Collection are located in the `content/blog` folder.\n\n```yaml\ncollections_config:\n  blog:\n    path: content/blog\n```",
       "type": "string",
+      "description": "This key defines the folder path for the collection key in which it is nested.\n\nThe value for this key is relative to your [Site source](https://cloudcannon.com/documentation/developer-reference/configuration-file/source/).\n\nEach Collection must have a unique path.\n\n## Examples\n\nIn this example, the files for the `blog` Collection are located in the `content/blog` folder.\n\n```yaml\ncollections_config:\n  blog:\n    path: content/blog\n```",
       "documented": true,
       "title": "path",
       "markdownDescription": "This key defines the folder path for the collection key in which it is nested.\n\nThe value for this key is relative to your [Site source](https://cloudcannon.com/documentation/developer-reference/configuration-file/source/).\n\nEach Collection must have a unique path.\n\n## Examples\n\nIn this example, the files for the `blog` Collection are located in the `content/blog` folder.\n\n```yaml\ncollections_config:\n  blog:\n    path: content/blog\n```"
@@ -948,7 +948,6 @@
       "description": "This key defines globs which filter the files visible in the *Collection browser* for a given Collection.\n\nGlobs can be positive (e.g. `*.yml`), or negative (e.g. `!**/*.json`).\n\nFiles are included in a Collection if they match any positive globs and do not match any negative globs.\n\nIf you do not define any positive globs, CloudCannon will include all non-developer files in a Collection unless they match a negative\nglob.\n\nDefining a negative glob for a Collection does not remove a file from the associated Collection folder in your Git repository.\n\nSimilarly, defining a positive glob for a file in a folder outside your Collection path does not move the file.\n\n## Examples\n\nIn this example, the *Collection browser* will show all files in the `data` folder except for the `secret.yml` file.\n\n```yaml\ncollections_config:\n  data:\n    path: data\n    glob:\n      - '!secret.yml'\n```\n\nIn this example, the *Collection browser* will show only `.yml` files in the `data` folder or any nested folders.\n\n```yaml\ncollections_config:\n  data:\n    path: data\n    glob: '**/*.yml'\n```\n\nIn this example, the *Collection browser* will show only `.yml` files in the `data` folder, except for the `secret.yml` file.\n\n```yaml\ncollections_config:\n  data:\n    path: data\n    glob:\n      - '**/*.yml'\n      - '!secret.yml'\n```",
       "anyOf": [
         {
-          "title": "Glob Array",
           "type": "array",
           "items": {
             "type": "string",
@@ -957,13 +956,14 @@
             "description": "This key represents an individual glob pattern string in the `collections_config.*.glob` array.\n\nThe value is a string that specifies a file path pattern relative to the Collection path. Globs can be positive (e.g., `*.yml`) or negative (e.g., `!**/*.json`).\n\n## Examples\n\nIn this example, the `data` Collection uses a negative glob pattern to exclude the `secret.yml` file from the *Collection browser*.\n\n```yaml\ncollections_config:\n  data:\n    path: data\n    glob:\n      - '!secret.yml'\n```",
             "markdownDescription": "This key represents an individual glob pattern string in the `collections_config.*.glob` array.\n\nThe value is a string that specifies a file path pattern relative to the Collection path. Globs can be positive (e.g., `*.yml`) or negative (e.g., `!**/*.json`).\n\n## Examples\n\nIn this example, the `data` Collection uses a negative glob pattern to exclude the `secret.yml` file from the *Collection browser*.\n\n```yaml\ncollections_config:\n  data:\n    path: data\n    glob:\n      - '!secret.yml'\n```"
           },
+          "title": "Glob Array",
           "documented": true,
           "description": "This key represents an array format for the `collections_config.*.glob` key.\n\nThe value is an array of glob pattern strings. Each string specifies a file path pattern relative to the Collection path. Globs can be positive (e.g., `*.yml`) or negative (e.g., `!**/*.json`).\n\nFiles are included in a Collection if they match any positive globs and do not match any negative globs.\n\n## Examples\n\nIn this example, the `data` Collection uses an array of glob patterns to show only `.yml` files, except for the `secret.yml` file.\n\n```yaml\ncollections_config:\n  data:\n    path: data\n    glob:\n      - '**/*.yml'\n      - '!secret.yml'\n```",
           "markdownDescription": "This key represents an array format for the `collections_config.*.glob` key.\n\nThe value is an array of glob pattern strings. Each string specifies a file path pattern relative to the Collection path. Globs can be positive (e.g., `*.yml`) or negative (e.g., `!**/*.json`).\n\nFiles are included in a Collection if they match any positive globs and do not match any negative globs.\n\n## Examples\n\nIn this example, the `data` Collection uses an array of glob patterns to show only `.yml` files, except for the `secret.yml` file.\n\n```yaml\ncollections_config:\n  data:\n    path: data\n    glob:\n      - '**/*.yml'\n      - '!secret.yml'\n```"
         },
         {
-          "title": "Glob",
           "type": "string",
+          "title": "Glob",
           "documented": true,
           "description": "This key represents a single glob pattern string format for the `collections_config.*.glob` key.\n\nThe value is a string that specifies a file path pattern relative to the Collection path. Globs can be positive (e.g., `*.yml`) or negative (e.g., `!**/*.json`).\n\nFiles are included in a Collection if they match any positive globs and do not match any negative globs.\n\n## Examples\n\nIn this example, the `data` Collection uses a single glob pattern to show only `.yml` files in the `data` folder or any nested folders.\n\n```yaml\ncollections_config:\n  data:\n    path: data\n    glob: '**/*.yml'\n```",
           "markdownDescription": "This key represents a single glob pattern string format for the `collections_config.*.glob` key.\n\nThe value is a string that specifies a file path pattern relative to the Collection path. Globs can be positive (e.g., `*.yml`) or negative (e.g., `!**/*.json`).\n\nFiles are included in a Collection if they match any positive globs and do not match any negative globs.\n\n## Examples\n\nIn this example, the `data` Collection uses a single glob pattern to show only `.yml` files in the `data` folder or any nested folders.\n\n```yaml\ncollections_config:\n  data:\n    path: data\n    glob: '**/*.yml'\n```"
@@ -974,8 +974,6 @@
       "markdownDescription": "This key defines globs which filter the files visible in the *Collection browser* for a given Collection.\n\nGlobs can be positive (e.g. `*.yml`), or negative (e.g. `!**/*.json`).\n\nFiles are included in a Collection if they match any positive globs and do not match any negative globs.\n\nIf you do not define any positive globs, CloudCannon will include all non-developer files in a Collection unless they match a negative\nglob.\n\nDefining a negative glob for a Collection does not remove a file from the associated Collection folder in your Git repository.\n\nSimilarly, defining a positive glob for a file in a folder outside your Collection path does not move the file.\n\n## Examples\n\nIn this example, the *Collection browser* will show all files in the `data` folder except for the `secret.yml` file.\n\n```yaml\ncollections_config:\n  data:\n    path: data\n    glob:\n      - '!secret.yml'\n```\n\nIn this example, the *Collection browser* will show only `.yml` files in the `data` folder or any nested folders.\n\n```yaml\ncollections_config:\n  data:\n    path: data\n    glob: '**/*.yml'\n```\n\nIn this example, the *Collection browser* will show only `.yml` files in the `data` folder, except for the `secret.yml` file.\n\n```yaml\ncollections_config:\n  data:\n    path: data\n    glob:\n      - '**/*.yml'\n      - '!secret.yml'\n```"
     },
     "icon": {
-      "title": "Icon",
-      "description": "Material Symbol icon names available in CloudCannon for UI elements and content previews.",
       "type": "string",
       "enum": [
         "123",
@@ -4563,17 +4561,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```"
@@ -4602,24 +4600,24 @@
         "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```"
     },
     "EditorKey": {
-      "title": "Editor Key",
-      "description": "The available editors in CloudCannon: visual, content, and data editors.",
       "type": "string",
       "enum": [
         "visual",
         "content",
         "data"
       ],
+      "title": "Editor Key",
+      "description": "The available editors in CloudCannon: visual, content, and data editors.",
       "documented": false,
       "markdownDescription": "The available editors in CloudCannon: visual, content, and data editors."
     },
     "type.create": {
-      "title": "Create",
-      "description": "This key defines the path to which CloudCannon will save new files in a Collection.\n\nCloudCannon generates \"Create Paths\" when you open the *Review changes* modal.\n\nFor more information, please read our documentation on [Create Paths](https://cloudcannon.com/documentation/articles/set-the-path-for-new-files/).\n\n## Examples\n\nIn this example, CloudCannon will generate a Create Path for new files in the `blog` Collection using the `date` and `title` structured data keys. For example, CloudCannon will generate a create path of `blog/2024-10-31-spooky-getaway.md` for a file with the date 31st October 2024 and the title \"Spooky Getaway\".\n\n```yaml\ncollections_config:\n  blog:\n    create:\n      extra_data:\n        filename: '{date|year}-{date|month}-{date|day}-{title}'\n      path: '[relative_base_path]/{filename|slugify}.[ext]'\n```",
       "type": "object",
       "properties": {
         "path": {
@@ -4700,12 +4698,12 @@
         }
       },
       "additionalProperties": false,
+      "title": "Create",
+      "description": "This key defines the path to which CloudCannon will save new files in a Collection.\n\nCloudCannon generates \"Create Paths\" when you open the *Review changes* modal.\n\nFor more information, please read our documentation on [Create Paths](https://cloudcannon.com/documentation/articles/set-the-path-for-new-files/).\n\n## Examples\n\nIn this example, CloudCannon will generate a Create Path for new files in the `blog` Collection using the `date` and `title` structured data keys. For example, CloudCannon will generate a create path of `blog/2024-10-31-spooky-getaway.md` for a file with the date 31st October 2024 and the title \"Spooky Getaway\".\n\n```yaml\ncollections_config:\n  blog:\n    create:\n      extra_data:\n        filename: '{date|year}-{date|month}-{date|day}-{title}'\n      path: '[relative_base_path]/{filename|slugify}.[ext]'\n```",
       "documented": true,
       "markdownDescription": "This key defines the path to which CloudCannon will save new files in a Collection.\n\nCloudCannon generates \"Create Paths\" when you open the *Review changes* modal.\n\nFor more information, please read our documentation on [Create Paths](https://cloudcannon.com/documentation/articles/set-the-path-for-new-files/).\n\n## Examples\n\nIn this example, CloudCannon will generate a Create Path for new files in the `blog` Collection using the `date` and `title` structured data keys. For example, CloudCannon will generate a create path of `blog/2024-10-31-spooky-getaway.md` for a file with the date 31st October 2024 and the title \"Spooky Getaway\".\n\n```yaml\ncollections_config:\n  blog:\n    create:\n      extra_data:\n        filename: '{date|year}-{date|month}-{date|day}-{title}'\n      path: '[relative_base_path]/{filename|slugify}.[ext]'\n```"
     },
     "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"
@@ -4713,15 +4711,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"
@@ -4781,6 +4778,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```"
         },
@@ -4788,13 +4787,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": {
@@ -4839,8 +4837,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",
@@ -4852,11 +4848,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": {
@@ -4964,6 +4961,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```"
@@ -4973,6 +4971,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```"
     },
@@ -4984,7 +4984,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": {
@@ -5022,6 +5021,7 @@
         }
       },
       "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```"
@@ -5038,15 +5038,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```"
@@ -5061,15 +5061,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```"
@@ -5285,8 +5285,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",
@@ -5312,17 +5312,16 @@
       "title": "icon_color(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)"
@@ -5340,17 +5339,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```"
@@ -5360,17 +5359,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```"
@@ -5380,17 +5379,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```"
@@ -5400,28 +5399,27 @@
         "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```"
     },
     "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": {
@@ -5466,15 +5464,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": {
@@ -5557,6 +5554,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```"
@@ -5566,12 +5564,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": {
@@ -5616,15 +5614,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": {
@@ -5753,6 +5750,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."
@@ -5762,6 +5760,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."
     },
@@ -5798,8 +5798,6 @@
       "title": "theme(theme)"
     },
     "Syntax": {
-      "title": "Syntax",
-      "description": "Available syntax highlighting languages for code editors in CloudCannon.",
       "type": "string",
       "enum": [
         "c_cpp",
@@ -5871,12 +5869,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": {
@@ -5921,15 +5919,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": {
@@ -6039,6 +6036,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."
@@ -6048,12 +6046,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": {
@@ -6098,13 +6096,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```"
         }
@@ -6113,12 +6111,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": {
@@ -6163,15 +6161,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": {
@@ -6218,6 +6215,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```"
@@ -6227,12 +6225,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",
@@ -6243,15 +6243,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```"
@@ -6278,8 +6278,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": {
@@ -6324,15 +6322,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": {
@@ -6371,6 +6368,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."
@@ -6380,12 +6378,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": {
@@ -6430,18 +6428,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": {
@@ -6647,11 +6644,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.",
@@ -6670,6 +6667,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."
@@ -6679,6 +6677,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."
     },
@@ -6768,8 +6768,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```"
@@ -7060,8 +7060,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": {
@@ -7106,18 +7104,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": {
@@ -7150,10 +7147,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."
@@ -7180,10 +7177,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."
@@ -7208,6 +7205,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."
@@ -7217,11 +7215,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",
@@ -7820,13 +7819,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": {
@@ -7871,15 +7869,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": {
@@ -7899,6 +7896,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."
@@ -7908,12 +7906,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": {
@@ -7958,19 +7956,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": {
@@ -8092,6 +8089,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."
@@ -8101,6 +8099,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."
     },
@@ -8108,18 +8108,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```"
@@ -8130,8 +8130,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",
@@ -8568,6 +8566,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```"
     },
@@ -8610,8 +8610,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": {
@@ -8656,15 +8654,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": {
@@ -8818,6 +8815,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."
@@ -8827,12 +8825,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": {
@@ -8877,15 +8875,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": {
@@ -8989,6 +8986,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```"
@@ -8998,11 +8996,12 @@
         "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```"
     },
     "type.preview": {
-      "title": "Preview",
       "type": "object",
       "properties": {
         "text": {
@@ -9034,6 +9033,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```"
@@ -9230,37 +9230,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"
@@ -9270,10 +9268,10 @@
                 "documented": false,
                 "title": "values(any-of-1)(text-object).*"
               },
+              "title": "Text Object",
               "documented": false
             },
             {
-              "title": "Object Array",
               "type": "array",
               "items": {
                 "type": "object",
@@ -9284,18 +9282,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."
@@ -9339,8 +9339,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": {
@@ -9385,15 +9383,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": {
@@ -9467,6 +9464,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```"
@@ -9476,6 +9474,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```"
     },
@@ -9522,8 +9522,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",
@@ -9534,8 +9534,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": {
@@ -9580,15 +9578,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": {
@@ -9689,6 +9686,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```"
@@ -9698,12 +9696,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": {
@@ -9748,15 +9746,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": {
@@ -9827,6 +9824,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```"
@@ -9836,12 +9834,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": {
@@ -9886,15 +9884,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": {
@@ -10117,6 +10114,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."
@@ -10126,12 +10124,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",
@@ -10142,15 +10142,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": {
@@ -10186,11 +10184,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```"
@@ -10234,12 +10232,12 @@
         "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.[*]": {
-      "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": {
@@ -10500,6 +10498,8 @@
         "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 represents a single value option within a structure, defining the data format and appearance for content editors."
     },
@@ -10518,27 +10518,23 @@
       "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)[*]"
             },
+            "title": "Text Array Select Data",
             "documented": true
           },
           {
-            "title": "Text Object Select Data",
             "type": "object",
             "propertyNames": {
               "type": "string"
@@ -10548,10 +10544,10 @@
               "documented": true,
               "title": "*(text-object).*"
             },
+            "title": "Text Object Select Data",
             "documented": true
           },
           {
-            "title": "Object Array Select Data",
             "type": "array",
             "items": {
               "type": "object",
@@ -10562,28 +10558,30 @@
               "documented": true,
               "title": "*(object-array)[*]"
             },
+            "title": "Object Array Select Data",
             "documented": true
           },
           {
-            "title": "Object Select Data",
             "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": {
-      "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"
@@ -10591,6 +10589,8 @@
       "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```"
     },
@@ -10616,8 +10616,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": {
@@ -10662,15 +10660,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": {
@@ -10731,6 +10728,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."
@@ -10740,6 +10738,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."
     },
@@ -10768,9 +10768,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": {
@@ -10815,10 +10812,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."
         },
@@ -10833,13 +10830,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": {
@@ -10891,6 +10888,9 @@
         }
       },
       "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."
     },
@@ -11374,18 +11374,16 @@
       "markdownDescription": "This key defines custom order and grouping for Collections in your *Site Navigation*.\n\nThe value is an array of group objects. Each group object must contain a `heading` key and a `collections` key.\n\nIf undefined, CloudCannon will sort your Collections in the order they are defined under the `collections_config` key.\n\n## Examples\n\nIn this example, we have configured Collection groups to organize Collections into \"Content\" and \"Data Files\" sections in the *Site Navigation*.\n\n```yaml\ncollection_groups:\n  - heading: Content\n    collections:\n      - pages\n      - blog\n  - heading: Data Files\n    collections:\n      - data\n```"
     },
     "CollectionGroup": {
-      "title": "Collection Group",
       "type": "object",
       "properties": {
         "heading": {
-          "description": "This key defines a short, descriptive label for a group of Collections displayed in the *Site Navigation*.\n\nThis key is required for each group entry in the `collection_groups` array.\n\n## Examples\n\nIn this example, we have configured two Collection groups with a heading that labels the group in the *Site Navigation*.\n\n```yaml\ncollection_groups:\n  - heading: Content\n    collections:\n      - pages\n      - blog\n  - heading: Data Files\n    collections:\n      - data\n```",
           "type": "string",
+          "description": "This key defines a short, descriptive label for a group of Collections displayed in the *Site Navigation*.\n\nThis key is required for each group entry in the `collection_groups` array.\n\n## Examples\n\nIn this example, we have configured two Collection groups with a heading that labels the group in the *Site Navigation*.\n\n```yaml\ncollection_groups:\n  - heading: Content\n    collections:\n      - pages\n      - blog\n  - heading: Data Files\n    collections:\n      - data\n```",
           "documented": true,
           "title": "heading",
           "markdownDescription": "This key defines a short, descriptive label for a group of Collections displayed in the *Site Navigation*.\n\nThis key is required for each group entry in the `collection_groups` array.\n\n## Examples\n\nIn this example, we have configured two Collection groups with a heading that labels the group in the *Site Navigation*.\n\n```yaml\ncollection_groups:\n  - heading: Content\n    collections:\n      - pages\n      - blog\n  - heading: Data Files\n    collections:\n      - data\n```"
         },
         "collections": {
-          "description": "This key defines the Collections displayed in a group in the *Site Navigation*.\n\nThe value is an array of Collection key name strings, matching the keys defined in `collections_config`.\n\nThis key is required for each group entry in the `collection_groups` array.\n\n## Examples\n\nIn this example, we have configured two Collection groups with collections arrays.\n\n```yaml\ncollection_groups:\n  - heading: Content\n    collections:\n      - pages\n      - blog\n  - heading: Data Files\n    collections:\n      - data\n```",
           "type": "array",
           "items": {
             "type": "string",
@@ -11394,6 +11392,7 @@
             "description": "This key represents an individual Collection key name string in the `collection_groups.[*].collections` array.\n\nThe value is a string that specifies the key name of a Collection defined in `collections_config` to include in a group in the *Site Navigation*.\n\n## Examples\n\nIn this example, we have configured a Collection group with multiple Collection key names in the collections array.\n\n```yaml\ncollection_groups:\n  - heading: Content\n    collections:\n      - pages\n      - blog\n  - heading: Data Files\n    collections:\n      - data\n```",
             "markdownDescription": "This key represents an individual Collection key name string in the `collection_groups.[*].collections` array.\n\nThe value is a string that specifies the key name of a Collection defined in `collections_config` to include in a group in the *Site Navigation*.\n\n## Examples\n\nIn this example, we have configured a Collection group with multiple Collection key names in the collections array.\n\n```yaml\ncollection_groups:\n  - heading: Content\n    collections:\n      - pages\n      - blog\n  - heading: Data Files\n    collections:\n      - data\n```"
           },
+          "description": "This key defines the Collections displayed in a group in the *Site Navigation*.\n\nThe value is an array of Collection key name strings, matching the keys defined in `collections_config`.\n\nThis key is required for each group entry in the `collection_groups` array.\n\n## Examples\n\nIn this example, we have configured two Collection groups with collections arrays.\n\n```yaml\ncollection_groups:\n  - heading: Content\n    collections:\n      - pages\n      - blog\n  - heading: Data Files\n    collections:\n      - data\n```",
           "documented": true,
           "title": "collections",
           "markdownDescription": "This key defines the Collections displayed in a group in the *Site Navigation*.\n\nThe value is an array of Collection key name strings, matching the keys defined in `collections_config`.\n\nThis key is required for each group entry in the `collection_groups` array.\n\n## Examples\n\nIn this example, we have configured two Collection groups with collections arrays.\n\n```yaml\ncollection_groups:\n  - heading: Content\n    collections:\n      - pages\n      - blog\n  - heading: Data Files\n    collections:\n      - data\n```"
@@ -11404,6 +11403,7 @@
         "collections"
       ],
       "additionalProperties": false,
+      "title": "Collection Group",
       "documented": true,
       "description": "This key represents an individual group entry in the `collection_groups` array.\n\nThe value defines a group of Collections displayed in the *Site Navigation*. Each group entry must contain a `heading` key and a `collections` key.\n\n## Examples\n\nIn this example, we have configured two Collection groups with a heading and collections array.\n\n```yaml\ncollection_groups:\n  - heading: Content\n    collections:\n      - pages\n      - blog\n  - heading: Data Files\n    collections:\n      - data\n```",
       "markdownDescription": "This key represents an individual group entry in the `collection_groups` array.\n\nThe value defines a group of Collections displayed in the *Site Navigation*. Each group entry must contain a `heading` key and a `collections` key.\n\n## Examples\n\nIn this example, we have configured two Collection groups with a heading and collections array.\n\n```yaml\ncollection_groups:\n  - heading: Content\n    collections:\n      - pages\n      - blog\n  - heading: Data Files\n    collections:\n      - data\n```"
@@ -11462,24 +11462,24 @@
       "type": "object",
       "properties": {
         "glob": {
-          "description": "This key defines the glob pattern(s) targeting a path to one or more files.\n\n## Examples\n\nIn this example, we have configured a file config to target the `data/tabs.yml` file with object input configuration.\n\n```yaml\nfile_config:\n  - glob: data/tabs.yml\n    _inputs:\n      $:\n        type: object\n        options:\n          subtype: tabbed\n```",
           "anyOf": [
             {
-              "title": "Glob Array",
               "type": "array",
               "items": {
                 "type": "string",
                 "documented": true,
                 "title": "glob(glob-array)[*]"
               },
+              "title": "Glob Array",
               "documented": true
             },
             {
-              "title": "Glob",
               "type": "string",
+              "title": "Glob",
               "documented": true
             }
           ],
+          "description": "This key defines the glob pattern(s) targeting a path to one or more files.\n\n## Examples\n\nIn this example, we have configured a file config to target the `data/tabs.yml` file with object input configuration.\n\n```yaml\nfile_config:\n  - glob: data/tabs.yml\n    _inputs:\n      $:\n        type: object\n        options:\n          subtype: tabbed\n```",
           "documented": true,
           "title": "glob",
           "markdownDescription": "This key defines the glob pattern(s) targeting a path to one or more files.\n\n## Examples\n\nIn this example, we have configured a file config to target the `data/tabs.yml` file with object input configuration.\n\n```yaml\nfile_config:\n  - glob: data/tabs.yml\n    _inputs:\n      $:\n        type: object\n        options:\n          subtype: tabbed\n```"
@@ -11627,8 +11627,6 @@
     "commit_templates": {
       "type": "array",
       "items": {
-        "title": "Commit Template",
-        "description": "This key represents an individual commit template object in the `commit_templates` array.\n\nThe value is an object that defines a template for commit messages when saving changes. Each template object can contain optional `label`, `template_path`, `template_string`, `wrap_width`, `extra_data`, and `_inputs` keys.\n\n## Examples\n\nIn this example, we have configured a commit template with a template string and input configuration.\n\n```yaml\ncommit_templates:\n  - label: Default\n    template_string: '{commit_type}: {message|trim}'\n    _inputs:\n      commit_type:\n        type: select\n        options:\n          allow_empty: true\n          values:\n            - feature\n            - fix\n            - test\n        cascade: true\n```",
         "type": "object",
         "properties": {
           "label": {
@@ -11687,6 +11685,8 @@
           }
         },
         "additionalProperties": false,
+        "title": "Commit Template",
+        "description": "This key represents an individual commit template object in the `commit_templates` array.\n\nThe value is an object that defines a template for commit messages when saving changes. Each template object can contain optional `label`, `template_path`, `template_string`, `wrap_width`, `extra_data`, and `_inputs` keys.\n\n## Examples\n\nIn this example, we have configured a commit template with a template string and input configuration.\n\n```yaml\ncommit_templates:\n  - label: Default\n    template_string: '{commit_type}: {message|trim}'\n    _inputs:\n      commit_type:\n        type: select\n        options:\n          allow_empty: true\n          values:\n            - feature\n            - fix\n            - test\n        cascade: true\n```",
         "documented": true,
         "markdownDescription": "This key represents an individual commit template object in the `commit_templates` array.\n\nThe value is an object that defines a template for commit messages when saving changes. Each template object can contain optional `label`, `template_path`, `template_string`, `wrap_width`, `extra_data`, and `_inputs` keys.\n\n## Examples\n\nIn this example, we have configured a commit template with a template string and input configuration.\n\n```yaml\ncommit_templates:\n  - label: Default\n    template_string: '{commit_type}: {message|trim}'\n    _inputs:\n      commit_type:\n        type: select\n        options:\n          allow_empty: true\n          values:\n            - feature\n            - fix\n            - test\n        cascade: true\n```"
       },
@@ -11703,8 +11703,6 @@
       "markdownDescription": "This key defines the commit template to use when pulling changes from the upstream repository.\n\nAn upstream commit message template can contain plain text and placeholders. Placeholders insert data related to the commit and use `[ ]` brackets. CloudCannon supports the following commit placeholders:\n\n* `[branch]` — the name of the current branch.\n* `[publish_branch]` — the name of the Publish Branch from which you merge upstream changes.\n* `[author]` — the email address of the person responsible for the upstream merge.\n* `[date]` — the date of the upstream merge in the format \"Tue Nov 28 2023 21:46:17 GMT+0000\".\n\n## Examples\n\nIn this example, we have configured a commit template with placeholders for upstream pulls.\n\n```yaml\nupstream_commit_template: \"Merge branch [publish_branch] into develop of [branch] by [author] at [date]\"\n```"
     },
     "markdown": {
-      "title": "Markdown Settings",
-      "description": "This key defines your markdown engine for parsing Markdown content into HTML and any configuration options for your engine.\n\n## Examples\n\nIn this example, we have configured CloudCannon to use the `commonmark` Markdown engine with various options including attributes and attribute elements.\n\n```yaml\nmarkdown:\n  engine: commonmark\n  options:\n    attributes: true\n    attributes_elements:\n      inline: none\n      block: space right\n      ul: below\n      ol: below\n      blockquote: below\n      p: below\n      img: below\n      hr: below\n      table: below\n      li: none\n```",
       "type": "object",
       "properties": {
         "engine": {
@@ -11869,7 +11867,6 @@
             },
             "attribute_elements": {
               "description": "This key defines positioning behavior of Markdown attributes for different element types when converting HTML to Markdown.\n\nThe value is an object that can contain `inline`, `block`, or element-specific properties. Each property value specifies where attribute lists should be positioned for that element type. Valid values are `none`, `right`, `space right`, `below`, `newline below`, or `right-of-prefix`.\n\nThis key only takes effect when `attributes` is enabled.\n\n## Examples\n\nIn this example, we have configured attribute positioning for inline and block elements.\n\n```yaml\nmarkdown:\n  engine: commonmark\n  options:\n    attributes: true\n    attribute_elements:\n      inline: right\n      block: below\n```",
-              "title": "Markdown Attribute Element Options",
               "type": "object",
               "properties": {
                 "inline": {
@@ -11898,6 +11895,7 @@
               "additionalProperties": {
                 "$ref": "#/definitions/AttributeListPosition"
               },
+              "title": "Markdown Attribute Element Options",
               "documented": true,
               "markdownDescription": "This key defines positioning behavior of Markdown attributes for different element types when converting HTML to Markdown.\n\nThe value is an object that can contain `inline`, `block`, or element-specific properties. Each property value specifies where attribute lists should be positioned for that element type. Valid values are `none`, `right`, `space right`, `below`, `newline below`, or `right-of-prefix`.\n\nThis key only takes effect when `attributes` is enabled.\n\n## Examples\n\nIn this example, we have configured attribute positioning for inline and block elements.\n\n```yaml\nmarkdown:\n  engine: commonmark\n  options:\n    attributes: true\n    attribute_elements:\n      inline: right\n      block: below\n```"
             }
@@ -11910,12 +11908,12 @@
         }
       },
       "additionalProperties": false,
+      "title": "Markdown Settings",
+      "description": "This key defines your markdown engine for parsing Markdown content into HTML and any configuration options for your engine.\n\n## Examples\n\nIn this example, we have configured CloudCannon to use the `commonmark` Markdown engine with various options including attributes and attribute elements.\n\n```yaml\nmarkdown:\n  engine: commonmark\n  options:\n    attributes: true\n    attributes_elements:\n      inline: none\n      block: space right\n      ul: below\n      ol: below\n      blockquote: below\n      p: below\n      img: below\n      hr: below\n      table: below\n      li: none\n```",
       "documented": true,
       "markdownDescription": "This key defines your markdown engine for parsing Markdown content into HTML and any configuration options for your engine.\n\n## Examples\n\nIn this example, we have configured CloudCannon to use the `commonmark` Markdown engine with various options including attributes and attribute elements.\n\n```yaml\nmarkdown:\n  engine: commonmark\n  options:\n    attributes: true\n    attributes_elements:\n      inline: none\n      block: space right\n      ul: below\n      ol: below\n      blockquote: below\n      p: below\n      img: below\n      hr: below\n      table: below\n      li: none\n```"
     },
     "AttributeListPosition": {
-      "title": "Attribute List Position",
-      "description": "Positioning options for Markdown attribute elements.",
       "type": "string",
       "enum": [
         "none",
@@ -11925,6 +11923,8 @@
         "newline below",
         "right-of-prefix"
       ],
+      "title": "Attribute List Position",
+      "description": "Positioning options for Markdown attribute elements.",
       "documented": false,
       "markdownDescription": "Positioning options for Markdown attribute elements."
     },
@@ -11942,8 +11942,6 @@
       "markdownDescription": "This key defines custom snippets for your Site.\n\nThis key has no default."
     },
     "type.snippet": {
-      "title": "Snippet",
-      "description": "This key defines a snippet configuration.",
       "type": "object",
       "properties": {
         "_inputs": {
@@ -12074,7 +12072,6 @@
           "additionalProperties": {
             "anyOf": [
               {
-                "title": "Argument List Parser Configuration",
                 "type": "object",
                 "properties": {
                   "parser": {
@@ -12114,12 +12111,12 @@
                   "options"
                 ],
                 "additionalProperties": false,
+                "title": "Argument List Parser Configuration",
                 "documented": true,
                 "description": "This key defines a parser configuration that parses a list of distinct positional arguments based on their position.\n\n## Examples\n\nIn this example, we have configured an argument list parser to parse distinct positional arguments based on their position.\n\n```markdown\n{{<figure \"image.png\" \"My image title\">}}\n          └──────────────────────────┘\n```",
                 "markdownDescription": "This key defines a parser configuration that parses a list of distinct positional arguments based on their position.\n\n## Examples\n\nIn this example, we have configured an argument list parser to parse distinct positional arguments based on their position.\n\n```markdown\n{{<figure \"image.png\" \"My image title\">}}\n          └──────────────────────────┘\n```"
               },
               {
-                "title": "Argument Parser Configuration",
                 "type": "object",
                 "properties": {
                   "parser": {
@@ -12152,12 +12149,12 @@
                   "options"
                 ],
                 "additionalProperties": false,
+                "title": "Argument Parser Configuration",
                 "documented": true,
                 "description": "This key defines a parser configuration that parses a single argument, optionally delimited by characters.\n\nUseful for matching a single positional argument.\n\nThe argument parser is also used to parse a list of repeating arguments.\n\n## Examples\n\nIn this example, we have configured an argument parser to parse a single positional argument.\n\n```markdown\n{{<figure image.png>}}\n          └───────┘\n```\n\nIn this example, we have configured an argument parser to parse a list of repeating arguments.\n\n```markdown\n{{<images image1.png image2.png image3.png>}}\n          └──────────────────────────────┘\n```",
                 "markdownDescription": "This key defines a parser configuration that parses a single argument, optionally delimited by characters.\n\nUseful for matching a single positional argument.\n\nThe argument parser is also used to parse a list of repeating arguments.\n\n## Examples\n\nIn this example, we have configured an argument parser to parse a single positional argument.\n\n```markdown\n{{<figure image.png>}}\n          └───────┘\n```\n\nIn this example, we have configured an argument parser to parse a list of repeating arguments.\n\n```markdown\n{{<images image1.png image2.png image3.png>}}\n          └──────────────────────────────┘\n```"
               },
               {
-                "title": "Content Parser Configuration",
                 "type": "object",
                 "properties": {
                   "parser": {
@@ -12289,12 +12286,12 @@
                   "options"
                 ],
                 "additionalProperties": false,
+                "title": "Content Parser Configuration",
                 "documented": true,
                 "description": "This key defines a parser configuration that parses rich multiline content, such as the content between paired tags. Can be configured to parse nested snippets within.\n\n## Examples\n\nIn this example, we have configured a content parser to parse rich multiline content between paired tags.\n\n```liquid\n{% highlight \"js\" %} let a = b; {% endhighlight %}\n                    └──────────┘\n```",
                 "markdownDescription": "This key defines a parser configuration that parses rich multiline content, such as the content between paired tags. Can be configured to parse nested snippets within.\n\n## Examples\n\nIn this example, we have configured a content parser to parse rich multiline content between paired tags.\n\n```liquid\n{% highlight \"js\" %} let a = b; {% endhighlight %}\n                    └──────────┘\n```"
               },
               {
-                "title": "Key Value List Parser Configuration",
                 "type": "object",
                 "properties": {
                   "parser": {
@@ -12339,12 +12336,12 @@
                   "parser"
                 ],
                 "additionalProperties": false,
+                "title": "Key Value List Parser Configuration",
                 "documented": true,
                 "description": "This key defines a parser configuration that parses repeating pairs of keys and values.\n\nUseful for most SSG snippets that take properties.\n\nCan be configured to handle most syntax forms of key value pairs.\n\n## Examples\n\nIn this example, we have configured a key-value list parser to parse repeating pairs of keys and values in Liquid syntax.\n\n```liquid\n{% include \"image.html\" image: \"tree.png\" alt: \"Image of a tree\" %}\n                        └──────────────────────────────────────┘\n```\n\nIn this example, we have configured a key-value list parser to parse repeating pairs of keys and values in Markdown syntax.\n\n```markdown\n<Link href=\"/about/\" new_tab={true}/>\n      └───────────────────────────┘\n```",
                 "markdownDescription": "This key defines a parser configuration that parses repeating pairs of keys and values.\n\nUseful for most SSG snippets that take properties.\n\nCan be configured to handle most syntax forms of key value pairs.\n\n## Examples\n\nIn this example, we have configured a key-value list parser to parse repeating pairs of keys and values in Liquid syntax.\n\n```liquid\n{% include \"image.html\" image: \"tree.png\" alt: \"Image of a tree\" %}\n                        └──────────────────────────────────────┘\n```\n\nIn this example, we have configured a key-value list parser to parse repeating pairs of keys and values in Markdown syntax.\n\n```markdown\n<Link href=\"/about/\" new_tab={true}/>\n      └───────────────────────────┘\n```"
               },
               {
-                "title": "Literal Parser Configuration",
                 "type": "object",
                 "properties": {
                   "parser": {
@@ -12405,12 +12402,12 @@
                   "options"
                 ],
                 "additionalProperties": false,
+                "title": "Literal Parser Configuration",
                 "documented": true,
                 "description": "This key defines a parser configuration that parses an exact literal value. Mainly useful when configuring a snippet template.",
                 "markdownDescription": "This key defines a parser configuration that parses an exact literal value. Mainly useful when configuring a snippet template."
               },
               {
-                "title": "Optional Parser Configuration",
                 "type": "object",
                 "properties": {
                   "parser": {
@@ -12454,12 +12451,12 @@
                   "options"
                 ],
                 "additionalProperties": false,
+                "title": "Optional Parser Configuration",
                 "documented": true,
                 "description": "This key toggles whether matching zero times is a valid state for this parser.\n\nSetting this key to `true` will allow matching zero times as a valid state. If `false`, this parser requires at least one matching value. Setting this to `true` is preferred to wrapping the `repeating` parser inside an `optional` parser.\n\nBy default, this key is `false` (i.e., at least one matching value is required).",
                 "markdownDescription": "This key toggles whether matching zero times is a valid state for this parser.\n\nSetting this key to `true` will allow matching zero times as a valid state. If `false`, this parser requires at least one matching value. Setting this to `true` is preferred to wrapping the `repeating` parser inside an `optional` parser.\n\nBy default, this key is `false` (i.e., at least one matching value is required)."
               },
               {
-                "title": "Repeating Literal Parser Config",
                 "type": "object",
                 "properties": {
                   "parser": {
@@ -12517,12 +12514,12 @@
                   "options"
                 ],
                 "additionalProperties": false,
+                "title": "Repeating Literal Parser Config",
                 "documented": true,
                 "description": "This key defines a parser configuration that parses a repeating set of exact literal values.",
                 "markdownDescription": "This key defines a parser configuration that parses a repeating set of exact literal values."
               },
               {
-                "title": "Repeating Parser Configuration",
                 "type": "object",
                 "properties": {
                   "parser": {
@@ -12590,12 +12587,12 @@
                   "options"
                 ],
                 "additionalProperties": false,
+                "title": "Repeating Parser Configuration",
                 "documented": true,
                 "description": "This key defines a higher-order parser configuration that wraps a snippet string and allows it to repeat.",
                 "markdownDescription": "This key defines a higher-order parser configuration that wraps a snippet string and allows it to repeat."
               },
               {
-                "title": "Wrapper Parser Configuration",
                 "type": "object",
                 "properties": {
                   "parser": {
@@ -12642,6 +12639,7 @@
                   "options"
                 ],
                 "additionalProperties": false,
+                "title": "Wrapper Parser Configuration",
                 "documented": true,
                 "description": "This key defines a wrapper parser configuration for wrapping another snippet configuration.\n\nThe value is an object that contains a `parser` property set to `wrapper` and an `options` object with `snippet` and optional `remove_empty` properties. The wrapper parser wraps another snippet configuration, allowing it to be used within a different snippet context.\n\n## Examples\n\nIn this example, we have configured a wrapper parser to wrap a content snippet.\n\n```yaml\n_snippets:\n  example:\n    snippet: \"<<example [[wrapped_content]]>>\"\n    params:\n      wrapped_content:\n        parser: wrapper\n        options:\n          snippet: 'content'\n  content:\n    snippet: \"<<content [[text]]>>\"\n    params:\n      text:\n        parser: content\n        options:\n          editor_key: content_text\n```",
                 "markdownDescription": "This key defines a wrapper parser configuration for wrapping another snippet configuration.\n\nThe value is an object that contains a `parser` property set to `wrapper` and an `options` object with `snippet` and optional `remove_empty` properties. The wrapper parser wraps another snippet configuration, allowing it to be used within a different snippet context.\n\n## Examples\n\nIn this example, we have configured a wrapper parser to wrap a content snippet.\n\n```yaml\n_snippets:\n  example:\n    snippet: \"<<example [[wrapped_content]]>>\"\n    params:\n      wrapped_content:\n        parser: wrapper\n        options:\n          snippet: 'content'\n  content:\n    snippet: \"<<content [[text]]>>\"\n    params:\n      text:\n        parser: content\n        options:\n          editor_key: content_text\n```"
@@ -12657,6 +12655,8 @@
         }
       },
       "additionalProperties": false,
+      "title": "Snippet",
+      "description": "This key defines a snippet configuration.",
       "documented": true,
       "markdownDescription": "This key defines a snippet configuration."
     },
@@ -13110,7 +13110,6 @@
       "markdownDescription": "This key defines styling options for snippet output formatting.\n\nThe value is an object that can contain `output`, `inline`, and `block` properties. These options control how snippet content is parsed and formatted to produce cleaner source code.\n\n## Examples\n\nIn this example, we have configured snippet style with inline and block formatting options.\n\n```yaml\n_snippets:\n  highlight:\n    snippet: \"<<highlight>> [[content]] <</highlight>>\"\n    params:\n      content:\n        parser: content\n        options:\n          style:\n            inline:\n              leading: ' '\n              trailing: ' '\n            block:\n              leading: '\\n'\n              trailing: '\\n'\n              indent: '  '\n```"
     },
     "type._snippets_imports": {
-      "title": "Snippets Imports",
       "type": "object",
       "properties": {
         "hugo": {
@@ -13139,6 +13138,7 @@
         }
       },
       "additionalProperties": false,
+      "title": "Snippets Imports",
       "documented": true,
       "description": "This key defines snippet templates or libraries for your Site.\n\nSome libraries are SSG specific while others work for most SSGs.\n\nFor more information, please read our documentation on [Docusaurus Components](https://cloudcannon.com/documentation/articles/snippets-using-docusaurus-components/),\n[Eleventy Shortcodes](https://cloudcannon.com/documentation/articles/snippets-using-eleventy-shortcodes/), [Hugo Shortcodes](https://cloudcannon.com/documentation/articles/snippets-using-hugo-shortcodes/), [MDX Components](https://cloudcannon.com/documentation/articles/snippets-using-mdx-components/), or [Python Markdown](https://cloudcannon.com/documentation/articles/snippets-using-python-markdown/).\n\n## Examples\n\nIn this example, we have configured Hugo shortcode imports for the Site.\n\n```yaml\n_snippets_imports:\n  hugo:\n    include:\n      - figure\n      - youtube\n```",
       "markdownDescription": "This key defines snippet templates or libraries for your Site.\n\nSome libraries are SSG specific while others work for most SSGs.\n\nFor more information, please read our documentation on [Docusaurus Components](https://cloudcannon.com/documentation/articles/snippets-using-docusaurus-components/),\n[Eleventy Shortcodes](https://cloudcannon.com/documentation/articles/snippets-using-eleventy-shortcodes/), [Hugo Shortcodes](https://cloudcannon.com/documentation/articles/snippets-using-hugo-shortcodes/), [MDX Components](https://cloudcannon.com/documentation/articles/snippets-using-mdx-components/), or [Python Markdown](https://cloudcannon.com/documentation/articles/snippets-using-python-markdown/).\n\n## Examples\n\nIn this example, we have configured Hugo shortcode imports for the Site.\n\n```yaml\n_snippets_imports:\n  hugo:\n    include:\n      - figure\n      - youtube\n```"
@@ -13150,7 +13150,6 @@
           "$ref": "#/definitions/type._snippets_imports.*.(full-import)"
         },
         {
-          "title": "Snippets Imports Exclude List",
           "type": "object",
           "properties": {
             "exclude": {
@@ -13161,10 +13160,10 @@
             "exclude"
           ],
           "additionalProperties": false,
+          "title": "Snippets Imports Exclude List",
           "documented": true
         },
         {
-          "title": "Snippets Imports Include List",
           "type": "object",
           "properties": {
             "include": {
@@ -13175,6 +13174,7 @@
             "include"
           ],
           "additionalProperties": false,
+          "title": "Snippets Imports Include List",
           "documented": true
         }
       ],
@@ -13182,30 +13182,30 @@
       "title": "hugo"
     },
     "type._snippets_imports.*.(full-import)": {
-      "title": "Snippets Imports Full Import",
       "type": "boolean",
+      "title": "Snippets Imports Full Import",
       "documented": true
     },
     "SnippetImportExclude": {
-      "description": "This key defines the list of excluded snippets.\n\nIf unset, all snippets are excluded unless defined in `include`.",
       "type": "array",
       "items": {
         "type": "string",
         "documented": true,
         "title": "exclude[*]"
       },
+      "description": "This key defines the list of excluded snippets.\n\nIf unset, all snippets are excluded unless defined in `include`.",
       "documented": true,
       "title": "exclude",
       "markdownDescription": "This key defines the list of excluded snippets.\n\nIf unset, all snippets are excluded unless defined in `include`."
     },
     "SnippetImportInclude": {
-      "description": "This key defines the list of included snippets.\n\nIf unset, all snippets are included unless defined in `exclude`.",
       "type": "array",
       "items": {
         "type": "string",
         "documented": true,
         "title": "include[*]"
       },
+      "description": "This key defines the list of included snippets.\n\nIf unset, all snippets are included unless defined in `exclude`.",
       "documented": true,
       "title": "include",
       "markdownDescription": "This key defines the list of included snippets.\n\nIf unset, all snippets are included unless defined in `exclude`."
@@ -13217,7 +13217,6 @@
           "$ref": "#/definitions/type._snippets_imports.*.(full-import)"
         },
         {
-          "title": "Snippets Imports Exclude List",
           "type": "object",
           "properties": {
             "exclude": {
@@ -13228,10 +13227,10 @@
             "exclude"
           ],
           "additionalProperties": false,
+          "title": "Snippets Imports Exclude List",
           "documented": true
         },
         {
-          "title": "Snippets Imports Include List",
           "type": "object",
           "properties": {
             "include": {
@@ -13242,6 +13241,7 @@
             "include"
           ],
           "additionalProperties": false,
+          "title": "Snippets Imports Include List",
           "documented": true
         }
       ],
@@ -13255,7 +13255,6 @@
           "$ref": "#/definitions/type._snippets_imports.*.(full-import)"
         },
         {
-          "title": "Snippets Imports Exclude List",
           "type": "object",
           "properties": {
             "exclude": {
@@ -13266,10 +13265,10 @@
             "exclude"
           ],
           "additionalProperties": false,
+          "title": "Snippets Imports Exclude List",
           "documented": true
         },
         {
-          "title": "Snippets Imports Include List",
           "type": "object",
           "properties": {
             "include": {
@@ -13280,6 +13279,7 @@
             "include"
           ],
           "additionalProperties": false,
+          "title": "Snippets Imports Include List",
           "documented": true
         }
       ],
@@ -13293,7 +13293,6 @@
           "$ref": "#/definitions/type._snippets_imports.*.(full-import)"
         },
         {
-          "title": "Snippets Imports Exclude List",
           "type": "object",
           "properties": {
             "exclude": {
@@ -13304,10 +13303,10 @@
             "exclude"
           ],
           "additionalProperties": false,
+          "title": "Snippets Imports Exclude List",
           "documented": true
         },
         {
-          "title": "Snippets Imports Include List",
           "type": "object",
           "properties": {
             "include": {
@@ -13318,6 +13317,7 @@
             "include"
           ],
           "additionalProperties": false,
+          "title": "Snippets Imports Include List",
           "documented": true
         }
       ],
@@ -13331,7 +13331,6 @@
           "$ref": "#/definitions/type._snippets_imports.*.(full-import)"
         },
         {
-          "title": "Snippets Imports Exclude List",
           "type": "object",
           "properties": {
             "exclude": {
@@ -13342,10 +13341,10 @@
             "exclude"
           ],
           "additionalProperties": false,
+          "title": "Snippets Imports Exclude List",
           "documented": true
         },
         {
-          "title": "Snippets Imports Include List",
           "type": "object",
           "properties": {
             "include": {
@@ -13356,6 +13355,7 @@
             "include"
           ],
           "additionalProperties": false,
+          "title": "Snippets Imports Include List",
           "documented": true
         }
       ],
@@ -13369,7 +13369,6 @@
           "$ref": "#/definitions/type._snippets_imports.*.(full-import)"
         },
         {
-          "title": "Snippets Imports Exclude List",
           "type": "object",
           "properties": {
             "exclude": {
@@ -13380,10 +13379,10 @@
             "exclude"
           ],
           "additionalProperties": false,
+          "title": "Snippets Imports Exclude List",
           "documented": true
         },
         {
-          "title": "Snippets Imports Include List",
           "type": "object",
           "properties": {
             "include": {
@@ -13394,6 +13393,7 @@
             "include"
           ],
           "additionalProperties": false,
+          "title": "Snippets Imports Include List",
           "documented": true
         }
       ],
@@ -13407,7 +13407,6 @@
           "$ref": "#/definitions/type._snippets_imports.*.(full-import)"
         },
         {
-          "title": "Snippets Imports Exclude List",
           "type": "object",
           "properties": {
             "exclude": {
@@ -13418,10 +13417,10 @@
             "exclude"
           ],
           "additionalProperties": false,
+          "title": "Snippets Imports Exclude List",
           "documented": true
         },
         {
-          "title": "Snippets Imports Include List",
           "type": "object",
           "properties": {
             "include": {
@@ -13432,6 +13431,7 @@
             "include"
           ],
           "additionalProperties": false,
+          "title": "Snippets Imports Include List",
           "documented": true
         }
       ],
@@ -13445,7 +13445,6 @@
           "$ref": "#/definitions/type._snippets_imports.*.(full-import)"
         },
         {
-          "title": "Snippets Imports Exclude List",
           "type": "object",
           "properties": {
             "exclude": {
@@ -13456,10 +13455,10 @@
             "exclude"
           ],
           "additionalProperties": false,
+          "title": "Snippets Imports Exclude List",
           "documented": true
         },
         {
-          "title": "Snippets Imports Include List",
           "type": "object",
           "properties": {
             "include": {
@@ -13470,6 +13469,7 @@
             "include"
           ],
           "additionalProperties": false,
+          "title": "Snippets Imports Include List",
           "documented": true
         }
       ],
@@ -13503,8 +13503,6 @@
       "markdownDescription": "A record of reusable values that can be referenced in snippet templates. Values are substituted using `{ ref: \"key\" }` for direct replacement or `{ spread_ref: \"key\" }` for spreading arrays/objects. Common definition types include parser formats, argument models, select option lists, and simple string values like shortcode names.\n\n## Examples\n\nDefine reusable values like shortcode names, argument models, and parser formats that can be referenced in snippet templates.\n\n```yaml\n_snippets_definitions:\n  # Simple string value for the shortcode name\n  shortcode_name: \"highlight\"\n  content_key: \"content\"\n\n  # Array of argument models for positional arguments\n  positional_args:\n    - editor_key: \"language\"\n      type: \"string\"\n    - editor_key: \"linenos\"\n      type: \"boolean\"\n      optional: true\n      default: false\n\n  # Parser format configuration\n  custom_format:\n    root_pair_delimiter:\n      - \" \"\n    root_value_delimiter: \"=\"\n    string_boundary:\n      - '\"'\n      - \"'\"\n      - \"\"\n    allow_booleans: true\n    allow_numbers: true\n```\n\nReference definitions in snippet templates using `{ ref: \"key\" }` syntax. This allows you to reuse common configurations across multiple snippets.\n\n```yaml\n_snippets_definitions:\n  shortcode_name: \"figure\"\n  named_args:\n    - editor_key: \"src\"\n      type: \"string\"\n    - editor_key: \"alt\"\n      type: \"string\"\n      optional: true\n\n_snippets_templates:\n  my_shortcode_template:\n    snippet: \"{{< [[name]] [[args]] >}}\"\n    params:\n      name:\n        parser: \"literal\"\n        options:\n          literal:\n            ref: \"shortcode_name\"\n      args:\n        parser: \"key_values\"\n        options:\n          models:\n            ref: \"named_args\"\n\n_snippets:\n  figure:\n    template: \"my_shortcode_template\"\n    definitions:\n      shortcode_name: \"figure\"\n      named_args:\n        - editor_key: \"src\"\n          type: \"string\"\n        - editor_key: \"alt\"\n          type: \"string\"\n```\n\nDefine a list of select options for use in snippet inputs, such as a list of programming languages for a code highlighting snippet.\n\n```yaml\n_snippets_definitions:\n  languages:\n    - name: \"JavaScript\"\n      value: \"js\"\n    - name: \"Python\"\n      value: \"python\"\n    - name: \"Ruby\"\n      value: \"ruby\"\n    - name: \"HTML\"\n      value: \"html\"\n    - name: \"CSS\"\n      value: \"css\"\n```"
     },
     "type.snippet-definition-value": {
-      "title": "Snippet Definition Value",
-      "description": "A reusable value that can be referenced in snippet templates via `{ ref: \"key\" }` or `{ spread_ref: \"key\" }`. Can be a string, number, boolean, parser format, parser model, array of models, or array of select options.",
       "anyOf": [
         {
           "$ref": "#/definitions/type.snippet-format"
@@ -13513,49 +13511,47 @@
           "$ref": "#/definitions/type.snippet-model"
         },
         {
-          "title": "Parser Model Array",
-          "description": "An array of parser model configurations. Typically used for `positional_args` or `named_args` definitions that specify the arguments a snippet accepts. Each model defines an argument's editor key, type, default value, and whether it's optional.",
           "type": "array",
           "items": {
             "$ref": "#/definitions/type.snippet-model"
           },
+          "title": "Parser Model Array",
+          "description": "An array of parser model configurations. Typically used for `positional_args` or `named_args` definitions that specify the arguments a snippet accepts. Each model defines an argument's editor key, type, default value, and whether it's optional.",
           "documented": true,
           "markdownDescription": "An array of parser model configurations. Typically used for `positional_args` or `named_args` definitions that specify the arguments a snippet accepts. Each model defines an argument's editor key, type, default value, and whether it's optional."
         },
         {
-          "title": "Select Values Array",
-          "description": "An array of select option values. Commonly used for language lists in code highlighting snippets, where each option has a display name and a value. For example: `[{ name: \"JavaScript\", value: \"js\" }, { name: \"Python\", value: \"python\" }]`.",
           "type": "array",
           "items": {
             "$ref": "#/definitions/type.snippet-definition-select-value"
           },
+          "title": "Select Values Array",
+          "description": "An array of select option values. Commonly used for language lists in code highlighting snippets, where each option has a display name and a value. For example: `[{ name: \"JavaScript\", value: \"js\" }, { name: \"Python\", value: \"python\" }]`.",
           "documented": true,
           "markdownDescription": "An array of select option values. Commonly used for language lists in code highlighting snippets, where each option has a display name and a value. For example: `[{ name: \"JavaScript\", value: \"js\" }, { name: \"Python\", value: \"python\" }]`."
         },
         {
+          "type": "string",
           "title": "String Value",
           "description": "A string value definition. Commonly used for `shortcode_name`, `tag_name`, `content_key`, `include_name`, and similar definitions that identify snippet components by name.",
-          "type": "string",
           "documented": true,
           "markdownDescription": "A string value definition. Commonly used for `shortcode_name`, `tag_name`, `content_key`, `include_name`, and similar definitions that identify snippet components by name."
         },
         {
+          "type": "number",
           "title": "Number Value",
           "description": "A numeric value definition. Use for counts, sizes, or other numeric values that can be referenced in snippet templates.",
-          "type": "number",
           "documented": true,
           "markdownDescription": "A numeric value definition. Use for counts, sizes, or other numeric values that can be referenced in snippet templates."
         },
         {
+          "type": "boolean",
           "title": "Boolean Value",
           "description": "A boolean value definition. Use for flags and toggles that can be referenced in snippet templates.",
-          "type": "boolean",
           "documented": true,
           "markdownDescription": "A boolean value definition. Use for flags and toggles that can be referenced in snippet templates."
         },
         {
-          "title": "String Array",
-          "description": "An array of string values. Useful for defining lists of allowed values, delimiters, or other string collections that can be referenced in snippet templates.",
           "type": "array",
           "items": {
             "type": "string",
@@ -13564,16 +13560,18 @@
             "description": "A string item in the array.",
             "markdownDescription": "A string item in the array."
           },
+          "title": "String Array",
+          "description": "An array of string values. Useful for defining lists of allowed values, delimiters, or other string collections that can be referenced in snippet templates.",
           "documented": true,
           "markdownDescription": "An array of string values. Useful for defining lists of allowed values, delimiters, or other string collections that can be referenced in snippet templates."
         }
       ],
+      "title": "Snippet Definition Value",
+      "description": "A reusable value that can be referenced in snippet templates via `{ ref: \"key\" }` or `{ spread_ref: \"key\" }`. Can be a string, number, boolean, parser format, parser model, array of models, or array of select options.",
       "documented": true,
       "markdownDescription": "A reusable value that can be referenced in snippet templates via `{ ref: \"key\" }` or `{ spread_ref: \"key\" }`. Can be a string, number, boolean, parser format, parser model, array of models, or array of select options."
     },
     "type.snippet-definition-select-value": {
-      "title": "Snippet Definition Select Value",
-      "description": "A value option for select inputs, typically used in language lists. Contains a display name and the actual value to use.",
       "type": "object",
       "properties": {
         "name": {
@@ -13584,24 +13582,24 @@
           "markdownDescription": "The display name shown to users when selecting this option. For example, \"JavaScript\" for a language with value \"js\"."
         },
         "value": {
-          "description": "The actual value used when this option is selected. Can be a string, number, or boolean. For example, \"js\" for JavaScript or 4 for an indentation level.",
           "anyOf": [
             {
-              "title": "String Select Value",
               "type": "string",
+              "title": "String Select Value",
               "documented": true
             },
             {
-              "title": "Number Select Value",
               "type": "number",
+              "title": "Number Select Value",
               "documented": true
             },
             {
-              "title": "Boolean Select Value",
               "type": "boolean",
+              "title": "Boolean Select Value",
               "documented": true
             }
           ],
+          "description": "The actual value used when this option is selected. Can be a string, number, or boolean. For example, \"js\" for JavaScript or 4 for an indentation level.",
           "documented": true,
           "title": "value",
           "markdownDescription": "The actual value used when this option is selected. Can be a string, number, or boolean. For example, \"js\" for JavaScript or 4 for an indentation level."
@@ -13611,6 +13609,8 @@
         "value"
       ],
       "additionalProperties": false,
+      "title": "Snippet Definition Select Value",
+      "description": "A value option for select inputs, typically used in language lists. Contains a display name and the actual value to use.",
       "documented": true,
       "markdownDescription": "A value option for select inputs, typically used in language lists. Contains a display name and the actual value to use."
     }