@cloudcannon/configuration-types 0.0.51 → 0.0.53

package/dist/cloudcannon-collections.schema.json

@@ -46,12 +46,12 @@
           "markdownDescription": "This key toggles whether CloudCannon will generate an output URL for a given Collection.\n\nSetting this key to `true` will prevent CloudCannon from generating an output URL for a Collection.\n\n## Examples\n\nIn this example, `data` is an non-output Collection and we don't want output URLs generated.\n\n```yaml\ncollections_config:\n  data:\n    disable_url: true\n```"
         },
         "include_developer_files": {
-          "description": "This key toggles whether CloudCannon removes developer files from your *Collection browser*. CloudCannon excludes files that probably shouldn't be edited in a CMS from your *Collection browser*, for example files like `README.md` or\n`package.json`. CloudCannon excludes these files even if you have configured globs to allow them.\n\nSetting this key to `true` will allow CloudCannon to show developer files,\nassuming they are not filtered out by any configured\n[globs](https://cloudcannon.com/documentation/articles/collections-reference/#glob).\n\n## Examples\n\nIn this example, we want to see developer files in the *Collection browser* for the `data` Collection.\n\n```yaml\ncollections_config:\n  data:\n    include_developer_files: true\n```",
+          "description": "This key toggles whether CloudCannon removes developer files from your *Collection browser*. CloudCannon excludes files that probably shouldn't be edited in a CMS from your *Collection browser*, for example files like `README.md` or\n`package.json`. CloudCannon excludes these files even if you have configured globs to allow them.\n\nSetting this key to `true` will allow CloudCannon to show developer files,\nassuming they are not filtered out by any configured\n[globs](https://cloudcannon.com/documentation/developer-reference/configuration-file/collections_config/*/glob/). \n\n## Examples\n\nIn this example, we want to see developer files in the *Collection browser* for the `data` Collection.\n\n```yaml\ncollections_config:\n  data:\n    include_developer_files: true\n```",
           "default": false,
           "type": "boolean",
           "documented": true,
           "title": "include_developer_files",
-          "markdownDescription": "This key toggles whether CloudCannon removes developer files from your *Collection browser*. CloudCannon excludes files that probably shouldn't be edited in a CMS from your *Collection browser*, for example files like `README.md` or\n`package.json`. CloudCannon excludes these files even if you have configured globs to allow them.\n\nSetting this key to `true` will allow CloudCannon to show developer files,\nassuming they are not filtered out by any configured\n[globs](https://cloudcannon.com/documentation/articles/collections-reference/#glob).\n\n## Examples\n\nIn this example, we want to see developer files in the *Collection browser* for the `data` Collection.\n\n```yaml\ncollections_config:\n  data:\n    include_developer_files: true\n```"
+          "markdownDescription": "This key toggles whether CloudCannon removes developer files from your *Collection browser*. CloudCannon excludes files that probably shouldn't be edited in a CMS from your *Collection browser*, for example files like `README.md` or\n`package.json`. CloudCannon excludes these files even if you have configured globs to allow them.\n\nSetting this key to `true` will allow CloudCannon to show developer files,\nassuming they are not filtered out by any configured\n[globs](https://cloudcannon.com/documentation/developer-reference/configuration-file/collections_config/*/glob/). \n\n## Examples\n\nIn this example, we want to see developer files in the *Collection browser* for the `data` Collection.\n\n```yaml\ncollections_config:\n  data:\n    include_developer_files: true\n```"
         },
         "name": {
           "description": "This key defines the display name for a Collection.\n\nThe name appears in the *Site Navigation* and at the top of the *Collection browser*.\n\nChanging the display name does not affect the Collection key name.\n\nBy default, CloudCannon uses the Collection key name in title case (i.e., `blog_files` becomes \"Blog Files\").\n\n## Examples\n\nIn this example, CloudCannon will call the `blog` Collection \"Travel Blog\" in the *Site Navigation* and the *Collection browser*.\n\n```yaml\ncollections_config:\n  blog:\n    name: Travel Blog\n```",
@@ -166,7 +166,7 @@
           "markdownDescription": "This key defines the singular noun for your Collection name.\n\nCloudCannon uses the singular noun in the *\\+ Add* button in the top right of the *Collection browser* when you select the option to add a new file.\n\nThis is useful if your Collection name is an irregular plural (e.g., \"syllabi\" or \"syllabuses\" to \"syllabus\").\n\n## Examples\n\nIn this example, the *\\+ Add* button option to add a Collection file will read \"Add Team Member\" rather that \"Add Team\".\n\n```yaml\ncollections_config:\n  team:\n    singular_name: Team Member\n```"
         },
         "add_options": {
-          "description": "This key defines the options available in the *\\+ Add* button dropdown at the top right of your *Collection browser*.\n\nConfiguring add options for a Collection will remove CloudCannon's default \"Add a file\" option from the *\\+ Add* button dropdown.\n\nAdditionally, any Schemas you have configured for a Collection will also appear in the *\\+ Add* dropdown.\n\nFor more information on these options, please read our reference documentation on [disable\\_add](https://cloudcannon.com/documentation/articles/collections-reference/#disable_add), [disable\\_add\\_folder](https://cloudcannon.com/documentation/articles/collections-reference/#disable_add_folder), and [schemas](https://cloudcannon.com/documentation/articles/schemas-reference/#schemas).\n\n## Examples\n\nIn this example, we have configured two standard add options for the `people` Collection. The first option uses the `employee` Schema, and the second option uses the `contractor` 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      - name: Add Contractor\n        icon: support_agent\n        schema: contractor\n        editor: data\n    schemas:\n      employee:\n        path: /.cloudcannon/schemas/employee.yml\n      contractor:\n        path: /.cloudcannon/schemas/contractor.yml\n```\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```",
+          "description": "This key defines the options available in the *\\+ Add* button dropdown at the top right of your *Collection browser*.\n\nConfiguring add options for a Collection will remove CloudCannon's default \"Add a file\" option from the *\\+ Add* button dropdown.\n\nAdditionally, any Schemas you have configured for a Collection will also appear in the *\\+ Add* dropdown.\n\n## Examples\n\nIn this example, we have configured two standard add options for the `people` Collection. The first option uses the `employee` Schema, and the second option uses the `contractor` 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      - name: Add Contractor\n        icon: support_agent\n        schema: contractor\n        editor: data\n    schemas:\n      employee:\n        path: /.cloudcannon/schemas/employee.yml\n      contractor:\n        path: /.cloudcannon/schemas/contractor.yml\n```\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": "array",
           "items": {
             "anyOf": [
@@ -205,11 +205,11 @@
                     "markdownDescription": "This key defines which editing interface CloudCannon will use when you select an option from the *\\+ Add* button dropdown.\n\nValues can be one of the following: `visual`, `content`, or `data`.\n\nBy default, CloudCannon will open the new file in an appropriate editing interface for that file type.\n\nIf CloudCannon cannot determine an appropriate editing interface, it will show a warning.\n\n## Examples\n\nIn this example, we have configured a standard add option for the `people` Collection that opens new 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```"
                   },
                   "base_path": {
-                    "description": "This key defines a path for files created using an option in the *\\+ Add* button dropdown.\n\nThis path overrides the path for the current Collection and subfolder open in the *Collection browser*.\n\nThis key is useful if you need to specify a specific subfolder within a Collection.\n\nThe value for this key is relative to your Collection [path](https://cloudcannon.com/documentation/articles/collections-reference/#path).\n\n## Examples\n\nIn this example, we want team members in the `_posts` Collection to create new files in the`blog` subfolder of the `_drafts` Collection rather than the current *Collection browser* they have open. By configuring the `base_path` value to `/../_drafts/blog`, new files will be created in a different Collection subfolder (i.e., `_drafts`) when a team member selects this option from the *\\+ Add* button dropdown.\n\n```yaml\ncollections_config:\n  _posts:\n    add_options:\n      - name: Add draft blog\n        icon: post_add\n        editor: content\n        base_path: /../_drafts/blog\n```",
+                    "description": "This key defines a path for files created using an option in the *\\+ Add* button dropdown.\n\nThis path overrides the path for the current Collection and subfolder open in the *Collection browser*.\n\nThis key is useful if you need to specify a specific subfolder within a Collection.\n\n## Examples\n\nIn this example, we want team members in the `_posts` Collection to create new files in the`blog` subfolder of the `_drafts` Collection rather than the current *Collection browser* they have open. By configuring the `base_path` value to `/../_drafts/blog`, new files will be created in a different Collection subfolder (i.e., `_drafts`) when a team member selects this option from the *\\+ Add* button dropdown.\n\n```yaml\ncollections_config:\n  _posts:\n    add_options:\n      - name: Add draft blog\n        icon: post_add\n        editor: content\n        base_path: /../_drafts/blog\n```",
                     "type": "string",
                     "documented": true,
                     "title": "base_path",
-                    "markdownDescription": "This key defines a path for files created using an option in the *\\+ Add* button dropdown.\n\nThis path overrides the path for the current Collection and subfolder open in the *Collection browser*.\n\nThis key is useful if you need to specify a specific subfolder within a Collection.\n\nThe value for this key is relative to your Collection [path](https://cloudcannon.com/documentation/articles/collections-reference/#path).\n\n## Examples\n\nIn this example, we want team members in the `_posts` Collection to create new files in the`blog` subfolder of the `_drafts` Collection rather than the current *Collection browser* they have open. By configuring the `base_path` value to `/../_drafts/blog`, new files will be created in a different Collection subfolder (i.e., `_drafts`) when a team member selects this option from the *\\+ Add* button dropdown.\n\n```yaml\ncollections_config:\n  _posts:\n    add_options:\n      - name: Add draft blog\n        icon: post_add\n        editor: content\n        base_path: /../_drafts/blog\n```"
+                    "markdownDescription": "This key defines a path for files created using an option in the *\\+ Add* button dropdown.\n\nThis path overrides the path for the current Collection and subfolder open in the *Collection browser*.\n\nThis key is useful if you need to specify a specific subfolder within a Collection.\n\n## Examples\n\nIn this example, we want team members in the `_posts` Collection to create new files in the`blog` subfolder of the `_drafts` Collection rather than the current *Collection browser* they have open. By configuring the `base_path` value to `/../_drafts/blog`, new files will be created in a different Collection subfolder (i.e., `_drafts`) when a team member selects this option from the *\\+ Add* button dropdown.\n\n```yaml\ncollections_config:\n  _posts:\n    add_options:\n      - name: Add draft blog\n        icon: post_add\n        editor: content\n        base_path: /../_drafts/blog\n```"
                   },
                   "collection": {
                     "description": "This key defines the Collection for files created using an option in the *\\+ Add* button dropdown.\n\nThis Collections overrides the current Collection open in the *Collection browser*.\n\nThe value for this key should be the key name of a Collection.\n\nBy default, this key is the current Collection open in the *Collection browser*.\n\n## Examples\n\nIn this example, we want team members in the articles Collection to create new files in the `new_articles` Collection rather than the current Collection browser they have open. By configuring the `collection` value to `new_articles`, new files will be created in a different Collection (i.e., `new_articles`) when a team member selects this option from the + Add button dropdown.\n\n```yaml\ncollections_config:\n  articles:\n    add_options:\n      - name: Add articles\n        collection: new_articles\n        schema: articles\n```",
@@ -284,7 +284,7 @@
           },
           "documented": true,
           "title": "add_options",
-          "markdownDescription": "This key defines the options available in the *\\+ Add* button dropdown at the top right of your *Collection browser*.\n\nConfiguring add options for a Collection will remove CloudCannon's default \"Add a file\" option from the *\\+ Add* button dropdown.\n\nAdditionally, any Schemas you have configured for a Collection will also appear in the *\\+ Add* dropdown.\n\nFor more information on these options, please read our reference documentation on [disable\\_add](https://cloudcannon.com/documentation/articles/collections-reference/#disable_add), [disable\\_add\\_folder](https://cloudcannon.com/documentation/articles/collections-reference/#disable_add_folder), and [schemas](https://cloudcannon.com/documentation/articles/schemas-reference/#schemas).\n\n## Examples\n\nIn this example, we have configured two standard add options for the `people` Collection. The first option uses the `employee` Schema, and the second option uses the `contractor` 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      - name: Add Contractor\n        icon: support_agent\n        schema: contractor\n        editor: data\n    schemas:\n      employee:\n        path: /.cloudcannon/schemas/employee.yml\n      contractor:\n        path: /.cloudcannon/schemas/contractor.yml\n```\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```"
+          "markdownDescription": "This key defines the options available in the *\\+ Add* button dropdown at the top right of your *Collection browser*.\n\nConfiguring add options for a Collection will remove CloudCannon's default \"Add a file\" option from the *\\+ Add* button dropdown.\n\nAdditionally, any Schemas you have configured for a Collection will also appear in the *\\+ Add* dropdown.\n\n## Examples\n\nIn this example, we have configured two standard add options for the `people` Collection. The first option uses the `employee` Schema, and the second option uses the `contractor` 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      - name: Add Contractor\n        icon: support_agent\n        schema: contractor\n        editor: data\n    schemas:\n      employee:\n        path: /.cloudcannon/schemas/employee.yml\n      contractor:\n        path: /.cloudcannon/schemas/contractor.yml\n```\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```"
         },
         "create": {
           "allOf": [
@@ -592,14 +592,14 @@
       "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/articles/configuration-file-reference/#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```",
+      "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",
       "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/articles/configuration-file-reference/#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```"
+      "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```"
     },
     "glob": {
-      "description": "This key defines globs which filter the files visible in the *Collection browser* for a given Collection.\n\nValues in this array are relative to the Collection [path](https://cloudcannon.com/documentation/articles/collections-reference/#path).\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\n> For more information about developer files, please read our documentation on the [include\\_developer\\_files](https://cloudcannon.com/documentation/articles/collections-reference/#include_developer_files) key.\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```",
+      "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",
@@ -625,7 +625,7 @@
       ],
       "documented": true,
       "title": "glob",
-      "markdownDescription": "This key defines globs which filter the files visible in the *Collection browser* for a given Collection.\n\nValues in this array are relative to the Collection [path](https://cloudcannon.com/documentation/articles/collections-reference/#path).\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\n> For more information about developer files, please read our documentation on the [include\\_developer\\_files](https://cloudcannon.com/documentation/articles/collections-reference/#include_developer_files) key.\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```"
+      "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",
@@ -4525,6 +4525,33 @@
             "min_length_message": {
               "$ref": "#/definitions/type._inputs.*.options.min_length_message"
             },
+            "max_words": {
+              "$ref": "#/definitions/type._inputs.*.options.max_words"
+            },
+            "max_words_message": {
+              "$ref": "#/definitions/type._inputs.*.options.max_words_message"
+            },
+            "min_words": {
+              "$ref": "#/definitions/type._inputs.*.options.min_words"
+            },
+            "min_words_message": {
+              "$ref": "#/definitions/type._inputs.*.options.min_words_message"
+            },
+            "max_graphemes": {
+              "$ref": "#/definitions/type._inputs.*.options.max_graphemes"
+            },
+            "max_graphemes_message": {
+              "$ref": "#/definitions/type._inputs.*.options.max_graphemes_message"
+            },
+            "min_graphemes": {
+              "$ref": "#/definitions/type._inputs.*.options.min_graphemes"
+            },
+            "min_graphemes_message": {
+              "$ref": "#/definitions/type._inputs.*.options.min_graphemes_message"
+            },
+            "locale": {
+              "$ref": "#/definitions/type._inputs.*.options.locale"
+            },
             "pattern": {
               "$ref": "#/definitions/type._inputs.*.options.pattern"
             },
@@ -4761,6 +4788,69 @@
       "title": "min_length_message",
       "markdownDescription": "This key defines a custom error message that explains why a value has failed the validation criteria from `options.min_length`.\n\nThis key requires you to define `options.min_length`.\n\nThis key has no default.\n\nThis key is available for Code, Color, File, Select, Text, Rich Text, and URL Inputs.\n\n## Examples\n\nIn this example, we prompt our team to enter a valid number of characters using a custom message.\n\n```yaml\n_inputs:\n  seo_description:\n    type: markdown\n    comment: Enter a brief description of this blog.\n    options:\n      max_length: 125\n      max_length_message: You are only allowed 125 characters.\n      min_length: 25\n      min_length_message: Please write more than 25 characters.\n```"
     },
+    "type._inputs.*.options.max_words": {
+      "description": "This key defines the maximum string length, in words, that CloudCannon will allow in an Input. When configured, CloudCannon will warn you when an Input value is too long. If the Input already contains a longer value, CloudCannon will require you to remove characters until the Input contains a valid string to save your changes, or discard your unsaved changes.",
+      "type": "number",
+      "documented": true,
+      "title": "max_words",
+      "markdownDescription": "This key defines the maximum string length, in words, that CloudCannon will allow in an Input. When configured, CloudCannon will warn you when an Input value is too long. If the Input already contains a longer value, CloudCannon will require you to remove characters until the Input contains a valid string to save your changes, or discard your unsaved changes."
+    },
+    "type._inputs.*.options.max_words_message": {
+      "description": "This key defines the message that explains which maximum string length an Input will accept. This key requires you to define `options.max_words.",
+      "type": "string",
+      "documented": true,
+      "title": "max_words_message",
+      "markdownDescription": "This key defines the message that explains which maximum string length an Input will accept. This key requires you to define `options.max_words."
+    },
+    "type._inputs.*.options.min_words": {
+      "description": "This key defines the minimum string length, in words, that CloudCannon will allow in an Input. When configured, CloudCannon will warn you when an Input value is too short. If the Input already contains a shorter value, CloudCannon will require you to add characters until the Input contains a valid string to save your changes, or discard your unsaved changes.",
+      "type": "number",
+      "documented": true,
+      "title": "min_words",
+      "markdownDescription": "This key defines the minimum string length, in words, that CloudCannon will allow in an Input. When configured, CloudCannon will warn you when an Input value is too short. If the Input already contains a shorter value, CloudCannon will require you to add characters until the Input contains a valid string to save your changes, or discard your unsaved changes."
+    },
+    "type._inputs.*.options.min_words_message": {
+      "description": "This key defines the message that explains which minimum string length an Input will accept. This key requires you to define `options.min_words`.",
+      "type": "string",
+      "documented": true,
+      "title": "min_words_message",
+      "markdownDescription": "This key defines the message that explains which minimum string length an Input will accept. This key requires you to define `options.min_words`."
+    },
+    "type._inputs.*.options.max_graphemes": {
+      "description": "This key defines the maximum string length, in graphemes, that CloudCannon will allow in an Input. When configured, CloudCannon will warn you when an Input value is too long. If the Input already contains a longer value, CloudCannon will require you to remove characters until the Input contains a valid string to save your changes, or discard your unsaved changes.",
+      "type": "number",
+      "documented": true,
+      "title": "max_graphemes",
+      "markdownDescription": "This key defines the maximum string length, in graphemes, that CloudCannon will allow in an Input. When configured, CloudCannon will warn you when an Input value is too long. If the Input already contains a longer value, CloudCannon will require you to remove characters until the Input contains a valid string to save your changes, or discard your unsaved changes."
+    },
+    "type._inputs.*.options.max_graphemes_message": {
+      "description": "This key defines the message that explains which maximum string length an Input will accept. This key requires you to define `options.max_graphemes.",
+      "type": "string",
+      "documented": true,
+      "title": "max_graphemes_message",
+      "markdownDescription": "This key defines the message that explains which maximum string length an Input will accept. This key requires you to define `options.max_graphemes."
+    },
+    "type._inputs.*.options.min_graphemes": {
+      "description": "This key defines the minimum string length, in graphemes, that CloudCannon will allow in an Input. When configured, CloudCannon will warn you when an Input value is too short. If the Input already contains a shorter value, CloudCannon will require you to add characters until the Input contains a valid string to save your changes, or discard your unsaved changes.",
+      "type": "number",
+      "documented": true,
+      "title": "min_graphemes",
+      "markdownDescription": "This key defines the minimum string length, in graphemes, that CloudCannon will allow in an Input. When configured, CloudCannon will warn you when an Input value is too short. If the Input already contains a shorter value, CloudCannon will require you to add characters until the Input contains a valid string to save your changes, or discard your unsaved changes."
+    },
+    "type._inputs.*.options.min_graphemes_message": {
+      "description": "This key defines the message that explains which minimum string length an Input will accept. This key requires you to define `options.min_graphemes`.",
+      "type": "string",
+      "documented": true,
+      "title": "min_graphemes_message",
+      "markdownDescription": "This key defines the message that explains which minimum string length an Input will accept. This key requires you to define `options.min_graphemes`."
+    },
+    "type._inputs.*.options.locale": {
+      "description": "This key defines the locale that CloudCannon uses to determine the number of words or graphemes in this Input, if you have `max_words`, `min_words`, `max_graphemes`, or `min_graphemes` configured.",
+      "type": "string",
+      "documented": true,
+      "title": "locale",
+      "markdownDescription": "This key defines the locale that CloudCannon uses to determine the number of words or graphemes in this Input, if you have `max_words`, `min_words`, `max_graphemes`, or `min_graphemes` configured."
+    },
     "type._inputs.*.options.pattern": {
       "description": "This key defines a [regular expression](https://re2js.leopard.in.ua/) that the Input value must match.\n\nWhen configured, CloudCannon will require you to enter a value that matches the REGEX pattern.\n\nIf the Input already contains an invalid value, CloudCannon will require you to enter a valid string to save your changes, or discard your unsaved\nchanges.\n\nValue must be a valid REGEX string.\n\nIf your REGEX string includes a `\\` character and CloudCannon Configuration File is a `.yml` file, use single quotes `'` around the string to avoid a\nbuild error.\n\nThis key has no default.\n\nThis key is available for Code, Color, File, Select, Text, Rich Text, and URL Inputs.\n\nTo use this key in a Select Input, `allow_create` must be set to `true`.\n\n## Examples\n\nIn this example, we want our team to add an email address to the `contact_email` Input using the correct email format.\n\n```yaml\n_inputs:\n  contact_email:\n    type: email\n    options:\n      pattern: '[a-zA-Z0-9._%+-]+@[a-zA-Z0-9.-]+\\.[a-zA-Z]{2,}'\n      pattern_message: 'Please use the format ___@___.__'\n```",
       "type": "string",
@@ -5053,6 +5143,33 @@
             "min_length_message": {
               "$ref": "#/definitions/type._inputs.*.options.min_length_message"
             },
+            "max_words": {
+              "$ref": "#/definitions/type._inputs.*.options.max_words"
+            },
+            "max_words_message": {
+              "$ref": "#/definitions/type._inputs.*.options.max_words_message"
+            },
+            "min_words": {
+              "$ref": "#/definitions/type._inputs.*.options.min_words"
+            },
+            "min_words_message": {
+              "$ref": "#/definitions/type._inputs.*.options.min_words_message"
+            },
+            "max_graphemes": {
+              "$ref": "#/definitions/type._inputs.*.options.max_graphemes"
+            },
+            "max_graphemes_message": {
+              "$ref": "#/definitions/type._inputs.*.options.max_graphemes_message"
+            },
+            "min_graphemes": {
+              "$ref": "#/definitions/type._inputs.*.options.min_graphemes"
+            },
+            "min_graphemes_message": {
+              "$ref": "#/definitions/type._inputs.*.options.min_graphemes_message"
+            },
+            "locale": {
+              "$ref": "#/definitions/type._inputs.*.options.locale"
+            },
             "pattern": {
               "$ref": "#/definitions/type._inputs.*.options.pattern"
             },
@@ -5212,6 +5329,33 @@
             "min_length_message": {
               "$ref": "#/definitions/type._inputs.*.options.min_length_message"
             },
+            "max_words": {
+              "$ref": "#/definitions/type._inputs.*.options.max_words"
+            },
+            "max_words_message": {
+              "$ref": "#/definitions/type._inputs.*.options.max_words_message"
+            },
+            "min_words": {
+              "$ref": "#/definitions/type._inputs.*.options.min_words"
+            },
+            "min_words_message": {
+              "$ref": "#/definitions/type._inputs.*.options.min_words_message"
+            },
+            "max_graphemes": {
+              "$ref": "#/definitions/type._inputs.*.options.max_graphemes"
+            },
+            "max_graphemes_message": {
+              "$ref": "#/definitions/type._inputs.*.options.max_graphemes_message"
+            },
+            "min_graphemes": {
+              "$ref": "#/definitions/type._inputs.*.options.min_graphemes"
+            },
+            "min_graphemes_message": {
+              "$ref": "#/definitions/type._inputs.*.options.min_graphemes_message"
+            },
+            "locale": {
+              "$ref": "#/definitions/type._inputs.*.options.locale"
+            },
             "pattern": {
               "$ref": "#/definitions/type._inputs.*.options.pattern"
             },
@@ -5454,6 +5598,33 @@
             "min_length_message": {
               "$ref": "#/definitions/type._inputs.*.options.min_length_message"
             },
+            "max_words": {
+              "$ref": "#/definitions/type._inputs.*.options.max_words"
+            },
+            "max_words_message": {
+              "$ref": "#/definitions/type._inputs.*.options.max_words_message"
+            },
+            "min_words": {
+              "$ref": "#/definitions/type._inputs.*.options.min_words"
+            },
+            "min_words_message": {
+              "$ref": "#/definitions/type._inputs.*.options.min_words_message"
+            },
+            "max_graphemes": {
+              "$ref": "#/definitions/type._inputs.*.options.max_graphemes"
+            },
+            "max_graphemes_message": {
+              "$ref": "#/definitions/type._inputs.*.options.max_graphemes_message"
+            },
+            "min_graphemes": {
+              "$ref": "#/definitions/type._inputs.*.options.min_graphemes"
+            },
+            "min_graphemes_message": {
+              "$ref": "#/definitions/type._inputs.*.options.min_graphemes_message"
+            },
+            "locale": {
+              "$ref": "#/definitions/type._inputs.*.options.locale"
+            },
             "pattern": {
               "$ref": "#/definitions/type._inputs.*.options.pattern"
             },
@@ -6077,6 +6248,33 @@
             "min_length_message": {
               "$ref": "#/definitions/type._inputs.*.options.min_length_message"
             },
+            "max_words": {
+              "$ref": "#/definitions/type._inputs.*.options.max_words"
+            },
+            "max_words_message": {
+              "$ref": "#/definitions/type._inputs.*.options.max_words_message"
+            },
+            "min_words": {
+              "$ref": "#/definitions/type._inputs.*.options.min_words"
+            },
+            "min_words_message": {
+              "$ref": "#/definitions/type._inputs.*.options.min_words_message"
+            },
+            "max_graphemes": {
+              "$ref": "#/definitions/type._inputs.*.options.max_graphemes"
+            },
+            "max_graphemes_message": {
+              "$ref": "#/definitions/type._inputs.*.options.max_graphemes_message"
+            },
+            "min_graphemes": {
+              "$ref": "#/definitions/type._inputs.*.options.min_graphemes"
+            },
+            "min_graphemes_message": {
+              "$ref": "#/definitions/type._inputs.*.options.min_graphemes_message"
+            },
+            "locale": {
+              "$ref": "#/definitions/type._inputs.*.options.locale"
+            },
             "pattern": {
               "$ref": "#/definitions/type._inputs.*.options.pattern"
             },
@@ -6102,12 +6300,20 @@
               "title": "empty_type"
             },
             "allow_resize": {
-              "description": "This 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).",
-              "default": false,
+              "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": "This 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": "**⚠️ 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)."
+            },
+            "prevent_resize": {
+              "description": "Shows or hides the resize handler to vertically resize the input.",
+              "default": false,
+              "type": "boolean",
+              "documented": true,
+              "title": "prevent_resize",
+              "markdownDescription": "Shows or hides the resize handler to vertically resize the input."
             },
             "initial_height": {
               "description": "This key defines the initial height of this input in pixels (px).",
@@ -6559,11 +6765,11 @@
       "markdownDescription": "This key toggles whether CloudCannon will display a tool in your WYSIWYG toolbar to insert a [Snippet](https://cloudcannon.com/documentation/articles/what-is-a-snippet/), if any are available.\n\nSetting this key to `true` will enable a tool in your WYSIWYG toolbar to insert a Snippet."
     },
     "type._editables.*.styles": {
-      "description": "This key toggles whether CloudCannon will display a dropdown menu in your WYSIWYG toolbar to apply a style to selected text.\n\nSetting this key to `true` will enable a dropdown menu in your WYSIWYG toolbar to apply a style to selected text. Styles are the combination of an element and class name. The value for this option is the path (either source or build output) for the CSS file containing styles.",
+      "description": "This key toggles whether CloudCannon will display a dropdown menu in your WYSIWYG toolbar to apply a style to selected text.\n\n## Examples\n\nIn this example, we have enabled a dropdown menu in our WYSIWYG toolbar to apply a style to selected text. The styles are defined in the `/css/styles.css` file.\n\n```yaml\n_editables:\n  content:\n    styles: /css/styles.css\n```\n\nThis example file defines the styles that CloudCannon can add to your WYSIWYG toolbar.\n\n```css\n/* Can be applied to blocks of content */\np.callout {\n  margin: 10px;\n  border: 1px solid #f5f5f5;\n  background-color: #eee;\n}\n\n/* Can be applied to inline content */\nspan.big-blue-text {\n  font-size: 2rem;\n  color: blue;\n}\n\n/* Applied to content, excluded from style dropdown */\nh2 {\n  font-family: cursive;\n}\n\n/* Applied to content, excluded from style dropdown */\n.align-left { text-align: left; }\n.align-center { text-align: center; }\n.align-right { text-align: right; }\n.align-justify { text-align: justify; }\n```",
       "type": "string",
       "documented": true,
       "title": "styles",
-      "markdownDescription": "This key toggles whether CloudCannon will display a dropdown menu in your WYSIWYG toolbar to apply a style to selected text.\n\nSetting this key to `true` will enable a dropdown menu in your WYSIWYG toolbar to apply a style to selected text. Styles are the combination of an element and class name. The value for this option is the path (either source or build output) for the CSS file containing styles."
+      "markdownDescription": "This key toggles whether CloudCannon will display a dropdown menu in your WYSIWYG toolbar to apply a style to selected text.\n\n## Examples\n\nIn this example, we have enabled a dropdown menu in our WYSIWYG toolbar to apply a style to selected text. The styles are defined in the `/css/styles.css` file.\n\n```yaml\n_editables:\n  content:\n    styles: /css/styles.css\n```\n\nThis example file defines the styles that CloudCannon can add to your WYSIWYG toolbar.\n\n```css\n/* Can be applied to blocks of content */\np.callout {\n  margin: 10px;\n  border: 1px solid #f5f5f5;\n  background-color: #eee;\n}\n\n/* Can be applied to inline content */\nspan.big-blue-text {\n  font-size: 2rem;\n  color: blue;\n}\n\n/* Applied to content, excluded from style dropdown */\nh2 {\n  font-family: cursive;\n}\n\n/* Applied to content, excluded from style dropdown */\n.align-left { text-align: left; }\n.align-center { text-align: center; }\n.align-right { text-align: right; }\n.align-justify { text-align: justify; }\n```"
     },
     "type._editables.*.table": {
       "description": "This key toggles whether CloudCannon will display a tool in your WYSIWYG toolbar to insert a table.\n\nSetting this key to `true` will enable a tool in your WYSIWYG toolbar to insert a table. Further table options are available from the table context menu in the rich text editor.",
@@ -7542,6 +7748,33 @@
             "min_length_message": {
               "$ref": "#/definitions/type._inputs.*.options.min_length_message"
             },
+            "max_words": {
+              "$ref": "#/definitions/type._inputs.*.options.max_words"
+            },
+            "max_words_message": {
+              "$ref": "#/definitions/type._inputs.*.options.max_words_message"
+            },
+            "min_words": {
+              "$ref": "#/definitions/type._inputs.*.options.min_words"
+            },
+            "min_words_message": {
+              "$ref": "#/definitions/type._inputs.*.options.min_words_message"
+            },
+            "max_graphemes": {
+              "$ref": "#/definitions/type._inputs.*.options.max_graphemes"
+            },
+            "max_graphemes_message": {
+              "$ref": "#/definitions/type._inputs.*.options.max_graphemes_message"
+            },
+            "min_graphemes": {
+              "$ref": "#/definitions/type._inputs.*.options.min_graphemes"
+            },
+            "min_graphemes_message": {
+              "$ref": "#/definitions/type._inputs.*.options.min_graphemes_message"
+            },
+            "locale": {
+              "$ref": "#/definitions/type._inputs.*.options.locale"
+            },
             "pattern": {
               "$ref": "#/definitions/type._inputs.*.options.pattern"
             },
@@ -8209,6 +8442,33 @@
             "min_length_message": {
               "$ref": "#/definitions/type._inputs.*.options.min_length_message"
             },
+            "max_words": {
+              "$ref": "#/definitions/type._inputs.*.options.max_words"
+            },
+            "max_words_message": {
+              "$ref": "#/definitions/type._inputs.*.options.max_words_message"
+            },
+            "min_words": {
+              "$ref": "#/definitions/type._inputs.*.options.min_words"
+            },
+            "min_words_message": {
+              "$ref": "#/definitions/type._inputs.*.options.min_words_message"
+            },
+            "max_graphemes": {
+              "$ref": "#/definitions/type._inputs.*.options.max_graphemes"
+            },
+            "max_graphemes_message": {
+              "$ref": "#/definitions/type._inputs.*.options.max_graphemes_message"
+            },
+            "min_graphemes": {
+              "$ref": "#/definitions/type._inputs.*.options.min_graphemes"
+            },
+            "min_graphemes_message": {
+              "$ref": "#/definitions/type._inputs.*.options.min_graphemes_message"
+            },
+            "locale": {
+              "$ref": "#/definitions/type._inputs.*.options.locale"
+            },
             "pattern": {
               "$ref": "#/definitions/type._inputs.*.options.pattern"
             },
@@ -8418,6 +8678,33 @@
             "min_length_message": {
               "$ref": "#/definitions/type._inputs.*.options.min_length_message"
             },
+            "max_words": {
+              "$ref": "#/definitions/type._inputs.*.options.max_words"
+            },
+            "max_words_message": {
+              "$ref": "#/definitions/type._inputs.*.options.max_words_message"
+            },
+            "min_words": {
+              "$ref": "#/definitions/type._inputs.*.options.min_words"
+            },
+            "min_words_message": {
+              "$ref": "#/definitions/type._inputs.*.options.min_words_message"
+            },
+            "max_graphemes": {
+              "$ref": "#/definitions/type._inputs.*.options.max_graphemes"
+            },
+            "max_graphemes_message": {
+              "$ref": "#/definitions/type._inputs.*.options.max_graphemes_message"
+            },
+            "min_graphemes": {
+              "$ref": "#/definitions/type._inputs.*.options.min_graphemes"
+            },
+            "min_graphemes_message": {
+              "$ref": "#/definitions/type._inputs.*.options.min_graphemes_message"
+            },
+            "locale": {
+              "$ref": "#/definitions/type._inputs.*.options.locale"
+            },
             "pattern": {
               "$ref": "#/definitions/type._inputs.*.options.pattern"
             },
@@ -8678,8 +8965,8 @@
       "markdownDescription": "This key toggles whether CloudCannon will allow new text values to be created at edit time.\n\nSetting this key to `true` will allow new text values to be created at edit time.\n\n## Examples\n\nIn this example, CloudCannon will allow users to add new values to a *Select Input*.\n\n```yaml\n_inputs:\n  category:\n    type: select\n    options:\n      values:\n        - Blog\n        - News\n      allow_create: true\n```"
     },
     "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```",
-      "default": true,
       "type": "boolean",
       "documented": true,
       "title": "allow_empty",
@@ -9091,6 +9378,33 @@
             "min_length_message": {
               "$ref": "#/definitions/type._inputs.*.options.min_length_message"
             },
+            "max_words": {
+              "$ref": "#/definitions/type._inputs.*.options.max_words"
+            },
+            "max_words_message": {
+              "$ref": "#/definitions/type._inputs.*.options.max_words_message"
+            },
+            "min_words": {
+              "$ref": "#/definitions/type._inputs.*.options.min_words"
+            },
+            "min_words_message": {
+              "$ref": "#/definitions/type._inputs.*.options.min_words_message"
+            },
+            "max_graphemes": {
+              "$ref": "#/definitions/type._inputs.*.options.max_graphemes"
+            },
+            "max_graphemes_message": {
+              "$ref": "#/definitions/type._inputs.*.options.max_graphemes_message"
+            },
+            "min_graphemes": {
+              "$ref": "#/definitions/type._inputs.*.options.min_graphemes"
+            },
+            "min_graphemes_message": {
+              "$ref": "#/definitions/type._inputs.*.options.min_graphemes_message"
+            },
+            "locale": {
+              "$ref": "#/definitions/type._inputs.*.options.locale"
+            },
             "pattern": {
               "$ref": "#/definitions/type._inputs.*.options.pattern"
             },
@@ -9623,13 +9937,13 @@
             "type": "string",
             "documented": true,
             "title": "values_from_glob[*]",
-            "description": "This key represents an individual glob pattern string in the `values_from_glob` array.\n\nThe value is a string that specifies a file path pattern relative to the root of your repository. The path must end in the file extension `.cloudcannon.structure-value.yml` (note the singular form of \"value\").\n\n## Examples\n\nIn this example, the `staff` Array Input uses inline *Structure* values from the main *Configuration File* and also references another value from the `boardMember.cloudcannon.structure-value.yml` in the `/.cloudcannon/structures/` folder.\n\n```yaml\n_inputs:\n  staff:\n    type: array\n    options:\n      structures:\n      values_from_glob: /.cloudcannon/structures/boardMember.cloudcannon.structure-value.yml\n      values:\n        - label: Employee\n          value:\n            name:\n            title:\n            profile_picture:\n        - label: Manager\n          value:\n            name:\n            title:\n            profile_picture:\n            url:\n```",
-            "markdownDescription": "This key represents an individual glob pattern string in the `values_from_glob` array.\n\nThe value is a string that specifies a file path pattern relative to the root of your repository. The path must end in the file extension `.cloudcannon.structure-value.yml` (note the singular form of \"value\").\n\n## Examples\n\nIn this example, the `staff` Array Input uses inline *Structure* values from the main *Configuration File* and also references another value from the `boardMember.cloudcannon.structure-value.yml` in the `/.cloudcannon/structures/` folder.\n\n```yaml\n_inputs:\n  staff:\n    type: array\n    options:\n      structures:\n      values_from_glob: /.cloudcannon/structures/boardMember.cloudcannon.structure-value.yml\n      values:\n        - label: Employee\n          value:\n            name:\n            title:\n            profile_picture:\n        - label: Manager\n          value:\n            name:\n            title:\n            profile_picture:\n            url:\n```"
+            "description": "This key represents an individual glob pattern string in the `values_from_glob` array.\n\nThe value is a string that specifies a file path pattern relative to the root of your repository. The path must end in the file extension `.cloudcannon.structure-value.yml` (note the singular form of \"value\").\n\n## Examples\n\nIn this example, the `staff` Array Input uses inline *Structure* values from the main *Configuration File* and also references another value from the `boardMember.cloudcannon.structure-value.yml` in the `/.cloudcannon/structures/` folder.\n\n```yaml\n_inputs:\n  staff:\n    type: array\n    options:\n      structures:\n        values_from_glob:\n          - /.cloudcannon/structures/boardMember.cloudcannon.structure-value.yml\n        values:\n          - label: Employee\n            value:\n              name:\n              title:\n              profile_picture:\n          - label: Manager\n            value:\n              name:\n              title:\n              profile_picture:\n              url:\n```",
+            "markdownDescription": "This key represents an individual glob pattern string in the `values_from_glob` array.\n\nThe value is a string that specifies a file path pattern relative to the root of your repository. The path must end in the file extension `.cloudcannon.structure-value.yml` (note the singular form of \"value\").\n\n## Examples\n\nIn this example, the `staff` Array Input uses inline *Structure* values from the main *Configuration File* and also references another value from the `boardMember.cloudcannon.structure-value.yml` in the `/.cloudcannon/structures/` folder.\n\n```yaml\n_inputs:\n  staff:\n    type: array\n    options:\n      structures:\n        values_from_glob:\n          - /.cloudcannon/structures/boardMember.cloudcannon.structure-value.yml\n        values:\n          - label: Employee\n            value:\n              name:\n              title:\n              profile_picture:\n          - label: Manager\n            value:\n              name:\n              title:\n              profile_picture:\n              url:\n```"
           },
           "documented": true,
           "title": "values_from_glob",
-          "description": "This key defines globs that filter which files CloudCannon should use for *Structure* value 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.structure-value.yml` (note the singular form of \"value\").\n\nYou can use this key anywhere you would use the `_structures.*.values` key.\n\nPlease see our documentation on [structures_from_glob](https://cloudcannon.com/documentation/articles/configuration-file-reference/#_structures_from_glob) for defining a\n*Structure* in a split *Configuration File*.\n\nThis key has no default.\n\n## Examples\n\nIn this example, the `staff` Array Input uses inline *Structure* values from the main *Configuration File* and also references another value from the `boardMember.cloudcannon.structure_value.yml` in the `/.cloudcannon/structures/` folder.\n\n```yaml\n_inputs:\n  staff:\n    type: array\n    options:\n      structures:\n      values_from_glob: /.cloudcannon/structures/boardMember.cloudcannon.structure-value.yml\n      values:\n        - label: Employee\n          value:\n            name:\n            title:\n            profile_picture:\n        - label: Manager\n          value:\n            name:\n            title:\n            profile_picture:\n            url:\n```\n\n```yaml\nlabel: Board\nvalue:\n  name:\n  title:\n  profile_picture:\n  url:\n  description:\n```",
-          "markdownDescription": "This key defines globs that filter which files CloudCannon should use for *Structure* value 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.structure-value.yml` (note the singular form of \"value\").\n\nYou can use this key anywhere you would use the `_structures.*.values` key.\n\nPlease see our documentation on [structures_from_glob](https://cloudcannon.com/documentation/articles/configuration-file-reference/#_structures_from_glob) for defining a\n*Structure* in a split *Configuration File*.\n\nThis key has no default.\n\n## Examples\n\nIn this example, the `staff` Array Input uses inline *Structure* values from the main *Configuration File* and also references another value from the `boardMember.cloudcannon.structure_value.yml` in the `/.cloudcannon/structures/` folder.\n\n```yaml\n_inputs:\n  staff:\n    type: array\n    options:\n      structures:\n      values_from_glob: /.cloudcannon/structures/boardMember.cloudcannon.structure-value.yml\n      values:\n        - label: Employee\n          value:\n            name:\n            title:\n            profile_picture:\n        - label: Manager\n          value:\n            name:\n            title:\n            profile_picture:\n            url:\n```\n\n```yaml\nlabel: Board\nvalue:\n  name:\n  title:\n  profile_picture:\n  url:\n  description:\n```"
+          "description": "This key defines globs that filter which files CloudCannon should use for *Structure* value 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.structure-value.yml` (note the singular form of \"value\").\n\nYou can use this key anywhere you would use the `_structures.*.values` key.\n\nPlease see our documentation on [structures_from_glob](https://cloudcannon.com/documentation/developer-reference/configuration-file/types/_structures_from_glob/) for defining a\n*Structure* in a split *Configuration File*.\n\nThis key has no default.\n\n## Examples\n\nIn this example, the `staff` Array Input uses inline *Structure* values from the main *Configuration File* and also references another value from the `boardMember.cloudcannon.structure_value.yml` in the `/.cloudcannon/structures/` folder.\n\n```yaml\n_inputs:\n  staff:\n    type: array\n    options:\n      structures:\n        values_from_glob:\n          - /.cloudcannon/structures/boardMember.cloudcannon.structure-value.yml\n        values:\n          - label: Employee\n            value:\n              name:\n              title:\n              profile_picture:\n          - label: Manager\n            value:\n              name:\n              title:\n              profile_picture:\n              url:\n```\n\n```yaml\nlabel: Board\nvalue:\n  name:\n  title:\n  profile_picture:\n  url:\n  description:\n```",
+          "markdownDescription": "This key defines globs that filter which files CloudCannon should use for *Structure* value 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.structure-value.yml` (note the singular form of \"value\").\n\nYou can use this key anywhere you would use the `_structures.*.values` key.\n\nPlease see our documentation on [structures_from_glob](https://cloudcannon.com/documentation/developer-reference/configuration-file/types/_structures_from_glob/) for defining a\n*Structure* in a split *Configuration File*.\n\nThis key has no default.\n\n## Examples\n\nIn this example, the `staff` Array Input uses inline *Structure* values from the main *Configuration File* and also references another value from the `boardMember.cloudcannon.structure_value.yml` in the `/.cloudcannon/structures/` folder.\n\n```yaml\n_inputs:\n  staff:\n    type: array\n    options:\n      structures:\n        values_from_glob:\n          - /.cloudcannon/structures/boardMember.cloudcannon.structure-value.yml\n        values:\n          - label: Employee\n            value:\n              name:\n              title:\n              profile_picture:\n          - label: Manager\n            value:\n              name:\n              title:\n              profile_picture:\n              url:\n```\n\n```yaml\nlabel: Board\nvalue:\n  name:\n  title:\n  profile_picture:\n  url:\n  description:\n```"
         },
         "id_key": {
           "description": "This key defines which key within `values[*].value` CloudCannon should use to identify the Structure option.\n\nIf CloudCannon cannot find this key in a Structure value, it will compare all other key names in the Structure value to find the correct one.\n\nBy default, this key is `_type`.\n\n## Examples\n\nIn this example, we have change the `id_key` from the default `_type` to `component` to match our existing configuration in the `content_blocks` Array input.\n\n```yaml\n_inputs:\n  content_blocks___1___:\n    type: array\n    options:\n    structures: _structures.page_components\n_structures:\n  page_components:\n    id_key___2___: component\n    values:\n      - label: Hero Component\n        value:\n          component___3___: hero\n          title:\n          description:\n          image_path:\n          link:\n            text:\n            url:\n      - label: Feature Component\n        value:\n          component: feature\n          image_path:\n          title:\n          description:\n          button:\n            link:\n            text:\n          reversed_layout: false\n      - label: Video Component\n        value:\n          component: video\n          image_path:\n          videoUrl:\n```",
@@ -10027,8 +10341,8 @@
       },
       "documented": true,
       "title": "_structures_from_glob",
-      "description": "This key defines globs that filter which files CloudCannon should use for *Structure* configuration.\n\nValues in this array are relative to the root of your repository (i.e., `/`, not the value of `source`) and must end in the file extension\n`.cloudcannon.structures.yml`.\n\nYou can use this key anywhere you would use the `_structures` key in the configuration cascade.\n\nPlease see our documentation on [values_from_glob](https://cloudcannon.com/documentation/articles/configuration-file-reference/#values_from_glob) for defining individual\n*Structure* values in a split *Configuration File*.\n\nThis key has no default.\n\n## Examples\n\nIn this example, we have several *Structure Configuration Files* in the `.cloudcannon/structures/` folder. The value of the `_structures_from_glob` key tells CloudCannon to use the `staffMembers.cloudcannon.structures.yml` file in that folder.\n\n```yaml\n_structures_from_glob:\n  - '/.cloudcannon/structures/staffMembers.cloudcannon.structures.yml'\n```\n\n```yaml\nstaff:\n  style: modal\n  values:\n    - label: Employee\n      value:\n        name:\n        job_description:\n        profile_picture:\n    - label: Manager\n      value:\n        name:\n        job_description:\n        profile_picture:\n        url:\n```",
-      "markdownDescription": "This key defines globs that filter which files CloudCannon should use for *Structure* configuration.\n\nValues in this array are relative to the root of your repository (i.e., `/`, not the value of `source`) and must end in the file extension\n`.cloudcannon.structures.yml`.\n\nYou can use this key anywhere you would use the `_structures` key in the configuration cascade.\n\nPlease see our documentation on [values_from_glob](https://cloudcannon.com/documentation/articles/configuration-file-reference/#values_from_glob) for defining individual\n*Structure* values in a split *Configuration File*.\n\nThis key has no default.\n\n## Examples\n\nIn this example, we have several *Structure Configuration Files* in the `.cloudcannon/structures/` folder. The value of the `_structures_from_glob` key tells CloudCannon to use the `staffMembers.cloudcannon.structures.yml` file in that folder.\n\n```yaml\n_structures_from_glob:\n  - '/.cloudcannon/structures/staffMembers.cloudcannon.structures.yml'\n```\n\n```yaml\nstaff:\n  style: modal\n  values:\n    - label: Employee\n      value:\n        name:\n        job_description:\n        profile_picture:\n    - label: Manager\n      value:\n        name:\n        job_description:\n        profile_picture:\n        url:\n```"
+      "description": "This key defines globs that filter which files CloudCannon should use for *Structure* configuration.\n\nValues in this array are relative to the root of your repository (i.e., `/`, not the value of `source`) and must end in the file extension\n`.cloudcannon.structures.yml`.\n\nYou can use this key anywhere you would use the `_structures` key in the configuration cascade.\n\nPlease see our documentation on [values_from_glob](https://cloudcannon.com/documentation/developer-reference/configuration-file/types/structure/values_from_glob/) for defining individual\n*Structure* values in a split *Configuration File*.\n\nThis key has no default.\n\n## Examples\n\nIn this example, we have several *Structure Configuration Files* in the `.cloudcannon/structures/` folder. The value of the `_structures_from_glob` key tells CloudCannon to use the `staffMembers.cloudcannon.structures.yml` file in that folder.\n\n```yaml\n_structures_from_glob:\n  - '/.cloudcannon/structures/staffMembers.cloudcannon.structures.yml'\n```\n\n```yaml\nstaff:\n  style: modal\n  values:\n    - label: Employee\n      value:\n        name:\n        job_description:\n        profile_picture:\n    - label: Manager\n      value:\n        name:\n        job_description:\n        profile_picture:\n        url:\n```",
+      "markdownDescription": "This key defines globs that filter which files CloudCannon should use for *Structure* configuration.\n\nValues in this array are relative to the root of your repository (i.e., `/`, not the value of `source`) and must end in the file extension\n`.cloudcannon.structures.yml`.\n\nYou can use this key anywhere you would use the `_structures` key in the configuration cascade.\n\nPlease see our documentation on [values_from_glob](https://cloudcannon.com/documentation/developer-reference/configuration-file/types/structure/values_from_glob/) for defining individual\n*Structure* values in a split *Configuration File*.\n\nThis key has no default.\n\n## Examples\n\nIn this example, we have several *Structure Configuration Files* in the `.cloudcannon/structures/` folder. The value of the `_structures_from_glob` key tells CloudCannon to use the `staffMembers.cloudcannon.structures.yml` file in that folder.\n\n```yaml\n_structures_from_glob:\n  - '/.cloudcannon/structures/staffMembers.cloudcannon.structures.yml'\n```\n\n```yaml\nstaff:\n  style: modal\n  values:\n    - label: Employee\n      value:\n        name:\n        job_description:\n        profile_picture:\n    - label: Manager\n      value:\n        name:\n        job_description:\n        profile_picture:\n        url:\n```"
     },
     "entries_comment": {
       "description": "This key defines the subtitle text above the key input when adding or renaming entries within a mutable *Object Input*.\n\nThe value is a string that supports a limited selection of Markdown formatting: links, bold, italic, subscript, superscript, and inline code elements are allowed.\n\nAvailable for Mutable Objects only.\n\n## Examples\n\nIn this example, we have configured a comment with Markdown formatting to provide help text above the key input.\n\n```yaml\n_inputs:\n  metadata:\n    type: object\n    options:\n      allow_create: true\n      entries:\n        comment: Key names should be **lowercase** and use underscores (e.g., `article_title`)\n```",