When using federated wiki with new users, we are experiencing situations that were not expected.
.
Sometimes double clicking does not work for users. Paragraphs appear to be blocked. Reloading the page helps to resolve the blocking. When optimizing wiki for handheld devices, should we omit double clicking/tapping at all?
Trying to click the flag (for forking, deleting, restoring an older version) sometimes results in a drag of the whole journal area, which we might want to suppress for this button.
Dragging a journal onto another is not widely known.
Implicitly forking a Welcome Visitors page when trying to edit a remote wiki (blue halo) often corrupts an existing wiki. We suggest implicit forks that would overwrite existing pages go to local storage instead. This would leave a message to the user that something unexpected happened. Overwriting existing content after an implicit fork would then need a second, conscious fork by the user.
The lineup of pages can contain multiple versions of a single page. If one edits one display, the other remains untouched and may hold an outdated state. How do we propagate state changes in the lineup from right to left?
When we create pages based on a template, and change the template afterwards, we would like to update all descendants
Reloading a wiki page that has wiki mode enabled will leave us with a page and wiki mode disabled. Would we want to remember being in wiki mode state instead?