@cloudcannon/configuration-types 0.0.50 → 0.0.52

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",
@@ -9628,8 +9628,8 @@
           },
           "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: /.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: /.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 +10027,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```",

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

@@ -10573,12 +10573,99 @@
     "type._snippets_definitions": {
       "id": "type._snippets_definitions",
       "title": "Snippets Definitions",
-      "description": "Extended option used when creating more complex custom snippets.",
+      "description": "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.",
       "type": "object",
       "propertyNames": {
         "type": "string"
       },
-      "additionalProperties": {}
+      "additionalProperties": {
+        "$ref": "#/$defs/type.snippet-definition-value"
+      }
+    },
+    "type.snippet-definition-value": {
+      "id": "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\" }.",
+      "anyOf": [
+        {
+          "$ref": "#/$defs/type.snippet-format"
+        },
+        {
+          "$ref": "#/$defs/type.snippet-model"
+        },
+        {
+          "title": "Parser Model Array",
+          "description": "An array of model configurations, typically used for positional_args or named_args.",
+          "type": "array",
+          "items": {
+            "$ref": "#/$defs/type.snippet-model"
+          }
+        },
+        {
+          "title": "Select Values Array",
+          "description": "An array of select options, typically used for language lists.",
+          "type": "array",
+          "items": {
+            "$ref": "#/$defs/type.snippet-definition-select-value"
+          }
+        },
+        {
+          "title": "String Value",
+          "description": "A string value, commonly used for shortcode_name, tag_name, content_key, and similar definitions.",
+          "type": "string"
+        },
+        {
+          "title": "Number Value",
+          "description": "A numeric value.",
+          "type": "number"
+        },
+        {
+          "title": "Boolean Value",
+          "description": "A boolean value.",
+          "type": "boolean"
+        },
+        {
+          "title": "String Array",
+          "description": "An array of strings.",
+          "type": "array",
+          "items": {
+            "type": "string"
+          }
+        }
+      ]
+    },
+    "type.snippet-definition-select-value": {
+      "id": "type.snippet-definition-select-value",
+      "title": "Snippet Definition Select Value",
+      "description": "A value option for select inputs, typically used in language lists.",
+      "type": "object",
+      "properties": {
+        "name": {
+          "description": "The display name for this option.",
+          "type": "string"
+        },
+        "value": {
+          "description": "The value for this option.",
+          "anyOf": [
+            {
+              "title": "String",
+              "type": "string"
+            },
+            {
+              "title": "Number",
+              "type": "number"
+            },
+            {
+              "title": "Boolean",
+              "type": "boolean"
+            }
+          ]
+        }
+      },
+      "required": [
+        "value"
+      ],
+      "additionalProperties": false
     }
   }
 }

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

@@ -392,12 +392,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```",
@@ -512,7 +512,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": [
@@ -551,11 +551,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```",
@@ -630,7 +630,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": [
@@ -938,14 +938,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",
@@ -971,7 +971,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",
@@ -9892,8 +9892,8 @@
           },
           "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: /.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: /.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```",
@@ -10291,8 +10291,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```",
@@ -13177,14 +13177,128 @@
     },
     "type._snippets_definitions": {
       "title": "Snippets Definitions",
-      "description": "This key defines extended options used when creating more complex custom snippets.",
+      "description": "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": "object",
       "propertyNames": {
         "type": "string"
       },
-      "additionalProperties": {},
+      "additionalProperties": {
+        "$ref": "#/definitions/type.snippet-definition-value"
+      },
       "documented": true,
-      "markdownDescription": "This key defines extended options used when creating more complex custom snippets."
+      "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"
+        },
+        {
+          "$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"
+          },
+          "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"
+          },
+          "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\" }]`."
+        },
+        {
+          "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."
+        },
+        {
+          "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."
+        },
+        {
+          "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",
+            "documented": true,
+            "title": "snippet-definition-value(string-array)[*]",
+            "description": "A string item in the array.",
+            "markdownDescription": "A string item in the array."
+          },
+          "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."
+        }
+      ],
+      "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": {
+          "description": "The display name shown to users when selecting this option. For example, \"JavaScript\" for a language with value \"js\".",
+          "type": "string",
+          "documented": true,
+          "title": "name",
+          "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",
+              "documented": true
+            },
+            {
+              "title": "Number Select Value",
+              "type": "number",
+              "documented": true
+            },
+            {
+              "title": "Boolean Select Value",
+              "type": "boolean",
+              "documented": true
+            }
+          ],
+          "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."
+        }
+      },
+      "required": [
+        "value"
+      ],
+      "additionalProperties": false,
+      "documented": true,
+      "markdownDescription": "A value option for select inputs, typically used in language lists. Contains a display name and the actual value to use."
     }
   },
   "documented": false,