BookStack icon indicating copy to clipboard operation
BookStack copied to clipboard

Add page revisioning option of all pages on book layer

Open tumbri1 opened this issue 2 years ago • 2 comments

Describe the feature you'd like

Users should be able to not only view change history specifically on page level, but also see revisioning of all pages on book or chapter level.

Describe the benefits this would bring to existing BookStack users

This would highly increase the overview users would have over recent changes not only specific to pages but also to the entire books and chapters.

Can the goal of this request already be achieved via other means?

There is already the option to view change history on page level. So in this case the requested feature would be to add another button when opening a book to view complete change history.

Have you searched for an existing open/closed issue?

  • [X] I have searched for existing issues and none cover my fundamental request

How long have you been using BookStack?

1 to 5 years

Additional context

No response

tumbri1 avatar Dec 20 '23 08:12 tumbri1

Thanks for the request @tumbri1.

Describe the benefits this would bring to existing BookStack users This would highly increase the overview users would have over recent changes not only specific to pages but also to the entire books and chapters.

What are the benefits to existing BookStack users of such an overview? What does this fundamentally allow BookStack users to achieve? Why is such an overview needed, or how does it help?

ssddanbrown avatar Dec 20 '23 15:12 ssddanbrown

Such an overview would not be highly beneficial, though it may help users to keep track of the different versions of all of the pages in a single book. I imagine this as a list. Like an additional button when clicking on a book which lists all pages in it and below every page a sublist with all versions and when this version was created/saved. Maybe also with a book specific changelog which can be accessed if wanted.

So again I would actually see a benefit in this but it's not too high, so if implementing and maintaining such a feature would cause too much effort relative to its use, then it would not make sense.

tumbri1 avatar Jan 03 '24 08:01 tumbri1