gcg/static-cms
0
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

Create netlify-cms-2-0-launches-with-bitbucket-support-and-a-new-monorepo-architecture.md

Browse Source
This commit is contained in:
Jessica Parsons 2018-07-25 11:58:31 -07:00 committed by GitHub
parent 04c44518b2
commit 232adbc69a
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 30 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

30
website/content/blog/netlify-cms-2-0-launches-with-bitbucket-support-and-a-new-monorepo-architecture.md Normal file
View File

@ -0,0 +1,30 @@
---
title: >-
Netlify CMS 2.0 launches with Bitbucket support and a new monorepo
architecture
author: Phil Hawksworth
description: >-
Announcing the release of Netlify CMS v2.0, with new Bitbucket support and an
improved project architecture designed to ease contribution and the extension
of features.
date: '2018-07-25'
---
Today we’re releasing Netlify CMS 2.0, which adds support for using Bitbucket as a backend.
With this release, [Netlify CMS](https://www.netlifycms.org/) now supports all major Git collaboration providers, adding Bitbucket to the list of supported providers which already includes GitLab and GitHub.
While you could already use Netlify CMS with most static site generators, our long-term vision is to be tool-agnostic so you can use whatever tool helps you work best. The latest release brings us one step closer by giving the option of an open source, Git-centric CMS to tens of thousands of businesses that depend on Bitbucket, including 60 of the Fortune 100.
## Becoming a Monorepo
The other big change with 2.0 is the migration from a single codebase to a collection of interdependent packages called a “monorepo”. Netlify CMS still lives in a [single repository on GitHub](https://github.com/netlify/netlify-cms), but the many extensions that were kept within Netlify CMS itself are now completely separate from the application core. This brings a few benefits:
* Extension authors can easily copy an existing extension from the Netlify CMS repo and create a custom version.
* Your custom extensions can now do anything the “official” extensions can do (because official extensions are no longer taking advantage of privileged internal code).
* The monorepo approach provides a foundation that will encourage a more modular CMS, with shared parts that make extension authoring easier.
## What’s next
Upcoming feature releases will bring new image handling features and a number of improved APIs, adding even more possibilities to future CMS extensions.
We’re always looking for more ideas and helping hands, so if you want to help build a smarter, safer, and more scalable CMS, we’d love your [contributions](https://www.netlifycms.org/docs/contributor-guide/). Give us a shout on [Twitter](https://twitter.com/netlifycms) or [Gitter](https://github.com/netlify/netlify-cms/pull/525) if you have questions or ideas.