CloudCannon upgrades are here 🎉

[george]

We’ve just released a big update to CloudCannon! Feel free to make the switch and try it out!

What’s new

Expanded Editable Regions

Editable Regions now support front matter, data files, and template files (.astro, .tsx, etc.). Your editors can modify text, images, arrays, and source content right where they appear, creating a more intuitive Visual Editor experience.

Check it out below, where we edit text, items in an array, and swap in a new image:

CloudCannon Editable Regions demo

We’ve been careful to ensure there are no breaking changes — your existing sites will work exactly as before.

Configuration Mode

Adjust site settings live within CloudCannon. Spot an input that needs tweaking? Click to change it. Available for sites on Unified Configuration, this feature accelerates your setup workflow. Switch Configuration Mode on to change your inputs, and off to preview the editor experience.

As an example below, we’ll change the img path to an image preview, and make our tags input a multiselect:

CloudCannon Configuration Mode demo

Interface refresh

Thanks to a behind-the-scenes rewrite, the whole CloudCannon platform feels faster and more streamlined. You’ll see reorganized navigation, improved dashboards with activity insights and bandwidth metrics, and performance boosts throughout.

Timeline

Now through February 2026: Opt in via the CloudCannon sidebar whenever you’re ready. You can revert if needed.

February 2026: Automatic upgrade for all remaining users.

Documentation

We’ve thoroughly refreshed our docs and guides as part of this release (thanks Ella!). If you’re interested in jumping straight to the newest features, check out the following:

• Set up Visual Editing (with Editable Regions)

• What is Configuration Mode?

• Full changelog for this release

Any questions?

Feel free to ask the team here, or contact support via the app.

[Lex]

Wow, these certainly are some great updates. The new visual editing, but also the configuration mode works so much better than the previous config editor. Really intuitive. However I can’t seem to find a way to edit global inputs, structures etc. with it now?

Also it would be really helpful that when there is an error in the config file that prevents saving it in Cloudcannon we could get a hint as to where we can find that error .

Tx team!

[Ryan]

Thanks Lex, glad you’re enjoying it!

You can still access the full config GUI by opening your config file from the File Browser, and then switching to the Data Editor using the toggle in the editing interface header. That’s still the only way to edit your global _structures (for now!).

You can also edit a global Input by turning on Config Mode, finding that input in the Data Editor, and clicking the purple “Edit” button on it. You’ll see there are options to edit the globally-scoped config for the Input, or add config scoped to the current collection.

We’d definitely like to add some better hints about where to find validation errors that are preventing a file from being saved. You can expect some improvements there in the not-too-distant future, I’ll make sure to keep you posted!

[Lex]

Ah Thanks Ryan, there it is

[Oliver_Lynch]

Hello, I’ve noticed a few small issues in the visual editor which only happen in the new version.

When opening a new window in the editor (via a snippet or the new config editor for example), the new window pops underneath the current one, and is often completely hidden which makes it feel like clicking edit did nothing.

Rich text fields are no longer resizable by default, but when opening the field options in the new configuration mode “Allow Resize” is auto-selected and the field becomes resizable. This doesn’t happen if allow_resize is enabled explicitly.

The new configuration mode is really cool, are there plans to let you edit bookshop components/structures?

Thanks for the help!

[Ryan]

Thanks for the feedback Oliver, we’ll get onto fixing those!

@Oliver_Lynch

are there plans to let you edit bookshop components/structures?

This isn’t something we’ve planned. It’s a bit tricky because Bookshop uses a slightly different configuration spec, which is turned into CloudCannon config when you use @bookshop/generate

Bookshop is partly a utility for helping you generate your CloudCannon config. Depending on your preference, you could move your structure/inputs config from your Bookshop components to the CloudCannon config file, or vice versa. Hopefully if we improve the general experience of configuring CloudCannon, it can benefit sites that use Bookshop and sites that don’t.

[Gio]

I wish I would’ve found this comment before trying to wire up my bookshop components to use the new editable regions.

Without knowing the inner workings of how CloudCannon renders the live editor and how bookshop hooks into it all, to me it seems like it’s a feature that could be supported. A data-component, data-id-key, and data-id exist which feels close to supporting bookshop components.

I was able to get some basic text to work with the new editable regions.

While technically possible to wire up bookshop components to use the new editable regions. It is not supported as you mentioned. As Oliver mentioned, having this work with bookshop components would be pretty cool.

[Ryan]

I think I might have misled you in a prior conversation, regarding the mixing of Bookshop and editable regions, sorry Gio!

Bookshop and Editable Regions are two different paths to live editing, and we don’t recommend combining the two. They each rely on their own sets of data attributes and event listeners, so they can get in each other’s way e.g. if one renders over the other. We are currently thinking about ways to help bridge the gap though…

RE: the error message in your screenshot, it looks like you’ve got a text editable whose data-prop is pointed at a text field on the content block, but no such field exists in the YML.

[Ryan]

@Oliver_Lynch

Rich text fields are no longer resizable by default

We’ve just released a fix for this, thanks for the heads-up @Oliver_Lynch!

[george]

@Gio We have added a new way to use editable regions with bookshop. See the full announcement at: Adding editable regions to Bookshop sites (Hugo, Jekyll, and Eleventy)

[Gio]

That’s awesome! Thanks for the ping. I can’t wait to dive in.