Open PancakeZik opened 1 year ago
Thanks for the request @PancakeZik.
Right now, I can't really tell what order do the books/chapters appear.
The default order is popularity (most accessed). We should probably better communicate this, along with the fact the list is limited by default until and a search is expected.
While I can understand it for your use-case, personally I wouldn't want to add proximity into the mix. The search is somewhat abstract/re-used, and adding proximity will add complexity to the process. Additionally, I feel that within-book move operations are usually better catered by the book sort interface.
Thinking about it further, I wonder if user-specific recent-accessed would be a better default than popularity. It can work context-unaware and I'd have thought it'd be likely that the user would have recently visited the destination in these kinds of operations. Would have to check it works for the other uses of the selector.
Thanks for the clarification, it makes sense. I would really appreciate some quicker way of moving things inside the a book without drag and drop like the sort feature.
Describe the feature you'd like
Hello, I've been using Bookstack for multiple projects, and something that I could be improved would be to have a logical sorting in the "move page" page. Right now, I can't really tell what order do the books/chapters appear. It would make sense to first list the Chapters in the same book as the page currently is, then the book itself, then everything else. For example, I have in the same Book a Chapter called "to be completed", and a chapter called "Completed". I always have to search for the "completed" chapter when I click Move Page, even though it is the only other chapter in that book.
Thank you!
Describe the benefits this would bring to existing BookStack users
Time-saving when moving pages
Can the goal of this request already be achieved via other means?
I don't know
Have you searched for an existing open/closed issue?
How long have you been using BookStack?
1 to 5 years
Additional context
No response