Open Beta: Publishing Conflict Resolution

Announcements
1

Hi everyone! :waving_hand:

We’ve just released our latest Open Beta for all CloudCannon users — you can opt in from the dashboard to test out the following features and updates:

  • Resolve publishing conflicts in CloudCannon
  • View text diffs of unsaved changes (one for you, @Joachim!)
  • Enhanced Source Editor
    • Multi-cursor editing with CMD+D / CTRL+D
    • Search and select via regex
    • A new default theme for better readability
    • Improved syntax highlighting
  • Improved publishing workflow
  • Streamlined domain management

If you’d like to find out more, check out our Beta docs — this is also where we’ll note any known issues as user feedback comes in.

Thanks to everyone who has already offered feedback on the Private Beta. We really appreciate it — keep it coming!

6 Likes
2

@Tim_G Gemma shared a couple of wins from your team planning board - would love to hear what you think of the resolving publishing conflicts in CloudCannon work :raising_hands:

3

Hey @Marlia_Morris :waving_hand: ooooh yep just saw this (was away last week). Thank you!!
I just signed up to the beta, now hunting for a conflict haha. Thank you!

2 Likes
4

Hope you had an awesome break away!! :chocolate_bar: Whoop whoop please let us know how you get on - the team would really love to hear feedback on Beta :raising_hands:

5

ummmm just tried this just now and I love love love love it.

Specifically, love that it immediately it tells you that there’s a conflict and tells you the file it’s having issues with. Love how it’s literally a case of ‘clicking the one you want’ to resolve the conflict. And love how that’s just it! No extra complication.

Thanks for this feature!! :folded_hands:t2:

5 Likes
6

This beta also tackles some accessibility improvements!

You may have noticed that some buttons in CloudCannon require a second click to confirm, generally when tied to an action that could be dangerous. The implementation of this behavior isn’t very friendly to screen readers. It also essentially imposes a three-second time limit to confirm the action before the button returns to its original state, which may pose accessibility challenges to some users.

We’ve replaced all of these with a confirmation modal, a pattern that is more familiar to web users and avoids these issues.

We’ve also identified and fixed some potential pitfalls for screen reader users. For example:

  • The form in the Site Authentication settings is now disabled with the appropriate HTML attributes instead of only being visually greyed-out.
  • The text content of a site file preview is now always loaded before the file is scrolled into view.
  • We’ve also cut down some unnecessary re-rendering of site file previews, which could cause visual flickering and loss of browser focus.

This is all part of our ongoing commitment to meet WCAG 2.1 at the AA level. If anyone has any feedback or ideas about other improvements, please reach out here in the community or at accessibility@cloudcannon.com!

4 Likes
7

A. Ma. Zing. feedback, Tim! I’m stoked this is useful to you :high_voltage: - the team saw your message and are appreciative for the feedback too :raising_hands:

1 Like