Next button

[aszasz]

This includes previous and next button with same name/number and style seen in the content.

It is still to properly css-styled and have the content (text of the button) discussed before merge. (not metioning a review from @jonasmalacofilho to request addition of best practices of programming that may have escaped).

[aszasz]

I think it is good for merge, because is a useful feature. We should eventually open issues about:

• using numbers in the buttons
• having a previous button in the top of the page (where it seems really useful).

[jonasmalacofilho]

I think this looks great and I will merge it as is!

In the future, I think we should:

• remove the "previous" button:
  • most of the time, I don't think it shows relevant information; in fact, in my tests it often made me wonder: "was i supposed to know about that deeply nested child of something that came before this?"
  • (as Arthur has mentioned somewhere else), it tries to reinvent the wheel; the browser's "back" button is easier to access (even more on mobile devices) and serves pretty much the same purpose
  • removing it would leave more room for the much more useful "next" button (particularly on mobile devices)
• keep the numbers, for consistency
• reintroduce the element name on mobile devices (using the space left by removing the "previous" button)

---

An example on why I think the "previous" button is confusing: when I've just entered a new chapter, the "previous" button will show me the last section of the previous chapter (as it should, since it's the opposite of "next"). However, that's doesn't seem useful at all: what I would perhaps like to be reminded of is the name of the last volume or chapter (depending on whether I've entered a new volume or not), something we already have on the nav bar.