Come together with the global Drupal community in Rotterdam, 28 Sept – 1 Oct 2026. Sessions, contribution, connection, and Early Bird savings until 8 June.in books navigation (navi under the body text), I am suggesting another word than "up".
In IT-language and Drupal-Speak, "up" in this context means "up one level in book's chapter hierarchy".
But for normal users, this is not obvious. "up" from their experience normally means "scroll to top".
I am suggesting a change here although I don't know a better more descriptive word right away.
Maybe, "Chapter Index", or "Chapter Overview", "back to index"... - any ideas?
My goal is to be as end-user friendly with any navigation, as possible.
That is why I am rising this subject.
| Comment | File | Size | Author |
|---|---|---|---|
| #8 | Same wording Up was seen after patch was applied.PNG | 75.75 KB | swati_qa |
| #8 | Created a new book node after applying patch.PNG | 71.13 KB | swati_qa |
| #8 | Applied patch.PNG | 55.71 KB | swati_qa |
| #8 | Before Applying Patch.PNG | 68.4 KB | swati_qa |
| #7 | 1503024.patch | 603 bytes | sanket_markan |
Comments
Comment #1
molave commentedThe phrase List all chapters might work. Just a suggestion.
Comment #2
ceberlin commentedSee that's why "up" does not work: Everybody understands something different here.
That is not what it does from my understanding... It jumps 1 level up: from a sub-sub chapter to a sub-chapter and from there to the main chapter
Comment #3
BrockBoland commentedWould it be clearer if it were just "Go up a level"?
Comment #4
BrockBoland commentedAlso, if this is changed, it will be done in 8.x and back ported to 7.x.
Comment #5
ceberlin commenteddifficult: Try to explain to an average user out there that a "book" can have a "level" and watch the face. :-)
English is not my native language. I can only ask questions but don't have a carefully evaluated suggestion... yet.
Would "Chapter" maybe do it?
Would users assume that "Chapter" stands for "Beginning of the chapter/sub-chapter with an introduction"?
What do you think?
Comment #6
trupti.dixit commentedWord All chapters would be more descriptive.
Comment #7
sanket_markan commentedChanged wordings to "Go up a level"
Comment #8
swati_qa commentedVerified the patch 1503024.patch mentioned in #7.
Steps performed to verify the patch:
1. Created a Book Page "Test Book".
2. Created a Child Node "Child Node".
3. Navigate to the Book Node and observe the wording "Up".
4. Applied the patch.
5. Repeat steps 1 to 3 with Book page as "Test_after patch" and child node as "Child node for testing".
6. Same wording "Up" was seen after applying the patch also.
This means the wordings are not changed to "Go up a level" and issue fails the test.
Comment #9
swati_qa commentedComment #10
imalabyaThe above patch works fine. But for the Bartik theme this alone doesn't solve the issue.
Bartik uses the Classy as the base in which the
book-navigation.html.twigis overwritten. So we need to make changes there as well to see the effect in Bartik. (But that is out of scope for this issue)Once the issue is resolved it is better to open up a new issue for the Classy for the same. Also it needs some css changes in Classy as well.
Comment #11
swati_qa commentedComment #12
imalabya@swati_qa can you please give some explanation as to why the status was changed to
Needs WorkIf you check #10 I mentioned that the patch is working as intended but the classy template is overriding the twig file in the book module.
Comment #13
swati_qa commentedDoes that mean the wording "Up" is fine? No changes needed in this context?
Comment #14
imalabyaNo, I agree that the word "Up" can get a bit confusing for a layman. The patch addresses the issue and changes it "Go one level up".
The issue here is that even though the patch works fine for book module the result will not be rendered in
Bartiktheme becauseBartikis usingClassyas it's base theme where thebook-navigation.html.twigis overwritten to display "Up".So I proposed that once this is fixed let's open up a new issue to fix it in the Classy as well.
Also, I feel "Go one level up" is still a question needs to be solved first. Level in a book might be confusing as it may represent as the difficulty level of the particular publication. Just my thought.
Comment #16
dawehner.
Comment #17
Bojhan commentedI am not convinced with this approach. I don't think people are aware that they are within a certain level. The book concept itself might not be known to them, if the hierarchy isn't clearly exposed.
Are their best practices from others here?
Comment #25
pameeela commentedSince there is no consensus on what this should be, and even the issue title is a question, I don't think it's a bug.
Comment #26
mohit_aghera commentedAdding tag for usability team review.
We can update the title after their feedback.
Comment #31
quietone commentedThis extension is being deprecated, see #3376070: [Meta] Tasks to deprecate Book module. It will be removed from core and moved to a contrib project, #3376101: [11.x] [Meta] Tasks to remove Book.
This is now Postponed. The status is set according to two policies. The Remove a core extension and move it to a contributed project and the Extensions approved for removal policies.
This issue may be re-opened if it can be considered critical, If unsure, re-open the issue and ask in a comment.
Comment #32
quietone commentedComment #33
smustgrave commentedWith little no movement going to say this is outdated since being removed from core. If anyone strongly disagrees please reopen.