I am not sure if this should be reported here, or in the core issue queue, but let's go.
I never really understood why the book module came with it's own content type, because the book functionality can be easily enabled on any content type.
Over the past few years I have hit multiple strange situations with the book module;
Books have a built-in hierarchical navigation. Use for handbooks or tutorials.
It is perfectly accurate, but it also implies that handbooks and tutorials need to be made with the same (book) content type (Which makes no sense). Instead it should explained that book functionality could be used for such situations.
Ever since that content editor situation, I find myself deleting the book content type and enabling book functionality for basic pages, so all static pages can be used either as stand alone pages, or as hierarchical pages.
I understand that some of you want the book module to do something as soon as it is enabled, but Content Moderation and Workbench moderation are using a per-content type opt-in system, which works perfect.
In order to avoid confusion (for builders and editors), can we delete the default book content type from the book module and change its documentation to include the step to enable book functionality for the content types that need it?
Active
1.0
Code
Not all content is available!
It's likely this issue predates Contrib.social: some issue and comment data are missing.
The Book Module was removed from core and is now in contrib.
I'm fine with this but will probably need to move config to a test module because this will break a lot.