Version history per page

[Lunariz]

Describe the problem

Sometimes you might accidentally delete something you shouldn't have. Or maybe you want to see the past layout of the page, or see when stuff was created.

Feature implementation

With version history, you can solve all these problems.

As for UI, this is already implemented by other apps, so can probably be very similar in design. See: Evernote, Google Docs, Wikipedia. The focus should be on which Changes were made (strike-through old, highlight new, etc).

Additional info per bullet to be shown:

• When was the bullet created
• When was the bullet changed, what changed
• Who changed the bullet (multiplayer)

[justshaun]

I think this is a crucial missing element for mid to large sized collaborative projects. You need to know which accounts made certain changes to have accountability and/or to be able to take action (e.g. removing editing rights). You also need to be able to revert to earlier versions if the group disagrees on any changes made by an individual.

How e.g. google docs does it would be fine.

We were considering using Roam for an academic wiki, but without this feature it isn't possible.

[jtrakk]

Ideally the full edit history tree would be preserved, like a git revision tree, so I can undo a edit and replace it with another edit, and then compare the two branches. I want to visualize the whole tree. See tools for visualizing history.

That way, no matter what undo/redo operations I apply, I can always understand where I am in the history and how to move to get back to where I was.

[chinarut]

sounds like this could be merged with #73 and I like how things are being articulated here as I’ve always been a big fan of visual version trees from my Atria ClearCase days (yeah, I’m dating myself :)