@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
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.
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!
A huge thanks to everyone who participated in our Publishing Conflict Resolution Beta. Your feedback helped us identify several improvements before we released these features to all users (Which we’ve just done — see the full changelog).
The ability to resolve Git conflicts directly in CloudCannon was frequently requested, and your beta testing assisted us in developing a workable interface that fits with your existing workflows.
We really appreciated all reports that highlighted areas needing refinement in the conflict highlighting and resolution options. Community input continues to be valuable as we develop CloudCannon’s features, and we welcome your ongoing thoughts about these and other changes in the product.