- #.YML FILE EDITOR HOW TO#
- #.YML FILE EDITOR FULL#
extension: see detailed description below.delete: false prevents users from deleting items in a collection defaults to true.Useful when using the relation widget to hide referenced collections. hide: true hides a collection in the CMS UI defaults to false.
publish: for publish_mode: editorial_workflow only false hides UI publishing controls for a collection defaults to true. create: for folder collections only true allows users to create new items in the collection defaults to false. filter: optional filter for folder collections details in Collection Types. files or folder (requires one of these): specifies the collection type and location details in Collection Types. description: optional text, displayed below the label when viewing a collection. label_singular: singular label for certain elements in the editor defaults to the value of label. label: label for the collection in the editor UI defaults to the value of name. identifier_field: see detailed description below. name (required): unique identifier for the collection, used as the key when referenced in other contexts (like the relation widget). 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.Ĭollections accepts a list of collection objects, each with the following options: 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. Slug : encoding : "ascii" clean_accents : true sanitize_replacement : "_" Collections You can enable the Editorial Workflow with the following line in your Netlify CMS config.yml file: Note: Editorial workflow works with GitHub repositories, and support for GitLab and Bitbucket is in beta. All unpublished entries will be arranged in a board according to their status, and they can be further reviewed and edited before going live. The publish_mode option allows you to enable "Editorial Workflow" mode for more control over the content publishing phases. Publish Modeīy default, all entries created or edited in the Netlify CMS are committed directly into the main repository branch. If you want to have your local CMS write to a local repository, try the local_backend setting, currently in beta. It also means that content saved using the admin UI will save directly to the hosted repository, even if you're running the UI locally or in staging. This means that content fetched in the admin UI will match the content in the repository, which may be different from your locally running site. Note: no matter where you access Netlify CMS - whether running locally, in a staging environment, or in your published site - it will always fetch and commit files in your hosted repository (for example, on GitHub), on the branch you configured in your Netlify CMS config.yml file. #.YML FILE EDITOR FULL#
Full details and code samples can be found in Backends.
#.YML FILE EDITOR HOW TO#
The backend option specifies how to access the content for your site, including authentication. Note that YAML syntax allows lists and objects to be written in block or inline style, and the code samples below include a mix of both. You can find details about all configuration options below.
(No login required: click the login button and the CMS will open.) You can refer to the demo configuration code to see how each option was configured. To see working configuration examples, you can start from a template or check out the CMS demo site.
0 kommentar(er)
