mirror of
https://github.com/BookStackApp/BookStack.git
synced 2026-02-05 00:29:48 +03:00
Link on full chapter in page #1666
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 @Smoin1 on GitHub (Apr 18, 2020).
Describe the feature you'd like
It is posible to incle content from other pages (like: {{@83#bkmrk-position-skylight-%22o}} )
It seems to me that it is only possible to pick out certain text blocks. it would be nice and more intuitive to select a text and generate a link on that ( independently from e.g. headers in between)
Describe the benefits this feature would bring to BookStack users
It would be more intuitive, save effort to include the text on other pages. Include a wole "page-chapter" including the sub chapters to other pages
Additional context
@ssddanbrown commented on GitHub (Apr 25, 2020):
Hi @Smoin1,
With the inclusion syntax, you can just remove everything after the hash to include the entire content of page instead of a specific section, For example:
{{@83}}.Upon that, I would not be looking to expand upon the inclusion system with anything much more advanced like content ranges or chapter inclusion, since this is a little-used feature of BookStack which doesn't really fit the intention of not storing custom-syntax content.
@Smoin1 commented on GitHub (Apr 26, 2020):
"doesn't really fit the intention of not storing custom-syntax content." could you elaborate on that? I do not understand the meaingn :(
regarding the rest: in general it is possible to inclkude everythig like you showed or parts of the page (like I showed) but the "parts" seems not obvious to me. what is shown? al content of the lowest "header-level"?
@ssddanbrown commented on GitHub (Apr 26, 2020):
Where possible, I generally prefer not to introduce custom-BookStack-syntax or logic "Magic" when it comes to page content. I prefer to keep it as fairly standard, flat HTML to ensure that it's easily transferable if a user needs to take their content elsewhere.
{{@83}}- This will include all the page content (Stored HTML) from the page of ID83. This does not include the name/title of the page itself.{{@83#bkmrk-position-skylight-%22o}}- This will include the HTML of the element of IDbkmrk-position-skylight-%22oon the page of ID83. If a list or table, the HTML will be the "outer" html, otherwise it will be the inner-content of that block.Nothing in this system is specifically tied to header-levels. It's generally top-level block based.
@Smoin1 commented on GitHub (Apr 28, 2020):
ok, thank you for clarifying! :)
Maybe add a preview to make it more obvious which part is selected right now? to me it looked like the selected text is the one which is reused via the link, but that is not the case...