Description of the need
We ran into this issue on backdropcms.org, where any node type can be classified as a book page, but then the book navigation shows up at the bottom of the page whether you want it there or not. It would be nice if we could provide a UI to control the placement of this navigation.
Proposed solution
Provide an interface to disable book navigation per node type.
* Use hook_fields_extra_fields() to allow book navigation to be disabled, or placed between fields. (Update: check the global setting for "Display default book navigation on book pages" and only show the per-node-type display option if that value is TRUE"
Draft of feature description for Press Release (1 paragraph at most)
Backdrop now includes the ability to hide or show book navigation per content type.
See https://github.com/backdrop/backdrop-issues/issues/3639 [META][UX] Improve book module.
Recent comments
I second this-- I have a module in contrib now that I just marked as "deprecated", and I removed its sole alpha release (because a fix in Core made it obsolete). Just plain deleting the module...
Weekly Meetings July 23rd 2026
If there's some time left in the dev meeting - although it might rather be a topic for the PMC: We have nice documentation and procedures, how to provide projects in backdrop-contrib space...
Weekly Meetings July 23rd 2026
The need for a clear AI policy is growing. Please can this be a priority.
Weekly Meetings July 23rd 2026