mirror of
https://github.com/BookStackApp/BookStack.git
synced 2026-02-07 03:09:44 +03:00
[Feature Request]: Reuse a page section rather than just a block #2654
Reference in New Issue
Block a user
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @ssoulaimana on GitHub (Feb 14, 2022).
Describe the feature you'd like
I'd like the reuse syntax, {{@page_id}}, to support bigger sections of a page. At the moment you can either reuse a whole page or just a block.
When I select multiple paragraphs, the text copied is the last sentence before a (shift+enter) or (enter).
This would work the same way Synched blocks work in Notion:
https://www.notion.so/help/synced-blocks
Describe the benefits this feature would bring to BookStack users
Sync content for larger sections of a page but not the entire page
Additional context
No response
@jasonF1000 commented on GitHub (Oct 25, 2022):
Hi, i want to ask is there any news of this Feature Request?
We are also interested to this feature.
Or ist there a posibility to create your own bkmrk range to specify which content should we reused with this tag?
i had tried it but it will be overwritten when i save the page.
kind regards,
jason
@ssddanbrown commented on GitHub (Oct 25, 2022):
@jasonF1000 No further news of this specific request, and to be honest I doubt this would be something I'd look to include as I don't plan to expand the include system much further.
Within BookStack v22.09, I did add a new "Page Include Parse" logical theme system event which is mentioned, with example, in this blogpost: https://www.bookstackapp.com/blog/bookstack-release-v22-09/#page-include-parse-logical-theme-event
Using that theme event it would be possible to extend bookstack to add your own implementation of section range usages, or any other customization of page include behavior.
@jasonF1000 commented on GitHub (Oct 26, 2022):
@ssddanbrown thank you for the quick reply and i really understand that you don´t want to expand the include system to avoid more complexity.
So if i understand you right:
Whit this functionality it would be possible to create a section in a page and use this section tag with the include syntax on another page to reuse the defined section. But for this customizing of the code is needed right?
Our problem is that we want to reuse specific content of a page in much other pages. As an example, we have an installation guide and need to reuse this guide in 4 other pages. And it takes much effort to get all bkmrk tags of this content to reuse it (like 40 bkmrk tags). And if i also understand it right, we should rename the bkmrk tags because it could be possible that there will be renamed if we change the content of the part which are reused, right?
So a way to define a tag for a range which i want to reuse by customizing of the code is possible? like
<StartofSection-Tag>
<p id=bkmrk-xx> content1 </p>
<p id=bkmrk-xy> contentX </p>
<EndofSection-Tag>
All content between this section tags should be reused if i use the pageID+sectionTag on another page.
is something like this possible to realisize with customizing?
Kind regards,
jason
@jeffshead commented on GitHub (Jan 17, 2023):
+1 for this functionality.
@jasonF1000
Did you figure out how to get this working? I don't know how to go about implementing this via the "Page Include Parse" logical theme system event.
@jasonF1000 commented on GitHub (Jan 17, 2023):
@jeffshead
i also not know how the "Page Include Parse" is working to implement it.
But what works for me was to set my own sections in the source code editor of the page.
I am able now to reuse exact the parts of a page which i want.
If you want to know how it is exactly work, you can write me :)
@sm100327 commented on GitHub (Apr 2, 2025):
Hi,
if you have a solution, it would probably be helpful to put it here - i think alot of people have the same problem.
Maybe it can even be integrated into the documentation as "advanced" or so ??
Cheers
Soeren