Page turn buttons below each page for a continuous reading experience #1336

Closed
opened 2026-02-05 00:38:30 +03:00 by OVERLORD · 3 comments
Owner

Originally created by @Wookbert on GitHub (Sep 1, 2019).

Describe the feature you'd like
The name and UI concept clearly implies to organize your information in books with chapters and pages. Reading a book however comes with the experience and convenience of continuous reading through a simple page turn. This does not only apply for paper books, but also has been mimicked on any eBook reader.

On BookStack I'm missing this convenience however so far. Yes, we do have the Book Navigation in the left side panel next to the current page (hereunder; which BTW only follows your scrolling and thus is always in instant reach, if the browser window is wide enough, so that there’s enough space for a right side panel as well), but that’s just not as convenient as a simple page turn.

image

I therefore suggest to additionally place four buttons between the end of the page and the comments section:

  • Previous chapter (jumps to first page thereof)
  • Previous page
  • Next page
  • Next chapter (jumps to first page thereof)

Here’s a quick mockup of how that could look:

image

Further behaviour

  • Buttons are ghosted if there is no previous/next chapter/page.
  • Buttons could be hidden entirely if there is just a single page (UX consistency?). (Hide chapter buttons if there aren’t any chapters??)

Discussion: Floating navigation?
Another concept might be to have this navigation with its 4 buttons visible not only when reaching the end of the page, but instead visible and thus accessible at all times, so one can e.g. jump to the next page, even if one’s only half-way through a long page. The preferable place for such a floating navigation would be the bottom of the window IMO.

The problem I see in this approach however is the waste of screen real estate. A solution to this problem could be to make the navigation only appear (instantly) when a) the mouse pointer gets moved to the lower something pixels at the window or b) one scrolls to the very end of the screen.

Originally created by @Wookbert on GitHub (Sep 1, 2019). **Describe the feature you'd like** The name and UI concept clearly implies to organize your information in books with chapters and pages. Reading a book however comes with the experience and convenience of continuous reading through a simple page turn. This does not only apply for paper books, but also has been mimicked on any eBook reader. On BookStack I'm missing this convenience however so far. Yes, we do have the Book Navigation in the left side panel next to the current page (hereunder; which BTW only follows your scrolling and thus is always in instant reach, if the browser window is wide enough, so that there’s enough space for a right side panel as well), but that’s just not as convenient as a simple page turn. ![image](https://user-images.githubusercontent.com/3104762/64083991-bb84ba80-cd26-11e9-966c-6414000b93ea.png) I therefore suggest to additionally place four buttons between the end of the page and the comments section: - Previous chapter (jumps to first page thereof) - Previous page - Next page - Next chapter (jumps to first page thereof) Here’s a quick mockup of how that could look: ![image](https://user-images.githubusercontent.com/3104762/64079956-c58ac700-ccee-11e9-9160-41dafc1b3022.png) **Further behaviour** - Buttons are ghosted if there is no previous/next chapter/page. - Buttons could be hidden entirely if there is just a single page (UX consistency?). (Hide chapter buttons if there aren’t any chapters??) **Discussion: Floating navigation?** Another concept might be to have this navigation with its 4 buttons visible not only when reaching the end of the page, but instead visible and thus accessible at all times, so one can e.g. jump to the next page, even if one’s only half-way through a long page. The preferable place for such a floating navigation would be the bottom of the window IMO. The problem I see in this approach however is the waste of screen real estate. A solution to this problem could be to make the navigation only appear (instantly) when a) the mouse pointer gets moved to the lower something pixels at the window or b) one scrolls to the very end of the screen.
Author
Owner

@over-soul commented on GitHub (Sep 1, 2019):

I agree that having the next page and next chapter buttons would be massively useful.

@over-soul commented on GitHub (Sep 1, 2019): I agree that having the next page and next chapter buttons would be massively useful.
Author
Owner

@Wookbert commented on GitHub (Sep 1, 2019):

So, why not give it a Thumb Up? 👍 🤪

@Wookbert commented on GitHub (Sep 1, 2019): So, why not give it a Thumb Up? 👍 🤪
Author
Owner

@ssddanbrown commented on GitHub (Sep 1, 2019):

Hi @Wookbert,
Thanks for the detailed request. This has already been requested under #1381 so I'm going to close this but I'll copy your detail and imagery across to continue the discussion.

@ssddanbrown commented on GitHub (Sep 1, 2019): Hi @Wookbert, Thanks for the detailed request. This has already been requested under #1381 so I'm going to close this but I'll copy your detail and imagery across to continue the discussion.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/BookStack#1336