Redesign "Done" button in default edit mode

[marcoambrosini]

Is your feature request related to a problem? Please describe. When I am defaulting edit mode, which is where I want to be for most of my use, the big done button on the top right doesn't make much sense.

Describe the solution you'd like

• Abandon the concept of "edit" and "done"
• Adopt concept of "lock" and "unlock"

[marcoambrosini]

My bad, I see that that's already there 😄

[marcoambrosini]

The thing is though that when I am defaulting edit mode, which is where I want to be for most of my use, the big done button on the top right doesn't make much sense.

I would prefer to have a lock button and the locked state of the document being remembered. WDYT @mejo- @juliushaertl @max-nextcloud ?

This would allow for a default and some exceptions that are manually set and remembered

[juliushaertl]

I'm not sure lock is the right term for that as we use lock in other contexts, but agree that we probably can improve the wording to be more specific then Done for the case where you use editing as a default page view mode.

[marcoambrosini]

we use lock in other contexts

Do you mean files @juliushaertl ?

[marcoambrosini]

In default edit mode, I would actually remove the one button altogether and add a "Lock page" entry in the 3 dot menu.

[juliushaertl]

File locking is used as a term with https://apps.nextcloud.com/apps/files_lock where a user or desktop client locks the file to take ownership of file changes and prevent other users or clients from writing to the file as long as the lock is active.

[chmac]

@marcoambrosini Could you edit the title of this issue if it's now about a different change? Or close it if you think the topic that's raised has been answered. I'm not sure if the issue is about a feature which already exists (default edit mode) or has now evolved into a different request for a different feature.

[almereyda]

The part of the original idea about an edit-only workflow could really easy accessibility, by removing a few clicks/taps when changing the open document more often. Which can happen during wiki gardening and foraging.

"Adopt" was part of the initial criteria, but I would second any voice suggesting to drop it.

Maybe "voluntary file locking per page" is useful to carry on in a follow up issue? (:

This is me, trying to advance the partial milestone expressed above, in order to reduce perceived frictions in the workflow.

A current, extreme example of frictions in editorial workflows and their impact on user experience would be:

• https://github.com/outline/outline/issues/5310

---

Edit:

Changing the default behaviour is already possible in a Collective's settings: