static-cms/website/data/landing.yaml

hero:
  headline: "Open source content management for your Git&nbsp;workflow"
  subhead: "Use Netlify CMS with any static site generator for a faster and more flexible web&nbsp;project"
  devfeatures:
    - feature: "Static + content management = ♥"
      description: "Get the speed, security, and scalability of a static site, while still providing a convenient editing interface for content."
    - feature: "An integrated part of your Git workflow"
      description: "Content is stored in your Git repository alongside your code for easier versioning, multi-channel publishing, and the option to handle content updates directly in Git."
    - feature: "An extensible CMS built on React"
      description: "Netlify CMS is built as a single-page React app. Create custom-styled previews, UI widgets, and editor plugins or add backends to support different Git platform APIs."

cta:
  primaryhook: "Getting started is simple and free."
  primary: "Choose a template that’s pre-configured with a static site generator and deploys to a global CDN in one&nbsp;click."
  button: "[Get started](/docs/start-with-a-template/)"

editors:
  hook: "A CMS that developers and content editors can&nbsp;agree&nbsp;on"
  intro: "You get to implement modern front end tools to deliver a faster, safer, and more scalable site. Editors get a friendly UI and intuitive workflow that meets their content management requirements."
  features:
    - feature: "Editor-friendly user interface"
      description: "The web-based app includes rich-text editing, real-time preview, and drag-and-drop media uploads."
      imgpath: "feature-editor.svg"
    - feature: "Intuitive workflow for content teams"
      description: "Writers and editors can easily manage content from draft to review to publish across any number of custom content types."
      imgpath: "feature-workflow.svg"
    - feature: "Instant access without GitHub&nbsp;account"
      description: "With [Git Gateway](/docs/git-gateway-backend/#git-gateway-with-netlify-identity), you can add CMS access for any team member — even if they don’t have a GitHub account. "
      imgpath: "feature-access.svg"

community:
  hook: "Supported by a growing&nbsp;community"
  features:
    - feature: "Built on the Jamstack"
      description: "Netlify CMS is based on client-side JavaScript, reusable APIs and prebuilt Markup. Compared to server-side CMS like WordPress, this means better performance, higher security, lower cost of scaling, and a better developer experience. You can learn more about the Jamstack on [jamstack.org](https://jamstack.org)."
    - feature: "Support when you need it"
      description: "Get up and running with comprehensive [documentation](/docs) and templates or work through difficult problems in our [community chat](https://netlifycms.org/chat)."
    - feature: "A community-driven project you can help evolve"
      description: "Netlify CMS is built by a community of more than 100 contributors — and you can help. Join our [bi-weekly planning sessions](/community) or read the [contributing guide](/docs/contributor-guide) to join in."
  contributors: "Made possible by awesome contributors"
-												Migrate netlify-cms-www site into this repo (#860)

* Add frontmatter to docs files (prep to move)

* Move docs into position for website migration

* Migrate website from netlify-cms-www

Some modifications, including most of the changes in https://github.com/netlify/netlify-cms-www/pull/58 (previously reverted).

Also updated the readme and added hugo-bin for quicker onboarding of new docs contributors.

* Remove netlify.toml

This allows separate build commands for cms-demo and netlifycms.org.

* Remove website/netlify.toml

May re-add later, but it's not doing anything for now.

* Remove unused content file

											
										
										
											2017-12-04 16:42:20 -08:00
+								hero:
-												docs(fix): revert prettier formatting on markdown files (#1612)

Prettier formatting our markdown files is causing bugs because of the
differences between Gatsby's parser and Prettier's. Also, Prettier
formats the inline code-blocks containing example CMS configs, but the
formatting it uses doesn't really make much sense or match the suggested
CMS config style.

It doesn't actually make much sense to format the docs anyway, since we
use the CMS itself to edit/generate them.

											
										
										
											2018-08-14 11:33:13 -06:00
+								  headline: "Open source content management for your Git&nbsp;workflow"
 								  subhead: "Use Netlify CMS with any static site generator for a faster and more flexible web&nbsp;project"
-												Website redesign

											
										
										
											2017-12-06 23:09:33 +01:00
+								  devfeatures:
-												docs(fix): revert prettier formatting on markdown files (#1612)

Prettier formatting our markdown files is causing bugs because of the
differences between Gatsby's parser and Prettier's. Also, Prettier
formats the inline code-blocks containing example CMS configs, but the
formatting it uses doesn't really make much sense or match the suggested
CMS config style.

It doesn't actually make much sense to format the docs anyway, since we
use the CMS itself to edit/generate them.

											
										
										
											2018-08-14 11:33:13 -06:00
+								    - feature: "Static + content management = ♥"
 								      description: "Get the speed, security, and scalability of a static site, while still providing a convenient editing interface for content."
 								    - feature: "An integrated part of your Git workflow"
 								      description: "Content is stored in your Git repository alongside your code for easier versioning, multi-channel publishing, and the option to handle content updates directly in Git."
 								    - feature: "An extensible CMS built on React"
 								      description: "Netlify CMS is built as a single-page React app. Create custom-styled previews, UI widgets, and editor plugins or add backends to support different Git platform APIs."
-												Migrate netlify-cms-www site into this repo (#860)

* Add frontmatter to docs files (prep to move)

* Move docs into position for website migration

* Migrate website from netlify-cms-www

Some modifications, including most of the changes in https://github.com/netlify/netlify-cms-www/pull/58 (previously reverted).

Also updated the readme and added hugo-bin for quicker onboarding of new docs contributors.

* Remove netlify.toml

This allows separate build commands for cms-demo and netlifycms.org.

* Remove website/netlify.toml

May re-add later, but it's not doing anything for now.

* Remove unused content file

											
										
										
											2017-12-04 16:42:20 -08:00
-												Website redesign

											
										
										
											2017-12-06 23:09:33 +01:00
+								cta:
-												docs(fix): revert prettier formatting on markdown files (#1612)

Prettier formatting our markdown files is causing bugs because of the
differences between Gatsby's parser and Prettier's. Also, Prettier
formats the inline code-blocks containing example CMS configs, but the
formatting it uses doesn't really make much sense or match the suggested
CMS config style.

It doesn't actually make much sense to format the docs anyway, since we
use the CMS itself to edit/generate them.

											
										
										
											2018-08-14 11:33:13 -06:00
+								  primaryhook: "Getting started is simple and free."
 								  primary: "Choose a template that’s pre-configured with a static site generator and deploys to a global CDN in one&nbsp;click."
 								  button: "[Get started](/docs/start-with-a-template/)"
-												Website redesign

											
										
										
											2017-12-06 23:09:33 +01:00
 								editors:
-												docs(fix): revert prettier formatting on markdown files (#1612)

Prettier formatting our markdown files is causing bugs because of the
differences between Gatsby's parser and Prettier's. Also, Prettier
formats the inline code-blocks containing example CMS configs, but the
formatting it uses doesn't really make much sense or match the suggested
CMS config style.

It doesn't actually make much sense to format the docs anyway, since we
use the CMS itself to edit/generate them.

											
										
										
											2018-08-14 11:33:13 -06:00
+								  hook: "A CMS that developers and content editors can&nbsp;agree&nbsp;on"
 								  intro: "You get to implement modern front end tools to deliver a faster, safer, and more scalable site. Editors get a friendly UI and intuitive workflow that meets their content management requirements."
-												Website redesign

											
										
										
											2017-12-06 23:09:33 +01:00
+								  features:
-												docs(fix): revert prettier formatting on markdown files (#1612)

Prettier formatting our markdown files is causing bugs because of the
differences between Gatsby's parser and Prettier's. Also, Prettier
formats the inline code-blocks containing example CMS configs, but the
formatting it uses doesn't really make much sense or match the suggested
CMS config style.

It doesn't actually make much sense to format the docs anyway, since we
use the CMS itself to edit/generate them.

											
										
										
											2018-08-14 11:33:13 -06:00
+								    - feature: "Editor-friendly user interface"
 								      description: "The web-based app includes rich-text editing, real-time preview, and drag-and-drop media uploads."
 								      imgpath: "feature-editor.svg"
 								    - feature: "Intuitive workflow for content teams"
 								      description: "Writers and editors can easily manage content from draft to review to publish across any number of custom content types."
 								      imgpath: "feature-workflow.svg"
 								    - feature: "Instant access without GitHub&nbsp;account"
-												docs: Update backend docs links (#3370)



											
										
										
											2020-03-04 02:46:59 -05:00
+								      description: "With [Git Gateway](/docs/git-gateway-backend/#git-gateway-with-netlify-identity), you can add CMS access for any team member — even if they don’t have a GitHub account. "
-												docs(fix): revert prettier formatting on markdown files (#1612)

Prettier formatting our markdown files is causing bugs because of the
differences between Gatsby's parser and Prettier's. Also, Prettier
formats the inline code-blocks containing example CMS configs, but the
formatting it uses doesn't really make much sense or match the suggested
CMS config style.

It doesn't actually make much sense to format the docs anyway, since we
use the CMS itself to edit/generate them.

											
										
										
											2018-08-14 11:33:13 -06:00
+								      imgpath: "feature-access.svg"
-												Website redesign

											
										
										
											2017-12-06 23:09:33 +01:00
 								community:
-												docs(fix): revert prettier formatting on markdown files (#1612)

Prettier formatting our markdown files is causing bugs because of the
differences between Gatsby's parser and Prettier's. Also, Prettier
formats the inline code-blocks containing example CMS configs, but the
formatting it uses doesn't really make much sense or match the suggested
CMS config style.

It doesn't actually make much sense to format the docs anyway, since we
use the CMS itself to edit/generate them.

											
										
										
											2018-08-14 11:33:13 -06:00
+								  hook: "Supported by a growing&nbsp;community"
-												Website redesign

											
										
										
											2017-12-06 23:09:33 +01:00
+								  features:
-												chore: fix misuse of the name JAMstack (#4290)


											
										
										
											2020-09-13 14:02:09 +02:00
+								    - feature: "Built on the Jamstack"
 								      description: "Netlify CMS is based on client-side JavaScript, reusable APIs and prebuilt Markup. Compared to server-side CMS like WordPress, this means better performance, higher security, lower cost of scaling, and a better developer experience. You can learn more about the Jamstack on [jamstack.org](https://jamstack.org)."
-												docs(fix): revert prettier formatting on markdown files (#1612)

Prettier formatting our markdown files is causing bugs because of the
differences between Gatsby's parser and Prettier's. Also, Prettier
formats the inline code-blocks containing example CMS configs, but the
formatting it uses doesn't really make much sense or match the suggested
CMS config style.

It doesn't actually make much sense to format the docs anyway, since we
use the CMS itself to edit/generate them.

											
										
										
											2018-08-14 11:33:13 -06:00
+								    - feature: "Support when you need it"
-												chore: switch chat links to slack (#2782)


											
										
										
											2019-10-22 20:59:04 -04:00
+								      description: "Get up and running with comprehensive [documentation](/docs) and templates or work through difficult problems in our [community chat](https://netlifycms.org/chat)."
-												docs(fix): revert prettier formatting on markdown files (#1612)

Prettier formatting our markdown files is causing bugs because of the
differences between Gatsby's parser and Prettier's. Also, Prettier
formats the inline code-blocks containing example CMS configs, but the
formatting it uses doesn't really make much sense or match the suggested
CMS config style.

It doesn't actually make much sense to format the docs anyway, since we
use the CMS itself to edit/generate them.

											
										
										
											2018-08-14 11:33:13 -06:00
+								    - feature: "A community-driven project you can help evolve"
 								      description: "Netlify CMS is built by a community of more than 100 contributors — and you can help. Join our [bi-weekly planning sessions](/community) or read the [contributing guide](/docs/contributor-guide) to join in."
 								  contributors: "Made possible by awesome contributors"