News & Announcements
Netlify CMS 2.0 launches with BitBucket support and a new monorepo architecture
Today we’re releasing Netlify CMS 2.0, which adds support for using Bitbucket as a backend.
With this release, Netlify CMS 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.
How it works
Netlify CMS is an open source content management system which harnesses your Git workflow. It enables you to provide editors with a friendly UI and intuitive workflow, while not requiring them to understand Git. You can use it with any static site generator to create faster, more flexible web projects. Content can be stored in your Bitbucket repository alongside your code for easier versioning, multi-channel publishing, and the option to handle content updates directly in Git.
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, 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.
Shawn Erquhart, project lead for Netlify CMS, spoke about this move to a monorepo architecture, saying,
“We see this as a big step for making the project even more productive for developers and contributors. This makes the process of contributing and extending the features of Netlify CMS more straightforward and will help the already active community to unleash more and more of their potential.”
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. Give us a shout on Twitter or Gitter if you have questions or ideas.