☁️ Loving our new documentation website? Provide feedback in the CloudCannon Community! ✨

Introduction to Publishing

Last modified: March 11th, 2026

On this page

CloudCannon is a Git-backed CMS, allowing you to store your website source files securely on a Git Provider. One benefit of Git is the capacity to work on content changes in parallel with separate Branches and control when changes are published to your live website. In CloudCannon, you can configure a Project for managing Sites connected to Branches in a single Git Repository, including designating a Main Branch and defining publishing workflows.

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

Here is a brief introduction to each of these topics.

Projects#

Some features are only available on our Team and Enterprise plans.

In CloudCannon, a Project is a group of Sites connected to Branches from a single Git Repository. Creating a Project allows you to designate a Main Branch in your Repository and define branching rules.

For a more in-depth explanation of Projects, please read our documentation:

Publishing Methods#

This feature is available on our Standard plans.

You can refine your publishing workflows in CloudCannon, choosing which Publish Branch each Site should publish to, selecting whether publishing is automatic or requires a Pull Request, and defining templates for Pull Requests for documenting your website changes.

For a more in-depth explanation of publishing methods, please read our documentation:

Related Resources

Open in a new tab