[System]
You are a helpful assistant that answers strictly in JSON. Here's the JSON schema you must adhere to:
<schema>
{"$schema":"http://json-schema.org/draft-07/schema#","$id":"https://json.schemastore.org/nest-cli.json","$comment":"https://docs.nestjs.com/cli/monorepo#cli-properties","definitions":{"CompilerOptions":{"$comment":"https://docs.nestjs.com/cli/monorepo#global-compiler-options","type":"object","description":"A map with keys specifying compiler options and values specifying the option setting. See https://docs.nestjs.com/cli/monorepo#global-compiler-options for details","default":{},"properties":{"tsConfigPath":{"$comment":"https://github.com/nestjs/nest-cli/blob/master/lib/compiler/defaults/webpac-defaults.ts","default":"tsconfig.build.json","type":"string","description":"(monorepo only) Points at the file containing the tsconfig.json settings that will be used when nest build or nest start is called without a project option (e.g., when the default project is built or started). 'nest build' will not work as expected without this file."},"builder":{"anyOf":[{"$comment":"https://github.com/nestjs/nest-cli/blob/master/commands/build.command.ts","default":"tsc","type":"string","enum":["tsc","webpack","swc"],"description":"Builder to be used (tsc, webpack, swc). For details on how to configure `SWC` see https://docs.nestjs.com/recipes/swc#getting-started"},{"type":"object","properties":{"type":{"$comment":"https://github.com/nestjs/nest-cli/blob/master/commands/build.command.ts","default":"tsc","type":"string","enum":["tsc","webpack","swc"],"description":"Builder to be used (tsc, webpack, swc). For details on how to configure `SWC` see https://docs.nestjs.com/recipes/swc#getting-started"},"options":{"type":"object","properties":{"outDir":{"type":"string","description":"The directory to output files."},"filenames":{"type":"array","items":{"type":"string"},"description":"Array of filenames to be included."},"sync":{"type":"boolean","description":"Whether to synchronize files or not."},"extensions":{"type":"array","items":{"type":"string"},"description":"Array of file extensions to be considered."},"copyFiles":{"type":"boolean","description":"Whether to copy files or not."},"includeDotfiles":{"type":"boolean","description":"Whether to include dotfiles or not."},"quiet":{"type":"boolean","description":"Whether to suppress logs or not."},"watch":{"type":"boolean","description":"Whether to watch files for changes or not."},"swcrcPath":{"type":"string","description":"Path to SWC config file to use."}}}}}]},"typeCheck":{"$comment":"https://github.com/nestjs/nest-cli/blob/master/commands/build.command.ts","default":false,"type":"boolean","description":"If true, enable type checking (when SWC is used). See https://docs.nestjs.com/recipes/swc#type-checking for details."},"webpack":{"$comment":"https://github.com/nestjs/nest-cli/blob/master/commands/build.command.ts","default":false,"type":"boolean","description":"If true, use webpack compiler (deprecated option, use `builder` instead). If false or not present, use tsc. In monorepo mode, the default is true (use webpack), in standard mode, the default is false (use tsc). See https://docs.nestjs.com/cli/monorepo#cli-properties for details."},"webpackConfigPath":{"$comment":"https://github.com/nestjs/nest-cli/blob/master/commands/build.command.ts","default":"webpack.config.js","type":"string","description":"Points at a webpack options file. If not specified, Nest looks for the file webpack.config.js."},"plugins":{"$comment":"https://docs.nestjs.com/openapi/cli-plugin#using-the-cli-plugin","default":[],"type":"array","items":{"$ref":"#/definitions/PluginItems"}},"assets":{"$comment":"https://docs.nestjs.com/cli/monorepo#assets","default":[],"type":"array","items":{"$ref":"#/definitions/AssetsOptions"},"description":"Enables automatically distributing non-TypeScript assets whenever a compilation step begins (asset distribution does not happen on incremental compiles in --watch mode). Accept glob-like string and object. See https://docs.nestjs.com/cli/monorepo#assets for details."},"watchAssets":{"default":false,"type":"boolean","description":"If true, run in watch-mode, watching all non-TypeScript assets. Setting watchAssets in a top-level compilerOptions property overrides any watchAssets settings within the assets property."},"deleteOutDir":{"type":"boolean","default":false,"description":"If true, whenever the compiler is invoked, it will first remove the compilation output directory (as configured in tsconfig.json, where the default is ./dist)."},"manualRestart":{"type":"boolean","default":false,"description":"If true, enables the shortcut `rs` to manually restart the server."}},"additionalProperties":false},"AssetsOptions":{"$comment":"https://docs.nestjs.com/cli/monorepo#assets","type":["string","object"],"description":"For finer control, the element can be object.","properties":{"include":{"type":"string","description":"Glob-like file specifications for the assets to be distributed."},"exclude":{"type":"string","description":"Glob-like file specifications for the assets to be excluded from the include list."},"outDir":{"type":"string","description":"A string specifying the path (relative to the root folder) where the assets should be distributed. Defaults to the same output directory configured for compiler output."},"watchAssets":{"type":"boolean","description":"If true, run in watch mode watching specified assets. Setting watchAssets in a top-level compilerOptions property overrides any watchAssets settings within the assets property."}},"additionalProperties":false},"GenerateOptions":{"$comment":"https://docs.nestjs.com/cli/monorepo#global-generate-options","type":"object","description":"A map with keys specifying global generate options and values specifying the option setting. See https://docs.nestjs.com/cli/monorepo#global-generate-options for details","properties":{"spec":{"$ref":"#/definitions/GenerateSpecOptions"},"flat":{"$ref":"#/definitions/GenerateFlatOptions"},"baseDir":{"$ref":"#/definitions/GenerateBaseDirOptions"}},"default":{},"additionalProperties":false},"GenerateFlatOptions":{"$comment":"https://docs.nestjs.com/cli/monorepo#global-generate-options","type":"boolean","default":false,"description":"If true, all generate commands will generate a flat structure"},"GenerateSpecOptions":{"$comment":"https://docs.nestjs.com/cli/monorepo#global-generate-options","type":["boolean","object"],"description":"If the value is boolean, a value of true enables spec generation by default and a value of false disables it. A flag passed on the CLI command line overrides this setting, as does a project-specific generateOptions setting (more below). If the value is an object, each key represents a schematic name, and the boolean value determines whether the default spec generation is enabled / disabled for that specific schematic. See https://docs.nestjs.com/cli/monorepo#global-generate-options for details.","properties":{"application":{"type":"boolean","description":"Generate spec file for application schematics or not."},"class":{"type":"boolean","description":"Disable spec file generation for class schematics."},"cl":{"type":"boolean","description":"Alias for class"},"configuration":{"type":"boolean","description":"Generate spec file for configuration schematics or not."},"config":{"type":"boolean","description":"Alias for configuration"},"controller":{"type":"boolean","description":"Generate spec file for controller schematics or not."},"co":{"type":"boolean","description":"Alias for controller"},"decorator":{"type":"boolean","description":"Generate spec file for decorator schematics or not."},"d":{"type":"boolean","description":"Alias for decorator"},"filter":{"type":"boolean","description":"Generate spec file for filter schematics or not."},"f":{"type":"boolean","description":"Alias for filter"},"gateway":{"type":"boolean","description":"Generate spec file for gateway schematics or not."},"ga":{"type":"boolean","description":"Alias for gateway"},"guard":{"type":"boolean","description":"Generate spec file for guard schematics or not."},"gu":{"type":"boolean","description":"Alias for guard"},"interceptor":{"type":"boolean","description":"Generate spec file for interceptor schematics or not."},"in":{"type":"boolean","description":"Alias for interceptor"},"interface":{"type":"boolean","description":"Generate spec file for interface schematics or not."},"middleware":{"type":"boolean","description":"Generate spec file for middleware schematics or not."},"mi":{"type":"boolean","description":"Alias for middleware"},"module":{"type":"boolean","description":"Generate spec file for module schematics or not."},"mo":{"type":"boolean","description":"Alias for module"},"pipe":{"type":"boolean","description":"Generate spec file for pipe schematics or not."},"pi":{"type":"boolean","description":"Alias for pipe"},"provider":{"type":"boolean","description":"Generate spec file for provider schematics or not."},"pr":{"type":"boolean","description":"Alias for provider"},"resolver":{"type":"boolean","description":"Generate spec file for resolver schematics or not."},"r":{"type":"boolean","description":"Alias for resolver"},"service":{"type":"boolean","description":"Generate spec file for service schematics or not."},"s":{"type":"boolean","description":"Alias for resolver"},"library":{"type":"boolean","description":"Generate spec file for library schematics or not."},"lib":{"type":"boolean","description":"Alias for library"},"sub-app":{"type":"boolean","description":"Generate spec file for sub-app schematics or not."},"app":{"type":"boolean","description":"Alias for sub-app"},"resource":{"type":"boolean","description":"Generate spec file for resource schematics or not."},"res":{"type":"boolean","description":"Alias for resource"}},"additionalProperties":false},"GenerateBaseDirOptions":{"type":"string","default":"","description":"Base directory"},"ProjectConfiguration":{"type":"object","properties":{"type":{"type":"string"},"root":{"type":"string"},"entryFile":{"type":"string"},"sourceRoot":{"type":"string"},"compilerOptions":{"$ref":"#/definitions/CompilerOptions"},"generateOptions":{"$ref":"#/definitions/GenerateOptions"}},"additionalProperties":false},"PluginItems":{"$comment":"https://docs.nestjs.com/openapi/cli-plugin#using-the-cli-plugin","type":["string","object"],"properties":{"name":{"type":"string","description":"The npm package name of the cli plugin, eg @nestjs/swagger."},"options":{"anyOf":[{"$ref":"#/definitions/PluginOptions"},{"$ref":"#/definitions/GraphQLPluginOptions"},{"$ref":"#/definitions/SwaggerPluginOptions"}]}}},"PluginOptions":{"type":"object","properties":{"introspectComments":{"type":"boolean","default":true,"description":"If set to true, plugin will generate descriptions and example values for properties based on comments."}}},"GraphQLPluginOptions":{"$comment":"https://docs.nestjs.com/graphql/cli-plugin#using-the-cli-plugin","type":"object","properties":{"typeFileNameSuffix":{"type":"array","default":[".input.ts",".args.ts",".entity.ts",".model.ts"],"description":"(GraphQL Only) GraphQL types files suffix. Default value: ['.input.ts', '.args.ts', '.entity.ts', '.model.ts']. See https://docs.nestjs.com/graphql/cli-plugin#using-the-cli-plugin for details."}}},"SwaggerPluginOptions":{"$comment":"https://docs.nestjs.com/openapi/cli-plugin#using-the-cli-plugin","type":"object","properties":{"dtoFileNameSuffix":{"type":"array","items":{"type":"string"},"default":[".dto.ts",".entity.ts"],"description":"(Swagger Only) DTO (Data Transfer Object) files suffix. Default value: ['.dto.ts', '.entity.ts']. See https://docs.nestjs.com/openapi/cli-plugin#using-the-cli-plugin for details"},"controllerFileNameSuffix":{"type":"string","default":".controller.ts","description":"(Swagger Only) Controller files suffix. See https://docs.nestjs.com/openapi/cli-plugin#using-the-cli-plugin for details"},"classValidatorShim":{"type":"boolean","default":true,"description":"(Swagger Only) If set to true, the module will reuse class-validator validation decorators (e.g. @Max(10) will add max: 10 to schema definition). See https://docs.nestjs.com/openapi/cli-plugin#using-the-cli-plugin for details"},"dtoKeyOfComment":{"type":"string","default":"description","description":"(Swagger Only) The property key to set the comment text to on ApiProperty. See https://docs.nestjs.com/openapi/cli-plugin#using-the-cli-plugin for details"},"controllerKeyOfComment":{"type":"string","default":"description","description":"(Swagger Only) The property key to set the comment text to on ApiOperation. See https://docs.nestjs.com/openapi/cli-plugin#using-the-cli-plugin for details"}}}},"properties":{"language":{"type":"string","default":"ts"},"collection":{"type":"string","default":"@nestjs/schematics","description":"Points at the collection of schematics used to generate components. you generally should not change this value."},"sourceRoot":{"$comment":"https://github.com/nestjs/nest-cli/blob/master/actions/add.action.ts","type":"string","default":"src","description":"Points at the root of the source code for the single project in standard mode structures, or the default project in monorepo mode structures."},"entryFile":{"$comment":"https://github.com/nestjs/nest-cli/blob/master/actions/start.action.ts","type":"string","default":"main","description":"The entry file where 'nest start' work with. Default to 'main'."},"monorepo":{"type":"boolean","description":"(monorepo only) For a monorepo mode structure, this value is always true.","default":false},"root":{"type":"string","description":"(monorepo only) Points at the project root of the default project.","default":""},"compilerOptions":{"$ref":"#/definitions/CompilerOptions"},"generateOptions":{"$ref":"#/definitions/GenerateOptions"},"projects":{"type":"object","additionalProperties":{"$ref":"#/definitions/ProjectConfiguration"},"default":{}},"defaultLibraryPrefix":{"type":"string","description":"Default import prefix for newly generated libraries.","default":"@app"}},"title":"Nest CLI configuration","type":"object"}
</schema>

[User] Provide a JSON object that satisfies the schema "Nest CLI configuration". Here are the required top‑level fields: none (all optional). Return only the valid JSON object.

A map with keys specifying compiler options and values specifying the option setting. See https://docs.nestjs.com/cli/monorepo#global-compiler-options for details

(monorepo only) Points at the file containing the tsconfig.json settings that will be used when nest build or nest start is called without a project option (e.g., when the default project is built or started). 'nest build' will not work as expected without this file.

Builder to be used (tsc, webpack, swc). For details on how to configure `SWC` see https://docs.nestjs.com/recipes/swc#getting-started

The directory to output files.

Array of filenames to be included.

Whether to synchronize files or not.

Array of file extensions to be considered.

Whether to copy files or not.

Whether to include dotfiles or not.

Whether to suppress logs or not.

Whether to watch files for changes or not.

Path to SWC config file to use.

If true, enable type checking (when SWC is used). See https://docs.nestjs.com/recipes/swc#type-checking for details.

If true, use webpack compiler (deprecated option, use `builder` instead). If false or not present, use tsc. In monorepo mode, the default is true (use webpack), in standard mode, the default is false (use tsc). See https://docs.nestjs.com/cli/monorepo#cli-properties for details.

Points at a webpack options file. If not specified, Nest looks for the file webpack.config.js.

Enables automatically distributing non-TypeScript assets whenever a compilation step begins (asset distribution does not happen on incremental compiles in --watch mode). Accept glob-like string and object. See https://docs.nestjs.com/cli/monorepo#assets for details.

If true, run in watch-mode, watching all non-TypeScript assets. Setting watchAssets in a top-level compilerOptions property overrides any watchAssets settings within the assets property.

If true, whenever the compiler is invoked, it will first remove the compilation output directory (as configured in tsconfig.json, where the default is ./dist).

If true, enables the shortcut `rs` to manually restart the server.

For finer control, the element can be object.

Glob-like file specifications for the assets to be distributed.

Glob-like file specifications for the assets to be excluded from the include list.

A string specifying the path (relative to the root folder) where the assets should be distributed. Defaults to the same output directory configured for compiler output.

If true, run in watch mode watching specified assets. Setting watchAssets in a top-level compilerOptions property overrides any watchAssets settings within the assets property.

A map with keys specifying global generate options and values specifying the option setting. See https://docs.nestjs.com/cli/monorepo#global-generate-options for details

If true, all generate commands will generate a flat structure

If the value is boolean, a value of true enables spec generation by default and a value of false disables it. A flag passed on the CLI command line overrides this setting, as does a project-specific generateOptions setting (more below). If the value is an object, each key represents a schematic name, and the boolean value determines whether the default spec generation is enabled / disabled for that specific schematic. See https://docs.nestjs.com/cli/monorepo#global-generate-options for details.

Generate spec file for application schematics or not.

Disable spec file generation for class schematics.

Alias for class

Generate spec file for configuration schematics or not.

Alias for configuration

Generate spec file for controller schematics or not.

Alias for controller

Generate spec file for decorator schematics or not.

Alias for decorator

Generate spec file for filter schematics or not.

Alias for filter

Generate spec file for gateway schematics or not.

Alias for gateway

Generate spec file for guard schematics or not.

Alias for guard

Generate spec file for interceptor schematics or not.

Alias for interceptor

Generate spec file for interface schematics or not.

Generate spec file for middleware schematics or not.

Alias for middleware

Generate spec file for module schematics or not.

Alias for module

Generate spec file for pipe schematics or not.

Alias for pipe

Generate spec file for provider schematics or not.

Alias for provider

Generate spec file for resolver schematics or not.

Alias for resolver

Generate spec file for service schematics or not.

Alias for resolver

Generate spec file for library schematics or not.

Alias for library

Generate spec file for sub-app schematics or not.

Alias for sub-app

Generate spec file for resource schematics or not.

Alias for resource

Base directory

The npm package name of the cli plugin, eg @nestjs/swagger.

If set to true, plugin will generate descriptions and example values for properties based on comments.

(GraphQL Only) GraphQL types files suffix. Default value: ['.input.ts', '.args.ts', '.entity.ts', '.model.ts']. See https://docs.nestjs.com/graphql/cli-plugin#using-the-cli-plugin for details.

(Swagger Only) DTO (Data Transfer Object) files suffix. Default value: ['.dto.ts', '.entity.ts']. See https://docs.nestjs.com/openapi/cli-plugin#using-the-cli-plugin for details

(Swagger Only) Controller files suffix. See https://docs.nestjs.com/openapi/cli-plugin#using-the-cli-plugin for details

(Swagger Only) If set to true, the module will reuse class-validator validation decorators (e.g. @Max(10) will add max: 10 to schema definition). See https://docs.nestjs.com/openapi/cli-plugin#using-the-cli-plugin for details

(Swagger Only) The property key to set the comment text to on ApiProperty. See https://docs.nestjs.com/openapi/cli-plugin#using-the-cli-plugin for details

(Swagger Only) The property key to set the comment text to on ApiOperation. See https://docs.nestjs.com/openapi/cli-plugin#using-the-cli-plugin for details

Points at the collection of schematics used to generate components. you generally should not change this value.

Points at the root of the source code for the single project in standard mode structures, or the default project in monorepo mode structures.

The entry file where 'nest start' work with. Default to 'main'.

(monorepo only) For a monorepo mode structure, this value is always true.

(monorepo only) Points at the project root of the default project.

Default import prefix for newly generated libraries.

Nest CLI configuration

Provide a JSON object that satisfies the schema "Nest CLI configuration". Here are the required top‑level fields: none (all optional). Return only the valid JSON object.


[System]
You are a helpful assistant that answers strictly in JSON. Here's the JSON schema you must adhere to:
<schema>
{"$schema":"http://json-schema.org/draft-07/schema#","$id":"https://json.schemastore.org/netlify.json","definitions":{"collectionItems":{"properties":{"fields":{"$ref":"#/definitions/fields"},"label":{"description":"label for the collection in the editor UI; defaults to the value of name","type":"string"},"label_singular":{"description":"singular label for certain elements in the editor; defaults to the value of label"},"folder":{"description":"Folder collections represent one or more files with the same format, fields, and configuration options, all stored within the same folder in the repository. \nNote: Folder collections must have at least one field with the name title for creating new entry slugs. That field should use the default string widget. The label for the field can be any string value. If you wish to use a different field as your identifier, set identifier_field to the field name. See the Collections reference doc for details on how collections and fields are configured. If you forget to add this field, you will get an error that your collection \"must have a field that is a valid entry identifier\".","type":"string"},"files":{"$ref":"#/definitions/files"},"path":{"description":"Path","type":"string"},"format":{"description":"determines how collection files are parsed and saved. It will be inferred if the extension field or existing collection file extensions match one of the supported extensions.","type":"string","enum":["yml","yaml","toml","json","frontmatter","yaml-frontmatter","toml-frontmatter","json-frontmatter"]},"slug":{"description":"For folder collections where users can create new items, the slug option specifies a template for generating new filenames based on a file's creation date and title field. (This means that all collections with create: true must have a title field (a different field can be used via identifier_field)).\n \nAny field can be referenced by wrapping the field name in double curly braces, eg. {{author}} \n{{slug}}: a url-safe version of the title field (or identifier field) for the file \n{{year}}: 4-digit year of the file creation date \n{{month}}: 2-digit month of the file creation date \n{{day}}: 2-digit day of the month of the file creation date \n{{hour}}: 2-digit hour of the file creation date \n{{minute}}: 2-digit minute of the file creation date \n{{second}}: 2-digit second of the file creation date","type":"string"},"create":{"description":"for folder collections only; allows users to create new items in the collection","type":"boolean","default":false},"hide":{"description":"hides a collection in the CMS UI; defaults to false. Useful when using the relation widget to hide referenced collections.","type":"boolean","default":false},"delete":{"description":"prevents users from deleting items in a collection; defaults to true","type":"boolean","default":true},"name":{"description":"unique identifier for the collection, used as the key when referenced in other contexts","type":"string"},"filter":{"description":"optional filter for folder collections"},"description":{"description":"optional text, displayed below the label when viewing a collection","type":"string"},"extension":{"description":"the file extension searched for when finding existing entries in a folder collection and it determines the file extension used to save new collection items","type":"string"}},"required":["name"],"oneOf":[{"required":["files"]},{"required":["folder"]}]},"fields":{"type":"array","description":"The fields option maps editor UI widgets to field-value pairs in the saved file. The order of the fields in your Netlify CMS config.yml file determines their order in the editor UI and in the saved file.","items":{"properties":{"name":{"type":"string","description":"unique identifier for the field, used as the key when referenced in other contexts (like the relation widget)"},"label":{"type":"string","description":"label for the field in the editor UI; defaults to the value of name"},"widget":{"$ref":"#/definitions/widget"},"default":{"description":"specify a default value for a field; available for most widget types. Please note that field default value only works for folder collection type."},"required":{"type":"boolean","default":true,"description":"makes a field required; defaults to true"},"pattern":{"type":"array","description":"add field validation by specifying a list with a regex pattern and an error message (first entry in array is regex pattern, second is the error message)"},"fields":{"$ref":"#/definitions/fields"}},"required":["name"]}},"widget":{"properties":{"required":{"type":"boolean","description":"Defaults to True"},"hint":{"description":"optionally add helper text directly below a widget.","type":"string"},"pattern":{"description":"add field validation by specifying a list with a regex pattern and an error message; more extensive validation can be achieved with custom widgets","type":"array"}}},"files":{"type":"array","items":{"properties":{"name":{"description":"unique identifier for the file","type":"string"},"label":{"description":"file label","type":"string"},"file":{"description":"unique filepath (relative to the base of the repo).","type":"string"},"fields":{"$ref":"#/definitions/fields"}}}}},"dependencies":{},"description":"Config file for Netlify CMS","properties":{"backend":{"type":"object","description":"specifies how to access the content for your site, including authentication"},"local_backend":{"type":"boolean","description":"Set this property to connect Netlify to a local Git repo instead of a live one"},"publish_mode":{},"media_folder":{"type":"string","description":"specifies the folder path where uploaded files should be saved, relative to the base of the repo."},"public_folder":{"type":"string","description":"specifies the folder path where the files uploaded by the media library will be accessed, relative to the base of the built site. For fields controlled by [file] or [image] widgets, the value of the field is generated by prepending this path to the filename of the selected file. Defaults to the value of media_folder, with an opening / if one is not already included."},"media_library":{"description":"Media library integrations are configured via the media_library property, and its value should be an object with at least a name property. A config property can also be used for options that should be passed to the library in use.","type":"object","properties":{"name":{"type":"string"},"config":{"type":"object"}},"required":["name"]},"site_url":{"description":"should provide a URL to your published site. May be used by the CMS for various functionality. Used together with a collection's preview_path to create links to live content.","type":"string"},"display_url":{"description":"When the display_url setting is specified, the CMS UI will include a link in the fixed area at the top of the page, allowing content authors to easily return to your main site. The text of the link consists of the URL without the protocol portion (e.g., your-site.com).\nDefaults to site_url.","type":"string"},"logo_url":{"type":"string","description":"Logo at the top of the login page. Assumed to be a URL to an image file"},"locale":{"type":"string","default":"en"},"show_preview_links":{"description":"shows Deploy Preview Links","type":"boolean"},"slug":{"type":"object","description":"For folder collections where users can create new items, the slug option specifies a template for generating new filenames based on a file's creation date and title field. (This means that all collections with create: true must have a title field (a different field can be used via identifier_field).\n \nThe slug template can also reference a field value by name, eg. {{title}}. If a field name conflicts with a built in template tag name - for example, if you have a field named slug, and would like to reference that field via {{slug}}, you can do so by adding the explicit fields. prefix, eg. {{fields.slug}}.\n \nAvailable template tags:\n \nAny field can be referenced by wrapping the field name in double curly braces, eg. {{author}} \n{{slug}}: a url-safe version of the title field (or identifier field) for the file \n{{year}}: 4-digit year of the file creation date \n{{month}}: 2-digit month of the file creation date \n{{day}}: 2-digit day of the month of the file creation date \n{{hour}}: 2-digit hour of the file creation date \n{{minute}}: 2-digit minute of the file creation date \n{{second}}: 2-digit second of the file creation date","properties":{"encoding":{"description":"\nunicode (default): Sanitize filenames (slugs) according to RFC3987 and the WHATWG URL spec. This spec allows non-ASCII (or non-Latin) characters to exist in URLs.\nascii: Sanitize filenames (slugs) according to RFC3986. The only allowed characters are (0-9, a-z, A-Z, _, -, ~).","enum":["unicode","ascii"],"default":"unicode"},"clean_accents":{"type":"boolean","description":"Remove diacritics from slug characters before sanitizing. This is often helpful when using ascii encoding."},"sanitize_replacement":{"type":"string","description":"The replacement string used to substitute unsafe characters; defaults to -"}}},"collections":{"description":"The collections setting is the heart of your Netlify CMS configuration, as it determines how content types and editor fields in the UI generate files and content in your repository. Each collection you configure displays in the left sidebar of the Content page of the editor UI, in the order they are entered into your Netlify CMS config.yml file.","type":"array","items":{"$ref":"#/definitions/collectionItems"}},"editor":{"description":"This setting changes options for the editor view of the collection. It has one option so far: preview","type":"object","properties":{"preview":{"type":"boolean","description":"Enable preview pane for this collection; defaults to true","default":true}}},"summary":{"description":"This setting allows the customization of the collection list view. Similar to the slug field, a string with templates can be used to include values of different fields, e.g. {{title}}. This option over-rides the default of title field and identifier_field\nTemplate tags are the same as those for slug, with the following additions: \n\n \n{{filename}} The file name without the extension part. \n{{extension}} The file extension. \n{{commit_date}} The file commit date on supported backends (git based backends). \n{{commit_author}} The file author date on supported backends (git based backends).","type":"string"},"sortableFields":{"type":"array","description":"An optional list of sort fields to show in the UI.\nDefaults to inferring title, date, author and description fields and will also show Update On sort field in git based backends.\nWhen author field can't be inferred commit author will be used."},"view_filters":{"type":"array","description":"An optional list of predefined view filters to show in the UI.\nDefaults to an empty list."}},"required":["backend","media_folder","collections"],"title":"Netlify config schema","type":"object"}
</schema>

[User] Provide a JSON object that satisfies the schema "Netlify config schema". Here are the required top‑level fields: backend, media_folder, collections. Return only the valid JSON object.

label for the collection in the editor UI; defaults to the value of name

singular label for certain elements in the editor; defaults to the value of label

Folder collections represent one or more files with the same format, fields, and configuration options, all stored within the same folder in the repository.
Note: Folder collections must have at least one field with the name title for creating new entry slugs. That field should use the default string widget. The label for the field can be any string value. If you wish to use a different field as your identifier, set identifier_field to the field name. See the Collections reference doc for details on how collections and fields are configured. If you forget to add this field, you will get an error that your collection "must have a field that is a valid entry identifier".

Path

determines how collection files are parsed and saved. It will be inferred if the extension field or existing collection file extensions match one of the supported extensions.

yml yaml toml json frontmatter yaml-frontmatter toml-frontmatter json-frontmatter

For folder collections where users can create new items, the slug option specifies a template for generating new filenames based on a file's creation date and title field. (This means that all collections with create: true must have a title field (a different field can be used via identifier_field)).

Any field can be referenced by wrapping the field name in double curly braces, eg. {{author}}
{{slug}}: a url-safe version of the title field (or identifier field) for the file
{{year}}: 4-digit year of the file creation date
{{month}}: 2-digit month of the file creation date
{{day}}: 2-digit day of the month of the file creation date
{{hour}}: 2-digit hour of the file creation date
{{minute}}: 2-digit minute of the file creation date
{{second}}: 2-digit second of the file creation date

for folder collections only; allows users to create new items in the collection

hides a collection in the CMS UI; defaults to false. Useful when using the relation widget to hide referenced collections.

prevents users from deleting items in a collection; defaults to true

unique identifier for the collection, used as the key when referenced in other contexts

optional filter for folder collections

optional text, displayed below the label when viewing a collection

the file extension searched for when finding existing entries in a folder collection and it determines the file extension used to save new collection items

The fields option maps editor UI widgets to field-value pairs in the saved file. The order of the fields in your Netlify CMS config.yml file determines their order in the editor UI and in the saved file.

unique identifier for the field, used as the key when referenced in other contexts (like the relation widget)

label for the field in the editor UI; defaults to the value of name

specify a default value for a field; available for most widget types. Please note that field default value only works for folder collection type.

makes a field required; defaults to true

add field validation by specifying a list with a regex pattern and an error message (first entry in array is regex pattern, second is the error message)

Defaults to True

optionally add helper text directly below a widget.

add field validation by specifying a list with a regex pattern and an error message; more extensive validation can be achieved with custom widgets

unique identifier for the file

file label

unique filepath (relative to the base of the repo).

Config file for Netlify CMS

specifies how to access the content for your site, including authentication

Set this property to connect Netlify to a local Git repo instead of a live one

specifies the folder path where uploaded files should be saved, relative to the base of the repo.

specifies the folder path where the files uploaded by the media library will be accessed, relative to the base of the built site. For fields controlled by [file] or [image] widgets, the value of the field is generated by prepending this path to the filename of the selected file. Defaults to the value of media_folder, with an opening / if one is not already included.

Media library integrations are configured via the media_library property, and its value should be an object with at least a name property. A config property can also be used for options that should be passed to the library in use.

should provide a URL to your published site. May be used by the CMS for various functionality. Used together with a collection's preview_path to create links to live content.

When the display_url setting is specified, the CMS UI will include a link in the fixed area at the top of the page, allowing content authors to easily return to your main site. The text of the link consists of the URL without the protocol portion (e.g., your-site.com).
Defaults to site_url.

Logo at the top of the login page. Assumed to be a URL to an image file

shows Deploy Preview Links

For folder collections where users can create new items, the slug option specifies a template for generating new filenames based on a file's creation date and title field. (This means that all collections with create: true must have a title field (a different field can be used via identifier_field).

The slug template can also reference a field value by name, eg. {{title}}. If a field name conflicts with a built in template tag name - for example, if you have a field named slug, and would like to reference that field via {{slug}}, you can do so by adding the explicit fields. prefix, eg. {{fields.slug}}.

Available template tags:

Any field can be referenced by wrapping the field name in double curly braces, eg. {{author}}
{{slug}}: a url-safe version of the title field (or identifier field) for the file
{{year}}: 4-digit year of the file creation date
{{month}}: 2-digit month of the file creation date
{{day}}: 2-digit day of the month of the file creation date
{{hour}}: 2-digit hour of the file creation date
{{minute}}: 2-digit minute of the file creation date
{{second}}: 2-digit second of the file creation date

unicode (default): Sanitize filenames (slugs) according to RFC3987 and the WHATWG URL spec. This spec allows non-ASCII (or non-Latin) characters to exist in URLs.
ascii: Sanitize filenames (slugs) according to RFC3986. The only allowed characters are (0-9, a-z, A-Z, _, -, ~).

Remove diacritics from slug characters before sanitizing. This is often helpful when using ascii encoding.

The replacement string used to substitute unsafe characters; defaults to -

The collections setting is the heart of your Netlify CMS configuration, as it determines how content types and editor fields in the UI generate files and content in your repository. Each collection you configure displays in the left sidebar of the Content page of the editor UI, in the order they are entered into your Netlify CMS config.yml file.

This setting changes options for the editor view of the collection. It has one option so far: preview

Enable preview pane for this collection; defaults to true

This setting allows the customization of the collection list view. Similar to the slug field, a string with templates can be used to include values of different fields, e.g. {{title}}. This option over-rides the default of title field and identifier_field
Template tags are the same as those for slug, with the following additions:

{{filename}} The file name without the extension part.
{{extension}} The file extension.
{{commit_date}} The file commit date on supported backends (git based backends).
{{commit_author}} The file author date on supported backends (git based backends).

An optional list of sort fields to show in the UI.
Defaults to inferring title, date, author and description fields and will also show Update On sort field in git based backends.
When author field can't be inferred commit author will be used.

An optional list of predefined view filters to show in the UI.
Defaults to an empty list.

Netlify config schema

Provide a JSON object that satisfies the schema "Netlify config schema". Here are the required top‑level fields: backend, media_folder, collections. Return only the valid JSON object.