Changelog

Project Browser performance improvements

January 23rd, 2026 | Changelog

This release improved the loading time of the Projects Browser, added more sorting options for the Projects Browser, added a better UI for Site Transfers, and added a warning when cancelling your CloudCannon subscription.

It also addressed several issues, including automatically assigning Sites to Projects, incorrect CloudCannon DNS zones, Input configuration, Inboxes, Schema parsing, and more.

Features & Improvements

• The Projects Browser loads more quickly, particularly for Projects with many Sites.
• Added the option to sort the Projects Browser by recently built.
• Added better UI and messaging for Site transfers, such as:
  • Paginating transfer requests.
  • More details about the Organization transferring the Site to you.
  • Better copy for SSL Certificate lists.
  • A clearer warning message when a Transfer Request will increase your billing due to Site Sharing or Client Sharing.
• Added an extra warning about your live websites going down before you cancel your CloudCannon subscription.

Fixes

• Fixed an issue where, in some cases, CloudCannon did not automatically assign new Sites to the appropriate Project.
• Fixed an issue where, in some cases, CloudCannon would incorrectly configure the DNS zone for a Custom Domain.
• Fixed an issue where CloudCannon did not immediately update Input configuration after you made changes using Configuration Mode.
• Fixed an issue where CloudCannon did not re-render the page correctly when switching between Inboxes.
• Fixed an issue where CloudCannon would incorrectly parse Schema files with a trailing newline in the file content.
• Fixed an issue where, in some cases, CloudCannon would incorrectly display an error message on Snippets in the Content Editor.
• Fixed an issue where, in some cases, CloudCannon would not immediately create a folder after you selected the Create a Folder option in the Collection Browser or File Browser.
• Fixed an issue where CloudCannon would prevent you from deleting a file if it contained an empty required Input.
• Updated dependencies to patch security vulnerabilities.

Spam detection improvement

December 24th, 2025 | Changelog

This release fixed an issue relating to spam detection in form submissions.

New Color Input configuration options

December 18th, 2025 | Changelog

This release added the palette and hide_picker configuration keys for Color Inputs, improved filter behavior for straight and curly quote marks, changed how CloudCannon determines developer files, added better warning messages, and improved overall app performance.

It also addressed several issues, including those affecting SSG suggestions, File Card icons in the Collection Browser, endless loading states after a failed Sync, and .yml and .json Schema files.

Features & Improvements

• You can now configure the palette option for Color Inputs. This key provides a palette below the color picker for important color values.
• You can now configure the hide_picker option for Color Inputs with the palette option configured. This key toggles whether CloudCannon displays the color spectrum picker and the palette. When set to true, the Color Input will only display the palette.

_inputs:
  theme_color:
    type: color
    options:
      palette:
        - rgb(255, 128, 0)
        - hsv(00, 70, 50)
        - lightyellow
      hide_picker: true

{
  "_inputs": {
    "theme_color": {
      "type": "color",
      "options": {
        "palette": [
          "rgb(255, 128, 0)",
          "hsv(00, 70, 50)",
          "lightyellow"
        ],
        "hide_picker": true
      }
    }
  }
}

• When using a filter to search files or Sites in one of CloudCannon's Browsers, the filter will now return results for straight quotation marks ( ' or " ) and curly quotation marks ( ’ or ”) whenever a string contains either type of quote character.
• CloudCannon no longer automatically treats files in a folder called components as developer files.
• Added a warning message to the Site Navigation when your Site uses features that require the new version of CloudCannon.
• Improved overall app performance.

Fixes

• Fixed an issue where files with the + character in the filename would not open in CloudCannon Editing Interfaces.
• Fixed an issue where, when creating your CloudCannon Configuration File, CloudCannon would incorrectly suggest Hugo as your SSG.
• Fixed an issue where, in some cases, editing your Collection configuration would incorrectly change the file icons in the Collection Browser to notes.
• Fixed an issue where, for non-unified Sites or Sites without live configuration, updating the title of a new file did not update the title displayed on the File Card or in the Editing Interface Header.
• Fixed an issue where CloudCannon could enter an endless loading state after a failed Sync.
• Fixed an issue causing the Site Icon, and icons, images, and gallery images on File Cards to have incorrect rounding.
• Fixed an issue where, when editing the content of an HTML Input, CloudCannon would incorrectly update the value for the loading attribute on images.
• Fixed an issue causing the Content Editor to lag when a file contained many Snippets.
• Fixed an issue where you could not clear the value of a Date Input.
• Fixed an issue where CloudCannon did not parse .yml or .json Schema files correctly.
• Fixed an issue where, in some cases, CloudCannon would incorrectly re-render Rich Text Inputs and lose focus.
• Preview images now load correctly on the Projects list.
• Fixed an issue where _enabled_editors was not properly respected for new collection items.
• Fixed an issue where the interface would not update correctly after an image was added to an array.

New Input validation options

December 12th, 2025 | Changelog

This release added several new Input validation keys, a template HTML element and better default behavior for Array Editable Regions, and support for square brackets in data-prop key.

It also addressed several issues, including those affecting Component Editable Regions where data-prop referenced an external file, the Avatars list when collaboratively editing a file, and the image cropper in File Inputs.

Features & Improvements

• Added the min_graphemes, min_graphemes_message, max_graphemes, max_graphemes_message, min_words, min_words_message, max_words, max_words_message, and locale configuration keys for Input validation. These keys are available for Code, Color, File, Select, Text, Rich Text, and URL Inputs. To use this key in a Select Input, allow_create must be set to true.
  • The min_graphemes and max_graphemes keys define the string length, in graphemes, that CloudCannon will allow in an Input. The min_graphemes_message and max_graphemes_message keys define custom error messages that explain why a value has failed the validation criteria.
  • The min_words and max_words keys define the string length, in words, that CloudCannon will allow in an Input. The min_words_message and max_words_message keys define custom error messages that explain why a value has failed the validation criteria.
  • The locale key defines which language CloudCannon should use to determine a single grapheme or word. This key accepts a single language subtag.

_inputs:
  description:
    type: markdown
    options:
      min_words: 1
      max_words: 10
      locale: jp
  caption:
    type: markdown
    options:
      min_graphemes: 1
      max_graphemes: 10
      locale: en-US

{
  "_inputs": {
    "description": {
      "type": "markdown",
      "options": {
        "min_words": 1,
        "max_words": 10,
        "locale": "jp"
      }
    },
    "caption": {
      "type": "markdown",
      "options": {
        "min_graphemes": 1,
        "max_graphemes": 10,
        "locale": "en-US"
      }
    }
  }
}

• For Array Editable Regions, you can now use <template> HTML elements to populate new array items rather than registering components. You can add the data-id attribute to each <template> element, allowing you to define several array item templates.

<editable-array data-prop="my_array" data-id-key="_name">
	<template data-id="hero">
		<h1 data-editable="text" data-prop="title"></h1>
	</template>
	<template data-id="testimonials">
		<div>
			<p data-editable="text" data-prop="message"></p>
		</div>
	</template>
	...
</editable-array>

• For Array Editable Regions in complex arrays or page building, CloudCannon will now use the value of data-component-key and data-component as the value for data-id-key and data-id by default, when the latter are undefined.
• Editable Regions now support [] square brackets in the file path for @file, @data, and @collection special values for data-prop. If your file path contains a single set of [] brackets, you can surround the file path with double [[]] brackets.

Fixes

• Fixed an issue where Component Editable Regions did not populate correctly when data-prop was an external file.
• Fixed an issue where switching which person was editing a file would make everyone appear to have the same avatar in the Avatars list in the Editing Interface Header.
• Fixed an issue where, when uploading an image using a File Input, CloudCannon would open the image cropper even when the image had the correct dimensions.
• Updated dependencies to patch security vulnerabilities.

Use a filename as the value_key for Select Inputs

December 5th, 2025 | Changelog

This release added new values for value_key in Select Inputs, better copy for in-app guides, Status and Guide Progress tooltips, and improved clarity for error and activity messaging and the Bandwidth Usage table.

It also addressed several issues, including those affecting the in-app guides, broken links, Rich Text Inputs, file titles, and UI appearance.

Features & Improvements

• You can now use value_key: filename and value_key: filename_without_ext to populate a Select Input with the filename from a file on your Site. Here is an example Input configuration:

_inputs:
  related_articles:
    type: multiselect
    options:
      values: collections.articles
      value_key: filename_without_ext

{
  "_inputs": {
    "related_articles": {
      "type": "multiselect",
      "options": {
        "values": "collections.articles",
        "value_key": "filename_without_ext"
      }
    }
  }
}

• Better copy for the Getting Started with Editing in-app guide.
• The Set up Visual Editing in-app guide now tells you which Collections are using an automatically detected URL, an explicitly configured URL, or have URL disabled.
• Improved the clarity of URLs in the Bandwidth table under the Usage tab on your Site Dashboard by removing the domain name.
• Added a tooltip to the Status and Guide Progress indicators next to Dashboard in your Site Navigation.
• Better error messaging for the Invalid global paths warning on your Site Dashboard.
• Better copy for Cards under the Activity tab on your Site Dashboard to provide more context when you update your Site settings.

Fixes

• Fixed a broken link for the Syncs tab on your Site Dashboard.
• Removed the Complete the Guide: Getting Started with Editing from the Host your website on the Internet in-app guide, as web hosting does not require you to have configured WYSIWYG editing.
• Fixed an issue where the Skip Tour button was still visible after a task was completed in the Getting Started with Editing in-app guide.
• Fixed an issue where Rich Text Inputs were not resizable by default.
• Fixed an issue where, when updating the title of a file, the title in the Collection Browser, Editing Interface Header, and Save changes modal did not immediately update.
• Fixed spacing issues and UI appearance across the app.

Pull Request templates

December 4th, 2025 | Changelog

This release added Pull Request templates, the new Lume logo, and minor improvements for the Source Editor.

It also addressed several issues, including those affecting files with & in the filename, branching inside of Projects, broken links, and incorrect error messages.

Features & Improvements

• Added Pull Request templates, allowing you to configure default title and body content, customize the title and body inputs, and reference a file for more complex body content. Please read our latest documentation for more information:
  • What is a Pull Request template?
  • Configure a Pull Request template
• Updated the in-app logo for Lume.
• Performance improvements for the Source Editor.

Fixes

• Fixed an issue where you could not open files with the & character in the filename.
• Fixed an issue where Create a Site button in the Project Sites Browser did not automatically copy the Main Branch when one was configured.
• Fixed a broken link for the Configure button on the Setup instructions modal under your Subdomain page.

Improved Projects loading time

November 27th, 2025 | Changelog

This release improved loading time for the Projects Browser and added better error handling, Ruby file syntax highlighting, and an Export as CSV button for bandwidth.

It also addressed several issues affecting the Datetime Input and adding base domains.

Features & Improvements

• Improved loading time for the Projects Browser.
• Better error handling when loading your Site configuration.
• Added syntax highlighting for .rb files in the Code Editor.
• Added an Export as CSV button below the Bandwidth Table for the Usage tab on your Site Dashboard and Org Home pages.

Fixes

• Fixed an issue where adding a date to a Datetime Input did not work unless time was also added. It now defaults to 00:00:00.
• Fixed an issue where you could incorrectly add a subdomain to your base domain.

Split your Configuration File

November 26th, 2025 | Changelog

This release added the ability to split your Site configuration across multiple files.

Features & Improvements

• You can now split your Site configuration across multiple Configuration Files. Please read our latest documentation for more information:

  • Why split your Configuration File?
  • Defining the same key in multiple Configuration Files
  • Best practice for splitting your Configuration File
  • Split your Configuration File
  • Configuration File reference

• Added the following keys for your CloudCannon Configuration File: collections_config_from_glob, schemas_from_glob, _inputs_from_glob, _structures_from_glob, values_from_glob, _snippets_from_glob, _snippets_imports_from_glob, and _editables_from_glob.

   

Edit Input buttons in Configuration Mode

November 20th, 2025 | Changelog

This release added several improvements, including Input configuration to Configuration Mode, better app behavior when merging a branch, better UI for the Build Configuration page, better error messaging, and the capacity to browse DAM assets.

It also addressed several issues, including those affecting Configuration Mode data panels, the Conflict Resolution code editor, and filters in Inboxes.

Features & Improvements

• You can now edit your Input configuration using Configuration Mode.
  • Turning Configuration Mode on in an editing interface will show purple Edit buttons next to each Input, which will open the Edit Input data panel.
  • You can use the Edit Input data panel to update the configuration across several levels of the configuration cascade and review where an input is already configured.
  • Any configuration updated using Configuration Mode will immediately change the Input in your editing interface, unless superseded by a more specific configuration.
• CloudCannon now returns you to your Site Browser after merging and deleting a branch, rather than showing an error.
• Better UI for the Initial Site Settings prompt on the Build Configuration page under Site Settings.
• Better UI for the Needs Attention prompt on the Site Dashboard.
• Removed the Needs Attention warning when two or more Collections have the same path.
• Added error messaging in the Needs Attention prompt on your Site Dashboard when you have a parsing issue in your CloudCannon Configuration File.
• You can no longer see Inboxes in your Site Navigation if you do not have permission to use them.
• You can now browse through your DAM assets using the Browse tab on your DAM page, through the Assets page under Org Settings.
• You can now configure _inputs.$ to add comments and documentation links to the top-level object or array in a data file.
• Improved the performance of the File Input upload browser.

Fixes

• Fixed an issue where, for some screen sizes, the Edit Configuration data panel would appear outside the boundaries of the app.
• Fixed an issue where data panels would open at the bottom of the app with a small window size.
• Fixed an issue where linking to a URL for the Sites Browser with a search term would not preserve the search results.
• Fixed an issue where undefined or null Input values would interfere when merging cascading configuration.
• Fixed an issue where CloudCannon would warn you that Git LFS was not enabled even if you had no Git LFS settings in your /.gitattributes file.
• Fixed an issue where updates to a Structure did not immediately appear in the Data Editor.
• Fixed an issue where CloudCannon's autosave would shift which field was focused in the Data Editor.
• Fixed an issue causing JavaScript content from .astro file front matter to appear as text in the Data Editor or editing interface sidebar.
• Fixed an issue where, in some cases, the Conflict Resolution code editor would shrink.
• Fixed incorrect spacing for the Save and Discard buttons in the Save Changes modal.
• Fixed an issue where CloudCannon did not resolve the output URL correctly for new files using a data placeholder (e.g., {title}).
• Fixed an issue where the form submission filter in an Inbox did not work.
• Updated dependencies to patch security vulnerabilities.

General fixes

November 14th, 2025 | Changelog

This release addressed an issue which sometimes prevented the Visual Editor from loading. It also included a number of UI improvements.

Fixes

• Improved error handling when an authentication error occurs in the Visual Editor.
• Links inside Editable Regions no longer redirect the Visual Editor when clicked.
• Organization guides can now be disabled.
• Fixed some incorrect error messaging within the Visual Editor.
• Fixed an issue preventing some objects from opening in the Data Editor.
• Fixed some modals overflowing beyond the edge of the screen.
• Various improvements to the mobile UI.
• Updated dependencies to patch security vulnerabilities.