Stay inside shelve after deleting a book

[Tomblarom]

Describe the feature you'd like

When a user is inside a specific shelf (/shelves/<your-shelf>) and viewing the books contained within it, deleting a book currently redirects the user to the global books overview page (/books).

Current behavior

1. User navigates to: /shelves/<your-shelf>
2. User creates a book (e.g. for testing purposes).
3. User deletes that book.
4. User is redirected to: /books (All Books overview)

Expected behavior
After deleting a book that was accessed from within a shelf, the user should be redirected back to /shelves/<your-shelf>.

Describe the benefits this would bring to existing BookStack users

• Preserves user context: Users remain within the shelf they were working in, reducing cognitive load.
• Improves workflow efficiency: Eliminates unnecessary navigation steps after deletion.
• Reduces confusion and frustration: Avoids “Book not found” errors when using the browser back button
• Lowers workload for IT support desk: No potential tickets in this regard
• Better UX consistency: Aligns with common UX patterns where users are returned to their previous container view after deleting an item.

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

The user now has two inconvenient options to return to the original shelf:

1. Navigate back using the browser-back-button, while passing 2x ugly book not found error messages:
   /books --[back]--> /books/<deleted-book>/delete --[back]--> /books/<deleted-book> --[back]--> /shelves/<your-shelf>

2. Manually navigating back to the shelve:
   Home / --> /shelves/<your-shelf>

Have you searched for an existing open/closed issue?

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

How long have you been using BookStack?

3 months to 1 year

Additional context

No response

[ssddanbrown]

Thanks @Tomblarom, this is a good idea, and I think this should be an easy UX improvement so have assigned to the next release.

[ssddanbrown]

Added in 8e99fc6, to be part of the next release. Thanks again @Tomblarom!