From 82a6256458f1aea412836c7c6923f83bf6d5a525 Mon Sep 17 00:00:00 2001 From: Kurt collins <42543284+kurtgcollins@users.noreply.github.com> Date: Mon, 20 Aug 2018 17:05:06 -0400 Subject: [PATCH] Edited for style and grammar across all Quick Start docs (#1637) **Summary** Noticed a lot of future tense, passive voice, and general formatting/wording changes to be made. **A picture of a cute animal (not mandatory but encouraged)** ![image](https://user-images.githubusercontent.com/42543284/44362259-6f096c80-a48e-11e8-8734-c747491463c9.png) --- website/content/docs/add-to-your-site.md | 50 +++++++++---------- .../content/docs/authentication-backends.md | 40 +++++++-------- website/content/docs/collection-types.md | 12 ++--- .../content/docs/update-the-cms-version.md | 18 +++---- 4 files changed, 57 insertions(+), 63 deletions(-) diff --git a/website/content/docs/add-to-your-site.md b/website/content/docs/add-to-your-site.md index 24567452..4c681205 100755 --- a/website/content/docs/add-to-your-site.md +++ b/website/content/docs/add-to-your-site.md @@ -4,13 +4,13 @@ weight: 20 group: start --- -Netlify CMS is adaptable to a wide variety of projects. It works with any content written in markdown, JSON, YAML, or TOML files, stored in a repo on [GitHub](https://github.com/), [GitLab](https://about.gitlab.com/), or [Bitbucket](https://bitbucket.org). You can also create your own custom backend. +You can adapt Netlify CMS to a wide variety of projects. It works with any content written in markdown, JSON, YAML, or TOML files, stored in a repo on [GitHub](https://github.com/), [GitLab](https://about.gitlab.com/), or [Bitbucket](https://bitbucket.org). You can also create your own custom backend. -This tutorial will guide you through the steps for adding Netlify CMS to a site that's built with a common [static site generator](https://www.staticgen.com/), like Jekyll, Hugo, Hexo, or Gatsby. Alternatively, you can [start from a template](https://www.netlifycms.org/docs/start-with-a-template) or dive right into [configuration options](https://www.netlifycms.org/docs/configuration-options). +This tutorial guides you through the steps for adding Netlify CMS to a site that's built with a common [static site generator](https://www.staticgen.com/), like Jekyll, Hugo, Hexo, or Gatsby. Alternatively, you can [start from a template](https://www.netlifycms.org/docs/start-with-a-template) or dive right into [configuration options](https://www.netlifycms.org/docs/configuration-options). ## App File Structure -All Netlify CMS files are contained in a static `admin` folder, stored at the root of your published site. Where you store this folder in the source files depends on your static site generator. Here's the static file location for a few of the most popular static site generators: +A static `admin` folder contains all Netlify CMS files, stored at the root of your published site. Where you store this folder in the source files depends on your static site generator. Here's the static file location for a few of the most popular static site generators: | These generators ... | store static files in | | ----------------------- | --------------------- | @@ -30,7 +30,7 @@ admin └ config.yml ``` -The first file, `admin/index.html`, is the entry point for the Netlify CMS admin interface. This means that users can navigate to `yoursite.com/admin/` to access it. On the code side, it's a basic HTML starter page that loads the Netlify CMS JavaScript file. In this example, we pull the file from a public CDN: +The first file, `admin/index.html`, is the entry point for the Netlify CMS admin interface. This means that users navigate to `yoursite.com/admin/` to access it. On the code side, it's a basic HTML starter page that loads the Netlify CMS JavaScript file. In this example, we pull the file from a public CDN: ```html @@ -51,7 +51,7 @@ The second file, `admin/config.yml`, is the heart of your Netlify CMS installati ### Installing with npm -You can also use Netlify CMS as an npm module. Wherever you import Netlify CMS, it will automatically run, taking over the current page. Make sure the script that imports it is only run on your CMS page. First install the package and save it to your project: +You can also use Netlify CMS as an npm module. Wherever you import Netlify CMS, it automatically runs, taking over the current page. Make sure the script that imports it only runs on your CMS page. First install the package and save it to your project: ```bash npm install netlify-cms --save @@ -68,7 +68,7 @@ CMS.registerPreviewTemplate('my-template', MyTemplate) ## Configuration -Configuration will be different for every site, so we'll break it down into parts. All code snippets in this section will be added to your `admin/config.yml` file. +Configuration is different for every site, so we'll break it down into parts. Add all the code snippets in this section to your `admin/config.yml` file. ### Backend @@ -84,13 +84,13 @@ backend: _(For Bitbucket repositories, use the [Bitbucket backend](https://www.netlifycms.org/docs/authentication-backends/#bitbucket-backend) instructions instead.)_ -The configuration above specifies your backend protocol and your publication branch. Git Gateway is an open source API that acts as a proxy between authenticated users of your site and your site repo. (We'll get to the details of that in the [Authentication section](#authentication) below.) If you leave out the `branch` declaration, it will default to `master`. +The configuration above specifies your backend protocol and your publication branch. Git Gateway is an open source API that acts as a proxy between authenticated users of your site and your site repo. (We'll get to the details of that in the [Authentication section](#authentication) below.) If you leave out the `branch` declaration, it defaults to `master`. ### Editorial Workflow **Note:** Editorial workflow works with GitHub repositories only. Support for other Git hosts is [coming soon](https://github.com/netlify/netlify-cms/issues/568). -By default, saving a post in the CMS interface will push a commit directly to the publication branch specified in `backend`. However, you also have the option to enable the [Editorial Workflow](https://www.netlifycms.org/docs/configuration-options/#publish-mode), which adds an interface for drafting, reviewing, and approving posts. To do this, add the following line to your Netlify CMS `config.yml`: +By default, saving a post in the CMS interface pushes a commit directly to the publication branch specified in `backend`. However, you also have the option to enable the [Editorial Workflow](https://www.netlifycms.org/docs/configuration-options/#publish-mode), which adds an interface for drafting, reviewing, and approving posts. To do this, add the following line to your Netlify CMS `config.yml`: ```yaml # This line should *not* be indented @@ -116,13 +116,13 @@ media_folder: "static/images/uploads" # Media files will be stored in the repo u public_folder: "/images/uploads" # The src attribute for uploaded media will begin with /images/uploads ``` -The configuration above adds a new setting, `public_folder`. While `media_folder` specifies where uploaded files will be saved in the repo, `public_folder` indicates where they can be found in the published site. This path is used in image `src` attributes and is relative to the file where it's called. For this reason, we usually start the path at the site root, using the opening `/`. +The configuration above adds a new setting, `public_folder`. While `media_folder` specifies where uploaded files are saved in the repo, `public_folder` indicates where they are found in the published site. Image `src` attributes use this path, which is relative to the file where it's called. For this reason, we usually start the path at the site root, using the opening `/`. -*If `public_folder` is not set, Netlify CMS will default to the same value as `media_folder`, adding an opening `/` if one is not included.* +*If `public_folder` is not set, Netlify CMS defaults to the same value as `media_folder`, adding an opening `/` if one is not included.* ### Collections -Collections define the structure for the different content types on your static site. Since every site is different, the `collections` settings will be very different from one site to the next. +Collections define the structure for the different content types on your static site. Since every site is different, the `collections` settings differ greatly from one site to the next. Let's say your site has a blog, with the posts stored in `_posts/blog`, and files saved in a date-title format, like `1999-12-31-lets-party.md`. Each post begins with settings in yaml-formatted front matter, like so: @@ -165,7 +165,7 @@ Let's break that down: label - What the post type will be called in the admin UI. + What the admin UI calls the post type. folder @@ -178,7 +178,7 @@ Let's break that down: slug - Template for filenames. {{year}}, {{month}}, and {{day}} will pull from the post's date field or save date. {{slug}} is a url-safe version of the post's title. Default is simply {{slug}}. + Template for filenames. {{year}}, {{month}}, and {{day}} pulls from the post's date field or save date. {{slug}} is a url-safe version of the post's title. Default is simply {{slug}}. @@ -194,13 +194,13 @@ Let's break that down: -As described above, the `widget` property specifies a built-in or custom UI widget for a given field. When a content editor enters a value into a widget, that value will be saved in the document front matter as the value for the `name` specified for that field. A full listing of available widgets can be found in the [Widgets doc](https://www.netlifycms.org/docs/widgets). +As described above, the `widget` property specifies a built-in or custom UI widget for a given field. When a content editor enters a value into a widget, that value is saved in the document front matter as the value for the `name` specified for that field. A full listing of available widgets can be found in the [Widgets doc](https://www.netlifycms.org/docs/widgets). Based on this example, you can go through the post types in your site and add the appropriate settings to your Netlify CMS `config.yml` file. Each post type should be listed as a separate node under the `collections` field. See the [Collections reference doc](https://www.netlifycms.org/docs/configuration-options/#collections) for more configuration options. ### Filter -The entries for any collection can be filtered based on the value of a single field. The example collection below would only show post entries with the value `en` in the `language` field. +The entries for any collection can be filtered based on the value of a single field. The example collection below only shows post entries with the value `en` in the `language` field. ```yaml collections: @@ -220,28 +220,28 @@ Now that you have your Netlify CMS files in place and configured, all that's lef ### Setup on Netlify -Netlify offers a built-in authentication service called Identity. In order to use it, you'll need to connect your site repo with Netlify. Netlify has published a general [Step-by-Step Guide](https://www.netlify.com/blog/2016/10/27/a-step-by-step-guide-deploying-a-static-site-or-single-page-app/) for this, along with detailed guides for many popular static site generators, including [Jekyll](https://www.netlify.com/blog/2015/10/28/a-step-by-step-guide-jekyll-3.0-on-netlify/), [Hugo](https://www.netlify.com/blog/2016/09/21/a-step-by-step-guide-victor-hugo-on-netlify/), [Hexo](https://www.netlify.com/blog/2015/10/26/a-step-by-step-guide-hexo-on-netlify/), [Middleman](https://www.netlify.com/blog/2015/10/01/a-step-by-step-guide-middleman-on-netlify/), [Gatsby](https://www.netlify.com/blog/2016/02/24/a-step-by-step-guide-gatsby-on-netlify/) and more. +Netlify offers a built-in authentication service called Identity. In order to use it, connect your site repo with Netlify. Netlify has published a general [Step-by-Step Guide](https://www.netlify.com/blog/2016/10/27/a-step-by-step-guide-deploying-a-static-site-or-single-page-app/) for this, along with detailed guides for many popular static site generators, including [Jekyll](https://www.netlify.com/blog/2015/10/28/a-step-by-step-guide-jekyll-3.0-on-netlify/), [Hugo](https://www.netlify.com/blog/2016/09/21/a-step-by-step-guide-victor-hugo-on-netlify/), [Hexo](https://www.netlify.com/blog/2015/10/26/a-step-by-step-guide-hexo-on-netlify/), [Middleman](https://www.netlify.com/blog/2015/10/01/a-step-by-step-guide-middleman-on-netlify/), [Gatsby](https://www.netlify.com/blog/2016/02/24/a-step-by-step-guide-gatsby-on-netlify/), and more. ### Enable Identity and Git Gateway Netlify's Identity and Git Gateway services allow you to manage CMS admin users for your site without requiring them to have an account with your Git host or commit access on your repo. From your site dashboard on Netlify: 1. Go to **Settings > Identity**, and select **Enable Identity service**. -2. Under **Registration preferences**, select **Open** or **Invite only**. In most cases, you'll want only invited users to access your CMS, but if you're just experimenting, you can leave it open for convenience. +2. Under **Registration preferences**, select **Open** or **Invite only**. In most cases, you want only invited users to access your CMS, but if you're just experimenting, you can leave it open for convenience. 3. If you'd like to allow one-click login with services like Google and GitHub, check the boxes next to the services you'd like to use, under **External providers**. -4. Scroll down to **Services > Git Gateway**, and click **Enable Git Gateway**. This will authenticate with your Git host and generate an API access token. In this case, we're leaving the **Roles** field blank, which means any logged in user may access the CMS. For information on changing this, check the [Netlify Identity documentation](https://www.netlify.com/docs/identity/). +4. Scroll down to **Services > Git Gateway**, and click **Enable Git Gateway**. This authenticates with your Git host and generates an API access token. In this case, we're leaving the **Roles** field blank, which means any logged in user may access the CMS. For information on changing this, check the [Netlify Identity documentation](https://www.netlify.com/docs/identity/). ### Add the Netlify Identity Widget -With the backend set to handle authentication, now you need a frontend interface to connect to it. The open source Netlify Identity Widget is a drop-in widget made for just this purpose. To include the widget in your site, you'll need to add the following script tag in two places: +With the backend set to handle authentication, now you need a frontend interface to connect to it. The open source Netlify Identity Widget is a drop-in widget made for just this purpose. To include the widget in your site, add the following script tag in two places: ```html ``` -You'll need to add this to the `` of your CMS index page at `/admin/index.html`, as well as the `` of your site's main index page. Depending on how your site generator is set up, this may mean you need to add it to the default template, or to a "partial" or "include" template. If you can find where the site stylesheet is linked, that's probably the right place. Alternatively, you can include the script in your site using Netlify's [Script Injection](https://www.netlify.com/docs/inject-analytics-snippets/) feature. +Add this to the `` of your CMS index page at `/admin/index.html`, as well as the `` of your site's main index page. Depending on how your site generator is set up, this may mean you need to add it to the default template, or to a "partial" or "include" template. If you can find where the site stylesheet is linked, that's probably the right place. Alternatively, you can include the script in your site using Netlify's [Script Injection](https://www.netlify.com/docs/inject-analytics-snippets/) feature. -When a user logs in with the Netlify Identity widget, they will be directed to the site homepage with an access token. In order to complete the login and get back to the CMS, we'll need to redirect the user back to the `/admin/` path. To do this, add the following script before the closing `body` tag of your site's main index page: +When a user logs in with the Netlify Identity widget, an access token directs to the site homepage. In order to complete the login and get back to the CMS, redirect the user back to the `/admin/` path. To do this, add the following script before the closing `body` tag of your site's main index page: ```html ``` -Note: This example script requires modern JavaScript and will not work on IE11. For legacy browser support, use function expressions (`function () {}`) in place of the arrow functions (`() => {}`), or use a transpiler like [Babel](https://babeljs.io/). +Note: This example script requires modern JavaScript and does not work on IE11. For legacy browser support, use function expressions (`function () {}`) in place of the arrow functions (`() => {}`), or use a transpiler such as [Babel](https://babeljs.io/). ## Accessing the CMS Your site CMS is now fully configured and ready for login! -If you set your registration preference to "Invite only," you'll need to invite yourself (and anyone else you choose) as a site user. To do this, select the **Identity** tab from your site dashboard, and then select the **Invite users** button. Invited users will receive an email invitation with a confirmation link. Clicking the link will take you to your site with a login prompt. +If you set your registration preference to "Invite only," invite yourself (and anyone else you choose) as a site user. To do this, select the **Identity** tab from your site dashboard, and then select the **Invite users** button. Invited users receive an email invitation with a confirmation link. Clicking the link will take you to your site with a login prompt. -If you left your site registration open, or for return visits after comfirming an email invitation, you can access your site's CMS at `yoursite.com/admin/`. +If you left your site registration open, or for return visits after comfirming an email invitation, access your site's CMS at `yoursite.com/admin/`. -**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. 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. 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. +**Note:** No matter where you access Netlify CMS — whether running locally, in a staging environment, or in your published site — it always fetches and commits files in your hosted repository (for example, on GitHub), on the branch you configured in your Netlify CMS config.yml file. This means that content fetched in the admin UI matches the content in the repository, which may be different from your locally running site. It also means that content saved using the admin UI saves directly to the hosted repository, even if you're running the UI locally or in staging. Happy posting! diff --git a/website/content/docs/authentication-backends.md b/website/content/docs/authentication-backends.md index a4b1eb77..52174738 100644 --- a/website/content/docs/authentication-backends.md +++ b/website/content/docs/authentication-backends.md @@ -4,9 +4,9 @@ weight: 25 group: start --- -Netlify CMS stores content in your GitHub, GitLab, or Bitbucket repository. In order for this to work, you need to authenticate with your Git host, and in most cases that requires a server. We have a few options for handling this. +Netlify CMS stores content in your GitHub, GitLab, or Bitbucket repository. In order for this to work, authenticate with your Git host. In most cases that requires a server. We have a few options for handling this. -**Note:** some static site generators have plugins for optimized integration with Netlify CMS, and starter templates may utilize these plugins. If you're using a starter template, read the template documentation before proceeding, as their instructions may differ. +**Note:** Some static site generators have plugins for optimized integration with Netlify CMS, and starter templates may utilize these plugins. If you're using a starter template, read the template documentation before proceeding, as their instructions may differ. ## Git Gateway with Netlify Identity @@ -14,8 +14,7 @@ Netlify CMS stores content in your GitHub, GitLab, or Bitbucket repository. In o To use it in your own project stored on GitHub or GitLab, follow these steps: -1. Head over to the [Netlify Identity docs](https://www.netlify.com/docs/identity) and follow the - steps to get started. +1. Head over to the [Netlify Identity docs](https://www.netlify.com/docs/identity) and follow the steps to get started. 2. Add the following lines to your Netlify CMS `config.yml` file: ```yaml @@ -26,9 +25,7 @@ To use it in your own project stored on GitHub or GitLab, follow these steps: - editor ``` -3. Optionally, you can assign roles to users in your Netlify dashboard, and then limit which - roles can access the CMS by defining the `accept_roles` field as shown in the example above. - Otherwise `accept_roles` can be left out, and all Netlify Identity users on your site will have access. +3. Optionally, you can assign roles to users in your Netlify dashboard, and then limit which roles can access the CMS by defining the `accept_roles` field as shown in the example above. Otherwise `accept_roles` can be left out, and all Netlify Identity users on your site have access. ## Git Gateway without Netlify @@ -40,14 +37,11 @@ To configure in Netlify CMS, use the same `backend` settings in your Netlify CMS For repositories stored on GitHub, the `github` backend allows CMS users to log in directly with their GitHub account. Note that all users must have push access to your content repository for this to work. -Because Github [requires a -server](https://github.com/netlify/netlify-cms/issues/663#issuecomment-335023723) for -authentication, Netlify facilitates basic GitHub authentication. +Because Github [requires a server](https://github.com/netlify/netlify-cms/issues/663#issuecomment-335023723) for authentication, Netlify facilitates basic GitHub authentication. -To enable it: +To enable basic GitHub authentication: -1. Follow the authentication provider setup steps in the [Netlify - docs](https://www.netlify.com/docs/authentication-providers/#using-an-authentication-provider). +1. Follow the authentication provider setup steps in the [Netlify docs](https://www.netlify.com/docs/authentication-providers/#using-an-authentication-provider). 2. Add the following lines to your Netlify CMS `config.yml` file: ```yaml @@ -62,7 +56,10 @@ If you prefer to run your own authentication server, check out the section on [e For repositories stored on GitLab, the `gitlab` backend allows CMS users to log in directly with their GitLab account. Note that all users must have push access to your content repository for this to work. -The GitLab API allows for two types of OAuth2 flows: [Web Application Flow](https://docs.gitlab.com/ce/api/oauth2.html#web-application-flow), which works much like the GitHub OAuth flow described above, and [Implicit Grant](https://docs.gitlab.com/ce/api/oauth2.html#implicit-grant), which operates _without_ the need for an authentication server. +The GitLab API allows for two types of OAuth2 flows: + +* [Web Application Flow](https://docs.gitlab.com/ce/api/oauth2.html#web-application-flow), which works much like the GitHub OAuth flow described above. +* [Implicit Grant](https://docs.gitlab.com/ce/api/oauth2.html#implicit-grant), which operates _without_ the need for an authentication server. ### Web Application Flow with Netlify @@ -71,9 +68,8 @@ When using GitLab's Web Application Flow for authentication, you can use Netlify To enable it: 1. Follow the [GitLab docs](https://docs.gitlab.com/ee/integration/oauth_provider.html#adding-an-application-through-the-profile) to add your Netlify CMS instance as an OAuth application. For the **Redirect URI**, enter `https://api.netlify.com/auth/done`, and check the box for `api` scope. -2. Follow the [Netlify - docs](https://www.netlify.com/docs/authentication-providers/#using-an-authentication-provider) to add your new GitLab Application ID and Secret to your Netlify site dashboard. -2. In your repository, add the following lines to your Netlify CMS `config.yml` file: +2. Follow the [Netlify docs](https://www.netlify.com/docs/authentication-providers/#using-an-authentication-provider) to add your new GitLab Application ID and Secret to your Netlify site dashboard. +3. In your repository, add the following lines to your Netlify CMS `config.yml` file: ```yaml backend: @@ -86,7 +82,7 @@ To enable it: With GitLab's Implicit Grant, users can authenticate with GitLab directly from the client. To do this: 1. Follow the [GitLab docs](https://docs.gitlab.com/ee/integration/oauth_provider.html#adding-an-application-through-the-profile) to add your Netlify CMS instance as an OAuth application. For the **Redirect URI**, enter the address where you access Netlify CMS, for example, `https://www.mysite.com/admin/`. For scope, select `api`. -2. GitLab will give you an **Application ID**. Copy this and enter it in your Netlify CMS `config.yml` file, along with the following settings: +2. GitLab gives you an **Application ID**. Copy this ID and enter it in your Netlify CMS `config.yml` file, along with the following settings: ```yaml backend: @@ -109,7 +105,7 @@ With GitLab's Implicit Grant, users can authenticate with GitLab directly from t auth_endpoint: oauth/authorize ``` -Note that in both cases, GitLab will also provide you with a client secret. You should _never_ store this in your repo or reveal it in the client. +**Note:** In both cases, GitLab also provides you with a client secret. You should _never_ store this in your repo or reveal it in the client. ## Bitbucket Backend @@ -117,8 +113,7 @@ For repositories stored on Bitbucket, the `bitbucket` backend allows CMS users t To enable it: -1. Follow the authentication provider setup steps in the [Netlify - docs](https://www.netlify.com/docs/authentication-providers/#using-an-authentication-provider). +1. Follow the authentication provider setup steps in the [Netlify docs](https://www.netlify.com/docs/authentication-providers/#using-an-authentication-provider). 2. Add the following lines to your Netlify CMS `config.yml` file: ```yaml @@ -129,8 +124,7 @@ To enable it: ## External OAuth Clients -If you would like to facilitate your own OAuth authentication rather than use Netlify's service or implicit grant, you -can use one of the community-maintained projects below. Feel free to [submit a pull request](https://github.com/netlify/netlify-cms/blob/master/CONTRIBUTING.md) if you'd like to add yours! +If you would like to facilitate your own OAuth authentication rather than use Netlify's service or implicit grant, you can use one of the community-maintained projects below. Feel free to [submit a pull request](https://github.com/netlify/netlify-cms/blob/master/CONTRIBUTING.md) if you'd like to add yours! | Author | Supported Git hosts | Language(s)/Platform(s) | Link | | ---------------------------------------------- | ------------------------- | ----------------------- | -------------------------------------------------------------------------------------------------------------------------------------------- | diff --git a/website/content/docs/collection-types.md b/website/content/docs/collection-types.md index 839d226e..1c4a8502 100644 --- a/website/content/docs/collection-types.md +++ b/website/content/docs/collection-types.md @@ -37,8 +37,8 @@ The entries for any folder collection can be filtered based on the value of a si The `filter` option requires two fields: -* `field`: the name of the collection field to filter on -* `value`: the desired field value +* `field`: The name of the collection field to filter on. +* `value`: The desired field value. The example below creates two collections in the same folder, filtered by the `language` field. The first collection includes posts with `language: en`, and the second, with `language: es`. @@ -51,7 +51,7 @@ collections: fields: - {label: "Language", name: "language", widget: "select", options: ["en", "es"]} - {label: "Title", name: "title", widget: "string"} - - {label: "Content", name: "body", widget: "markdown"} + - {label: "Content", name: "body", widget: "markdown"} - label: "Blog en Español" name: "spanish_posts" folder: "_posts" @@ -59,16 +59,16 @@ collections: fields: - {label: "Lenguaje", name: "language", widget: "select", options: ["en", "es"]} - {label: "Titulo", name: "title", widget: "string"} - - {label: "Contenido", name: "body", widget: "markdown"} + - {label: "Contenido", name: "body", widget: "markdown"} ``` ## File collections A `files` collection contains one or more uniquely configured files. Unlike items in `folder` collections, which repeat the same configuration over all files in the folder, each item in a `files` collection has an explicitly set path, filename, and configuration. This can be useful for unique files with a custom set of fields, like a settings file or a custom landing page with a unique content structure. -When configuring a `files` collection, each file in the collection is configured separately, and listed under the `files` field of the collection. Each file has its own list of `fields`, and a unique filepath specified in the `file` field (relative to the base of the repo). +When configuring a `files` collection, configure each file in the collection separately, and list them under the `files` field of the collection. Each file has its own list of `fields` and a unique filepath specified in the `file` field (relative to the base of the repo). -**Note**: Files listed in a file collection must already exist in the hosted repository branch set in your Netlify CMS [backend configuration](https://www.netlifycms.org/docs/authentication-backends/). Files must also have a valid value for the file type. For example, an empty file works as valid YAML, but a JSON file must have a non-empty value to be valid, such as an empty object. +**Note:** Files listed in a file collection must already exist in the hosted repository branch set in your Netlify CMS [backend configuration](https://www.netlifycms.org/docs/authentication-backends/). Files must also have a valid value for the file type. For example, an empty file works as valid YAML, but a JSON file must have a non-empty value to be valid, such as an empty object. Example: diff --git a/website/content/docs/update-the-cms-version.md b/website/content/docs/update-the-cms-version.md index b6650ae9..6ab1f683 100644 --- a/website/content/docs/update-the-cms-version.md +++ b/website/content/docs/update-the-cms-version.md @@ -8,18 +8,18 @@ The update procedure for your CMS depends upon the method you used to install Ne ## Package Manager -If you are using a package manager like Yarn or NPM, you will use their standard procedure to update. This is how both the Hugo and Gatsby starters are set up. +If you are using a package manager like Yarn or NPM, use their standard procedure to update. This is how both the Hugo and Gatsby starters are set up. ## CDN -If you are using the CMS through a CDN like Unpkg, then that depends on the version tag you are using. You can find the version tag you are using in the `/admin/index.html` file of your site. +If you are using the CMS through a CDN like Unpkg, then that depends on the version tag you are using. You can find the version tag in the `/admin/index.html` file of your site. -- (Recommended) If you use `^2.0.0`, the CMS will do all updates except major versions automatically. - - It will upgrade to `2.0.1`, `2.1.0`, `2.1.2`. - - It will not upgrade to `3.0.0` or higher. - - It will not upgrade to beta versions. +- (Recommended) If you use `^2.0.0`, the CMS does all updates except major versions automatically. + - It upgrades to `2.0.1`, `2.1.0`, `2.1.2`. + - It does not upgrade to `3.0.0` or higher. + - It does not upgrade to beta versions. - If you use `~2.0.0`, the CMS will do only patch updates automatically. - - It will upgrade `2.0.1`, `2.0.2`. - - It will not upgrade to `2.1.0` or higher. - - It will not upgrade beta versions. + - It upgrades `2.0.1`, `2.0.2`. + - It does not upgrade to `2.1.0` or higher. + - It does not upgrade beta versions.