Bringing Git Workflows to Editors

headshot of Mike smiling
Mike Neumegen
08 May 2019 | 2 mins

In the past we’ve talked about our mission of bringing publishing workflows to non-technical editors. This post is an update on some interesting new CloudCannon features bringing us closer to fully realising our vision.


A typical workflow on CloudCannon is to have editors work on a staging site, with a separate production site serving a live copy to the public. This is a great workflow because it allows editors to preview changes and iterate on content before publishing to production. One issue of this approach is having multiple sites in CloudCannon for each repository soon gets overwhelming.

Projects address this issue, providing a logical grouping to the sites in your CloudCannon account. Each project is centered around a single Git repository.


Selecting a project lists the sites connected to that repository. You can also add a description, and links to resources outside of CloudCannon.


In this example the production branch has a lock icon which indicates an editing lock. In most cases you’ll want an editing lock for production sites to force content changes to go through the staging branch.

Edit Lock


A staging/production workflow is fine for simple content changes but falls down when you have multiple editors trying to time their content. For example, you might spend a week overhauling a landing page, meanwhile your colleague needs to release a blog post. You can’t release a half finished landing page so your changes are now blocking the blog post from releasing. These situations only get more complicated and harder to resolve as you add more editors.

With Projects this workflow is improved, as editors can now harness the power of branching. Editors click the + button and set a name. This creates a branch on GitHub and a completely isolated site with its own URL on CloudCannon.


The editor is now free to update this site without blocking the main staging branch.


When the content is ready for primetime, editors can publish the content. Behind the scenes we perform a Git merge into the staging branch.


What’s next?

We’re excited at how these workflows are progressing for editors, enabling them to work with Git and collaborate more effectively. The next step is to provide more confidence and context to editors merging to another branch. Stayed tuned to find out more!

You might also be interested in

CloudCannon, SvelteKit and Next.js logos

Next.js and SvelteKit support in CloudCannon


7 October 2021 | 2 mins

Read more

Making a Page Builder with CloudCannon

Jordan Trbuhovic

7 October 2021 | 5 mins

Read more
Graphic showing components managed by Bookshop being used in multiple websites

Introducing Bookshop: component-driven workflow for static websites


6 October 2021 | 1 min

Read more
Don’t miss the latest
A monthly newsletter to keep you up-to-date with the latest CloudCannon news
Illustration of woman holding an envilope