To me, the most interesting feedback here is that seamless-editable-by-default is a negative for this user, and as a work-around, this organization locks/unlocks every page. This is surprising to me because I find content locks and editing friction very annoying. For example I used Quip for many years, which locks any block currently being edited by someone else, which can be quite frustrating when someone happens to have an idling cursor in a random position. Likewise, wouldn’t you be baffled if you needed to click a “Start Editing” button in Word or Google Docs? But it’s an interesting perspective to consider especially for users coming from Confluence, where editing has much more ceremony, and more generally for read-heavy wiki use case. In any case, it’s really the accidental edits at the root of the problem.
Like many other commenters, my biggest pain point is page load speed.
To me, the most interesting feedback here is that seamless-editable-by-default is a negative for this user, and as a work-around, this organization locks/unlocks every page. This is surprising to me because I find content locks and editing friction very annoying. For example I used Quip for many years, which locks any block currently being edited by someone else, which can be quite frustrating when someone happens to have an idling cursor in a random position. Likewise, wouldn’t you be baffled if you needed to click a “Start Editing” button in Word or Google Docs? But it’s an interesting perspective to consider especially for users coming from Confluence, where editing has much more ceremony, and more generally for read-heavy wiki use case. In any case, it’s really the accidental edits at the root of the problem.
Like many other commenters, my biggest pain point is page load speed.