BookStack
BookStack copied to clipboard
BookStackApp
Page to book/chapter relationship
Desired Feature: Allow a single page to be related to multiple books and/or chapters.
maybe the attachments area can have a page id associated with it, a book id or even a chapter?
Hmm. I can see value in this. Nice to have but not required 👍 I like @ChangePlaces 's idea of being able to facilitate attachments being a part of this as well.
I'm very new to this app, so my apologies if this is a dumb question, but has this idea been implemented at all? I like the idea of being able to associate a single page with multiple books. My use case would be: I have a book with world information and pages for different characters or locations. I would then include that page in other books where the character has a role. This way I can view/edit the character information without having to navigate out of the current book.
@MattKaiser85 Not currently implemented. Please add a thumbs-up to the original issue comment to show support.
You can currently dynamically include page content, or event just a single section, within another page using include tags. I've written how to use these here: https://github.com/BookStackApp/BookStack/issues/978#issuecomment-415963168
You can remove the # and everything after it within the tag itself to include all page content.
This would be great to have. The way I would use it is to have a book which contains all the pages which have are set to be public. As far as I know there's no way to get an overview over the permissions so that would help me a bit.
Would love to be able to add the same page to multiple books. Would reduce trying to maintain duplicate content throughout workflow books and methodologies
I have the same issue and it seems like it is a reoccuring topic: https://github.com/BookStackApp/BookStack/issues/1360 https://github.com/BookStackApp/BookStack/issues/122 https://github.com/BookStackApp/BookStack/issues/48
would be nice :)
If this is implemented it would be great if pages that are part of multiple books can independently inherit the permissions of those books, so that you can create collections of pages available to specific users or guests.
This would be a useful feature for us when it comes to definition/glossary pages. We have multiple systems as books and each has their own definitions page. This is helpful to keep the definitions with the corresponding system (especially as some terms are used across systems but have different meanings), but it would be nice to be able to have a definitions book that contains all of these pages for quick access to all definitions across the enterprise.
Will this be ever implemented? Would be really useful. Let me describe my case: we have two teams using our KB - tech support and sysadmins. Sysadmins have some books for our internal services. These books include troubleshooting chapters which are frequently used by sysadmins and tech support both. It is not very convinient for tech support guys to search sysadmins books since they include a lot of non relevant information. Currently tech support collects links to specific troubleshooting pages and publishes them in their "general troubleshooting" book. It would be great if this book could contain pages from another books instead of pages with links to other pages.
Just found this issue as I wanted the same thing. I found this solution that works well for now. Although I would still like a more intuitive way to do it.
I had an idea how this could be accomplished with using existing features in BookStack. It may make it easier to implement it.
Instead of only "New Page" and "New Chapter" on the right menu, I would suggest ta third button called "Link Page". This Button would open a menu where you select a page. After that, you get redirected to the normal "New Page" area, where you can enter a page title. On, The content of the page is already filled with the include tag of the previously selected page.
Unfortunately, included page do not appear at searches. On one hand, it's not a big problem if you include the hole page, but if only little bits get included it would be useful. My suggestion for this problem would be, that the index knows on which pages the content was included. This way, included stuff does not need to be reindexed, but BookStack needs to store on the included part, where it was included.
I hope it's more or less clear what I mean. If not, just mention me!
The problem I have with including the whole page using the ID is that the preview in the layer above does not show any content. So, when in a book or chapter there are some original and some reused pages it is quite inconsistent.
Just found this issue as I wanted the same thing. I found this solution that works well for now. Although I would still like a more intuitive way to do it.
I see that this might lead into some complexity regarding topics like access permissions and where the page belongs to originally. Would still be useful and also something that Confluence doesn't support (they also use the include by defining an excerpt of a page).
I see that this might lead into some complexity regarding topics like access permissions and where the page belongs to originally. Would still be useful and also something that Confluence doesn't support (they also use the include by defining an excerpt of a page).
I would also appreciate this. Maybe a good idea would be to create an empty page, thread it as a separate object in regards to permission. But instead of loading a separate page on open, it would pull content from the original page in read-only mode, and editable content would be editable only in the original page. Then there would be a possibility to clone it (take original content, move it to a linked object, and remove the link, treating the page as a separate one, leaving original permissions set to link intact). This feature would took big amount of work when manually syncing multiple pages.
