CloudCannon Processes

CloudCannon is a headless CMS we use to deploy changes to our websites, including banno.com and the Knowledge Base. It allows for creating and editing pages within the site without going directly into markdown tiles and making changes in a code editor. We have a few processes required to ensure security and traceability when making changes to sites using CloudCannon.

Getting a CloudCannon account

An existing team member will invite you via email to any CloudCannon projects relevant to your work. These emails will contain a link to click to accept the invite and create your account, if you don’t already have one.

Selecting a project

You may be added to one or more CloudCannon projects, depending on your role. When you log in to CloudCannon, the Projects link on the lefthand navigation will show a list of all projects you’ve been invited to.

Editing a site

Editing a site will look different depending on which site you’re working on, and in some cases, which pages within those sites you’re working on. For more information, see the process documents for individual projects:

• [../statement-management](Statement Management)

Publishing your changes

Once you create a pull request, it must be approved by at least one designated GitHub approver. As soon as you have an approval, you are responsible for merging your own changes in by clicking Merge pull request and then clicking Confirm merge. This gives us a clear audit trail for who made the changes, who did the approval, and who took the changes live. Once you have merged the pull request, there may be additional steps required to deploy the live site. See the pages listed above for any additional actions needed to deploy the requested site.