Better Content Hierarchy in Core?

The core Book module has long been a useful but under-utilized tool for structuring large amounts of content in hierarchies, including for documentation and wiki-like sites.

Is the name alone the reason it's over-looked, or are their other key feature or usability gaps?

This core conversation will solicit your input and discussion and propose possibly replacing Book with a core module that is functionally similar (and has an upgrade path) but with a more intuitive name, possibly better re-use of other core code and any key UX improvments we can identify.