CloudCannon is a Git-backed A distributed version control system used to track changes in source code during software development. In CloudCannon, Git serves as the foundation for all Site content, allowing developers to work in their preferred tools while content teams edit through CloudCannon's interface. All changes made in CloudCannon are automatically committed to your Git Repository, ensuring a complete history and enabling seamless collaboration. An abbreviation of Content Management System, a CMS is a software that helps users create, manage, and modify content on a website. CloudCannon is a Git-based Content Management System for Git-backed websites that empowers both technical and non-technical team members to edit website code and content. A way to group multiple Sites from the same Git Repository, allowing you to define a main branch, as well as branching and publishing rules. You can access the Projects Browser using the Projects link in the App Sidebar. A website in CloudCannon that includes all the files, content, configuration, and settings needed to edit, build, and host a complete website. A storage location for the code and files that make up your website. CloudCannon supports the repository providers GitHub, GitLab, and Bitbucket, and highly recommends using a repository to store your website's files for better version control and collaboration. A workflow that controls how changes move between multiple Sites in a Project. Branching an existing Site allows Team Members to draft changes on an independent, identical copy, then publish those changes back when they are ready. Common workflows move changes from draft Sites to a Staging Site to a Production Site, protecting each upstream Site from changes until they are ready.Git
CMS
Project
Site
Git Repository
Publishing Workflow
Articles in this section are useful for developers responsible for configuring Publishing Workflows, commit messages, and branching in CloudCannon.
In the Publishing section of our Developer documentation, we cover:
- Projects — Learn how to group multiple Sites connected to a single Git Repository and enable upstream publishing
- Publishing Methods — Learn how to configure the method of publishing changes from one branch to another
- Pull Requests — Learn how to configure Pull Request templates and review and merge Pull Requests opened by CloudCannon
- Deploy Previews — Learn how CloudCannon can comment on Pull Requests and automatically create Sites for them
Here is a brief introduction to each of these topics.
Projects#
Projects are available on all plans. Site branching and Allow all branching are available on our Team or Enterprise plan.
In CloudCannon, a Project A way to group multiple Sites from the same Git Repository, allowing you to define a main branch, as well as branching and publishing rules. You can access the Projects Browser using the Projects link in the App Sidebar.Project
For a more in-depth explanation of Projects, please read our documentation:
- Create a Project
- Add a Site to your Project
- Turn on optional Project tabs
- Set the Main Branch for your Project
- What is Allow all branching?
- Turn on Allow all branching
- What are Branch Defaults?
- Configure Branch Defaults for your Project
- Delete a Project
Publishing Methods#
This feature is available on our Standard plan.
You can refine your Publishing Workflows in CloudCannon, choosing which Publish Branch The branch containing the copy of your website to which you want to publish your changes (sometimes called the "upstream" branch). Defining a Publish Branch allows Team Members to work on separate branches in parallel before publishing their changes to a shared branch. A Git feature that proposes changes to a repository and allows for review before merging. In CloudCannon, Pull Requests are one method of publishing changes from a Site to its Publish Branch. Unlike direct merging, Pull Requests require approval before changes are combined.Publish Branch
Pull Request
For a more in-depth explanation of Publishing Methods, please read our documentation:
- Connect a Publish Branch
- Change your Publishing Method
- Turn on Delete after Publishing
- Review and merge a Pull Request
Pull Requests#
You can configure Pull Request templates for Sites using the Pull Request Publishing Method, so your team can pre-fill the title, body, and other details when opening a Pull Request from CloudCannon.
For a more in-depth explanation of Pull Request templates, please read our documentation:
Deploy Previews#
This feature is available on our Team or Enterprise plan.
When a Pull Request is opened in your Git Repository, CloudCannon can post a Deploy Preview comment with build and editor links, create a branch Site for the Pull Request automatically, and clean that Site up when the Pull Request is closed or merged.
For a more in-depth explanation of Deploy Previews, please read our documentation: